diff --git a/umn/source/_static/images/en-us_image_0000001499513972.png b/umn/source/_static/images/en-us_image_0000001499513972.png new file mode 100644 index 0000000..8d5670b Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001499513972.png differ diff --git a/umn/source/_static/images/en-us_image_0124306703.png b/umn/source/_static/images/en-us_image_0124306703.png deleted file mode 100644 index dfac6bc..0000000 Binary files a/umn/source/_static/images/en-us_image_0124306703.png and /dev/null differ diff --git a/umn/source/change_history.rst b/umn/source/change_history.rst index 43aaac0..d63df71 100644 --- a/umn/source/change_history.rst +++ b/umn/source/change_history.rst @@ -8,6 +8,13 @@ Change History +-----------------------------------+----------------------------------------------------------------------------------+ | Release Date | What's New | +===================================+==================================================================================+ +| 2023-03-30 | Modified the following sections: | +| | | +| | - :ref:`General Procedure ` | +| | - :ref:`Step 1: Creating a DIS Stream ` | +| | - :ref:`Viewing Stream Monitoring Metrics ` | +| | - :ref:`Configuring Sample Projects ` | ++-----------------------------------+----------------------------------------------------------------------------------+ | 2022-09-30 | Removed the following section: | | | | | | CDR Specification | diff --git a/umn/source/dis_sdk_usage_guide/configuring_sample_projects.rst b/umn/source/dis_sdk_usage_guide/configuring_sample_projects.rst index 6632024..cedcd59 100644 --- a/umn/source/dis_sdk_usage_guide/configuring_sample_projects.rst +++ b/umn/source/dis_sdk_usage_guide/configuring_sample_projects.rst @@ -45,7 +45,7 @@ Procedure #. Click **Apply and Close**. - .. figure:: /_static/images/en-us_image_0124306703.png + .. figure:: /_static/images/en-us_image_0000001499513972.png :alt: **Figure 2** Resource **Figure 2** Resource diff --git a/umn/source/faqs.rst b/umn/source/faqs.rst new file mode 100644 index 0000000..990004f --- /dev/null +++ b/umn/source/faqs.rst @@ -0,0 +1,8 @@ +:original_name: en-us_topic_0124374673.html + +.. _en-us_topic_0124374673: + +FAQs +==== + +This chapter describes some FAQs. diff --git a/umn/source/faqs/how_do_i_check_software_package_integrity.rst b/umn/source/faqs/how_do_i_check_software_package_integrity.rst deleted file mode 100644 index 1250e09..0000000 --- a/umn/source/faqs/how_do_i_check_software_package_integrity.rst +++ /dev/null @@ -1,37 +0,0 @@ -:original_name: dis_faq_0009.html - -.. _dis_faq_0009: - -How Do I Check Software Package Integrity? -========================================== - -This section describes how to verify integrity of the DIS SDK software package on a Linux system by using a verification file. - -Prerequisites -------------- - -- The PuTTY tool is available. -- The WinSCP tool is available. - -Procedure ---------- - -#. Upload the DIS SDK software package **dis-sdk-1.2.3.zip** to any directory on the Linux system by using WinSCP. - -#. .. _dis_faq_0009__l8c35f745b7e945219234467020564558: - - Log in to the Linux system by using PuTTY. In the directory in which **dis-sdk-1.2.3.zip** is stored, run the following command to obtain the verification code of the DIS SDK software package: - - **sha256sum dis-sdk-1.2.3.zip** - - Example verification code: - - .. code-block:: - - # sha256sum dis-sdk-1.2.3.zip - 8be2c937e8d78b1a9b99777cee4e7131f8bf231de3f839cf214e7c5b5ba3c088 dis-sdk-1.2.3.zip - -#. Open the DIS SDK verification file **dis-sdk-1.2.3.zip.sha256sum** and compare it with the verification code obtained in :ref:`Step 2 `. - - - If they are consistent, it indicates that the DIS SDK software package is not tampered with. - - If they are inconsistent, the DIS SDK software package is tampered with and you need to obtain an untampered package. diff --git a/umn/source/faqs/how_does_dis_send_and_receive_data.rst b/umn/source/faqs/how_does_dis_send_and_receive_data.rst deleted file mode 100644 index 9a7fc37..0000000 --- a/umn/source/faqs/how_does_dis_send_and_receive_data.rst +++ /dev/null @@ -1,13 +0,0 @@ -:original_name: dis_faq_0003.html - -.. _dis_faq_0003: - -How Does DIS Send and Receive Data? -=================================== - -#. Create a DIS stream, and obtain your Access Key ID/Secret Access Key (AK/SK) from the Identity and Access Management (IAM) service. -#. Download the package from https://dis.obs.eu-de.otc.t-systems.com/dis/download/dis-sdk-1.2.3.zip. -#. Create a project and configure the user AK/SK, endpoint, project ID, region, stream name, and partition quantity. -#. After the configuration is completed, run the application to send data. -#. Create a project and configure the user AK/SK, endpoint, project, region, stream name, partition ID, and startingSequenceNumber. -#. After the configuration is completed, run the application to receive data. diff --git a/umn/source/faqs/index.rst b/umn/source/faqs/index.rst deleted file mode 100644 index 8560f46..0000000 --- a/umn/source/faqs/index.rst +++ /dev/null @@ -1,18 +0,0 @@ -:original_name: dis_faq_0000.html - -.. _dis_faq_0000: - -FAQs -==== - -- :ref:`How Does DIS Send and Receive Data? ` -- :ref:`What Is the Difference Between Storing Data into DIS and Dumping Data Elsewhere? ` -- :ref:`How Do I Check Software Package Integrity? ` - -.. toctree:: - :maxdepth: 1 - :hidden: - - how_does_dis_send_and_receive_data - what_is_the_difference_between_storing_data_into_dis_and_dumping_data_elsewhere - how_do_i_check_software_package_integrity diff --git a/umn/source/faqs/what_is_the_difference_between_storing_data_into_dis_and_dumping_data_elsewhere.rst b/umn/source/faqs/what_is_the_difference_between_storing_data_into_dis_and_dumping_data_elsewhere.rst deleted file mode 100644 index 1696872..0000000 --- a/umn/source/faqs/what_is_the_difference_between_storing_data_into_dis_and_dumping_data_elsewhere.rst +++ /dev/null @@ -1,27 +0,0 @@ -:original_name: dis_faq_0007.html - -.. _dis_faq_0007: - -What Is the Difference Between Storing Data into DIS and Dumping Data Elsewhere? -================================================================================ - -After DIS is enabled, data is stored in DIS by default. After a dump task is added, the data can be dumped to other resources. :ref:`Table 1 ` describes the specific differences. - -- Data is stored in DIS by default. -- If **Dump Destination** is set to **OBS**, data is stored in DIS and periodically imported to Object Storage Service (OBS). - -.. _dis_faq_0007__tdc4c4ec0b2454cfeb8421d92412355e6: - -.. table:: **Table 1** Difference between storing data into DIS and dumping data elsewhere - - +---------------------------------------------------------------------+-----------------------------------------------------------------------------+ - | DIS Storage | OBS Storage | - +=====================================================================+=============================================================================+ - | You can store data into DIS without applying for storage resources. | You must apply for OBS resources before dumping data to OBS. | - +---------------------------------------------------------------------+-----------------------------------------------------------------------------+ - | No additional payment is required. | Additional cost for the use of OBS. For details, see the OBS price details. | - +---------------------------------------------------------------------+-----------------------------------------------------------------------------+ - | Data is temporarily stored in DIS for up to 168 hours. | Data is stored in OBS until your OBS bucket expires. | - +---------------------------------------------------------------------+-----------------------------------------------------------------------------+ - | Data is stored only in DIS. | Data is stored in DIS and periodically dumped to OBS. | - +---------------------------------------------------------------------+-----------------------------------------------------------------------------+ diff --git a/umn/source/getting_started/general_procedure.rst b/umn/source/getting_started/general_procedure.rst index ac139fe..e1286d9 100644 --- a/umn/source/getting_started/general_procedure.rst +++ b/umn/source/getting_started/general_procedure.rst @@ -7,7 +7,7 @@ General Procedure The following is the general procedure for using DIS: -:ref:`4.2-Step 1: Creating a DIS Stream ` +:ref:`Step 1: Creating a DIS Stream ` You need to create a stream before using DIS. diff --git a/umn/source/getting_started/step_1_creating_a_dis_stream.rst b/umn/source/getting_started/step_1_creating_a_dis_stream.rst index 3d0fbfa..015cfb2 100644 --- a/umn/source/getting_started/step_1_creating_a_dis_stream.rst +++ b/umn/source/getting_started/step_1_creating_a_dis_stream.rst @@ -20,9 +20,9 @@ Procedure #. Click |image1| in the upper left corner of the page and select a region and project. -#. .. _dis_01_0601__li23032735111458: +#. Click Create Stream and set related parameters. - Click Create Stream and set related parameters. + .. _dis_01_0601__table1518745742610: .. table:: **Table 1** Stream parameters @@ -42,7 +42,7 @@ Procedure | | | | | | - For a common DIS stream, the value of **Partitions** is an integer from 1 to 50. A tenant can create a maximum of 50 partitions. | | | | - For an advanced DIS stream, the value of **Partitions** is an integer from 1 to 10. A tenant can create a maximum of 10 partitions. | | - | | - Both common DIS sreams and advanced DIS streams can automatically scale up. You can also scale them up manually. **Significantly**, a maximum of 10 automatic scale-up, 10 manual scale-up, and 1 scale-down operations can be performed for each stream **within one hour.** | | + | | - Both common DIS streams and advanced DIS streams can automatically scale up. You can also scale them up manually. **Significantly**, a maximum of 10 automatic scale-up, 10 manual scale-up, and 1 scale-down operations can be performed for each stream **within one hour.** | | +------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Partition Calculator | Calculator used to calculate the estimated number of partitions based on the information you entered. | ``-`` | | | | | @@ -80,7 +80,7 @@ Procedure | Tag | Identifier of the stream. Adding tags to streams can help you identify and manage your stream resources. | ``-`` | +------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ -#. Click **Submit**. The **Details** page is displayed. +#. Click **Next**. The **Details** page is displayed. #. Click **Submit**. diff --git a/umn/source/getting_started/step_3_sending_data_to_dis.rst b/umn/source/getting_started/step_3_sending_data_to_dis.rst index 51fe7bd..578f1cc 100644 --- a/umn/source/getting_started/step_3_sending_data_to_dis.rst +++ b/umn/source/getting_started/step_3_sending_data_to_dis.rst @@ -19,7 +19,7 @@ Local data is continuously uploaded to DIS. Sample Code ----------- -The example code file is the **ProducerDemo.java** file in the **\\dis-sdk-demo\\src\\main\\java\\com\\bigdata\\dis\\sdk\\demo** directory decompressed from the **dis-sdk-1.2.3.zip** package. +The example code file is the **ProducerDemo.java** file in the **\\dis-sdk-demo\\src\\main\\java\\com\\bigdata\\dis\\sdk\\demo** directory decompressed from the **dis-sdk-1.2.3.zip** package. The compression package is downloaded from the `DIS SDK `__. Running the Producer Program ---------------------------- diff --git a/umn/source/getting_started/step_4_obtaining_data_from_dis.rst b/umn/source/getting_started/step_4_obtaining_data_from_dis.rst index 8f699ac..5c6bde3 100644 --- a/umn/source/getting_started/step_4_obtaining_data_from_dis.rst +++ b/umn/source/getting_started/step_4_obtaining_data_from_dis.rst @@ -13,7 +13,7 @@ You can retrieve data from DIS when needed. Sample Code ----------- -The example code file is the **ConsumerDemo.java** file in the **\\dis-sdk-demo\\src\\main\\java\\com\\bigdata\\dis\\sdk\\demo** directory decompressed from the **dis-sdk-XXX.zip** package. +The example code file is the **ConsumerDemo.java** file in the **\\dis-sdk-demo\\src\\main\\java\\com\\bigdata\\dis\\sdk\\demo** directory decompressed from the **dis-sdk-XXX.zip** package. The compression package is downloaded from the `DIS SDK `__. Running the Consumer Application -------------------------------- diff --git a/umn/source/index.rst b/umn/source/index.rst index 2fa4dbb..2fbc0a8 100644 --- a/umn/source/index.rst +++ b/umn/source/index.rst @@ -11,5 +11,5 @@ Data Ingestion Service - User Guide managing_a_dump_task/index monitoring/index dis_sdk_usage_guide/index - faqs/index + faqs change_history diff --git a/umn/source/managing_dis_streams/viewing_stream_monitoring_metrics.rst b/umn/source/managing_dis_streams/viewing_stream_monitoring_metrics.rst index eca353e..981fb94 100644 --- a/umn/source/managing_dis_streams/viewing_stream_monitoring_metrics.rst +++ b/umn/source/managing_dis_streams/viewing_stream_monitoring_metrics.rst @@ -21,7 +21,7 @@ You can view stream monitoring information on the console and monitor the data c **Figure 1** Monitoring page -#. On the **Monitoring** page, click the **Streams** or **Partitions** tab to view stream or partition monitoring metrics. :ref:`Table 1 ` describes the monitoring parameters. For details about basic stream information, see :ref:`Step 3 `. +#. On the **Monitoring** page, click the **Streams** or **Partitions** tab to view stream or partition monitoring metrics. :ref:`Table 1 ` describes the monitoring parameters. For details about basic stream information, see :ref:`Table 1 `. .. _dis_01_0012__table2942144318834: diff --git a/umn/source/overview/functions.rst b/umn/source/overview/functions.rst index c89042b..b1e1d91 100644 --- a/umn/source/overview/functions.rst +++ b/umn/source/overview/functions.rst @@ -41,5 +41,5 @@ Key Capabilities - Scalable: A DIS stream can seamlessly scale its data throughput from megabytes to terabytes per hour, and from thousands to millions of PUT records per second. - Easy to use: You can create a DIS stream within seconds. It is easy to put data into a stream, and build a data processing application. - Low cost: DIS has no upfront cost and you only pay for the resources you use. -- Parallel processing: DIS allows you to have multiple DIS applications processing the same stream concurrently. For example, you can have one application running real-time analytics and another sending data to OBS from the same stream. +- Parallel processing: DIS allows you to have multiple DIS applications processing the same stream concurrently. - Secure and reliable: DIS can retain data for 24 to 72 hours to prevent data loss in case of application faults, individual machine faults, or facility faults.