From b8dbeabef4e9f50c4a6f980dc75e27d5b8302df8 Mon Sep 17 00:00:00 2001 From: "Su, Xiaomeng" Date: Wed, 26 Nov 2025 09:25:57 +0000 Subject: [PATCH] dli_umn_20250929 Reviewed-by: Pruthi, Vineet Co-authored-by: Su, Xiaomeng Co-committed-by: Su, Xiaomeng --- docs/dli/umn/ALL_META.TXT.json | 1920 +++++---- docs/dli/umn/CLASS.TXT.json | 1430 ++++--- docs/dli/umn/dli_01_00006.html | 17 +- docs/dli/umn/dli_01_0001.html | 11 +- docs/dli/umn/dli_01_0002.html | 23 +- docs/dli/umn/dli_01_0003.html | 49 +- docs/dli/umn/dli_01_0004.html | 4 +- docs/dli/umn/dli_01_0005.html | 161 +- docs/dli/umn/dli_01_0006.html | 186 +- docs/dli/umn/dli_01_0007.html | 4 +- docs/dli/umn/dli_01_0008.html | 8 +- docs/dli/umn/dli_01_0009.html | 24 + docs/dli/umn/dli_01_0010.html | 8 +- docs/dli/umn/dli_01_0011.html | 7 +- docs/dli/umn/dli_01_0013.html | 13 +- docs/dli/umn/dli_01_0014.html | 17 +- docs/dli/umn/dli_01_0015.html | 14 +- docs/dli/umn/dli_01_0017.html | 4 +- docs/dli/umn/dli_01_0018.html | 2 +- docs/dli/umn/dli_01_0019.html | 11 +- docs/dli/umn/dli_01_0020.html | 40 +- docs/dli/umn/dli_01_0021.html | 6 +- docs/dli/umn/dli_01_0022.html | 10 +- docs/dli/umn/dli_01_0220.html | 10 +- docs/dli/umn/dli_01_0228.html | 27 +- docs/dli/umn/dli_01_0253.html | 15 +- docs/dli/umn/dli_01_0318.html | 45 +- docs/dli/umn/dli_01_0320.html | 132 +- docs/dli/umn/dli_01_0363.html | 18 +- docs/dli/umn/dli_01_0367.html | 6 +- docs/dli/umn/dli_01_0369.html | 6 +- docs/dli/umn/dli_01_0375.html | 93 +- docs/dli/umn/dli_01_0376.html | 2 +- docs/dli/umn/dli_01_0377.html | 2 +- docs/dli/umn/dli_01_0378.html | 123 +- docs/dli/umn/dli_01_0379.html | 11 +- docs/dli/umn/dli_01_0384.html | 409 +- docs/dli/umn/dli_01_0385.html | 4 +- docs/dli/umn/dli_01_0389.html | 2 +- docs/dli/umn/dli_01_0390.html | 6 +- docs/dli/umn/dli_01_0397.html | 3543 +++++++++++------ docs/dli/umn/dli_01_0402.html | 4 +- docs/dli/umn/dli_01_0403.html | 2 +- docs/dli/umn/dli_01_0407.html | 4 +- docs/dli/umn/dli_01_0408.html | 15 +- docs/dli/umn/dli_01_0410.html | 4 +- docs/dli/umn/dli_01_0417.html | 98 +- docs/dli/umn/dli_01_0418.html | 62 +- docs/dli/umn/dli_01_0419.html | 13 +- docs/dli/umn/dli_01_0427.html | 6 +- docs/dli/umn/dli_01_0440.html | 195 +- docs/dli/umn/dli_01_0441.html | 1489 ++++--- docs/dli/umn/dli_01_0443.html | 4 +- docs/dli/umn/dli_01_0445.html | 460 ++- docs/dli/umn/dli_01_0447.html | 12 +- docs/dli/umn/dli_01_0448.html | 28 +- docs/dli/umn/dli_01_0451.html | 484 ++- docs/dli/umn/dli_01_0457.html | 365 +- docs/dli/umn/dli_01_0461.html | 8 +- docs/dli/umn/dli_01_0462.html | 158 +- docs/dli/umn/dli_01_0463.html | 29 +- docs/dli/umn/dli_01_0464.html | 20 +- docs/dli/umn/dli_01_0465.html | 2 +- docs/dli/umn/dli_01_0475.html | 88 +- docs/dli/umn/dli_01_0479.html | 2 +- docs/dli/umn/dli_01_0480.html | 4 +- docs/dli/umn/dli_01_0487.html | 6 +- docs/dli/umn/dli_01_0488.html | 10 +- docs/dli/umn/dli_01_0489.html | 12 +- docs/dli/umn/dli_01_0494.html | 23 +- docs/dli/umn/dli_01_0498.html | 325 +- docs/dli/umn/dli_01_0504.html | 256 +- docs/dli/umn/dli_01_0505.html | 41 +- docs/dli/umn/dli_01_0506.html | 16 +- docs/dli/umn/dli_01_0507.html | 12 +- docs/dli/umn/dli_01_0508.html | 4 +- docs/dli/umn/dli_01_0509.html | 4 +- docs/dli/umn/dli_01_05110.html | 2 +- docs/dli/umn/dli_01_0512.html | 186 +- docs/dli/umn/dli_01_0514.html | 70 - docs/dli/umn/dli_01_0515.html | 13 +- docs/dli/umn/dli_01_0516.html | 26 +- docs/dli/umn/dli_01_0524.html | 20 - docs/dli/umn/dli_01_0525.html | 10 +- docs/dli/umn/dli_01_0526.html | 8 +- docs/dli/umn/dli_01_0528.html | 12 +- docs/dli/umn/dli_01_0529.html | 8 +- docs/dli/umn/dli_01_0530.html | 2 +- docs/dli/umn/dli_01_0531.html | 193 +- docs/dli/umn/dli_01_0532.html | 11 +- docs/dli/umn/dli_01_0535.html | 4 +- docs/dli/umn/dli_01_0536.html | 16 +- docs/dli/umn/dli_01_0538.html | 8 +- docs/dli/umn/dli_01_0550.html | 2 +- docs/dli/umn/dli_01_0551.html | 2 +- docs/dli/umn/dli_01_0552.html | 23 +- docs/dli/umn/dli_01_0553.html | 2 +- docs/dli/umn/dli_01_0555.html | 19 + docs/dli/umn/dli_01_0556.html | 4 +- docs/dli/umn/dli_01_0558.html | 4 +- docs/dli/umn/dli_01_0559.html | 2 +- docs/dli/umn/dli_01_0560.html | 6 +- docs/dli/umn/dli_01_0561.html | 8 +- docs/dli/umn/dli_01_0563.html | 121 +- docs/dli/umn/dli_01_0567.html | 2 +- docs/dli/umn/dli_01_0612.html | 396 ++ docs/dli/umn/dli_01_0616.html | 21 +- docs/dli/umn/dli_01_0618.html | 36 +- docs/dli/umn/dli_01_0621.html | 15 +- docs/dli/umn/dli_01_0622.html | 38 +- docs/dli/umn/dli_01_0623.html | 4 +- docs/dli/umn/dli_01_0625.html | 4 +- docs/dli/umn/dli_01_0626.html | 3 +- docs/dli/umn/dli_01_0631.html | 21 + docs/dli/umn/dli_01_0632.html | 314 ++ docs/dli/umn/dli_01_0633.html | 172 + docs/dli/umn/dli_01_0634.html | 6 +- docs/dli/umn/dli_01_0635.html | 2 +- docs/dli/umn/dli_01_0636.html | 31 +- docs/dli/umn/dli_01_0637.html | 11 +- docs/dli/umn/dli_01_0638.html | 2 +- docs/dli/umn/dli_01_0650.html | 2 +- docs/dli/umn/dli_01_0651.html | 14 +- docs/dli/umn/dli_01_0652.html | 4 +- docs/dli/umn/dli_01_0661.html | 9 +- docs/dli/umn/dli_01_0662.html | 16 +- docs/dli/umn/dli_01_0664.html | 16 - docs/dli/umn/dli_01_0665.html | 118 - docs/dli/umn/dli_01_0666.html | 110 - docs/dli/umn/dli_01_0667.html | 436 -- docs/dli/umn/dli_01_0671.html | 19 + docs/dli/umn/dli_01_0672.html | 144 + docs/dli/umn/dli_01_0685.html | 73 + docs/dli/umn/dli_01_0686.html | 57 + docs/dli/umn/dli_01_0687.html | 18 + docs/dli/umn/dli_01_0689.html | 20 + docs/dli/umn/dli_01_0690.html | 82 + docs/dli/umn/dli_01_0691.html | 3144 +++++++++++++++ docs/dli/umn/dli_01_0692.html | 62 + docs/dli/umn/dli_01_0693.html | 47 + docs/dli/umn/dli_01_0695.html | 157 + docs/dli/umn/dli_03_0032.html | 2 +- docs/dli/umn/dli_03_0044.html | 11 +- docs/dli/umn/dli_03_0047.html | 2 +- docs/dli/umn/dli_03_0091.html | 9 +- docs/dli/umn/dli_03_0092.html | 3 +- docs/dli/umn/dli_03_0093.html | 9 +- docs/dli/umn/dli_03_0102.html | 13 +- docs/dli/umn/dli_03_0106.html | 9 +- docs/dli/umn/dli_03_0115.html | 2 - docs/dli/umn/dli_03_0136.html | 3 + docs/dli/umn/dli_03_0186.html | 11 +- docs/dli/umn/dli_03_0196.html | 15 +- docs/dli/umn/dli_03_0211.html | 2 + docs/dli/umn/dli_03_0217.html | 2 + docs/dli/umn/dli_03_0218.html | 4 + docs/dli/umn/dli_03_0236.html | 11 +- docs/dli/umn/dli_03_0253.html | 11 +- docs/dli/umn/dli_03_0273.html | 16 + docs/dli/umn/dli_03_0275.html | 9 +- docs/dli/umn/dli_03_0277.html | 163 + docs/dli/umn/dli_03_0278.html | 15 + docs/dli/umn/dli_03_0279.html | 17 + docs/dli/umn/dli_07_0002.html | 6 +- docs/dli/umn/dli_07_0003.html | 36 +- docs/dli/umn/dli_07_0004.html | 64 + docs/dli/umn/dli_07_0005.html | 6 +- docs/dli/umn/dli_07_0006.html | 40 +- docs/dli/umn/dli_07_0007.html | 1 + docs/dli/umn/dli_07_0009.html | 2 +- docs/dli/umn/dli_07_0027.html | 132 +- docs/dli/umn/en-us_image_0000001570712116.png | Bin 11971 -> 0 bytes ...3.png => en-us_image_0000001620741493.png} | Bin docs/dli/umn/en-us_image_0000001620789569.png | Bin 11169 -> 0 bytes docs/dli/umn/en-us_image_0000001897113369.png | Bin 957 -> 0 bytes docs/dli/umn/en-us_image_0000002031125321.png | Bin 0 -> 21917 bytes docs/dli/umn/en-us_image_0000002174135216.png | Bin 0 -> 217 bytes docs/dli/umn/en-us_image_0000002295795461.png | Bin 0 -> 44947 bytes docs/dli/umn/en-us_image_0000002337417937.png | Bin 0 -> 183 bytes docs/dli/umn/en-us_image_0000002348096834.png | Bin 0 -> 20407 bytes docs/dli/umn/en-us_image_0000002363051176.png | Bin 0 -> 25932 bytes docs/dli/umn/en-us_image_0000002363080342.png | Bin 0 -> 207 bytes docs/dli/umn/en-us_image_0000002363115912.png | Bin 0 -> 17521 bytes docs/dli/umn/en-us_image_0000002363450016.png | Bin 0 -> 39939 bytes docs/dli/umn/en-us_image_0000002381617561.png | Bin 0 -> 24198 bytes docs/dli/umn/en-us_image_0000002381737281.png | Bin 0 -> 26231 bytes docs/dli/umn/en-us_image_0000002397300825.png | Bin 0 -> 17521 bytes docs/dli/umn/en-us_image_0000002398199205.png | Bin 0 -> 57631 bytes docs/dli/umn/en-us_image_0000002410128586.png | Bin 0 -> 661 bytes docs/dli/umn/en-us_image_0000002415789969.png | Bin 0 -> 19203 bytes docs/dli/umn/en-us_image_0206789726.jpg | Bin 11526 -> 0 bytes docs/dli/umn/en-us_image_0206789784.png | Bin 17923 -> 0 bytes .../umn/public_sys-resources/imageclose.gif | Bin 0 -> 1238 bytes .../public_sys-resources/imageclosehover.gif | Bin 0 -> 1172 bytes .../dli/umn/public_sys-resources/imagemax.gif | Bin 0 -> 1267 bytes .../public_sys-resources/imagemaxhover.gif | Bin 0 -> 1199 bytes .../umn/public_sys-resources/macFFBgHack.png | Bin 0 -> 1014 bytes 197 files changed, 13740 insertions(+), 5982 deletions(-) create mode 100644 docs/dli/umn/dli_01_0009.html delete mode 100644 docs/dli/umn/dli_01_0514.html delete mode 100644 docs/dli/umn/dli_01_0524.html create mode 100644 docs/dli/umn/dli_01_0555.html create mode 100644 docs/dli/umn/dli_01_0612.html create mode 100644 docs/dli/umn/dli_01_0631.html create mode 100644 docs/dli/umn/dli_01_0632.html create mode 100644 docs/dli/umn/dli_01_0633.html delete mode 100644 docs/dli/umn/dli_01_0664.html delete mode 100644 docs/dli/umn/dli_01_0665.html delete mode 100644 docs/dli/umn/dli_01_0666.html delete mode 100644 docs/dli/umn/dli_01_0667.html create mode 100644 docs/dli/umn/dli_01_0671.html create mode 100644 docs/dli/umn/dli_01_0672.html create mode 100644 docs/dli/umn/dli_01_0685.html create mode 100644 docs/dli/umn/dli_01_0686.html create mode 100644 docs/dli/umn/dli_01_0687.html create mode 100644 docs/dli/umn/dli_01_0689.html create mode 100644 docs/dli/umn/dli_01_0690.html create mode 100644 docs/dli/umn/dli_01_0691.html create mode 100644 docs/dli/umn/dli_01_0692.html create mode 100644 docs/dli/umn/dli_01_0693.html create mode 100644 docs/dli/umn/dli_01_0695.html create mode 100644 docs/dli/umn/dli_03_0273.html create mode 100644 docs/dli/umn/dli_03_0277.html create mode 100644 docs/dli/umn/dli_03_0278.html create mode 100644 docs/dli/umn/dli_03_0279.html create mode 100644 docs/dli/umn/dli_07_0004.html delete mode 100644 docs/dli/umn/en-us_image_0000001570712116.png rename docs/dli/umn/{en-us_image_0000001151957753.png => en-us_image_0000001620741493.png} (100%) delete mode 100644 docs/dli/umn/en-us_image_0000001620789569.png delete mode 100644 docs/dli/umn/en-us_image_0000001897113369.png create mode 100644 docs/dli/umn/en-us_image_0000002031125321.png create mode 100644 docs/dli/umn/en-us_image_0000002174135216.png create mode 100644 docs/dli/umn/en-us_image_0000002295795461.png create mode 100644 docs/dli/umn/en-us_image_0000002337417937.png create mode 100644 docs/dli/umn/en-us_image_0000002348096834.png create mode 100644 docs/dli/umn/en-us_image_0000002363051176.png create mode 100644 docs/dli/umn/en-us_image_0000002363080342.png create mode 100644 docs/dli/umn/en-us_image_0000002363115912.png create mode 100644 docs/dli/umn/en-us_image_0000002363450016.png create mode 100644 docs/dli/umn/en-us_image_0000002381617561.png create mode 100644 docs/dli/umn/en-us_image_0000002381737281.png create mode 100644 docs/dli/umn/en-us_image_0000002397300825.png create mode 100644 docs/dli/umn/en-us_image_0000002398199205.png create mode 100644 docs/dli/umn/en-us_image_0000002410128586.png create mode 100644 docs/dli/umn/en-us_image_0000002415789969.png delete mode 100644 docs/dli/umn/en-us_image_0206789726.jpg delete mode 100644 docs/dli/umn/en-us_image_0206789784.png create mode 100644 docs/dli/umn/public_sys-resources/imageclose.gif create mode 100644 docs/dli/umn/public_sys-resources/imageclosehover.gif create mode 100644 docs/dli/umn/public_sys-resources/imagemax.gif create mode 100644 docs/dli/umn/public_sys-resources/imagemaxhover.gif create mode 100644 docs/dli/umn/public_sys-resources/macFFBgHack.png diff --git a/docs/dli/umn/ALL_META.TXT.json b/docs/dli/umn/ALL_META.TXT.json index 4b3478871..b6c0ac1a8 100644 --- a/docs/dli/umn/ALL_META.TXT.json +++ b/docs/dli/umn/ALL_META.TXT.json @@ -16,8 +16,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Service Overview", @@ -37,8 +37,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"What Is Data Lake Insight", @@ -58,8 +58,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Advantages", @@ -72,18 +72,18 @@ "code":"4", "des":"DLI is applicable to large-scale log analysis, federated analysis of heterogeneous data sources, and big data ETL processing.Gaming operations data analysisDifferent depa", "doc_type":"usermanual", - "kw":"Application Scenarios,Service Overview,User Guide", + "kw":"Use Cases,Service Overview,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Application Scenarios", + "title":"Use Cases", "githuburl":"" }, { @@ -100,8 +100,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Notes and Constraints", @@ -112,20 +112,20 @@ "node_id":"dli_07_0027.xml", "product_code":"dli", "code":"6", - "des":"An elastic resource pool provides compute resources (CPU and memory) for running DLI jobs. The unit is CU. One CU contains one CPU and 4 GB memory.You can create multiple", + "des":"DLI compute resources are the foundation for job execution. Both DLI's elastic resource pools and queues fall under compute resources. This section introduces the types a", "doc_type":"usermanual", - "kw":"Specifications,Service Overview,User Guide", + "kw":"Compute Resource Types and Specifications,Service Overview,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Specifications", + "title":"Compute Resource Types and Specifications", "githuburl":"" }, { @@ -135,18 +135,18 @@ "code":"7", "des":"If you need to assign different permissions to employees in your enterprise to access your DLI resources, IAM is a good choice for fine-grained permissions management. IA", "doc_type":"usermanual", - "kw":"Permissions Management,Service Overview,User Guide", + "kw":"Permission Management,Service Overview,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Permissions Management", + "title":"Permission Management", "githuburl":"" }, { @@ -163,19 +163,40 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Quotas", "githuburl":"" }, + { + "uri":"dli_07_0004.html", + "node_id":"dli_07_0004.xml", + "product_code":"dli", + "code":"9", + "des":"OBS works as the data source and data storage system for DLI, and delivers the following capabilities:Data source: DLI provides an API for you to import data from corresp", + "doc_type":"usermanual", + "kw":"Related Services,Service Overview,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Related Services", + "githuburl":"" + }, { "uri":"dli_07_0003.html", "node_id":"dli_07_0003.xml", "product_code":"dli", - "code":"9", - "des":"Dedicated computing resources. They are isolated by resource pools and can only be shared by queues in the same elastic resource pool. You can set scaling policies of dif", + "code":"10", + "des":"An elastic resource pool consists of dedicated compute resources where the resources in different pools are completely isolated from each other. Within a single elastic r", "doc_type":"usermanual", "kw":"Basic Concepts,Service Overview,User Guide", "search_title":"", @@ -184,8 +205,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Basic Concepts", @@ -195,7 +216,7 @@ "uri":"dli_01_0220.html", "node_id":"dli_01_0220.xml", "product_code":"dli", - "code":"10", + "code":"11", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Getting Started", @@ -205,8 +226,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Getting Started", @@ -216,112 +237,112 @@ "uri":"dli_01_0002.html", "node_id":"dli_01_0002.xml", "product_code":"dli", - "code":"11", - "des":"DLI can query data stored in OBS. This section describes how to use DLI to submit a SQL job to query OBS data.To illustrate, create a new file called sampledata.csv and u", + "code":"12", + "des":"DLI can query data stored in OBS. This section describes how to use DLI to submit a SQL job to query OBS data.To illustrate, create a file called sampledata.csv and uploa", "doc_type":"usermanual", - "kw":"Using DLI to Submit a SQL Job to Query OBS Data,Getting Started,User Guide", + "kw":"Submitting a SQL Job to Query OBS Data Using DLI,Getting Started,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Using DLI to Submit a SQL Job to Query OBS Data", + "title":"Submitting a SQL Job to Query OBS Data Using DLI", "githuburl":"" }, { "uri":"dli_01_0020.html", "node_id":"dli_01_0020.xml", "product_code":"dli", - "code":"12", + "code":"13", "des":"DLI can query data stored in RDS. This section describes how to use DLI to submit a SQL job to query RDS for MySQL data.In this example, we will create an RDS for MySQL D", "doc_type":"usermanual", - "kw":"Using DLI to Submit a SQL Job to Query RDS for MySQL Data,Getting Started,User Guide", + "kw":"Submitting a SQL Job to Query RDS for MySQL Data Using DLI,Getting Started,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Using DLI to Submit a SQL Job to Query RDS for MySQL Data", + "title":"Submitting a SQL Job to Query RDS for MySQL Data Using DLI", "githuburl":"" }, { "uri":"dli_01_0531.html", "node_id":"dli_01_0531.xml", "product_code":"dli", - "code":"13", + "code":"14", "des":"DLI Flink jobs can use other cloud services as data sources and sink streams for real-time compute.This example describes how to create and submit a Flink OpenSource SQL ", "doc_type":"usermanual", - "kw":"Using DLI to Submit a Flink OpenSource SQL Job to Query RDS for MySQL Data,Getting Started,User Guid", + "kw":"Submitting a Flink OpenSource SQL Job to Query RDS for MySQL Data Using DLI,Getting Started,User Gui", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Using DLI to Submit a Flink OpenSource SQL Job to Query RDS for MySQL Data", + "title":"Submitting a Flink OpenSource SQL Job to Query RDS for MySQL Data Using DLI", "githuburl":"" }, { "uri":"dli_01_0512.html", "node_id":"dli_01_0512.xml", "product_code":"dli", - "code":"14", + "code":"15", "des":"Flink Jar jobs are suitable for data analysis scenarios that require custom stream processing logic, complex state management, or integration with specific libraries. You", "doc_type":"usermanual", - "kw":"Using DLI to Submit a Flink Jar Job,Getting Started,User Guide", + "kw":"Submitting a Flink Jar Job Using DLI,Getting Started,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Using DLI to Submit a Flink Jar Job", + "title":"Submitting a Flink Jar Job Using DLI", "githuburl":"" }, { "uri":"dli_01_0375.html", "node_id":"dli_01_0375.xml", "product_code":"dli", - "code":"15", + "code":"16", "des":"DLI allows you to submit Spark jobs compiled as JAR files, which contain the necessary code and dependency information for executing the job. These files are used for spe", "doc_type":"usermanual", - "kw":"Using DLI to Submit a Spark Jar Job,Getting Started,User Guide", + "kw":"Submitting a Spark Jar Job Using DLI,Getting Started,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Using DLI to Submit a Spark Jar Job", + "title":"Submitting a Spark Jar Job Using DLI", "githuburl":"" }, { "uri":"dli_01_0001.html", "node_id":"dli_01_0001.xml", "product_code":"dli", - "code":"16", + "code":"17", "des":"This chapter walks you through on how to develop a DLI job.To manage fine-grained permissions for your DLI resources using IAM, create an IAM user and grant them permissi", "doc_type":"usermanual", "kw":"DLI Job Development Process,User Guide", @@ -331,8 +352,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"DLI Job Development Process", @@ -342,7 +363,7 @@ "uri":"dli_01_0611.html", "node_id":"dli_01_0611.xml", "product_code":"dli", - "code":"17", + "code":"18", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Preparations", @@ -352,8 +373,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Preparations", @@ -363,8 +384,8 @@ "uri":"dli_01_0618.html", "node_id":"dli_01_0618.xml", "product_code":"dli", - "code":"18", - "des":"To use DLI, you must first configure permissions.This section applies to the following scenarios:If you use DLI for the first time, configure DLI agency permissions by re", + "code":"19", + "des":"Before using DLI, configure DLI agency permissions. This section describes the scenarios and steps for configuring DLI agency permissions (dli_management_agency).If you u", "doc_type":"usermanual", "kw":"Configuring DLI Agency Permissions,Preparations,User Guide", "search_title":"", @@ -373,8 +394,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Configuring DLI Agency Permissions", @@ -384,8 +405,8 @@ "uri":"dli_01_0418.html", "node_id":"dli_01_0418.xml", "product_code":"dli", - "code":"19", - "des":"You can use Identity and Access Management (IAM) to implement fine-grained permissions control on DLI resources. For details, see Overview.If your cloud account does not ", + "code":"20", + "des":"You can use Identity and Access Management (IAM) to implement fine-grained permissions management for your DLI resources. For details, see Overview.If your cloud account ", "doc_type":"usermanual", "kw":"Creating an IAM User and Granting Permissions,Preparations,User Guide", "search_title":"", @@ -394,8 +415,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating an IAM User and Granting Permissions", @@ -405,7 +426,7 @@ "uri":"dli_01_0536.html", "node_id":"dli_01_0536.xml", "product_code":"dli", - "code":"20", + "code":"21", "des":"Before using DLI, you need to configure a DLI job bucket. The bucket is used to store temporary data generated during DLI job running, such as job logs and results.Config", "doc_type":"usermanual", "kw":"Configuring a DLI Job Bucket,Preparations,User Guide", @@ -415,8 +436,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Configuring a DLI Job Bucket", @@ -426,39 +447,39 @@ "uri":"dli_01_0508.html", "node_id":"dli_01_0508.xml", "product_code":"dli", - "code":"21", + "code":"22", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Creating an Elastic Resource Pool and Queues Within It", + "kw":"Creating an Elastic Resource Pool and Creating Queues Within It", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Creating an Elastic Resource Pool and Queues Within It", + "title":"Creating an Elastic Resource Pool and Creating Queues Within It", "githuburl":"" }, { "uri":"dli_01_0504.html", "node_id":"dli_01_0504.xml", "product_code":"dli", - "code":"22", + "code":"23", "des":"DLI compute resources are the foundation to run jobs. This section describes the modes of DLI compute resources and queue types.Before we dive into the compute resource m", "doc_type":"usermanual", - "kw":"Overview of DLI Elastic Resource Pools and Queues,Creating an Elastic Resource Pool and Queues Withi", + "kw":"Overview of DLI Elastic Resource Pools and Queues,Creating an Elastic Resource Pool and Creating Que", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Overview of DLI Elastic Resource Pools and Queues", @@ -468,7 +489,7 @@ "uri":"dli_01_0505.html", "node_id":"dli_01_0505.xml", "product_code":"dli", - "code":"23", + "code":"24", "des":"An elastic resource pool offers compute resources (CPU and memory) required for running DLI jobs, which can adapt to the changing demands of services.You can create multi", "doc_type":"usermanual", "kw":"Creating an Elastic Resource Pool and Creating Queues Within It,Creating an Elastic Resource Pool an", @@ -478,8 +499,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating an Elastic Resource Pool and Creating Queues Within It", @@ -489,7 +510,7 @@ "uri":"dli_01_0529.html", "node_id":"dli_01_0529.xml", "product_code":"dli", - "code":"24", + "code":"25", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Elastic Resource Pools", @@ -499,8 +520,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing Elastic Resource Pools", @@ -510,28 +531,28 @@ "uri":"dli_01_0622.html", "node_id":"dli_01_0622.xml", "product_code":"dli", - "code":"25", + "code":"26", "des":"After creating an elastic resource pool, you can check and manage it on the management console.This section describes how to check basic information about an elastic reso", "doc_type":"usermanual", - "kw":"Viewing Basic Information,Managing Elastic Resource Pools,User Guide", + "kw":"Checking Basic Information,Managing Elastic Resource Pools,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Viewing Basic Information", + "title":"Checking Basic Information", "githuburl":"" }, { "uri":"dli_01_0526.html", "node_id":"dli_01_0526.xml", "product_code":"dli", - "code":"26", + "code":"27", "des":"Administrators can assign permissions of different operation scopes to users for each elastic resource pool.The administrator and elastic resource pool owner have all per", "doc_type":"usermanual", "kw":"Managing Permissions,Managing Elastic Resource Pools,User Guide", @@ -541,8 +562,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing Permissions", @@ -552,7 +573,7 @@ "uri":"dli_01_0530.html", "node_id":"dli_01_0530.xml", "product_code":"dli", - "code":"27", + "code":"28", "des":"If you want a queue to use resources in an elastic resource pool, bind the queue to the pool.You can click Associate Queue on the Resource Pool page to bind a queue to an", "doc_type":"usermanual", "kw":"Binding a Queue,Managing Elastic Resource Pools,User Guide", @@ -562,19 +583,40 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Binding a Queue", "githuburl":"" }, + { + "uri":"dli_01_0686.html", + "node_id":"dli_01_0686.xml", + "product_code":"dli", + "code":"29", + "des":"Scaling out or in an elastic resource pool essentially means adjusting the actual CUs of the resource pool.In an elastic resource pool:Actual CUs: actual size of resource", + "doc_type":"usermanual", + "kw":"Scaling Out or In an Elastic Resource Pool,Managing Elastic Resource Pools,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Scaling Out or In an Elastic Resource Pool", + "githuburl":"" + }, { "uri":"dli_01_0507.html", "node_id":"dli_01_0507.xml", "product_code":"dli", - "code":"28", - "des":"CU settings are used to control the maximum and minimum CU ranges for elastic resource pools to avoid unlimited resource scaling.For example, an elastic resource pool has", + "code":"30", + "des":"CU settings are used to control the maximum and minimum CU ranges for elastic resource pool scaling to prevent unlimited resource expansion risks.For example, if the curr", "doc_type":"usermanual", "kw":"Setting CUs,Managing Elastic Resource Pools,User Guide", "search_title":"", @@ -583,40 +625,19 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Setting CUs", "githuburl":"" }, - { - "uri":"dli_01_0524.html", - "node_id":"dli_01_0524.xml", - "product_code":"dli", - "code":"29", - "des":"If the current specifications of your elastic resource pool do not meet your service needs, you can modify them using the change yearly/monthly CUs function.In the naviga", - "doc_type":"usermanual", - "kw":"Modifying Specifications,Managing Elastic Resource Pools,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"dli", - "opensource":"true", - "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" - } - ], - "title":"Modifying Specifications", - "githuburl":"" - }, { "uri":"dli_01_0525.html", "node_id":"dli_01_0525.xml", "product_code":"dli", - "code":"30", - "des":"A tag is a key-value pair that you can customize to identify cloud resources. It helps you to classify and search for cloud resources. A tag consists of a tag key and a t", + "code":"31", + "des":"A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value.If you use ", "doc_type":"usermanual", "kw":"Managing Tags,Managing Elastic Resource Pools,User Guide", "search_title":"", @@ -625,8 +646,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing Tags", @@ -636,7 +657,7 @@ "uri":"dli_01_0506.html", "node_id":"dli_01_0506.xml", "product_code":"dli", - "code":"31", + "code":"32", "des":"Multiple queues can be added to an elastic resource pool. For how to add a queue, see Creating an Elastic Resource Pool and Creating Queues Within It. You can configure t", "doc_type":"usermanual", "kw":"Adjusting Scaling Policies for Queues in an Elastic Resource Pool,Managing Elastic Resource Pools,Us", @@ -646,8 +667,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Adjusting Scaling Policies for Queues in an Elastic Resource Pool", @@ -657,7 +678,7 @@ "uri":"dli_01_0532.html", "node_id":"dli_01_0532.xml", "product_code":"dli", - "code":"32", + "code":"33", "des":"If you added a queue to or deleted one from an elastic resource pool, or you scaled an added queue, the CU quantity of the elastic resource pool may be changed. You can v", "doc_type":"usermanual", "kw":"Viewing Scaling History,Managing Elastic Resource Pools,User Guide", @@ -667,8 +688,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Viewing Scaling History", @@ -678,7 +699,7 @@ "uri":"dli_01_0566.html", "node_id":"dli_01_0566.xml", "product_code":"dli", - "code":"33", + "code":"34", "des":"You can create enterprise projects matching the organizational structure of your enterprises to centrally manage cloud resources across regions by project. Then you can c", "doc_type":"usermanual", "kw":"Allocating to an Enterprise Project,Managing Elastic Resource Pools,User Guide", @@ -688,8 +709,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Allocating to an Enterprise Project", @@ -699,7 +720,7 @@ "uri":"dli_01_0528.html", "node_id":"dli_01_0528.xml", "product_code":"dli", - "code":"34", + "code":"35", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Queues", @@ -709,8 +730,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing Queues", @@ -720,7 +741,7 @@ "uri":"dli_01_0663.html", "node_id":"dli_01_0663.xml", "product_code":"dli", - "code":"35", + "code":"36", "des":"This section walks you through how to view basic information about a queue on the management console, including the engine type and version.Log in to the DLI management c", "doc_type":"usermanual", "kw":"Viewing Basic Information About a Queue,Managing Queues,User Guide", @@ -730,8 +751,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Viewing Basic Information About a Queue", @@ -741,7 +762,7 @@ "uri":"dli_01_0015.html", "node_id":"dli_01_0015.xml", "product_code":"dli", - "code":"36", + "code":"37", "des":"Administrators and queue owners have full operation permissions on queues. They can grant operation permissions to other users based on service needs. This ensures that u", "doc_type":"usermanual", "kw":"Queue Permission Management,Managing Queues,User Guide", @@ -751,8 +772,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Queue Permission Management", @@ -762,7 +783,7 @@ "uri":"dli_01_0565.html", "node_id":"dli_01_0565.xml", "product_code":"dli", - "code":"37", + "code":"38", "des":"You can create enterprise projects matching the organizational structure of your enterprises to centrally manage cloud resources across regions by project. Then you can c", "doc_type":"usermanual", "kw":"Allocating a Queue to an Enterprise Project,Managing Queues,User Guide", @@ -772,8 +793,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Allocating a Queue to an Enterprise Project", @@ -783,7 +804,7 @@ "uri":"dli_01_0421.html", "node_id":"dli_01_0421.xml", "product_code":"dli", - "code":"38", + "code":"39", "des":"Once you have created an SMN topic, you can easily subscribe to it by going to the Topic Management > Topics page of the SMN console. You can choose to receive notificati", "doc_type":"usermanual", "kw":"Creating an SMN Topic,Managing Queues,User Guide", @@ -793,8 +814,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating an SMN Topic", @@ -804,8 +825,8 @@ "uri":"dli_01_0022.html", "node_id":"dli_01_0022.xml", "product_code":"dli", - "code":"39", - "des":"A tag is a key-value pair that you can customize to identify cloud resources. It helps you to classify and search for cloud resources. A tag consists of a tag key and a t", + "code":"40", + "des":"A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value.If you use ", "doc_type":"usermanual", "kw":"Managing Queue Tags,Managing Queues,User Guide", "search_title":"", @@ -814,8 +835,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing Queue Tags", @@ -825,8 +846,8 @@ "uri":"dli_01_0563.html", "node_id":"dli_01_0563.xml", "product_code":"dli", - "code":"40", - "des":"DLI allows you to set properties for queues.You can set Spark driver parameters to improve the scheduling efficiency of queues.This section describes how to set queue pro", + "code":"41", + "des":"DLI allows you to set properties for queues.You can currently set the following property parameters:Spark driver parameters: Set them to improve the scheduling efficiency", "doc_type":"usermanual", "kw":"Setting Queue Properties,Managing Queues,User Guide", "search_title":"", @@ -835,39 +856,60 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Setting Queue Properties", "githuburl":"" }, { - "uri":"dli_01_0489.html", - "node_id":"dli_01_0489.xml", + "uri":"dli_01_0685.html", + "node_id":"dli_01_0685.xml", "product_code":"dli", - "code":"41", - "des":"DLI's address connectivity testing feature can be used to verify network connectivity between DLI queues and destination addresses.This feature is typically utilized for ", + "code":"42", + "des":"Spark Native is a core component of Apache Spark designed to enhance the performance of Spark SQL computations. By utilizing vectorized C++ acceleration libraries, it acc", "doc_type":"usermanual", - "kw":"Testing Address Connectivity,Managing Queues,User Guide", + "kw":"Enabling Spark Native Operator Optimization,Managing Queues,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Testing Address Connectivity", + "title":"Enabling Spark Native Operator Optimization", + "githuburl":"" + }, + { + "uri":"dli_01_0489.html", + "node_id":"dli_01_0489.xml", + "product_code":"dli", + "code":"43", + "des":"DLI's address connectivity testing feature can be used to verify network connectivity between DLI queues and destination addresses.This feature is typically utilized for ", + "doc_type":"usermanual", + "kw":"Testing the Network Connectivity Between a Queue and a Data Source,Managing Queues,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Testing the Network Connectivity Between a Queue and a Data Source", "githuburl":"" }, { "uri":"dli_01_0016.html", "node_id":"dli_01_0016.xml", "product_code":"dli", - "code":"42", + "code":"44", "des":"You can delete a queue based on actual conditions.This operation will fail if there are jobs in the Submitting or Running state on this queue.Deleting a queue does not ca", "doc_type":"usermanual", "kw":"Deleting a Queue,Managing Queues,User Guide", @@ -877,8 +919,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Deleting a Queue", @@ -888,70 +930,70 @@ "uri":"dli_01_0487.html", "node_id":"dli_01_0487.xml", "product_code":"dli", - "code":"43", - "des":"Newly created queues need to run jobs before they can be scaled in or out.The operations described in this section only apply to standard queues.Queues with 16 CUs do not", + "code":"45", + "des":"Newly created queues need to run jobs before they can be scaled in or out.The operations described in this section only apply to queues in non-elastic resource pools.Queu", "doc_type":"usermanual", - "kw":"Auto Scaling of Standard Queues,Managing Queues,User Guide", + "kw":"Enabling Elastic Scaling for a Queue in a Non-Elastic Resource Pool,Managing Queues,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Auto Scaling of Standard Queues", + "title":"Enabling Elastic Scaling for a Queue in a Non-Elastic Resource Pool", "githuburl":"" }, { "uri":"dli_01_0488.html", "node_id":"dli_01_0488.xml", "product_code":"dli", - "code":"44", + "code":"46", "des":"When services are busy, you might need to use more compute resources to process services in a period. After this period, you do not require the same amount of resources. ", "doc_type":"usermanual", - "kw":"Setting a Scheduled Auto Scaling Task for a Standard Queue,Managing Queues,User Guide", + "kw":"Creating a Scheduled Elastic Scaling Task for a Queue in a Non-Elastic Resource Pool,Managing Queues", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Setting a Scheduled Auto Scaling Task for a Standard Queue", + "title":"Creating a Scheduled Elastic Scaling Task for a Queue in a Non-Elastic Resource Pool", "githuburl":"" }, { "uri":"dli_01_0443.html", "node_id":"dli_01_0443.xml", "product_code":"dli", - "code":"45", + "code":"47", "des":"If the CIDR block of the DLI queue conflicts with that of the user data source, you can change the CIDR block of the queue.If the queue whose CIDR block is to be modified", "doc_type":"usermanual", - "kw":"Changing the CIDR Block for a Standard Queue,Managing Queues,User Guide", + "kw":"Changing the CIDR Block of a Queue in a Non-Elastic Resource Pool,Managing Queues,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Changing the CIDR Block for a Standard Queue", + "title":"Changing the CIDR Block of a Queue in a Non-Elastic Resource Pool", "githuburl":"" }, { "uri":"dli_01_0515.html", "node_id":"dli_01_0515.xml", "product_code":"dli", - "code":"46", + "code":"48", "des":"This section walks you through the procedure of adding a queue to an elastic resource pool and binding an enhanced datasource connection to the elastic resource pool.Proc", "doc_type":"usermanual", "kw":"Example Use Case: Creating an Elastic Resource Pool and Running Jobs,Creating an Elastic Resource Po", @@ -961,8 +1003,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Example Use Case: Creating an Elastic Resource Pool and Running Jobs", @@ -972,7 +1014,7 @@ "uri":"dli_01_0516.html", "node_id":"dli_01_0516.xml", "product_code":"dli", - "code":"47", + "code":"49", "des":"A company has multiple departments that perform data analysis in different periods during a day.Department A requires a large number of compute resources from 00:00 a.m. ", "doc_type":"usermanual", "kw":"Example Use Case: Configuring Scaling Policies for Queues in an Elastic Resource Pool,Creating an El", @@ -982,8 +1024,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Example Use Case: Configuring Scaling Policies for Queues in an Elastic Resource Pool", @@ -993,60 +1035,60 @@ "uri":"dli_01_0363.html", "node_id":"dli_01_0363.xml", "product_code":"dli", - "code":"48", + "code":"50", "des":"Queues in the non-elastic resource pool mode are the previous-gen of resource management for DLI. It involved purchasing and releasing resources based on usage demands, r", "doc_type":"usermanual", - "kw":"Creating a Non-Elastic Resource Pool Queue (Discarded and Not Recommended),Creating an Elastic Resou", + "kw":"Creating a Non-Elastic Resource Pool Queue (Deprecated, Not Recommended),Creating an Elastic Resourc", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Creating a Non-Elastic Resource Pool Queue (Discarded and Not Recommended)", + "title":"Creating a Non-Elastic Resource Pool Queue (Deprecated, Not Recommended)", "githuburl":"" }, { "uri":"dli_01_0390.html", "node_id":"dli_01_0390.xml", "product_code":"dli", - "code":"49", + "code":"51", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Creating Databases and Tables", + "kw":"Creating a Data Directory, Database, and Table", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Creating Databases and Tables", + "title":"Creating a Data Directory, Database, and Table", "githuburl":"" }, { "uri":"dli_01_0228.html", "node_id":"dli_01_0228.xml", "product_code":"dli", - "code":"50", + "code":"52", "des":"Databases and tables are the basis for developing SQL and Spark jobs. Before running a job, you need to define databases and tables based on your service scenarios.Flink ", "doc_type":"usermanual", - "kw":"Understanding Data Catalogs, Databases, and Tables,Creating Databases and Tables,User Guide", + "kw":"Understanding Data Catalogs, Databases, and Tables,Creating a Data Directory, Database, and Table,Us", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Understanding Data Catalogs, Databases, and Tables", @@ -1056,49 +1098,91 @@ "uri":"dli_01_0005.html", "node_id":"dli_01_0005.xml", "product_code":"dli", - "code":"51", - "des":"A database, built on the computer storage device, is a data warehouse where data is organized, stored, and managed based on its structure.The table is an important part o", + "code":"53", + "des":"A database is a repository of data organized, stored, and managed on computer storage devices according to data structures.A table is one of the most essential components", "doc_type":"usermanual", - "kw":"Creating a Database and Table on the DLI Console,Creating Databases and Tables,User Guide", + "kw":"Creating a Data Catalog, Database, and Table on the DLI Console,Creating a Data Directory, Database,", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Creating a Database and Table on the DLI Console", + "title":"Creating a Data Catalog, Database, and Table on the DLI Console", "githuburl":"" }, { "uri":"dli_01_0008.html", "node_id":"dli_01_0008.xml", "product_code":"dli", - "code":"52", - "des":"Metadata is used to define data types. It describes information about the data, including the source, size, format, and other data features. In database fields, metadata ", + "code":"54", + "des":"Metadata is data used to define the type of data. It primarily describes information about the data itself, including its source, size, format, or other characteristics. ", "doc_type":"usermanual", - "kw":"Viewing Table Metadata,Creating Databases and Tables,User Guide", + "kw":"Viewing Table Metadata,Creating a Data Directory, Database, and Table,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Viewing Table Metadata", "githuburl":"" }, + { + "uri":"dli_01_0671.html", + "node_id":"dli_01_0671.xml", + "product_code":"dli", + "code":"55", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Managing Data Catalogs on the DLI Console", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Managing Data Catalogs on the DLI Console", + "githuburl":"" + }, + { + "uri":"dli_01_0672.html", + "node_id":"dli_01_0672.xml", + "product_code":"dli", + "code":"56", + "des":"DLI data catalogs support authorization on the DLI console or authentication through IAM. By setting permissions, you can grant varying data catalog permissions to differ", + "doc_type":"usermanual", + "kw":"Configuring Data Catalog Permissions on the DLI Console,Managing Data Catalogs on the DLI Console,Us", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Configuring Data Catalog Permissions on the DLI Console", + "githuburl":"" + }, { "uri":"dli_01_0004.html", "node_id":"dli_01_0004.xml", "product_code":"dli", - "code":"53", + "code":"57", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Database Resources on the DLI Console", @@ -1108,8 +1192,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing Database Resources on the DLI Console", @@ -1119,7 +1203,7 @@ "uri":"dli_01_0447.html", "node_id":"dli_01_0447.xml", "product_code":"dli", - "code":"54", + "code":"58", "des":"By setting permissions, you can assign varying database permissions to different users.The administrator and database owner have all permissions, which cannot be set or m", "doc_type":"usermanual", "kw":"Configuring Database Permissions on the DLI Console,Managing Database Resources on the DLI Console,U", @@ -1129,8 +1213,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Configuring Database Permissions on the DLI Console", @@ -1140,8 +1224,8 @@ "uri":"dli_01_0011.html", "node_id":"dli_01_0011.xml", "product_code":"dli", - "code":"55", - "des":"You can delete databases as needed.You are not allowed to delete databases or tables that are being used for running jobs.The administrator, database owner, and users wit", + "code":"59", + "des":"You can delete an unused database from the DLI console: when a database is no longer needed, such as after a test database has completed testing; if a database has errors", "doc_type":"usermanual", "kw":"Deleting a Database on the DLI Console,Managing Database Resources on the DLI Console,User Guide", "search_title":"", @@ -1150,8 +1234,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Deleting a Database on the DLI Console", @@ -1161,7 +1245,7 @@ "uri":"dli_01_0376.html", "node_id":"dli_01_0376.xml", "product_code":"dli", - "code":"56", + "code":"60", "des":"In practical use, developers create databases and tables, which are then handed over to testers for testing. Once testing is complete, the databases and tables are handed", "doc_type":"usermanual", "kw":"Changing the Database Owner on the DLI Console,Managing Database Resources on the DLI Console,User G", @@ -1171,8 +1255,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Changing the Database Owner on the DLI Console", @@ -1182,28 +1266,28 @@ "uri":"dli_01_0552.html", "node_id":"dli_01_0552.xml", "product_code":"dli", - "code":"57", - "des":"A tag is a key-value pair that you can customize to identify cloud resources. It helps you to classify and search for cloud resources. A tag consists of a tag key and a t", + "code":"61", + "des":"A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value. If you use", "doc_type":"usermanual", - "kw":"Managing Tags,Managing Database Resources on the DLI Console,User Guide", + "kw":"Managing Tags for Database Tables,Managing Database Resources on the DLI Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Managing Tags", + "title":"Managing Tags for Database Tables", "githuburl":"" }, { "uri":"dli_01_0625.html", "node_id":"dli_01_0625.xml", "product_code":"dli", - "code":"58", + "code":"62", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Table Resources on the DLI Console", @@ -1213,8 +1297,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing Table Resources on the DLI Console", @@ -1224,7 +1308,7 @@ "uri":"dli_01_0448.html", "node_id":"dli_01_0448.xml", "product_code":"dli", - "code":"59", + "code":"63", "des":"By setting permissions, you can assign varying table permissions to different users.The administrator and table owner have all permissions, which cannot be set or modifie", "doc_type":"usermanual", "kw":"Configuring Table Permissions on the DLI Console,Managing Table Resources on the DLI Console,User Gu", @@ -1234,8 +1318,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Configuring Table Permissions on the DLI Console", @@ -1245,8 +1329,8 @@ "uri":"dli_01_0626.html", "node_id":"dli_01_0626.xml", "product_code":"dli", - "code":"60", - "des":"You can delete tables as needed.Databases or tables that are being used for running jobs cannot be deleted.Only administrators, table owners, and users with table deletio", + "code":"64", + "des":"You can delete an unused data table from the DLI console: when a data table is no longer needed, such as after a test data table has completed testing; if a data table ha", "doc_type":"usermanual", "kw":"Deleting a Table on the DLI Console,Managing Table Resources on the DLI Console,User Guide", "search_title":"", @@ -1255,8 +1339,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Deleting a Table on the DLI Console", @@ -1266,7 +1350,7 @@ "uri":"dli_01_0627.html", "node_id":"dli_01_0627.xml", "product_code":"dli", - "code":"61", + "code":"65", "des":"In practical use, developers create databases and tables, which are then handed over to testers for testing. Once testing is complete, the databases and tables are handed", "doc_type":"usermanual", "kw":"Changing the Table Owner on the DLI Console,Managing Table Resources on the DLI Console,User Guide", @@ -1276,8 +1360,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Changing the Table Owner on the DLI Console", @@ -1287,28 +1371,28 @@ "uri":"dli_01_0253.html", "node_id":"dli_01_0253.xml", "product_code":"dli", - "code":"62", - "des":"This section describes how to import data stored in OBS to a table on the DLI console.Only one path can be specified during data import. The path cannot contain commas (,", + "code":"66", + "des":"This section describes how to import data stored in OBS to a table on the DLI console. Data can be imported to both DLI tables (table type: MANAGED) and OBS tables (table", "doc_type":"usermanual", - "kw":"Importing OBS Data to DLI,Managing Table Resources on the DLI Console,User Guide", + "kw":"Importing OBS Data to a DLI Table,Managing Table Resources on the DLI Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Importing OBS Data to DLI", + "title":"Importing OBS Data to a DLI Table", "githuburl":"" }, { "uri":"dli_01_0010.html", "node_id":"dli_01_0010.xml", "product_code":"dli", - "code":"63", + "code":"67", "des":"You can export data from a DLI table to OBS. During the export, a folder is created in OBS or the content in the existing folder is overwritten.The exported file can be i", "doc_type":"usermanual", "kw":"Exporting DLI Table Data to OBS,Managing Table Resources on the DLI Console,User Guide", @@ -1318,8 +1402,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Exporting DLI Table Data to OBS", @@ -1329,7 +1413,7 @@ "uri":"dli_01_0007.html", "node_id":"dli_01_0007.xml", "product_code":"dli", - "code":"64", + "code":"68", "des":"The Preview page displays the first 10 records in the table.You can preview data on either the Data Management page or the SQL Editor page.To preview data on the Data Man", "doc_type":"usermanual", "kw":"Previewing Table Data on the DLI Console,Managing Table Resources on the DLI Console,User Guide", @@ -1339,8 +1423,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Previewing Table Data on the DLI Console", @@ -1350,49 +1434,112 @@ "uri":"dli_01_0661.html", "node_id":"dli_01_0661.xml", "product_code":"dli", - "code":"65", + "code":"69", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Data Migration and Transmission", + "kw":"Data Import and Migration", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Data Migration and Transmission", + "title":"Data Import and Migration", "githuburl":"" }, { "uri":"dli_01_0662.html", "node_id":"dli_01_0662.xml", "product_code":"dli", - "code":"66", + "code":"70", "des":"DLI enables direct access to data stored in OBS for query and analysis, eliminating the need for data migration.To begin using DLI for data analysis, just import your loc", "doc_type":"usermanual", - "kw":"Overview,Data Migration and Transmission,User Guide", + "kw":"Overview,Data Import and Migration,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Overview", "githuburl":"" }, + { + "uri":"dli_01_0631.html", + "node_id":"dli_01_0631.xml", + "product_code":"dli", + "code":"71", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Migrating Data from External Data Sources to DLI", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Migrating Data from External Data Sources to DLI", + "githuburl":"" + }, + { + "uri":"dli_01_0632.html", + "node_id":"dli_01_0632.xml", + "product_code":"dli", + "code":"72", + "des":"To centrally analyze and manage scattered data from various systems, you can utilize migration tools like Cloud Data Migration (CDM) to migrate the data to DLI. Once the ", + "doc_type":"usermanual", + "kw":"Overview of Data Migration Scenarios,Migrating Data from External Data Sources to DLI,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Overview of Data Migration Scenarios", + "githuburl":"" + }, + { + "uri":"dli_01_0633.html", + "node_id":"dli_01_0633.xml", + "product_code":"dli", + "code":"73", + "des":"On its GUI, CDM enables you to create data migration tasks from multiple data sources to a data lake.This section describes how to use CDM to migrate data from data sourc", + "doc_type":"usermanual", + "kw":"Using CDM to Migrate Data to DLI,Migrating Data from External Data Sources to DLI,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Using CDM to Migrate Data to DLI", + "githuburl":"" + }, { "uri":"dli_01_0634.html", "node_id":"dli_01_0634.xml", "product_code":"dli", - "code":"67", + "code":"74", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Configuring DLI to Read and Write Data from and to External Data Sources", @@ -1402,8 +1549,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Configuring DLI to Read and Write Data from and to External Data Sources", @@ -1413,7 +1560,7 @@ "uri":"dli_01_0635.html", "node_id":"dli_01_0635.xml", "product_code":"dli", - "code":"68", + "code":"75", "des":"To read and write external data sources when running DLI jobs, two conditions must be met:Establish network connectivity between DLI and the external data source to ensur", "doc_type":"usermanual", "kw":"Configuring DLI to Read and Write External Data Sources,Configuring DLI to Read and Write Data from ", @@ -1423,8 +1570,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Configuring DLI to Read and Write External Data Sources", @@ -1434,7 +1581,7 @@ "uri":"dli_01_0426.html", "node_id":"dli_01_0426.xml", "product_code":"dli", - "code":"69", + "code":"76", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Configuring the Network Connection Between DLI and Data Sources (Enhanced Datasource Connection)", @@ -1444,8 +1591,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Configuring the Network Connection Between DLI and Data Sources (Enhanced Datasource Connection)", @@ -1455,8 +1602,8 @@ "uri":"dli_01_0003.html", "node_id":"dli_01_0003.xml", "product_code":"dli", - "code":"70", - "des":"In cross-source data analysis scenarios, DLI needs to connect to external data sources. However, due to the different VPCs between the data source and DLI, the network ca", + "code":"77", + "des":"Imagine DLI elastic resource pools and data sources as two isolated islands surrounded by water.To enable traffic between these two islands, you need to first construct a", "doc_type":"usermanual", "kw":"Overview of Enhanced Datasource Connections,Configuring the Network Connection Between DLI and Data ", "search_title":"", @@ -1465,8 +1612,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Overview of Enhanced Datasource Connections", @@ -1476,7 +1623,7 @@ "uri":"dli_01_0006.html", "node_id":"dli_01_0006.xml", "product_code":"dli", - "code":"71", + "code":"78", "des":"Create an enhanced datasource connection for DLI to access, import, query, and analyze data of other data sources.For example, to connect DLI to the MRS, RDS, CSS, Kafka,", "doc_type":"usermanual", "kw":"Creating an Enhanced Datasource Connection,Configuring the Network Connection Between DLI and Data S", @@ -1486,8 +1633,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating an Enhanced Datasource Connection", @@ -1497,7 +1644,7 @@ "uri":"dli_01_0410.html", "node_id":"dli_01_0410.xml", "product_code":"dli", - "code":"72", + "code":"79", "des":"If DLI needs to access external data sources, you need to establish enhanced datasource connections to enable the network between DLI and the data sources, and then devel", "doc_type":"usermanual", "kw":"Common Development Methods for DLI Cross-Source Analysis,Configuring the Network Connection Between ", @@ -1507,8 +1654,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Common Development Methods for DLI Cross-Source Analysis", @@ -1518,28 +1665,49 @@ "uri":"dli_01_0636.html", "node_id":"dli_01_0636.xml", "product_code":"dli", - "code":"73", - "des":"When using DLI to submit jobs that involve reading and writing data from external sources, it is crucial to securely access these sources by properly storing their access", + "code":"80", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Using DEW to Manage Access Credentials for Data Sources,Configuring DLI to Read and Write Data from ", + "kw":"Managing Data Source Access Credentials Using DEW", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Using DEW to Manage Access Credentials for Data Sources", + "title":"Managing Data Source Access Credentials Using DEW", + "githuburl":"" + }, + { + "uri":"dli_01_0687.html", + "node_id":"dli_01_0687.xml", + "product_code":"dli", + "code":"81", + "des":"When submitting Flink or Spark jobs through DLI to access external data sources (such as OBS and Kafka), there is a risk of plaintext exposure if AK/SK, usernames/passwor", + "doc_type":"usermanual", + "kw":"Overview,Managing Data Source Access Credentials Using DEW,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Overview", "githuburl":"" }, { "uri":"dli_01_0422.html", "node_id":"dli_01_0422.xml", "product_code":"dli", - "code":"74", + "code":"82", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Using DLI Datasource Authentication to Manage Access Credentials for Data Sources", @@ -1549,8 +1717,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Using DLI Datasource Authentication to Manage Access Credentials for Data Sources", @@ -1560,7 +1728,7 @@ "uri":"dli_01_0561.html", "node_id":"dli_01_0561.xml", "product_code":"dli", - "code":"75", + "code":"83", "des":"When analyzing across multiple sources, you are advised not to configure authentication information directly in a job as it can lead to password leakage. Instead, you are", "doc_type":"usermanual", "kw":"Overview,Using DLI Datasource Authentication to Manage Access Credentials for Data Sources,User Guid", @@ -1570,8 +1738,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Overview", @@ -1581,7 +1749,7 @@ "uri":"dli_01_0427.html", "node_id":"dli_01_0427.xml", "product_code":"dli", - "code":"76", + "code":"84", "des":"Create a CSS datasource authentication on the DLI console to store the authentication information of the CSS security cluster to DLI. This will allow you to access to the", "doc_type":"usermanual", "kw":"Creating a CSS Datasource Authentication,Using DLI Datasource Authentication to Manage Access Creden", @@ -1591,8 +1759,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating a CSS Datasource Authentication", @@ -1602,7 +1770,7 @@ "uri":"dli_01_0558.html", "node_id":"dli_01_0558.xml", "product_code":"dli", - "code":"77", + "code":"85", "des":"Create a Kerberos datasource authentication on the DLI console to store the authentication information of the data source to DLI. This will allow you to access to the dat", "doc_type":"usermanual", "kw":"Creating a Kerberos Datasource Authentication,Using DLI Datasource Authentication to Manage Access C", @@ -1612,8 +1780,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating a Kerberos Datasource Authentication", @@ -1623,7 +1791,7 @@ "uri":"dli_01_0560.html", "node_id":"dli_01_0560.xml", "product_code":"dli", - "code":"78", + "code":"86", "des":"Create a Kafka_SSL datasource authentication on the DLI console to store the Kafka authentication information to DLI. This will allow you to access to Kafka instances wit", "doc_type":"usermanual", "kw":"Creating a Kafka_SSL Datasource Authentication,Using DLI Datasource Authentication to Manage Access ", @@ -1633,8 +1801,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating a Kafka_SSL Datasource Authentication", @@ -1644,7 +1812,7 @@ "uri":"dli_01_0559.html", "node_id":"dli_01_0559.xml", "product_code":"dli", - "code":"79", + "code":"87", "des":"Create a password datasource authentication on the DLI console to store passwords of the GaussDB(DWS), RDS, DCS, and DDS data sources to DLI. This will allow you to acces", "doc_type":"usermanual", "kw":"Creating a Password Datasource Authentication,Using DLI Datasource Authentication to Manage Access C", @@ -1654,8 +1822,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating a Password Datasource Authentication", @@ -1665,7 +1833,7 @@ "uri":"dli_01_0480.html", "node_id":"dli_01_0480.xml", "product_code":"dli", - "code":"80", + "code":"88", "des":"Grant permissions on a datasource authentication to users so multiple user jobs can use the datasource authentication without affecting each other.The administrator and t", "doc_type":"usermanual", "kw":"Datasource Authentication Permission Management,Using DLI Datasource Authentication to Manage Access", @@ -1675,8 +1843,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Datasource Authentication Permission Management", @@ -1686,7 +1854,7 @@ "uri":"dli_01_0509.html", "node_id":"dli_01_0509.xml", "product_code":"dli", - "code":"81", + "code":"89", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Enhanced Datasource Connections", @@ -1696,8 +1864,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing Enhanced Datasource Connections", @@ -1707,7 +1875,7 @@ "uri":"dli_01_0623.html", "node_id":"dli_01_0623.xml", "product_code":"dli", - "code":"82", + "code":"90", "des":"After creating an enhanced datasource connection, you can view and manage it on the management console.This section describes how to view basic information about an enhan", "doc_type":"usermanual", "kw":"Viewing Basic Information About an Enhanced Datasource Connection,Managing Enhanced Datasource Conne", @@ -1717,8 +1885,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Viewing Basic Information About an Enhanced Datasource Connection", @@ -1728,7 +1896,7 @@ "uri":"dli_01_0018.html", "node_id":"dli_01_0018.xml", "product_code":"dli", - "code":"83", + "code":"91", "des":"Enhanced connections support user authorization by project. After authorization, users in the project have the permission to perform operations on the enhanced connection", "doc_type":"usermanual", "kw":"Enhanced Connection Permission Management,Managing Enhanced Datasource Connections,User Guide", @@ -1738,40 +1906,61 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Enhanced Connection Permission Management", "githuburl":"" }, { - "uri":"dli_01_0514.html", - "node_id":"dli_01_0514.xml", + "uri":"dli_01_0009.html", + "node_id":"dli_01_0009.xml", "product_code":"dli", - "code":"84", - "des":"Bind an elastic resource pool to a queue to connect the queue to a target data source. When an enhanced datasource connection is no longer needed, unbind the queue that w", + "code":"92", + "des":"To connect other resource pools to data sources through enhanced datasource connections, bind enhanced datasource connections to resource pools on the Enhanced tab page.T", "doc_type":"usermanual", - "kw":"Binding or Unbinding an Enhanced Datasource Connection to a Queue,Managing Enhanced Datasource Conne", + "kw":"Binding an Enhanced Datasource Connection to an Elastic Resource Pool,Managing Enhanced Datasource C", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Binding or Unbinding an Enhanced Datasource Connection to a Queue", + "title":"Binding an Enhanced Datasource Connection to an Elastic Resource Pool", + "githuburl":"" + }, + { + "uri":"dli_01_0555.html", + "node_id":"dli_01_0555.xml", + "product_code":"dli", + "code":"93", + "des":"Unbind an enhanced datasource connection from an elastic resource pool that does not need to access a data source through an enhanced datasoruce connection.If the status ", + "doc_type":"usermanual", + "kw":"Unbinding an Enhanced Datasource Connection from an Elastic Resource Pool,Managing Enhanced Datasour", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Unbinding an Enhanced Datasource Connection from an Elastic Resource Pool", "githuburl":"" }, { "uri":"dli_01_0014.html", "node_id":"dli_01_0014.xml", "product_code":"dli", - "code":"85", - "des":"A route is configured with the destination, next hop type, and next hop to determine where the network traffic is directed. Routes are classified into system routes and c", + "code":"94", + "des":"Enhanced datasource connections establish peering connections between DLI elastic resource pools and data sources to interconnect two VPC networks. If we liken these peer", "doc_type":"usermanual", "kw":"Adding a Route for an Enhanced Datasource Connection,Managing Enhanced Datasource Connections,User G", "search_title":"", @@ -1780,8 +1969,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Adding a Route for an Enhanced Datasource Connection", @@ -1791,8 +1980,8 @@ "uri":"dli_01_0556.html", "node_id":"dli_01_0556.xml", "product_code":"dli", - "code":"86", - "des":"Delete a route that is no longer used.A custom route table cannot be deleted if it is associated with a subnet.Log in to the DLI management console.In the left navigation", + "code":"95", + "des":"Delete a route that is no longer used.A custom route table cannot be deleted if it is associated with a subnet.Log in to the DLI management console.In the navigation pane", "doc_type":"usermanual", "kw":"Deleting the Route for an Enhanced Datasource Connection,Managing Enhanced Datasource Connections,Us", "search_title":"", @@ -1801,8 +1990,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Deleting the Route for an Enhanced Datasource Connection", @@ -1812,7 +2001,7 @@ "uri":"dli_01_0013.html", "node_id":"dli_01_0013.xml", "product_code":"dli", - "code":"87", + "code":"96", "des":"Host information is the mapping between host IP addresses and domain names. After you configure host information, jobs can only use the configured domain names to access ", "doc_type":"usermanual", "kw":"Modifying Host Information in an Elastic Resource Pool,Managing Enhanced Datasource Connections,User", @@ -1822,8 +2011,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Modifying Host Information in an Elastic Resource Pool", @@ -1833,8 +2022,8 @@ "uri":"dli_01_0019.html", "node_id":"dli_01_0019.xml", "product_code":"dli", - "code":"88", - "des":"A tag is a key-value pair customized by users and used to identify cloud resources. It helps users to classify and search for cloud resources. A tag consists of a tag key", + "code":"97", + "des":"A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value.If you use ", "doc_type":"usermanual", "kw":"Enhanced Datasource Connection Tag Management,Managing Enhanced Datasource Connections,User Guide", "search_title":"", @@ -1843,8 +2032,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Enhanced Datasource Connection Tag Management", @@ -1854,8 +2043,8 @@ "uri":"dli_01_0553.html", "node_id":"dli_01_0553.xml", "product_code":"dli", - "code":"89", - "des":"Delete an enhanced datasource connection that is no longer used on the console.Log in to the DLI management console.In the left navigation pane, choose Datasource Connect", + "code":"98", + "des":"Delete an enhanced datasource connection that is no longer used on the console.Log in to the DLI management console.In the navigation pane on the left, choose Datasource ", "doc_type":"usermanual", "kw":"Deleting an Enhanced Datasource Connection,Managing Enhanced Datasource Connections,User Guide", "search_title":"", @@ -1864,8 +2053,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Deleting an Enhanced Datasource Connection", @@ -1875,7 +2064,7 @@ "uri":"dli_01_0486.html", "node_id":"dli_01_0486.xml", "product_code":"dli", - "code":"90", + "code":"99", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Configuring an Agency to Allow DLI to Access Other Cloud Services", @@ -1885,8 +2074,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Configuring an Agency to Allow DLI to Access Other Cloud Services", @@ -1896,7 +2085,7 @@ "uri":"dli_01_0419.html", "node_id":"dli_01_0419.xml", "product_code":"dli", - "code":"91", + "code":"100", "des":"Cloud services often interact with each other, with some of which dependent on other services. You can create an agency to delegate DLI to use other cloud services and pe", "doc_type":"usermanual", "kw":"DLI Agency Overview,Configuring an Agency to Allow DLI to Access Other Cloud Services,User Guide", @@ -1906,8 +2095,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"DLI Agency Overview", @@ -1917,7 +2106,7 @@ "uri":"dli_01_0616.html", "node_id":"dli_01_0616.xml", "product_code":"dli", - "code":"92", + "code":"101", "des":"When Flink 1.15, Spark 3.3, or a later version is used to execute jobs and the required agency is not included in the DLI system agency dli_management_agency, you need to", "doc_type":"usermanual", "kw":"Creating a Custom DLI Agency,Configuring an Agency to Allow DLI to Access Other Cloud Services,User ", @@ -1927,8 +2116,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating a Custom DLI Agency", @@ -1938,7 +2127,7 @@ "uri":"dli_01_0617.html", "node_id":"dli_01_0617.xml", "product_code":"dli", - "code":"93", + "code":"102", "des":"This section provides agency permission policies for common scenarios, which can be used to configure agency permission policies when you customize your permissions. The ", "doc_type":"usermanual", "kw":"Agency Permission Policies in Common Scenarios,Configuring an Agency to Allow DLI to Access Other Cl", @@ -1948,8 +2137,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Agency Permission Policies in Common Scenarios", @@ -1959,39 +2148,39 @@ "uri":"dli_01_0402.html", "node_id":"dli_01_0402.xml", "product_code":"dli", - "code":"94", + "code":"103", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Submitting a SQL Job Using DLI", + "kw":"Submitting a SQL Job on the DLI Management Console", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Submitting a SQL Job Using DLI", + "title":"Submitting a SQL Job on the DLI Management Console", "githuburl":"" }, { "uri":"dli_01_0320.html", "node_id":"dli_01_0320.xml", "product_code":"dli", - "code":"95", - "des":"The SQL Editor allows you to execute data query operations using SQL statements.It supports SQL:2003 and is compatible with Spark SQL.To access the SQL editor, choose SQL", + "code":"104", + "des":"DLI offers a SQL editor for executing data query operations using SQL statements.This section describes how to create and submit a SQL job using the DLI SQL editor.Before", "doc_type":"usermanual", - "kw":"Creating and Submitting a SQL Job,Submitting a SQL Job Using DLI,User Guide", + "kw":"Creating and Submitting a SQL Job,Submitting a SQL Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating and Submitting a SQL Job", @@ -2001,39 +2190,60 @@ "uri":"dli_01_0621.html", "node_id":"dli_01_0621.xml", "product_code":"dli", - "code":"96", + "code":"105", "des":"Store the data results of analyzed SQL jobs in a specified location in the desired format.By default, DLI stores SQL job results in its job bucket. You can also download ", "doc_type":"usermanual", - "kw":"Exporting SQL Job Results,Submitting a SQL Job Using DLI,User Guide", + "kw":"Exporting SQL Job Results,Submitting a SQL Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Exporting SQL Job Results", "githuburl":"" }, { - "uri":"dli_01_0535.html", - "node_id":"dli_01_0535.xml", + "uri":"dli_01_0612.html", + "node_id":"dli_01_0612.xml", "product_code":"dli", - "code":"97", - "des":"In actual job running, it is necessary to prioritize and ensure the normal running of important and urgent tasks due to their varying levels of importance and urgency. Th", + "code":"106", + "des":"There are numerous SQL engines in the big data field, which bring diversity to the solutions but also expose some issues such as varying quality of SQL input statements, ", "doc_type":"usermanual", - "kw":"Setting the Priority for a SQL Job,Submitting a SQL Job Using DLI,User Guide", + "kw":"Creating a SQL Inspection Rule,Submitting a SQL Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Creating a SQL Inspection Rule", + "githuburl":"" + }, + { + "uri":"dli_01_0535.html", + "node_id":"dli_01_0535.xml", + "product_code":"dli", + "code":"107", + "des":"In actual job running, it is necessary to prioritize and ensure the normal running of important and urgent tasks due to their varying levels of importance and urgency. Th", + "doc_type":"usermanual", + "kw":"Setting the Priority for a SQL Job,Submitting a SQL Job on the DLI Management Console,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Setting the Priority for a SQL Job", @@ -2043,18 +2253,18 @@ "uri":"dli_01_0637.html", "node_id":"dli_01_0637.xml", "product_code":"dli", - "code":"98", + "code":"108", "des":"DLI job buckets are used to store temporary data generated during DLI job running, such as job logs and results.This section describes how to configure a bucket for DLI j", "doc_type":"usermanual", - "kw":"Querying Logs for SQL Jobs,Submitting a SQL Job Using DLI,User Guide", + "kw":"Querying Logs for SQL Jobs,Submitting a SQL Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Querying Logs for SQL Jobs", @@ -2064,18 +2274,18 @@ "uri":"dli_01_0017.html", "node_id":"dli_01_0017.xml", "product_code":"dli", - "code":"99", + "code":"109", "des":"The SQL Jobs page displays all SQL jobs, which may span multiple pages if there are many jobs. You can navigate to a specific page as needed. DLI allows you to view jobs ", "doc_type":"usermanual", - "kw":"Managing SQL Jobs,Submitting a SQL Job Using DLI,User Guide", + "kw":"Managing SQL Jobs,Submitting a SQL Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing SQL Jobs", @@ -2085,18 +2295,18 @@ "uri":"dli_01_0638.html", "node_id":"dli_01_0638.xml", "product_code":"dli", - "code":"100", + "code":"110", "des":"A SQL execution plan is a logical flowchart of a database query that shows how a database management system executes a specific SQL query. The execution plan details the ", "doc_type":"usermanual", - "kw":"Viewing a SQL Execution Plan,Submitting a SQL Job Using DLI,User Guide", + "kw":"Viewing a SQL Execution Plan,Submitting a SQL Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Viewing a SQL Execution Plan", @@ -2106,7 +2316,7 @@ "uri":"dli_01_05110.html", "node_id":"dli_01_05110.xml", "product_code":"dli", - "code":"101", + "code":"111", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Creating and Managing SQL Job Templates", @@ -2116,8 +2326,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating and Managing SQL Job Templates", @@ -2127,8 +2337,8 @@ "uri":"dli_01_0021.html", "node_id":"dli_01_0021.xml", "product_code":"dli", - "code":"102", - "des":"To facilitate SQL operation execution, DLI allows you to customize query templates or save the SQL statements in use as templates. After templates are saved, you do not n", + "code":"112", + "des":"DLI allows you to create custom templates or save currently used SQL statements as templates for quick and convenient SQL operations. Once a template is saved, you can ex", "doc_type":"usermanual", "kw":"Creating a SQL Job Template,Creating and Managing SQL Job Templates,User Guide", "search_title":"", @@ -2137,8 +2347,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating a SQL Job Template", @@ -2148,7 +2358,7 @@ "uri":"dli_01_0639.html", "node_id":"dli_01_0639.xml", "product_code":"dli", - "code":"103", + "code":"113", "des":"DLI allows you to create custom templates or save currently used SQL statements as templates for quick and convenient SQL operations. Once a template is saved, you can ex", "doc_type":"usermanual", "kw":"Developing and Submitting a SQL Job Using a SQL Job Template,Creating and Managing SQL Job Templates", @@ -2158,8 +2368,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Developing and Submitting a SQL Job Using a SQL Job Template", @@ -2169,7 +2379,7 @@ "uri":"dli_01_05111.html", "node_id":"dli_01_05111.xml", "product_code":"dli", - "code":"104", + "code":"114", "des":"TPC-H is a test set developed by the Transaction Processing Performance Council (TPC) to simulate decision-making support applications. It is widely used in academia and ", "doc_type":"usermanual", "kw":"TPC-H Sample Data in the SQL Templates Preset on DLI,Creating and Managing SQL Job Templates,User Gu", @@ -2179,8 +2389,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"TPC-H Sample Data in the SQL Templates Preset on DLI", @@ -2190,39 +2400,39 @@ "uri":"dli_01_0389.html", "node_id":"dli_01_0389.xml", "product_code":"dli", - "code":"105", + "code":"115", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Submitting a Flink Job Using DLI", + "kw":"Submitting a Flink Job on the DLI Management Console", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Submitting a Flink Job Using DLI", + "title":"Submitting a Flink Job on the DLI Management Console", "githuburl":"" }, { "uri":"dli_01_0403.html", "node_id":"dli_01_0403.xml", "product_code":"dli", - "code":"106", + "code":"116", "des":"DLI supports two types of Flink jobs:Flink OpenSource SQL job:It is fully compatible with Flink of the community edition, ensuring that jobs can run smoothly on these Fli", "doc_type":"usermanual", - "kw":"Flink Job Overview,Submitting a Flink Job Using DLI,User Guide", + "kw":"Flink Job Overview,Submitting a Flink Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Flink Job Overview", @@ -2232,18 +2442,18 @@ "uri":"dli_01_0498.html", "node_id":"dli_01_0498.xml", "product_code":"dli", - "code":"107", + "code":"117", "des":"This section describes how to create a Flink OpenSource SQL job.DLI Flink OpenSource SQL jobs are fully compatible with the syntax of Flink provided by the community. In ", "doc_type":"usermanual", - "kw":"Creating a Flink OpenSource SQL Job,Submitting a Flink Job Using DLI,User Guide", + "kw":"Creating a Flink OpenSource SQL Job,Submitting a Flink Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating a Flink OpenSource SQL Job", @@ -2253,18 +2463,18 @@ "uri":"dli_01_0457.html", "node_id":"dli_01_0457.xml", "product_code":"dli", - "code":"108", + "code":"118", "des":"A Flink Jar job involves developing a custom application Jar package based on Flink's capabilities and submitting it to a DLI queue for execution.To create a Flink Jar jo", "doc_type":"usermanual", - "kw":"Creating a Flink Jar Job,Submitting a Flink Job Using DLI,User Guide", + "kw":"Creating a Flink Jar Job,Submitting a Flink Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating a Flink Jar Job", @@ -2274,18 +2484,18 @@ "uri":"dli_01_0479.html", "node_id":"dli_01_0479.xml", "product_code":"dli", - "code":"109", + "code":"119", "des":"You can isolate Flink jobs allocated to different users by setting permissions to ensure data query performance.The administrator and job creator have all permissions, wh", "doc_type":"usermanual", - "kw":"Configuring Flink Job Permissions,Submitting a Flink Job Using DLI,User Guide", + "kw":"Configuring Flink Job Permissions,Submitting a Flink Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Configuring Flink Job Permissions", @@ -2295,7 +2505,7 @@ "uri":"dli_01_0377.html", "node_id":"dli_01_0377.xml", "product_code":"dli", - "code":"110", + "code":"120", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Flink Jobs", @@ -2305,8 +2515,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing Flink Jobs", @@ -2316,7 +2526,7 @@ "uri":"dli_01_0462.html", "node_id":"dli_01_0462.xml", "product_code":"dli", - "code":"111", + "code":"121", "des":"After creating a Flink job, you can check the basic information, job details, task list, and execution plan of the job on the DLI console.This section describes how to ch", "doc_type":"usermanual", "kw":"Viewing Flink Job Details,Managing Flink Jobs,User Guide", @@ -2326,8 +2536,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Viewing Flink Job Details", @@ -2337,7 +2547,7 @@ "uri":"dli_01_0650.html", "node_id":"dli_01_0650.xml", "product_code":"dli", - "code":"112", + "code":"122", "des":"In actual job running, it is necessary to prioritize and ensure the normal running of important and urgent tasks due to their varying levels of importance and urgency. Th", "doc_type":"usermanual", "kw":"Setting the Priority for a Flink Job,Managing Flink Jobs,User Guide", @@ -2347,8 +2557,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Setting the Priority for a Flink Job", @@ -2358,7 +2568,7 @@ "uri":"dli_01_0534.html", "node_id":"dli_01_0534.xml", "product_code":"dli", - "code":"113", + "code":"123", "des":"In actual job operations, the compute resources required by a job vary depending on the data volume. As a result, compute resources are wasted when the volume is small an", "doc_type":"usermanual", "kw":"Enabling Dynamic Scaling for Flink Jobs,Managing Flink Jobs,User Guide", @@ -2368,8 +2578,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Enabling Dynamic Scaling for Flink Jobs", @@ -2379,7 +2589,7 @@ "uri":"dli_01_0651.html", "node_id":"dli_01_0651.xml", "product_code":"dli", - "code":"114", + "code":"124", "des":"DLI job buckets are used to store temporary data generated during DLI job running, such as job logs and results.This section describes how to configure a bucket for DLI j", "doc_type":"usermanual", "kw":"Querying Logs for Flink Jobs,Managing Flink Jobs,User Guide", @@ -2389,8 +2599,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Querying Logs for Flink Jobs", @@ -2400,7 +2610,7 @@ "uri":"dli_01_0461.html", "node_id":"dli_01_0461.xml", "product_code":"dli", - "code":"115", + "code":"125", "des":"After creating a job, you can manage it by performing various operations such as editing its basic information, starting or stopping it, and importing or exporting it.You", "doc_type":"usermanual", "kw":"Common Operations of Flink Jobs,Managing Flink Jobs,User Guide", @@ -2410,8 +2620,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Common Operations of Flink Jobs", @@ -2421,18 +2631,18 @@ "uri":"dli_01_0464.html", "node_id":"dli_01_0464.xml", "product_code":"dli", - "code":"116", + "code":"126", "des":"Flink templates include sample templates and custom templates. You can modify an existing sample template to meet the actual job logic requirements and save time for edit", "doc_type":"usermanual", - "kw":"Managing Flink Job Templates,Submitting a Flink Job Using DLI,User Guide", + "kw":"Managing Flink Job Templates,Submitting a Flink Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing Flink Job Templates", @@ -2442,18 +2652,18 @@ "uri":"dli_01_0463.html", "node_id":"dli_01_0463.xml", "product_code":"dli", - "code":"117", - "des":"A tag is a key-value pair customized by users and used to identify cloud resources. It helps users to classify and search for cloud resources. A tag consists of a tag key", + "code":"127", + "des":"A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value.DLI allows ", "doc_type":"usermanual", - "kw":"Adding Tags to a Flink Job,Submitting a Flink Job Using DLI,User Guide", + "kw":"Adding Tags to a Flink Job,Submitting a Flink Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Adding Tags to a Flink Job", @@ -2463,39 +2673,39 @@ "uri":"dli_01_0465.html", "node_id":"dli_01_0465.xml", "product_code":"dli", - "code":"118", + "code":"128", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Submitting a Spark Job Using DLI", + "kw":"Submitting a Spark Job on the DLI Management Console", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Submitting a Spark Job Using DLI", + "title":"Submitting a Spark Job on the DLI Management Console", "githuburl":"" }, { "uri":"dli_01_0384.html", "node_id":"dli_01_0384.xml", "product_code":"dli", - "code":"119", - "des":"DLI provides fully-managed Spark computing services by allowing you to execute Spark jobs.On the Overview page, click Create Job in the upper right corner of the Spark Jo", + "code":"129", + "des":"DLI Spark jobs provide fully managed Spark computing services.On the Overview page, click Create Job in the upper right corner of the Spark Jobs tab or click Create Job i", "doc_type":"usermanual", - "kw":"Creating a Spark Job,Submitting a Spark Job Using DLI,User Guide", + "kw":"Creating a Spark Job,Submitting a Spark Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating a Spark Job", @@ -2505,18 +2715,18 @@ "uri":"dli_01_0652.html", "node_id":"dli_01_0652.xml", "product_code":"dli", - "code":"120", + "code":"130", "des":"In actual job running, it is necessary to prioritize and ensure the normal running of important and urgent tasks due to their varying levels of importance and urgency. Th", "doc_type":"usermanual", - "kw":"Setting the Priority for a Spark Job,Submitting a Spark Job Using DLI,User Guide", + "kw":"Setting the Priority for a Spark Job,Submitting a Spark Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Setting the Priority for a Spark Job", @@ -2526,18 +2736,18 @@ "uri":"dli_01_0379.html", "node_id":"dli_01_0379.xml", "product_code":"dli", - "code":"121", + "code":"131", "des":"DLI job buckets are used to store temporary data generated during DLI job running, such as job logs and results.This section describes how to configure a bucket for DLI j", "doc_type":"usermanual", - "kw":"Querying Logs for Spark Jobs,Submitting a Spark Job Using DLI,User Guide", + "kw":"Querying Logs for Spark Jobs,Submitting a Spark Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Querying Logs for Spark Jobs", @@ -2547,18 +2757,18 @@ "uri":"dli_01_0385.html", "node_id":"dli_01_0385.xml", "product_code":"dli", - "code":"122", + "code":"132", "des":"On the Overview page, click Spark Jobs to go to the SQL job management page. Alternatively, you can click Job Management > Spark Jobs. The page displays all Spark jobs. I", "doc_type":"usermanual", - "kw":"Managing Spark Jobs,Submitting a Spark Job Using DLI,User Guide", + "kw":"Managing Spark Jobs,Submitting a Spark Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing Spark Jobs", @@ -2568,18 +2778,18 @@ "uri":"dli_01_0551.html", "node_id":"dli_01_0551.xml", "product_code":"dli", - "code":"123", + "code":"133", "des":"You can modify a sample template to meet the Spark job requirements, saving time for editing SQL statements.Currently, the cloud platform does not provide preset Spark te", "doc_type":"usermanual", - "kw":"Managing Spark Job Templates,Submitting a Spark Job Using DLI,User Guide", + "kw":"Managing Spark Job Templates,Submitting a Spark Job on the DLI Management Console,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing Spark Job Templates", @@ -2589,112 +2799,28 @@ "uri":"dli_01_0445.html", "node_id":"dli_01_0445.xml", "product_code":"dli", - "code":"124", + "code":"134", "des":"This section describes metrics reported by DLI to Cloud Eye as well as their namespaces and dimensions. You can use the management console or APIs provided by Cloud Eye t", "doc_type":"usermanual", - "kw":"Using Cloud Eye to Monitor DLI,User Guide", + "kw":"Monitoring DLI Using Cloud Eye,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" - } - ], - "title":"Using Cloud Eye to Monitor DLI", - "githuburl":"" - }, - { - "uri":"dli_01_0664.html", - "node_id":"dli_01_0664.xml", - "product_code":"dli", - "code":"125", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"usermanual", - "kw":"Using AOM to Monitor DLI", - "search_title":"", - "metedata":[ - { - "prodname":"dli", - "opensource":"true", - "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" - } - ], - "title":"Using AOM to Monitor DLI", - "githuburl":"" - }, - { - "uri":"dli_01_0665.html", - "node_id":"dli_01_0665.xml", - "product_code":"dli", - "code":"126", - "des":"AOM's Prometheus Monitoring is a comprehensive solution that integrates with the open source Prometheus ecosystem. It supports monitoring of various types of components, ", - "doc_type":"usermanual", - "kw":"Connecting DLI to AOM's Prometheus Monitoring,Using AOM to Monitor DLI,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"dli", "IsMulti":"No;Yes;NO", - "IsBot":"No;Yes", - "opensource":"true", - "documenttype":"usermanual" + "IsBot":"No;Yes" } ], - "title":"Connecting DLI to AOM's Prometheus Monitoring", - "githuburl":"" - }, - { - "uri":"dli_01_0666.html", - "node_id":"dli_01_0666.xml", - "product_code":"dli", - "code":"127", - "des":"When connecting DLI to AOM's Prometheus Monitoring, the system automatically configures the parameters listed in table 1 in Configuration Items for Connecting DLI to AOM'", - "doc_type":"usermanual", - "kw":"Configuration Items for Connecting DLI to AOM's Prometheus Monitoring,Using AOM to Monitor DLI,User ", - "search_title":"", - "metedata":[ - { - "prodname":"dli", - "IsMulti":"No;Yes;NO", - "IsBot":"No;Yes", - "opensource":"true", - "documenttype":"usermanual" - } - ], - "title":"Configuration Items for Connecting DLI to AOM's Prometheus Monitoring", - "githuburl":"" - }, - { - "uri":"dli_01_0667.html", - "node_id":"dli_01_0667.xml", - "product_code":"dli", - "code":"128", - "des":"Table 1 lists the basic monitoring metrics that are reported by DLI to Prometheus. AOM Prometheus can store these basic metrics for free.", - "doc_type":"usermanual", - "kw":"Basic Monitoring Metrics Reported by DLI to Prometheus,Using AOM to Monitor DLI,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"dli", - "opensource":"true", - "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" - } - ], - "title":"Basic Monitoring Metrics Reported by DLI to Prometheus", + "title":"Monitoring DLI Using Cloud Eye", "githuburl":"" }, { "uri":"dli_01_0318.html", "node_id":"dli_01_0318.xml", "product_code":"dli", - "code":"129", + "code":"135", "des":"With CTS, you can log operations related to DLI, making it easier to search, audit, and trace in the future.", "doc_type":"usermanual", "kw":"Using CTS to Audit DLI,User Guide", @@ -2704,8 +2830,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Using CTS to Audit DLI", @@ -2715,133 +2841,259 @@ "uri":"dli_01_0408.html", "node_id":"dli_01_0408.xml", "product_code":"dli", - "code":"130", + "code":"136", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Permissions Management", + "kw":"DLI Permission Management", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Permissions Management", + "title":"DLI Permission Management", "githuburl":"" }, { "uri":"dli_01_0440.html", "node_id":"dli_01_0440.xml", "product_code":"dli", - "code":"131", - "des":"DLI has a comprehensive permission control mechanism and supports fine-grained authentication through Identity and Access Management (IAM). You can create policies in IAM", + "code":"137", + "des":"DLI features two sets of permission systems. These two permission control mechanisms are used in conjunction, with their permissions overlapping and complementing each ot", "doc_type":"usermanual", - "kw":"Overview,Permissions Management,User Guide", + "kw":"Overview of the DLI Permission System,DLI Permission Management,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Overview of the DLI Permission System", + "githuburl":"" + }, + { + "uri":"dli_01_0689.html", + "node_id":"dli_01_0689.xml", + "product_code":"dli", + "code":"138", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"DLI Permission Management", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"DLI Permission Management", + "githuburl":"" + }, + { + "uri":"dli_01_0690.html", + "node_id":"dli_01_0690.xml", + "product_code":"dli", + "code":"139", + "des":"The permission management function of DLI itself primarily applies to the permission control of internal DLI resources, rather than relying on the unified identity authen", + "doc_type":"usermanual", + "kw":"Overview,DLI Permission Management,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Overview", "githuburl":"" }, { - "uri":"dli_01_0451.html", - "node_id":"dli_01_0451.xml", + "uri":"dli_01_0691.html", + "node_id":"dli_01_0691.xml", "product_code":"dli", - "code":"132", - "des":"Custom policies can be created as a supplement to the system policies of DLI. You can add actions to custom policies. For the actions supported for custom policies, see \"", + "code":"140", + "des":"For details about authorization through the DLI console, see Managing Permissions.For details about authorization through the DLI console, see Queue Permission Management", "doc_type":"usermanual", - "kw":"Creating a Custom Policy,Permissions Management,User Guide", + "kw":"DLI Permissions,DLI Permission Management,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Creating a Custom Policy", + "title":"DLI Permissions", "githuburl":"" }, { - "uri":"dli_01_0417.html", - "node_id":"dli_01_0417.xml", + "uri":"dli_01_0692.html", + "node_id":"dli_01_0692.xml", "product_code":"dli", - "code":"133", - "des":"A resource is an object that exists within a service. You can select DLI resources by specifying their paths.", + "code":"141", + "des":"This section describes how to authorize resources on the DLI console.", "doc_type":"usermanual", - "kw":"DLI Resources,Permissions Management,User Guide", + "kw":"DLI Authorization Operation Guide,DLI Permission Management,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"DLI Resources", + "title":"DLI Authorization Operation Guide", "githuburl":"" }, { "uri":"dli_01_0475.html", "node_id":"dli_01_0475.xml", "product_code":"dli", - "code":"134", - "des":"Request conditions are useful in determining when a custom policy takes effect. A request condition consists of a condition key and operator. Condition keys are either gl", + "code":"142", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"DLI Request Conditions,Permissions Management,User Guide", + "kw":"IAM Permission Management", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"DLI Request Conditions", + "title":"IAM Permission Management", + "githuburl":"" + }, + { + "uri":"dli_01_0417.html", + "node_id":"dli_01_0417.xml", + "product_code":"dli", + "code":"143", + "des":"IAM is a foundational service for permission management, offering functions like user identity authentication, permission allocation, and access control, enabling you to ", + "doc_type":"usermanual", + "kw":"Overview,IAM Permission Management,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Overview", + "githuburl":"" + }, + { + "uri":"dli_01_0693.html", + "node_id":"dli_01_0693.xml", + "product_code":"dli", + "code":"144", + "des":"In IAM, authorization entities are primarily categorized into users and user groups. Integration with enterprise projects enables resource isolation by group and facilita", + "doc_type":"usermanual", + "kw":"IAM Authorization Entity,IAM Permission Management,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"IAM Authorization Entity", "githuburl":"" }, { "uri":"dli_01_0441.html", "node_id":"dli_01_0441.xml", "product_code":"dli", - "code":"135", - "des":"Table 1 lists the common operations supported by each system policy of DLI. Choose proper system policies according to this table. For details about the SQL statement per", + "code":"145", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Common Operations Supported by DLI System Policy,Permissions Management,User Guide", + "kw":"IAM Permissions,IAM Permission Management,User Guide", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Common Operations Supported by DLI System Policy", + "title":"IAM Permissions", + "githuburl":"" + }, + { + "uri":"dli_01_0451.html", + "node_id":"dli_01_0451.xml", + "product_code":"dli", + "code":"146", + "des":"The role/policy-based authorization model provided by Identity and Access Management (IAM) lets you control access to DLI resources. With IAM, you can:Based on the organi", + "doc_type":"usermanual", + "kw":"Using IAM Roles or Policies to Grant Access to DLI,IAM Permission Management,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Using IAM Roles or Policies to Grant Access to DLI", + "githuburl":"" + }, + { + "uri":"dli_01_0695.html", + "node_id":"dli_01_0695.xml", + "product_code":"dli", + "code":"147", + "des":"An e-commerce company conducts data analysis operations in region A. The marketing department's employees, user 1 and user 2, along with the technical department's employ", + "doc_type":"usermanual", + "kw":"Example Use Case: Creating a User Group and Granting Permissions for Using DLI Elastic Resource Pool", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" + } + ], + "title":"Example Use Case: Creating a User Group and Granting Permissions for Using DLI Elastic Resource Pools and Databases", "githuburl":"" }, { "uri":"dli_01_0567.html", "node_id":"dli_01_0567.xml", "product_code":"dli", - "code":"136", + "code":"148", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Common DLI Management Operations", @@ -2851,8 +3103,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Common DLI Management Operations", @@ -2862,28 +3114,28 @@ "uri":"dli_01_0494.html", "node_id":"dli_01_0494.xml", "product_code":"dli", - "code":"137", + "code":"149", "des":"To enhance the functions and performance of Spark and Flink jobs, you can create custom images by downloading the base images provided by DLI and adding dependencies (fil", "doc_type":"usermanual", - "kw":"Using a Custom Image to Enhance the Job Running Environment,Common DLI Management Operations,User Gu", + "kw":"Enhancing the Job Runtime Environment Using a Custom Image,Common DLI Management Operations,User Gui", "search_title":"", "metedata":[ { "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], - "title":"Using a Custom Image to Enhance the Job Running Environment", + "title":"Enhancing the Job Runtime Environment Using a Custom Image", "githuburl":"" }, { "uri":"dli_01_0476.html", "node_id":"dli_01_0476.xml", "product_code":"dli", - "code":"138", + "code":"150", "des":"DLI allows you to set variables that are frequently used during job development as global variables on the DLI management console. This avoids repeated definitions during", "doc_type":"usermanual", "kw":"Managing DLI Global Variables,Common DLI Management Operations,User Guide", @@ -2893,8 +3145,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing DLI Global Variables", @@ -2904,7 +3156,7 @@ "uri":"dli_01_0366.html", "node_id":"dli_01_0366.xml", "product_code":"dli", - "code":"139", + "code":"151", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Program Packages of Jar Jobs", @@ -2914,8 +3166,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing Program Packages of Jar Jobs", @@ -2925,7 +3177,7 @@ "uri":"dli_01_0407.html", "node_id":"dli_01_0407.xml", "product_code":"dli", - "code":"140", + "code":"152", "des":"Before running DLI jobs, UDF JAR files or Jar job packages need to be uploaded to the cloud platform for unified management and maintenance.There are two ways to manage p", "doc_type":"usermanual", "kw":"Package Management Overview,Managing Program Packages of Jar Jobs,User Guide", @@ -2935,8 +3187,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Package Management Overview", @@ -2946,7 +3198,7 @@ "uri":"dli_01_0367.html", "node_id":"dli_01_0367.xml", "product_code":"dli", - "code":"141", + "code":"153", "des":"DLI allows you to submit program packages in batches to the general-use queue for running.If you need to update a package, you can use the same package or file to upload ", "doc_type":"usermanual", "kw":"Creating a DLI Package,Managing Program Packages of Jar Jobs,User Guide", @@ -2956,8 +3208,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Creating a DLI Package", @@ -2967,7 +3219,7 @@ "uri":"dli_01_0477.html", "node_id":"dli_01_0477.xml", "product_code":"dli", - "code":"142", + "code":"154", "des":"By configuring permissions, you can grant different package groups or packages to various users, ensuring that job efficiency remains unaffected and job performance is ma", "doc_type":"usermanual", "kw":"Configuring DLI Package Permissions,Managing Program Packages of Jar Jobs,User Guide", @@ -2977,8 +3229,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Configuring DLI Package Permissions", @@ -2988,7 +3240,7 @@ "uri":"dli_01_0478.html", "node_id":"dli_01_0478.xml", "product_code":"dli", - "code":"143", + "code":"155", "des":"DLI allows you to change the owner of a package group or package.Log in to the DLI management console and choose Data Management > Package Management.On the Package Manag", "doc_type":"usermanual", "kw":"Changing the DLI Package Owner,Managing Program Packages of Jar Jobs,User Guide", @@ -2998,8 +3250,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Changing the DLI Package Owner", @@ -3009,7 +3261,7 @@ "uri":"dli_01_0369.html", "node_id":"dli_01_0369.xml", "product_code":"dli", - "code":"144", + "code":"156", "des":"Tags are key-value pairs that you can define to identify cloud resources. They assist you in categorizing and searching for cloud resources. A tag consists of a key and a", "doc_type":"usermanual", "kw":"Managing DLI Package Tags,Managing Program Packages of Jar Jobs,User Guide", @@ -3019,8 +3271,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing DLI Package Tags", @@ -3030,7 +3282,7 @@ "uri":"dli_01_0397.html", "node_id":"dli_01_0397.xml", "product_code":"dli", - "code":"145", + "code":"157", "des":"DLI built-in dependencies are provided by the platform by default. In case of conflicts, you do not need to upload them when packaging JAR packages of Spark or Flink Jar ", "doc_type":"usermanual", "kw":"DLI Built-in Dependencies,Managing Program Packages of Jar Jobs,User Guide", @@ -3040,8 +3292,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"DLI Built-in Dependencies", @@ -3051,7 +3303,7 @@ "uri":"dli_01_0550.html", "node_id":"dli_01_0550.xml", "product_code":"dli", - "code":"146", + "code":"158", "des":"A quota limits the quantity of a resource available to users, thereby preventing spikes in the usage of the resource.You can also request for an increased quota if your e", "doc_type":"usermanual", "kw":"Managing DLI Resource Quotas,Common DLI Management Operations,User Guide", @@ -3061,8 +3313,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Managing DLI Resource Quotas", @@ -3072,7 +3324,7 @@ "uri":"dli_01_0539.html", "node_id":"dli_01_0539.xml", "product_code":"dli", - "code":"147", + "code":"159", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"FAQ", @@ -3082,8 +3334,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"FAQ", @@ -3093,7 +3345,7 @@ "uri":"dli_03_0001.html", "node_id":"dli_03_0001.xml", "product_code":"dli", - "code":"148", + "code":"160", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"DLI Basics", @@ -3113,7 +3365,7 @@ "uri":"dli_03_0115.html", "node_id":"dli_03_0115.xml", "product_code":"dli", - "code":"149", + "code":"161", "des":"Both DLI and MRS support Spark, but there are some differences in service mode, interface, application scenarios, and performance characteristics.The Spark component of D", "doc_type":"usermanual", "kw":"What Are the Differences Between MRS Spark and DLI Spark?,DLI Basics,User Guide", @@ -3133,7 +3385,7 @@ "uri":"dli_03_0029.html", "node_id":"dli_03_0029.xml", "product_code":"dli", - "code":"150", + "code":"162", "des":"Supported data formats:ParquetCSVORCJSONAvroOBS: Data used by SQL jobs, Spark jobs, and Flink jobs can be stored in OBS, reducing storage costs.DLI: The column-based Parq", "doc_type":"usermanual", "kw":"Where Can Data Be Stored in DLI?,DLI Basics,User Guide", @@ -3153,7 +3405,7 @@ "uri":"dli_03_0129.html", "node_id":"dli_03_0129.xml", "product_code":"dli", - "code":"151", + "code":"163", "des":"DLI supports importing data from OBS buckets shared by IAM users under the same tenant, but not from OBS buckets shared by other tenants.This ensures data security and is", "doc_type":"usermanual", "kw":"Can I Import OBS Bucket Data Shared by Other Tenants into DLI?,DLI Basics,User Guide", @@ -3173,7 +3425,7 @@ "uri":"dli_03_0263.html", "node_id":"dli_03_0263.xml", "product_code":"dli", - "code":"152", + "code":"164", "des":"No, a global variable can only be used by the user who created it. Global variables can be used to simplify complex parameters. For example, long and difficult variables ", "doc_type":"usermanual", "kw":"Can a Member Account Use Global Variables Created by Other Member Accounts?,DLI Basics,User Guide", @@ -3193,7 +3445,7 @@ "uri":"dli_03_0260.html", "node_id":"dli_03_0260.xml", "product_code":"dli", - "code":"153", + "code":"165", "des":"No.The spark.acls.enable configuration item is not used in DLI. The Apache Spark command injection vulnerability (CVE-2022-33891) does not exist in DLI.This vulnerability", "doc_type":"usermanual", "kw":"Is DLI Affected by the Apache Spark Command Injection Vulnerability (CVE-2022-33891)?,DLI Basics,Use", @@ -3213,7 +3465,7 @@ "uri":"dli_03_0126.html", "node_id":"dli_03_0126.xml", "product_code":"dli", - "code":"154", + "code":"166", "des":"To manage a large number of DLI jobs, you can use the following methods:Manage jobs by group.Group tens of thousands of jobs by type and run each group on a queue.Group t", "doc_type":"usermanual", "kw":"How Do I Manage Jobs Running on DLI?,DLI Basics,User Guide", @@ -3233,7 +3485,7 @@ "uri":"dli_03_0162.html", "node_id":"dli_03_0162.xml", "product_code":"dli", - "code":"155", + "code":"167", "des":"DLI does not support directly changing the field names of a table. However, you can solve this issue by migrating the table data using the following steps:Create a table:", "doc_type":"usermanual", "kw":"How Do I Change the Field Names of an Existing Table on DLI?,DLI Basics,User Guide", @@ -3253,7 +3505,7 @@ "uri":"dli_03_0049.html", "node_id":"dli_03_0049.xml", "product_code":"dli", - "code":"156", + "code":"168", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"DLI Elastic Resource Pools and Queues", @@ -3273,7 +3525,7 @@ "uri":"dli_03_0276.html", "node_id":"dli_03_0276.xml", "product_code":"dli", - "code":"157", + "code":"169", "des":"In daily big data analysis work, it is important to allocate and manage compute resources properly to provide a good job execution environment.You can allocate resources ", "doc_type":"usermanual", "kw":"How Can I Check the Actual and Used CUs for an Elastic Resource Pool as Well as the Required CUs for", @@ -3293,7 +3545,7 @@ "uri":"dli_03_0183.html", "node_id":"dli_03_0183.xml", "product_code":"dli", - "code":"158", + "code":"170", "des":"You need to check the large number of jobs in the Submitting and Running states on the queue.Use Cloud Eye to view jobs in different states on the queue. The procedure is", "doc_type":"usermanual", "kw":"How Do I Check for a Backlog of Jobs in the Current DLI Queue?,DLI Elastic Resource Pools and Queues", @@ -3313,7 +3565,7 @@ "uri":"dli_03_0095.html", "node_id":"dli_03_0095.xml", "product_code":"dli", - "code":"159", + "code":"171", "des":"To check the running status of the DLI queue and determine whether to run more jobs on that queue, you need to check the queue load.Search for Cloud Eye on the console.In", "doc_type":"usermanual", "kw":"How Do I View the Load of a DLI Queue?,DLI Elastic Resource Pools and Queues,User Guide", @@ -3333,7 +3585,7 @@ "uri":"dli_03_0098.html", "node_id":"dli_03_0098.xml", "product_code":"dli", - "code":"160", + "code":"172", "des":"DLI allows you to subscribe to an SMN topic for failed jobs.Log in to the DLI console.In the navigation pane on the left, choose Queue Management.On the Queue Management ", "doc_type":"usermanual", "kw":"How Do I Monitor Job Exceptions on a DLI Queue?,DLI Elastic Resource Pools and Queues,User Guide", @@ -3353,7 +3605,7 @@ "uri":"dli_03_0065.html", "node_id":"dli_03_0065.xml", "product_code":"dli", - "code":"161", + "code":"173", "des":"Currently, DLI provides two types of queues, For SQL and For general use. SQL queues are used to run SQL jobs. General-use queues are compatible with Spark queues of earl", "doc_type":"usermanual", "kw":"How Do I Migrate an Old Version Spark Queue to a General-Purpose Queue?,DLI Elastic Resource Pools a", @@ -3373,7 +3625,7 @@ "uri":"dli_03_0171.html", "node_id":"dli_03_0171.xml", "product_code":"dli", - "code":"162", + "code":"174", "des":"After a SQL job was submitted to the default queue, the job runs abnormally. The job log reported that the execution timed out. The exception logs are as follows:[ERROR] ", "doc_type":"usermanual", "kw":"How Do I Do If I Encounter a Timeout Exception When Executing DLI SQL Statements on the default Queu", @@ -3393,7 +3645,7 @@ "uri":"dli_03_0211.html", "node_id":"dli_03_0211.xml", "product_code":"dli", - "code":"163", + "code":"175", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"DLI Databases and Tables", @@ -3413,7 +3665,7 @@ "uri":"dli_03_0184.html", "node_id":"dli_03_0184.xml", "product_code":"dli", - "code":"164", + "code":"176", "des":"A DLI table exists but cannot be queried on the DLI console.If a table exists but cannot be queried, there is a high probability that the current user does not have the p", "doc_type":"usermanual", "kw":"Why Am I Unable to Query a Table on the DLI Console?,DLI Databases and Tables,User Guide", @@ -3433,7 +3685,7 @@ "uri":"dli_03_0013.html", "node_id":"dli_03_0013.xml", "product_code":"dli", - "code":"165", + "code":"177", "des":"When submitting a job to import data into a DLI table, if the compression rate of the Parquet/ORC file corresponding to the OBS table is high, exceeding 5 times the compr", "doc_type":"usermanual", "kw":"How Do I Do If the Compression Rate of an OBS Table Is High?,DLI Databases and Tables,User Guide", @@ -3453,7 +3705,7 @@ "uri":"dli_03_0009.html", "node_id":"dli_03_0009.xml", "product_code":"dli", - "code":"166", + "code":"178", "des":"To avoid garbled characters caused by inconsistent character encoding, you are advised to unify the encoding format of your data source when executing jobs in DLI.DLI onl", "doc_type":"usermanual", "kw":"How Do I Do If Inconsistent Character Encoding Leads to Garbled Characters?,DLI Databases and Tables", @@ -3473,7 +3725,7 @@ "uri":"dli_03_0175.html", "node_id":"dli_03_0175.xml", "product_code":"dli", - "code":"167", + "code":"179", "des":"User A created the testTable table in a database through a SQL job and granted user B the permission to insert and delete table data. User A deleted the testTable table a", "doc_type":"usermanual", "kw":"Do I Need to to Regrant Permissions to Users and Projects After Deleting and Recreating a Table With", @@ -3493,7 +3745,7 @@ "uri":"dli_03_0177.html", "node_id":"dli_03_0177.xml", "product_code":"dli", - "code":"168", + "code":"180", "des":"A CSV file is imported to a DLI partitioned table, but the imported file data does not contain the data in the partitioning column. The partitioning column needs to be sp", "doc_type":"usermanual", "kw":"How Do I Do If Files Imported Into a DLI Partitioned Table Lack Data for the Partition Columns, Caus", @@ -3513,7 +3765,7 @@ "uri":"dli_03_0181.html", "node_id":"dli_03_0181.xml", "product_code":"dli", - "code":"169", + "code":"181", "des":"When an OBS foreign table is created, a field in the specified OBS file contains a carriage return line feed (CRLF) character. As a result, the data is incorrect.The stat", "doc_type":"usermanual", "kw":"How Do I Fix Incorrect Data in an OBS Foreign Table Caused by Newline Characters in OBS File Fields?", @@ -3533,7 +3785,7 @@ "uri":"dli_03_0187.html", "node_id":"dli_03_0187.xml", "product_code":"dli", - "code":"170", + "code":"182", "des":"The on clause was not added to the SQL statement for joining tables. As a result, the Cartesian product query occurs due to multi-table association, and the queue resourc", "doc_type":"usermanual", "kw":"How Do I Prevent a Cartesian Product Query and Resource Overload Due to Missing \"ON\" Conditions in T", @@ -3553,7 +3805,7 @@ "uri":"dli_03_0190.html", "node_id":"dli_03_0190.xml", "product_code":"dli", - "code":"171", + "code":"183", "des":"Partition data is manually uploaded to a partition of an OBS table. However, the data cannot be queried using DLI SQL editor.After manually adding partition data, you nee", "doc_type":"usermanual", "kw":"How Do I Do If I Can't Query Data After Manually Adding It to the Partition Directory of an OBS Tabl", @@ -3573,7 +3825,7 @@ "uri":"dli_03_0212.html", "node_id":"dli_03_0212.xml", "product_code":"dli", - "code":"172", + "code":"184", "des":"When using the INSERT OVERWRITE statement to overwrite data in a partitioned table, if you find that it overwrites all data instead of the expected partitioned data, it m", "doc_type":"usermanual", "kw":"Why Does the \"insert overwrite\" Operation Affect All Data in a Partitioned Table Instead of Just the", @@ -3593,7 +3845,7 @@ "uri":"dli_03_0214.html", "node_id":"dli_03_0214.xml", "product_code":"dli", - "code":"173", + "code":"185", "des":"Spark does not have the datetime type and uses the TIMESTAMP type instead.You can use a function to convert data types.The following is an example.select cast(create_date", "doc_type":"usermanual", "kw":"Why Does the \"create_date\" Field in an RDS Table (Datetime Data Type) Appear as a Timestamp in DLI Q", @@ -3613,7 +3865,7 @@ "uri":"dli_03_0215.html", "node_id":"dli_03_0215.xml", "product_code":"dli", - "code":"174", + "code":"186", "des":"Changing a table name immediately after executing a SQL job may result in an incorrect data size for the table.This is because DLI updates the metadata of the table when ", "doc_type":"usermanual", "kw":"How Do I Do If Renaming a Table After a SQL Job Causes Incorrect Data Size?,DLI Databases and Tables", @@ -3633,7 +3885,7 @@ "uri":"dli_03_0231.html", "node_id":"dli_03_0231.xml", "product_code":"dli", - "code":"175", + "code":"187", "des":"When DLI is used to insert data into an OBS temporary table, only part of data is imported.Possible causes are as follows:The amount of data read during job execution is ", "doc_type":"usermanual", "kw":"How Can I Resolve Data Inconsistencies When Importing Data from DLI to OBS?,DLI Databases and Tables", @@ -3649,11 +3901,31 @@ "title":"How Can I Resolve Data Inconsistencies When Importing Data from DLI to OBS?", "githuburl":"" }, + { + "uri":"dli_03_0277.html", + "node_id":"dli_03_0277.xml", + "product_code":"dli", + "code":"188", + "des":"The Hudi table created using Flink SQL statements is not displayed on the DLI console, making it impossible to manage or perform query operations on the table through the", + "doc_type":"usermanual", + "kw":"Why Is a Hudi Table Not Displayed on the DLI Console?,DLI Databases and Tables,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "IsMulti":"No", + "documenttype":"usermanual", + "IsBot":"Yes" + } + ], + "title":"Why Is a Hudi Table Not Displayed on the DLI Console?", + "githuburl":"" + }, { "uri":"dli_03_0022.html", "node_id":"dli_03_0022.xml", "product_code":"dli", - "code":"176", + "code":"189", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Enhanced Datasource Connections", @@ -3673,7 +3945,7 @@ "uri":"dli_03_0238.html", "node_id":"dli_03_0238.xml", "product_code":"dli", - "code":"177", + "code":"190", "des":"The outbound rule had been configured for the security group of the queue associated with the enhanced datasource connection. The datasource authentication used a passwor", "doc_type":"usermanual", "kw":"How Do I Resolve a Failure in Connecting DLI to GaussDB(DWS) Through an Enhanced Datasource Connecti", @@ -3693,7 +3965,7 @@ "uri":"dli_03_0179.html", "node_id":"dli_03_0179.xml", "product_code":"dli", - "code":"178", + "code":"191", "des":"A datasource connection is created and bound to a queue. The connectivity test fails and the following error information is displayed:failed to connect to specified addre", "doc_type":"usermanual", "kw":"How Do I Do If the Datasource Connection Is Successfully Created but the Network Connectivity Test F", @@ -3713,7 +3985,7 @@ "uri":"dli_03_0186.html", "node_id":"dli_03_0186.xml", "product_code":"dli", - "code":"179", + "code":"192", "des":"Configuring the Connection Between a DLI Queue and a Data Source in a Private NetworkIf your DLI job needs to connect to a data source, for example, MRS, RDS, CSS, Kafka,", "doc_type":"usermanual", "kw":"How Do I Configure Network Connectivity Between a DLI Queue and a Data Source?,Enhanced Datasource C", @@ -3733,7 +4005,7 @@ "uri":"dli_03_0128.html", "node_id":"dli_03_0128.xml", "product_code":"dli", - "code":"180", + "code":"193", "des":"The main reason for creating a VPC peering connection for DLI's enhanced datasource connection is to establish network connectivity between DLI and data sources in differ", "doc_type":"usermanual", "kw":"Why Is Creating a VPC Peering Connection Necessary for Enhanced Datasource Connections in DLI?,Enhan", @@ -3753,7 +4025,7 @@ "uri":"dli_03_0257.html", "node_id":"dli_03_0257.xml", "product_code":"dli", - "code":"181", + "code":"194", "des":"The possible causes and solutions are as follows:If you have created a queue, do not bind it to a datasource connection immediately. Wait for 5 to 10 minutes. After the c", "doc_type":"usermanual", "kw":"How Do I Do If Creating a Datasource Connection in DLI Gets Stuck in the \"Creating\" State When Bindi", @@ -3773,7 +4045,7 @@ "uri":"dli_03_0047.html", "node_id":"dli_03_0047.xml", "product_code":"dli", - "code":"182", + "code":"195", "des":"The network connectivity is abnormal. Check whether the security group is correctly selected and whether the VPC is correctly configured.Example: When you create an RDS d", "doc_type":"usermanual", "kw":"How Do I Resolve the \"communication link failure\" Error When Using a Newly Created Datasource Connec", @@ -3793,7 +4065,7 @@ "uri":"dli_03_0080.html", "node_id":"dli_03_0080.xml", "product_code":"dli", - "code":"183", + "code":"196", "des":"If you have not added the cluster host information to the datasource connection, it can lead to KRB authentication failure, resulting in a connection timeout. In this cas", "doc_type":"usermanual", "kw":"How Do I Troubleshoot a Connection Timeout Issue That Isn't Recorded in Logs When Accessing MRS HBas", @@ -3813,7 +4085,7 @@ "uri":"dli_03_0239.html", "node_id":"dli_03_0239.xml", "product_code":"dli", - "code":"184", + "code":"197", "des":"A datasource RDS table was created in the DataArts Studio, and the insert overwrite statement was executed to write data into RDS. DLI.0999: BatchUpdateException: Incorre", "doc_type":"usermanual", "kw":"How Do I Do If I Encounter the \"Incorrect string value\" Error When Executing insert overwrite on a D", @@ -3833,7 +4105,7 @@ "uri":"dli_03_0250.html", "node_id":"dli_03_0250.xml", "product_code":"dli", - "code":"185", + "code":"198", "des":"The system failed to create a datasource RDS table, and null pointer error was reported.The following table creation statement was used:The RDS database is in a PostGre c", "doc_type":"usermanual", "kw":"How Do I Resolve the Null Pointer Error When Creating an RDS Datasource Table?,Enhanced Datasource C", @@ -3853,7 +4125,7 @@ "uri":"dli_03_0251.html", "node_id":"dli_03_0251.xml", "product_code":"dli", - "code":"186", + "code":"199", "des":"The system failed to execute insert overwrite on the datasource GaussDB(DWS) table, and org.postgresql.util.PSQLException: ERROR: tuple concurrently updated was displayed", "doc_type":"usermanual", "kw":"Error Message \"org.postgresql.util.PSQLException: ERROR: tuple concurrently updated\" Is Displayed Wh", @@ -3873,7 +4145,7 @@ "uri":"dli_03_0252.html", "node_id":"dli_03_0252.xml", "product_code":"dli", - "code":"187", + "code":"200", "des":"A datasource table was used to import data to a CloudTable HBase table. This HBase table contains a column family and a rowkey for 100 million simulating data records. Th", "doc_type":"usermanual", "kw":"RegionTooBusyException Is Reported When Data Is Imported to a CloudTable HBase Table Through a Datas", @@ -3893,7 +4165,7 @@ "uri":"dli_03_0253.html", "node_id":"dli_03_0253.xml", "product_code":"dli", - "code":"188", + "code":"201", "des":"A table was created on GaussDB(DWS) and then a datasource connection was created on DLI to read and write data. An error message was displayed during data writing, indica", "doc_type":"usermanual", "kw":"How Do I Do If A Null Value Is Written Into a Non-Null Field When Using a DLI Datasource Connection ", @@ -3913,7 +4185,7 @@ "uri":"dli_03_0254.html", "node_id":"dli_03_0254.xml", "product_code":"dli", - "code":"189", + "code":"202", "des":"A datasource GaussDB(DWS) table and the datasource connection were created in DLI, and the schema of the source table in GaussDB(DWS) were updated. During the job executi", "doc_type":"usermanual", "kw":"How Do I Do If an Insert Operation Failed After the Schema of the GaussDB(DWS) Source Table Is Updat", @@ -3933,7 +4205,7 @@ "uri":"dli_03_0028.html", "node_id":"dli_03_0028.xml", "product_code":"dli", - "code":"190", + "code":"203", "des":"When creating an associated RDS table in DLI, if the RDS table contains an auto-increment primary key or other auto-populated fields, you can take the following measures ", "doc_type":"usermanual", "kw":"How Do I Insert Data into an RDS Table with an Auto-Increment Primary Key Using DLI?,Enhanced Dataso", @@ -3953,7 +4225,7 @@ "uri":"dli_03_0020.html", "node_id":"dli_03_0020.xml", "product_code":"dli", - "code":"191", + "code":"204", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"SQL Jobs", @@ -3973,7 +4245,7 @@ "uri":"dli_03_0204.html", "node_id":"dli_03_0204.xml", "product_code":"dli", - "code":"192", + "code":"205", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"SQL Job Development", @@ -3993,7 +4265,7 @@ "uri":"dli_03_0200.html", "node_id":"dli_03_0200.xml", "product_code":"dli", - "code":"193", + "code":"206", "des":"A temporary table is used to store intermediate results. When a transaction or session ends, the data in the temporary table can be automatically deleted. For example, in", "doc_type":"usermanual", "kw":"SQL Jobs,SQL Job Development,User Guide", @@ -4013,7 +4285,7 @@ "uri":"dli_03_0086.html", "node_id":"dli_03_0086.xml", "product_code":"dli", - "code":"194", + "code":"207", "des":"If a large number of small files are generated during SQL execution, job execution and table query will take a long time. In this case, you should merge small files.You a", "doc_type":"usermanual", "kw":"How Do I Merge Small Files?,SQL Job Development,User Guide", @@ -4033,8 +4305,8 @@ "uri":"dli_03_0092.html", "node_id":"dli_03_0092.xml", "product_code":"dli", - "code":"195", - "des":"When creating an OBS table, you must specify a table path in the database. The path format is as follows: obs://xxx/database name/table name.If the specified path is akdc", + "code":"208", + "des":"When creating an OBS table, you must specify a table path in the database.The path format is as follows: obs://xxx/database name/table name.If the specified path is akdc.", "doc_type":"usermanual", "kw":"How Do I Specify an OBS Path When Creating an OBS Table?,SQL Job Development,User Guide", "search_title":"", @@ -4053,7 +4325,7 @@ "uri":"dli_03_0108.html", "node_id":"dli_03_0108.xml", "product_code":"dli", - "code":"196", + "code":"209", "des":"To associate JSON data nested in an OBS bucket, you can create a table in asynchronous mode.The following is an example of a table creation statement that shows how to us", "doc_type":"usermanual", "kw":"How Do I Create a Table Using JSON Data in an OBS Bucket?,SQL Job Development,User Guide", @@ -4073,7 +4345,7 @@ "uri":"dli_03_0069.html", "node_id":"dli_03_0069.xml", "product_code":"dli", - "code":"197", + "code":"210", "des":"The correct method for using the count function to perform aggregation is as follows:OrIf an incorrect method is used, an error will be reported.", "doc_type":"usermanual", "kw":"How Can I Use the count Function to Perform Aggregation?,SQL Job Development,User Guide", @@ -4093,7 +4365,7 @@ "uri":"dli_03_0072.html", "node_id":"dli_03_0072.xml", "product_code":"dli", - "code":"198", + "code":"211", "des":"You can use the cross-region replication function of OBS. The procedure is as follows:Export the DLI table data in region 1 to the user-defined OBS bucket.Use the OBS cro", "doc_type":"usermanual", "kw":"How Do I Synchronize DLI Table Data Across Regions?,SQL Job Development,User Guide", @@ -4113,7 +4385,7 @@ "uri":"dli_03_0191.html", "node_id":"dli_03_0191.xml", "product_code":"dli", - "code":"199", + "code":"212", "des":"If you need to insert data into a table but only want to specify certain fields, you can use the INSERT INTO statement combined with the SELECT clause.However, DLI curren", "doc_type":"usermanual", "kw":"How Do I Insert Table Data into Specific Fields of a Table Using a SQL Job?,SQL Job Development,User", @@ -4133,7 +4405,7 @@ "uri":"dli_03_0196.html", "node_id":"dli_03_0196.xml", "product_code":"dli", - "code":"200", + "code":"213", "des":"If the job runs slowly, perform the following steps to find the causes and rectify the fault:Check whether the problem is caused by FullGC.Log in to the DLI console. In t", "doc_type":"usermanual", "kw":"How Do I Troubleshoot Slow SQL Jobs?,SQL Job Development,User Guide", @@ -4153,7 +4425,7 @@ "uri":"dli_03_0091.html", "node_id":"dli_03_0091.xml", "product_code":"dli", - "code":"201", + "code":"214", "des":"You can view SQL job logs for routine O&M.Obtain the ID of the DLI job executed on the DataArts Studio console.Job IDOn the DLI console, choose Job Management > SQL Jobs.", "doc_type":"usermanual", "kw":"How Do I View DLI SQL Logs?,SQL Job Development,User Guide", @@ -4173,7 +4445,7 @@ "uri":"dli_03_0116.html", "node_id":"dli_03_0116.xml", "product_code":"dli", - "code":"202", + "code":"215", "des":"You can view the job execution records when a job is running.Log in to the DLI management console.In the navigation pane on the left, choose Job Management > SQL Jobs.Ent", "doc_type":"usermanual", "kw":"How Do I View SQL Execution Records in DLI?,SQL Job Development,User Guide", @@ -4193,7 +4465,7 @@ "uri":"dli_03_0093.html", "node_id":"dli_03_0093.xml", "product_code":"dli", - "code":"203", + "code":"216", "des":"Data skew is a common issue during the execution of SQL jobs. When data is unevenly distributed, some compute nodes process significantly more data than others, which can", "doc_type":"usermanual", "kw":"How Do I Do When Data Skew Occurs During the Execution of a SQL Job?,SQL Job Development,User Guide", @@ -4213,7 +4485,7 @@ "uri":"dli_03_0182.html", "node_id":"dli_03_0182.xml", "product_code":"dli", - "code":"204", + "code":"217", "des":"A SQL job contains join operations. After the job is submitted, it is stuck in the Running state and no result is returned.When a Spark SQL job has join operations on sma", "doc_type":"usermanual", "kw":"Why Does a SQL Job That Has Join Operations Stay in the Running State?,SQL Job Development,User Guid", @@ -4233,7 +4505,7 @@ "uri":"dli_03_0213.html", "node_id":"dli_03_0213.xml", "product_code":"dli", - "code":"205", + "code":"218", "des":"The possible causes and solutions are as follows:After you purchase a DLI queue and submit a SQL job for the first time, wait for 5 to 10 minutes. After the cluster is st", "doc_type":"usermanual", "kw":"Why Is a SQL Job Stuck in the Submitting State?,SQL Job Development,User Guide", @@ -4253,7 +4525,7 @@ "uri":"dli_03_0206.html", "node_id":"dli_03_0206.xml", "product_code":"dli", - "code":"206", + "code":"219", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"SQL Job O&M", @@ -4273,7 +4545,7 @@ "uri":"dli_03_0014.html", "node_id":"dli_03_0014.xml", "product_code":"dli", - "code":"207", + "code":"220", "des":"This message indicates that you are exporting data to an existing OBS path.Solution:Create an OBS directory.You can create an OBS directory that does not exist to store t", "doc_type":"usermanual", "kw":"Why Is Error \"path obs://xxx already exists\" Reported When Data Is Exported to OBS?,SQL Job O&M,User", @@ -4293,7 +4565,7 @@ "uri":"dli_03_0066.html", "node_id":"dli_03_0066.xml", "product_code":"dli", - "code":"208", + "code":"221", "des":"This message indicates that the two tables to be joined contain the same column, but the owner of the column is not specified when the command is executed.For example, ta", "doc_type":"usermanual", "kw":"Why Is Error \"SQL_ANALYSIS_ERROR: Reference 't.id' is ambiguous, could be: t.id, t.id.;\" Displayed W", @@ -4313,7 +4585,7 @@ "uri":"dli_03_0071.html", "node_id":"dli_03_0071.xml", "product_code":"dli", - "code":"209", + "code":"222", "des":"This message indicates that your operation is restricted because your account is in arrears or there is insufficient balance in your account.Solution:Check the account st", "doc_type":"usermanual", "kw":"Why Is Error \"The current account does not have permission to perform this operation,the current acc", @@ -4333,7 +4605,7 @@ "uri":"dli_03_0145.html", "node_id":"dli_03_0145.xml", "product_code":"dli", - "code":"210", + "code":"223", "des":"When you query the partitioned table XX.YYY, the partition column is not specified in the search criteria.A partitioned table can be queried only when the query condition", "doc_type":"usermanual", "kw":"Why Is Error \"There should be at least one partition pruning predicate on partitioned table XX.YYY\" ", @@ -4353,7 +4625,7 @@ "uri":"dli_03_0169.html", "node_id":"dli_03_0169.xml", "product_code":"dli", - "code":"211", + "code":"224", "des":"The following error message is displayed when the LOAD DATA command is executed by a Spark SQL job to import data to a DLI table:In some cases ,the following error messag", "doc_type":"usermanual", "kw":"Why Is Error \"IllegalArgumentException: Buffer size too small. size\" Reported When Data Is Loaded to", @@ -4373,7 +4645,7 @@ "uri":"dli_03_0189.html", "node_id":"dli_03_0189.xml", "product_code":"dli", - "code":"212", + "code":"225", "des":"An error is reported during SQL job execution:Please contact DLI service. DLI.0002: FileNotFoundException: getFileStatus on obs://xxx: status [404]Check whether there is ", "doc_type":"usermanual", "kw":"Why Is Error \"DLI.0002 FileNotFoundException\" Reported During SQL Job Running?,SQL Job O&M,User Guid", @@ -4393,7 +4665,7 @@ "uri":"dli_03_0046.html", "node_id":"dli_03_0046.xml", "product_code":"dli", - "code":"213", + "code":"226", "des":"Currently, DLI supports the creation of TEXTFILE, SEQUENCEFILE, RCFILE, ORC, AVRO, and PARQUET tables using the Hive syntax.If you create a table using CTAS statements, s", "doc_type":"usermanual", "kw":"Why Is a Schema Parsing Error Reported When I Create a Hive Table Using CTAS?,SQL Job O&M,User Guide", @@ -4413,7 +4685,7 @@ "uri":"dli_03_0173.html", "node_id":"dli_03_0173.xml", "product_code":"dli", - "code":"214", + "code":"227", "des":"When you run a DLI SQL script on DataArts Studio, the log shows that the statements fail to be executed. The error information is as follows:DLI.0999: RuntimeException: o", "doc_type":"usermanual", "kw":"Why Is Error \"org.apache.hadoop.fs.obs.OBSIOException\" Reported When I Run DLI SQL Scripts on DataAr", @@ -4433,7 +4705,7 @@ "uri":"dli_03_0207.html", "node_id":"dli_03_0207.xml", "product_code":"dli", - "code":"215", + "code":"228", "des":"Error message \"File not Found\" is displayed when a SQL job is accessed.The system may not be able to locate the specified file path or file due to an incorrect file path ", "doc_type":"usermanual", "kw":"Why Is Error \"File not Found\" Reported When I Access a SQL Job?,SQL Job O&M,User Guide", @@ -4453,7 +4725,7 @@ "uri":"dli_03_0208.html", "node_id":"dli_03_0208.xml", "product_code":"dli", - "code":"216", + "code":"229", "des":"Error message \"DLI.0003: AccessControlException XXX\" is reported when a SQL job is accessed.Check the permissions of the OBS bucket to ensure that the account has access ", "doc_type":"usermanual", "kw":"Why Is Error \"DLI.0003: AccessControlException XXX\" Reported When I Access a SQL Job?,SQL Job O&M,Us", @@ -4473,7 +4745,7 @@ "uri":"dli_03_0209.html", "node_id":"dli_03_0209.xml", "product_code":"dli", - "code":"217", + "code":"230", "des":"Error message \"DLI.0001: org.apache.hadoop.security.AccessControlException: verifyBucketExists on {{bucket name}}: status [403]\" is reported when a SQL job is Accessed.Ch", "doc_type":"usermanual", "kw":"Why Is Error \"DLI.0001: org.apache.hadoop.security.AccessControlException: verifyBucketExists on {{b", @@ -4493,7 +4765,7 @@ "uri":"dli_03_0210.html", "node_id":"dli_03_0210.xml", "product_code":"dli", - "code":"218", + "code":"231", "des":"Error message \"The current account does not have permission to perform this operation,the current account was restricted.\" is reported during SQL statement execution.Chec", "doc_type":"usermanual", "kw":"Why Am I Seeing the Error Message \"The current account does not have permission to perform this oper", @@ -4513,7 +4785,7 @@ "uri":"dli_03_0037.html", "node_id":"dli_03_0037.xml", "product_code":"dli", - "code":"219", + "code":"232", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Flink Jobs", @@ -4533,7 +4805,7 @@ "uri":"dli_03_0137.html", "node_id":"dli_03_0137.xml", "product_code":"dli", - "code":"220", + "code":"233", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Flink Job Consulting", @@ -4553,7 +4825,7 @@ "uri":"dli_03_0139.html", "node_id":"dli_03_0139.xml", "product_code":"dli", - "code":"221", + "code":"234", "des":"A sub-user can view queues but cannot view Flink jobs. You can authorize the sub-user using DLI or IAM.Authorization on DLILog in to the DLI console using a tenant accoun", "doc_type":"usermanual", "kw":"How Do I Authorize a Subuser to View Flink Jobs?,Flink Job Consulting,User Guide", @@ -4573,7 +4845,7 @@ "uri":"dli_03_0090.html", "node_id":"dli_03_0090.xml", "product_code":"dli", - "code":"222", + "code":"235", "des":"DLI Flink jobs are highly available. You can enable the automatic restart function to automatically restart your jobs after short-time faults of peripheral services are r", "doc_type":"usermanual", "kw":"How Do I Configure Auto Restart upon Exception for a Flink Job?,Flink Job Consulting,User Guide", @@ -4593,7 +4865,7 @@ "uri":"dli_03_0099.html", "node_id":"dli_03_0099.xml", "product_code":"dli", - "code":"223", + "code":"236", "des":"When you create a Flink SQL job or Flink Jar job, you can select Save Job Log on the job editing page to save job running logs to OBS.To set the OBS bucket for storing th", "doc_type":"usermanual", "kw":"How Do I Save Logs for Flink Jobs?,Flink Job Consulting,User Guide", @@ -4613,7 +4885,7 @@ "uri":"dli_03_0160.html", "node_id":"dli_03_0160.xml", "product_code":"dli", - "code":"224", + "code":"237", "des":"Choose Job Management > Flink Jobs. In the Operation column of the target job, choose More > Permissions. When a new user is authorized, No such user. userName:xxxx. is d", "doc_type":"usermanual", "kw":"Why Is Error \"No such user. userName:xxxx.\" Reported on the Flink Job Management Page When I Grant P", @@ -4633,7 +4905,7 @@ "uri":"dli_03_0180.html", "node_id":"dli_03_0180.xml", "product_code":"dli", - "code":"225", + "code":"238", "des":"Checkpoint was enabled when a Flink job is created, and the OBS bucket for storing checkpoints was specified. I am not sure how to restore a Flink job from a specific che", "doc_type":"usermanual", "kw":"How Do I Restore a Flink Job from a Specific Checkpoint After Manually Stopping the Job?,Flink Job C", @@ -4653,7 +4925,7 @@ "uri":"dli_03_0036.html", "node_id":"dli_03_0036.xml", "product_code":"dli", - "code":"226", + "code":"239", "des":"When you set running parameters of a DLI Flink job, you can enable Alarm Generation upon Job Exception to receive alarms when the job runs abnormally or is in arrears.If ", "doc_type":"usermanual", "kw":"Why Is a Message Displayed Indicating That the SMN Topic Does Not Exist When I Use the SMN Topic in ", @@ -4673,7 +4945,7 @@ "uri":"dli_03_0131.html", "node_id":"dli_03_0131.xml", "product_code":"dli", - "code":"227", + "code":"240", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Flink SQL Jobs", @@ -4693,7 +4965,7 @@ "uri":"dli_03_0089.html", "node_id":"dli_03_0089.xml", "product_code":"dli", - "code":"228", + "code":"241", "des":"When using a Flink SQL job, you need to create an OBS partition table for subsequent batch processing.In the following example, the day field is used as the partition fie", "doc_type":"usermanual", "kw":"How Do I Map an OBS Table to a DLI Partitioned Table?,Flink SQL Jobs,User Guide", @@ -4713,7 +4985,7 @@ "uri":"dli_03_0120.html", "node_id":"dli_03_0120.xml", "product_code":"dli", - "code":"229", + "code":"242", "des":"You used Flink 1.10 to run a Flink Opensource SQL job. You set the number of Kafka partitions for the job a small value at the beginning and need to increase the number n", "doc_type":"usermanual", "kw":"How Do I Change the Number of Kafka Partitions in a Flink SQL Job Without Stopping It?,Flink SQL Job", @@ -4733,7 +5005,7 @@ "uri":"dli_03_0167.html", "node_id":"dli_03_0167.xml", "product_code":"dli", - "code":"230", + "code":"243", "des":"When I run the creation statement with an EL expression in the table name in a Flink SQL job, the following error message is displayed:DLI.0005: AnalysisException: t_user", "doc_type":"usermanual", "kw":"How Do I Fix the DLI.0005 Error When Using EL Expressions to Create a Table in a Flink SQL Job?,Flin", @@ -4753,7 +5025,7 @@ "uri":"dli_03_0168.html", "node_id":"dli_03_0168.xml", "product_code":"dli", - "code":"231", + "code":"244", "des":"After data is written to OBS through the Flink job output stream, data cannot be queried from the DLI table created in the OBS file path.For example, use the following Fl", "doc_type":"usermanual", "kw":"Why Is No Data Queried in the DLI Table Created Using the OBS File Path When Data Is Written to OBS ", @@ -4773,7 +5045,7 @@ "uri":"dli_03_0174.html", "node_id":"dli_03_0174.xml", "product_code":"dli", - "code":"232", + "code":"245", "des":"After a Flink SQL job is submitted on DLI, the job fails to be executed. The following error information is displayed in the job log:connect to DIS failed java.lang.Illeg", "doc_type":"usermanual", "kw":"Why Does a Flink SQL Job Fails to Be Executed, and Is \"connect to DIS failed java.lang.IllegalArgume", @@ -4793,7 +5065,7 @@ "uri":"dli_03_0232.html", "node_id":"dli_03_0232.xml", "product_code":"dli", - "code":"233", + "code":"246", "des":"After a Flink SQL job consumed Kafka and sent data to the Elasticsearch cluster, the job was successfully executed, but no data is available.Possible causes are as follow", "doc_type":"usermanual", "kw":"Data Writing Fails After a Flink SQL Job Consumed Kafka and Sank Data to the Elasticsearch Cluster,F", @@ -4813,7 +5085,7 @@ "uri":"dli_03_0121.html", "node_id":"dli_03_0121.xml", "product_code":"dli", - "code":"234", + "code":"247", "des":"You used Flink 1.10 to run a Flink Opensource SQL job. The job failed after the following error was reported when Flink Sink wrote data to Kafka.The CPU usage is too high", "doc_type":"usermanual", "kw":"How Do I Configure Connection Retries for Kafka Sink If it is Disconnected?,Flink SQL Jobs,User Guid", @@ -4833,7 +5105,7 @@ "uri":"dli_03_0048.html", "node_id":"dli_03_0048.xml", "product_code":"dli", - "code":"235", + "code":"248", "des":"In a Flink job, you can use CREATE statements to define source and sink tables, and specify their connector types and related attributes.If you need to write data to diff", "doc_type":"usermanual", "kw":"How Do I Write Data to Different Elasticsearch Clusters in a Flink Job?,Flink SQL Jobs,User Guide", @@ -4853,7 +5125,7 @@ "uri":"dli_03_0040.html", "node_id":"dli_03_0040.xml", "product_code":"dli", - "code":"236", + "code":"249", "des":"To rectify this fault, perform the following steps:Log in to the DIS management console. In the navigation pane, choose Stream Management. View the Flink job SQL statemen", "doc_type":"usermanual", "kw":"Why Does DIS Stream Not Exist During Job Semantic Check?,Flink SQL Jobs,User Guide", @@ -4873,7 +5145,7 @@ "uri":"dli_03_0265.html", "node_id":"dli_03_0265.xml", "product_code":"dli", - "code":"237", + "code":"250", "des":"If the Flink JobManager prompts \"Timeout expired while fetching topic metadata\", it means that the Flink job timed out while trying to fetch metadata for the Kafka topic.", "doc_type":"usermanual", "kw":"Why Is Error \"Timeout expired while fetching topic metadata\" Repeatedly Reported in Flink JobManager", @@ -4893,7 +5165,7 @@ "uri":"dli_03_0132.html", "node_id":"dli_03_0132.xml", "product_code":"dli", - "code":"238", + "code":"251", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Flink Jar Jobs", @@ -4913,7 +5185,7 @@ "uri":"dli_03_0044.html", "node_id":"dli_03_0044.xml", "product_code":"dli", - "code":"239", + "code":"252", "des":"You can upload configuration files for custom jobs (Jar).Upload the configuration file to DLI through Package Management.In the Other Dependencies area of the Flink Jar j", "doc_type":"usermanual", "kw":"Can I Upload Configuration Files for Flink Jar Jobs?,Flink Jar Jobs,User Guide", @@ -4933,7 +5205,7 @@ "uri":"dli_03_0119.html", "node_id":"dli_03_0119.xml", "product_code":"dli", - "code":"240", + "code":"253", "des":"The dependency of your Flink job conflicts with a built-in dependency of the DLI Flink platform. As a result, the job submission fails.Check whether there are conflicting", "doc_type":"usermanual", "kw":"Why Does a Flink Jar Package Conflict Result in Job Submission Failure?,Flink Jar Jobs,User Guide", @@ -4953,7 +5225,7 @@ "uri":"dli_03_0161.html", "node_id":"dli_03_0161.xml", "product_code":"dli", - "code":"241", + "code":"254", "des":"When a Flink Jar job is submitted to access GaussDB(DWS), an error message is displayed indicating that the job fails to be started. The job log contains the following er", "doc_type":"usermanual", "kw":"Why Does a Flink Jar Job Fail to Access GaussDB(DWS) and a Message Is Displayed Indicating Too Many ", @@ -4973,7 +5245,7 @@ "uri":"dli_03_0233.html", "node_id":"dli_03_0233.xml", "product_code":"dli", - "code":"242", + "code":"255", "des":"The storage path of the Flink Jar job checkpoints was set to an OBS bucket. The job failed to be submitted, and an error message indicating an invalid OBS bucket name was", "doc_type":"usermanual", "kw":"Why Is Error Invalid OBS Bucket Name Reported After a Flink Job Submission Failed?,Flink Jar Jobs,Us", @@ -4993,7 +5265,7 @@ "uri":"dli_03_0234.html", "node_id":"dli_03_0234.xml", "product_code":"dli", - "code":"243", + "code":"256", "des":"Flink Job submission failed. The exception information is as follows:Flink JAR files conflicted. The submitted Flink JAR file conflicted with the HDFS JAR file of the DLI", "doc_type":"usermanual", "kw":"Why Does the Flink Submission Fail Due to Hadoop JAR File Conflict?,Flink Jar Jobs,User Guide", @@ -5013,7 +5285,7 @@ "uri":"dli_03_0103.html", "node_id":"dli_03_0103.xml", "product_code":"dli", - "code":"244", + "code":"257", "des":"On the Flink job management page, hover the cursor on the status of the job that fails to be submitted to view the brief information about the failure.The possible causes", "doc_type":"usermanual", "kw":"How Do I Locate a Flink Job Submission Error?,Flink Jar Jobs,User Guide", @@ -5033,7 +5305,7 @@ "uri":"dli_03_0133.html", "node_id":"dli_03_0133.xml", "product_code":"dli", - "code":"245", + "code":"258", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Flink Job Performance Tuning", @@ -5053,7 +5325,7 @@ "uri":"dli_03_0106.html", "node_id":"dli_03_0106.xml", "product_code":"dli", - "code":"246", + "code":"259", "des":"Data Stacking in a Consumer GroupThe accumulated data of a consumer group can be calculated by the following formula: Total amount of data to be consumed by the consumer ", "doc_type":"usermanual", "kw":"Flink Job Performance Tuning,Flink Job Performance Tuning,User Guide", @@ -5073,7 +5345,7 @@ "uri":"dli_03_0096.html", "node_id":"dli_03_0096.xml", "product_code":"dli", - "code":"247", + "code":"260", "des":"The DLI Flink checkpoint/savepoint mechanism is complete and reliable. You can use this mechanism to prevent data loss when a job is manually restarted or restarted due t", "doc_type":"usermanual", "kw":"How Do I Prevent Data Loss After Flink Job Restart?,Flink Job Performance Tuning,User Guide", @@ -5093,7 +5365,7 @@ "uri":"dli_03_0105.html", "node_id":"dli_03_0105.xml", "product_code":"dli", - "code":"248", + "code":"261", "des":"On the Flink job management, click Edit in the Operation column of the target job. On the displayed page, check whether Save Job Log in the Running Parameters tab is enab", "doc_type":"usermanual", "kw":"How Do I Locate a Flink Job Running Error?,Flink Job Performance Tuning,User Guide", @@ -5113,7 +5385,7 @@ "uri":"dli_03_0136.html", "node_id":"dli_03_0136.xml", "product_code":"dli", - "code":"249", + "code":"262", "des":"Flink's checkpointing is a fault tolerance and recovery mechanism. This mechanism ensures that real-time programs can self-recover in case of exceptions or machine issues", "doc_type":"usermanual", "kw":"How Can I Check if a Flink Job Can Be Restored From a Checkpoint After Restarting It?,Flink Job Perf", @@ -5133,7 +5405,7 @@ "uri":"dli_03_0064.html", "node_id":"dli_03_0064.xml", "product_code":"dli", - "code":"250", + "code":"263", "des":"Mode for storing generated job logs when a DLI Flink job fails to be submitted or executed. The options are as follows:If the submission fails, a submission log is genera", "doc_type":"usermanual", "kw":"Why Are Logs Not Written to the OBS Bucket After a DLI Flink Job Fails to Be Submitted for Running?,", @@ -5153,7 +5425,7 @@ "uri":"dli_03_0236.html", "node_id":"dli_03_0236.xml", "product_code":"dli", - "code":"251", + "code":"264", "des":"JobManager and TaskManager heartbeats timed out. As a result, the Flink job is abnormal.Check whether the network is intermittently disconnected and whether the cluster l", "doc_type":"usermanual", "kw":"Why Is the Flink Job Abnormal Due to Heartbeat Timeout Between JobManager and TaskManager?,Flink Job", @@ -5173,7 +5445,7 @@ "uri":"dli_03_0021.html", "node_id":"dli_03_0021.xml", "product_code":"dli", - "code":"252", + "code":"265", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Spark Jobs", @@ -5193,7 +5465,7 @@ "uri":"dli_03_0217.html", "node_id":"dli_03_0217.xml", "product_code":"dli", - "code":"253", + "code":"266", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Spark Job Development", @@ -5213,7 +5485,7 @@ "uri":"dli_03_0201.html", "node_id":"dli_03_0201.xml", "product_code":"dli", - "code":"254", + "code":"267", "des":"DLI Spark does not support job scheduling. You can use other services, such as DataArts Studio, or use APIs or SDKs to customize job schedule.The Spark SQL syntax does no", "doc_type":"usermanual", "kw":"Spark Jobs,Spark Job Development,User Guide", @@ -5233,7 +5505,7 @@ "uri":"dli_03_0107.html", "node_id":"dli_03_0107.xml", "product_code":"dli", - "code":"255", + "code":"268", "des":"To use Spark to write data into a DLI table, configure the following parameters:fs.obs.access.keyfs.obs.secret.keyfs.obs.implfs.obs.endpointThe following is an example:", "doc_type":"usermanual", "kw":"How Do I Use Spark to Write Data into a DLI Table?,Spark Job Development,User Guide", @@ -5253,7 +5525,7 @@ "uri":"dli_03_0017.html", "node_id":"dli_03_0017.xml", "product_code":"dli", - "code":"256", + "code":"269", "des":"To obtain the AK/SK, set the parameters as follows:Create a SparkContext using code.val sc: SparkContext = new SparkContext()\nsc.hadoopConfiguration.set(\"fs.obs.access.ke", "doc_type":"usermanual", "kw":"How Do I Set Up AK/SK So That a General Queue Can Access Tables Stored in OBS?,Spark Job Development", @@ -5273,7 +5545,7 @@ "uri":"dli_03_0102.html", "node_id":"dli_03_0102.xml", "product_code":"dli", - "code":"257", + "code":"270", "des":"Log in to the DLI console. In the navigation pane, choose Job Management > Spark Jobs. In the job list, locate the target job and click next to Job ID to view the parame", "doc_type":"usermanual", "kw":"How Do I View the Resource Usage of DLI Spark Jobs?,Spark Job Development,User Guide", @@ -5293,7 +5565,7 @@ "uri":"dli_03_0076.html", "node_id":"dli_03_0076.xml", "product_code":"dli", - "code":"258", + "code":"271", "des":"If the pymysql module is missing, check whether the corresponding EGG package exists. If the package does not exist, upload the pyFile package on the Package Management p", "doc_type":"usermanual", "kw":"How Do I Use Python Scripts to Access the MySQL Database If the pymysql Module Is Missing from the S", @@ -5313,7 +5585,7 @@ "uri":"dli_03_0082.html", "node_id":"dli_03_0082.xml", "product_code":"dli", - "code":"259", + "code":"272", "des":"DLI natively supports PySpark.For most cases, Python is preferred for data analysis, and PySpark is the best choice for big data analysis. Generally, JVM programs are pac", "doc_type":"usermanual", "kw":"How Do I Run a Complex PySpark Program in DLI?,Spark Job Development,User Guide", @@ -5333,7 +5605,7 @@ "uri":"dli_03_0068.html", "node_id":"dli_03_0068.xml", "product_code":"dli", - "code":"260", + "code":"273", "des":"When shuffle statements, such as GROUP BY and JOIN, are executed in Spark jobs, data skew occurs, which slows down the job execution.To solve this problem, you can config", "doc_type":"usermanual", "kw":"How Do I Use JDBC to Set the spark.sql.shuffle.partitions Parameter to Improve the Task Concurrency?", @@ -5353,7 +5625,7 @@ "uri":"dli_03_0118.html", "node_id":"dli_03_0118.xml", "product_code":"dli", - "code":"261", + "code":"274", "des":"You can use SparkFiles to read the file submitted using –-file form a local path: SparkFiles.get(\"Name of the uploaded file\").The file path in the Driver is different fro", "doc_type":"usermanual", "kw":"How Do I Read Uploaded Files for a Spark Jar Job?,Spark Job Development,User Guide", @@ -5369,11 +5641,31 @@ "title":"How Do I Read Uploaded Files for a Spark Jar Job?", "githuburl":"" }, + { + "uri":"dli_03_0279.html", + "node_id":"dli_03_0279.xml", + "product_code":"dli", + "code":"275", + "des":"When running a job with Spark 3.3.1, certain fields have empty default attribute values when queried in the view attribute on the client. In contrast, when using Spark 3.", + "doc_type":"usermanual", + "kw":"Why Are View Attributes Empty in Spark 3.3.1 Client?,Spark Job Development,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "IsMulti":"No", + "documenttype":"usermanual", + "IsBot":"Yes" + } + ], + "title":"Why Are View Attributes Empty in Spark 3.3.1 Client?", + "githuburl":"" + }, { "uri":"dli_03_0077.html", "node_id":"dli_03_0077.xml", "product_code":"dli", - "code":"262", + "code":"276", "des":"I cannot find the specified Python environment after adding the Python 3 package.Set spark.yarn.appMasterEnv.PYSPARK_PYTHON to python3 in the conf file to specify the Pyt", "doc_type":"usermanual", "kw":"Why Can't I Find the Specified Python Environment After Adding the Python Package?,Spark Job Develop", @@ -5393,7 +5685,7 @@ "uri":"dli_03_0220.html", "node_id":"dli_03_0220.xml", "product_code":"dli", - "code":"263", + "code":"277", "des":"The remaining CUs in the queue may be insufficient. As a result, the job cannot be submitted.To view the remaining CUs of a queue, perform the following steps:Check the C", "doc_type":"usermanual", "kw":"Why Is a Spark Jar Job Stuck in the Submitting State?,Spark Job Development,User Guide", @@ -5413,7 +5705,7 @@ "uri":"dli_03_0218.html", "node_id":"dli_03_0218.xml", "product_code":"dli", - "code":"264", + "code":"278", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Spark Job O&M", @@ -5433,7 +5725,7 @@ "uri":"dli_03_0156.html", "node_id":"dli_03_0156.xml", "product_code":"dli", - "code":"265", + "code":"279", "des":"The following error is reported when a Spark job accesses OBS data:Set the AK/SK to enable Spark jobs to access OBS data.For details, see How Do I Set Up AK/SK So That a ", "doc_type":"usermanual", "kw":"Why Do I Get \"ResponseCode: 403\" and \"ResponseStatus: Forbidden\" Errors When a Spark Job Accesses OB", @@ -5453,7 +5745,7 @@ "uri":"dli_03_0164.html", "node_id":"dli_03_0164.xml", "product_code":"dli", - "code":"266", + "code":"280", "des":"This error message may be due to the OBS bucket being set as the DLI log bucket, which cannot be used for other purposes.You can follow these steps to check:Check if the ", "doc_type":"usermanual", "kw":"Why Do I Encounter the Error \"verifyBucketExists on XXXX: status [403]\" When Using a Spark Job to Ac", @@ -5473,7 +5765,7 @@ "uri":"dli_03_0157.html", "node_id":"dli_03_0157.xml", "product_code":"dli", - "code":"267", + "code":"281", "des":"When running large amounts of data in a Spark job, if a timeout exception error occurs, it is usually due to insufficient resource configuration, data skew, network issue", "doc_type":"usermanual", "kw":"Why Does a Job Running Timeout Occur When Processing a Large Amount of Data with a Spark Job?,Spark ", @@ -5493,7 +5785,7 @@ "uri":"dli_03_0188.html", "node_id":"dli_03_0188.xml", "product_code":"dli", - "code":"268", + "code":"282", "des":"Spark jobs cannot access SFTP. Upload the files you want to access to OBS and then you can analyze the data using Spark jobs.Upload data to an OBS bucket: Upload data sto", "doc_type":"usermanual", "kw":"Why Does a Spark Job Fail to Execute with an Abnormal Access Directory Error When Accessing Files in", @@ -5513,7 +5805,7 @@ "uri":"dli_03_0192.html", "node_id":"dli_03_0192.xml", "product_code":"dli", - "code":"269", + "code":"283", "des":"When a Spark job is running, an error message is displayed, indicating that the user does not have the database permission. The error information is as follows:org.apache", "doc_type":"usermanual", "kw":"Why Does the Job Fail to Be Executed Due to Insufficient Database and Table Permissions?,Spark Job O", @@ -5533,7 +5825,7 @@ "uri":"dli_03_0272.html", "node_id":"dli_03_0272.xml", "product_code":"dli", - "code":"270", + "code":"284", "des":"I cannot find the global_temp database in the Spark 3.x job log.The global_temp database is the default built-in database of Spark 3.x and is Spark's global temporary vie", "doc_type":"usermanual", "kw":"Why Is the global_temp Database Missing in the Job Log of Spark 3.x?,Spark Job O&M,User Guide", @@ -5553,7 +5845,7 @@ "uri":"dli_03_0275.html", "node_id":"dli_03_0275.xml", "product_code":"dli", - "code":"271", + "code":"285", "des":"I failed to use the DataSource syntax to create an OBS table in Avro format when selecting Spark to access metadata.Spark 2.3.x does not support creating OBS tables in Av", "doc_type":"usermanual", "kw":"Why Does Using DataSource Syntax to Create an OBS Table of Avro Type Fail When Accessing Metadata Wi", @@ -5569,11 +5861,51 @@ "title":"Why Does Using DataSource Syntax to Create an OBS Table of Avro Type Fail When Accessing Metadata With Spark 2.3.x?", "githuburl":"" }, + { + "uri":"dli_03_0278.html", + "node_id":"dli_03_0278.xml", + "product_code":"dli", + "code":"286", + "des":"When the rand function is used in SQL statements of Spark 3.3.1, the error message \"Input argument to rand must be a constant\" is displayed.In Spark 3.3.1, the rand funct", + "doc_type":"usermanual", + "kw":"How Do I Resolve the \"Input argument to rand must be a constant\" Error in Spark 3.3.1 SQL Statements", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "IsMulti":"No", + "documenttype":"usermanual", + "IsBot":"Yes" + } + ], + "title":"How Do I Resolve the \"Input argument to rand must be a constant\" Error in Spark 3.3.1 SQL Statements?", + "githuburl":"" + }, + { + "uri":"dli_03_0273.html", + "node_id":"dli_03_0273.xml", + "product_code":"dli", + "code":"287", + "des":"When using Spark 3.3.1 client to create a subquery view with aggregate functions, an error occurs when attempting to write the data, stating \"Not allowed to create a perm", + "doc_type":"usermanual", + "kw":"When Using Spark 3.3.1 Client to Create a View and Perform a Join Query, an Error Occurs Stating \"No", + "search_title":"", + "metedata":[ + { + "prodname":"dli", + "IsMulti":"No", + "documenttype":"usermanual", + "IsBot":"Yes" + } + ], + "title":"When Using Spark 3.3.1 Client to Create a View and Perform a Join Query, an Error Occurs Stating \"Not allowed to create a permanent view\" When Attempting to Write the Data", + "githuburl":"" + }, { "uri":"dli_03_0053.html", "node_id":"dli_03_0053.xml", "product_code":"dli", - "code":"272", + "code":"288", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"DLI Resource Quotas", @@ -5593,7 +5925,7 @@ "uri":"dli_03_0031.html", "node_id":"dli_03_0031.xml", "product_code":"dli", - "code":"273", + "code":"289", "des":"Log in to the management console.Click in the upper left corner and select a region and a project.Click the My Quota icon in the upper right corner of the page.The Serv", "doc_type":"usermanual", "kw":"How Do I View My Quotas?,DLI Resource Quotas,User Guide", @@ -5613,7 +5945,7 @@ "uri":"dli_03_0032.html", "node_id":"dli_03_0032.xml", "product_code":"dli", - "code":"274", + "code":"290", "des":"The system does not support online quota adjustment. To increase a resource quota, dial the hotline or send an email to the customer service. We will process your applica", "doc_type":"usermanual", "kw":"How Do I Apply for a Higher Quota?,DLI Resource Quotas,User Guide", @@ -5633,7 +5965,7 @@ "uri":"dli_03_0054.html", "node_id":"dli_03_0054.xml", "product_code":"dli", - "code":"275", + "code":"291", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"DLI Permissions Management", @@ -5653,7 +5985,7 @@ "uri":"dli_03_0008.html", "node_id":"dli_03_0008.xml", "product_code":"dli", - "code":"276", + "code":"292", "des":"You are unable to perform permission operations on the partition columns of partitioned tables.However, when you grant the permission of any non-partition column in a par", "doc_type":"usermanual", "kw":"What Is Column-Level Authorization for DLI Partitioned Tables?,DLI Permissions Management,User Guide", @@ -5673,7 +6005,7 @@ "uri":"dli_03_0195.html", "node_id":"dli_03_0195.xml", "product_code":"dli", - "code":"277", + "code":"293", "des":"When the user update an existing program package, the following error information is displayed:\"error_code\"*DLI.0003\",\"error_msg\":\"Permission denied for resource 'resourc", "doc_type":"usermanual", "kw":"How Do I Do If I Encounter Insufficient Permissions While Updating Packages?,DLI Permissions Managem", @@ -5693,7 +6025,7 @@ "uri":"dli_03_0227.html", "node_id":"dli_03_0227.xml", "product_code":"dli", - "code":"278", + "code":"294", "des":"When the SQL query statement is executed, the system displays a message indicating that the user does not have the permission to query resources.Error information: DLI.00", "doc_type":"usermanual", "kw":"Why Is Error \"DLI.0003: Permission denied for resource...\" Reported When I Run a SQL Statement?,DLI ", @@ -5713,7 +6045,7 @@ "uri":"dli_03_0228.html", "node_id":"dli_03_0228.xml", "product_code":"dli", - "code":"279", + "code":"295", "des":"If you have already granted authorization to a table and a test query was successful, but you encounter an error when trying to query it again after some time, you should", "doc_type":"usermanual", "kw":"How Do I Do If I Can't Query Table Data After Being Granted Table Permissions?,DLI Permissions Manag", @@ -5733,7 +6065,7 @@ "uri":"dli_03_0057.html", "node_id":"dli_03_0057.xml", "product_code":"dli", - "code":"280", + "code":"296", "des":"If a table inherits database permissions, you do not need to regrant the inherited permissions to the table.Re-authorizing may cause confusion in table permission managem", "doc_type":"usermanual", "kw":"Will Granting Duplicate Permissions to a Table After Inheriting Database Permissions Cause an Error?", @@ -5753,7 +6085,7 @@ "uri":"dli_03_0067.html", "node_id":"dli_03_0067.xml", "product_code":"dli", - "code":"281", + "code":"297", "des":"User A created Table1.User B created View1 based on Table1.After the Select Table permission on Table1 is granted to user C, user C fails to query View1.User B does not h", "doc_type":"usermanual", "kw":"Why Can't I Query a View After I'm Granted the Select Table Permission on the View?,DLI Permissions ", @@ -5773,7 +6105,7 @@ "uri":"dli_03_0225.html", "node_id":"dli_03_0225.xml", "product_code":"dli", - "code":"282", + "code":"298", "des":"Despite configuring a job bucket and authorizing DLI to access it, I still receive an error message stating that DLI is not authorized to access the bucket when attemptin", "doc_type":"usermanual", "kw":"How Do I Do If I Receive a Message Saying I Don't Have Sufficient Permissions to Submit My Jobs to t", @@ -5793,7 +6125,7 @@ "uri":"dli_03_0056.html", "node_id":"dli_03_0056.xml", "product_code":"dli", - "code":"283", + "code":"299", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"DLI APIs", @@ -5813,7 +6145,7 @@ "uri":"dli_03_0060.html", "node_id":"dli_03_0060.xml", "product_code":"dli", - "code":"284", + "code":"300", "des":"In the REST API provided by DLI, the request header can be added to the request URI, for example, Content-Type.Content-Type indicates the request body type or format. The", "doc_type":"usermanual", "kw":"Why Is Error \"unsupported media Type\" Reported When I Subimt a SQL Job?,DLI APIs,User Guide", @@ -5833,7 +6165,7 @@ "uri":"dli_03_0178.html", "node_id":"dli_03_0178.xml", "product_code":"dli", - "code":"285", + "code":"301", "des":"When the API call for submitting a SQL job times out, and the following error information is displayed:There are currently no resources tracked in the state, so there is ", "doc_type":"usermanual", "kw":"What Can I Do If an Error Is Reported When the Execution of the API for Creating a SQL Job Times Out", @@ -5853,7 +6185,7 @@ "uri":"dli_01_00006.html", "node_id":"dli_01_00006.xml", "product_code":"dli", - "code":"286", + "code":"302", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Change History,User Guide", @@ -5863,8 +6195,8 @@ "prodname":"dli", "opensource":"true", "documenttype":"usermanual", - "IsMulti":"No;NO;Yes", - "IsBot":"Yes;No" + "IsMulti":"No;Yes;NO", + "IsBot":"No;Yes" } ], "title":"Change History", diff --git a/docs/dli/umn/CLASS.TXT.json b/docs/dli/umn/CLASS.TXT.json index 48621c444..6ccfd45c9 100644 --- a/docs/dli/umn/CLASS.TXT.json +++ b/docs/dli/umn/CLASS.TXT.json @@ -29,7 +29,7 @@ { "desc":"DLI is applicable to large-scale log analysis, federated analysis of heterogeneous data sources, and big data ETL processing.Gaming operations data analysisDifferent depa", "product_code":"dli", - "title":"Application Scenarios", + "title":"Use Cases", "uri":"dli_07_0002.html", "doc_type":"usermanual", "p_code":"1", @@ -45,9 +45,9 @@ "code":"5" }, { - "desc":"An elastic resource pool provides compute resources (CPU and memory) for running DLI jobs. The unit is CU. One CU contains one CPU and 4 GB memory.You can create multiple", + "desc":"DLI compute resources are the foundation for job execution. Both DLI's elastic resource pools and queues fall under compute resources. This section introduces the types a", "product_code":"dli", - "title":"Specifications", + "title":"Compute Resource Types and Specifications", "uri":"dli_07_0027.html", "doc_type":"usermanual", "p_code":"1", @@ -56,7 +56,7 @@ { "desc":"If you need to assign different permissions to employees in your enterprise to access your DLI resources, IAM is a good choice for fine-grained permissions management. IA", "product_code":"dli", - "title":"Permissions Management", + "title":"Permission Management", "uri":"dli_07_0006.html", "doc_type":"usermanual", "p_code":"1", @@ -72,13 +72,22 @@ "code":"8" }, { - "desc":"Dedicated computing resources. They are isolated by resource pools and can only be shared by queues in the same elastic resource pool. You can set scaling policies of dif", + "desc":"OBS works as the data source and data storage system for DLI, and delivers the following capabilities:Data source: DLI provides an API for you to import data from corresp", + "product_code":"dli", + "title":"Related Services", + "uri":"dli_07_0004.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"9" + }, + { + "desc":"An elastic resource pool consists of dedicated compute resources where the resources in different pools are completely isolated from each other. Within a single elastic r", "product_code":"dli", "title":"Basic Concepts", "uri":"dli_07_0003.html", "doc_type":"usermanual", "p_code":"1", - "code":"9" + "code":"10" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -87,52 +96,52 @@ "uri":"dli_01_0220.html", "doc_type":"usermanual", "p_code":"", - "code":"10" + "code":"11" }, { - "desc":"DLI can query data stored in OBS. This section describes how to use DLI to submit a SQL job to query OBS data.To illustrate, create a new file called sampledata.csv and u", + "desc":"DLI can query data stored in OBS. This section describes how to use DLI to submit a SQL job to query OBS data.To illustrate, create a file called sampledata.csv and uploa", "product_code":"dli", - "title":"Using DLI to Submit a SQL Job to Query OBS Data", + "title":"Submitting a SQL Job to Query OBS Data Using DLI", "uri":"dli_01_0002.html", "doc_type":"usermanual", - "p_code":"10", - "code":"11" + "p_code":"11", + "code":"12" }, { "desc":"DLI can query data stored in RDS. This section describes how to use DLI to submit a SQL job to query RDS for MySQL data.In this example, we will create an RDS for MySQL D", "product_code":"dli", - "title":"Using DLI to Submit a SQL Job to Query RDS for MySQL Data", + "title":"Submitting a SQL Job to Query RDS for MySQL Data Using DLI", "uri":"dli_01_0020.html", "doc_type":"usermanual", - "p_code":"10", - "code":"12" + "p_code":"11", + "code":"13" }, { "desc":"DLI Flink jobs can use other cloud services as data sources and sink streams for real-time compute.This example describes how to create and submit a Flink OpenSource SQL ", "product_code":"dli", - "title":"Using DLI to Submit a Flink OpenSource SQL Job to Query RDS for MySQL Data", + "title":"Submitting a Flink OpenSource SQL Job to Query RDS for MySQL Data Using DLI", "uri":"dli_01_0531.html", "doc_type":"usermanual", - "p_code":"10", - "code":"13" + "p_code":"11", + "code":"14" }, { "desc":"Flink Jar jobs are suitable for data analysis scenarios that require custom stream processing logic, complex state management, or integration with specific libraries. You", "product_code":"dli", - "title":"Using DLI to Submit a Flink Jar Job", + "title":"Submitting a Flink Jar Job Using DLI", "uri":"dli_01_0512.html", "doc_type":"usermanual", - "p_code":"10", - "code":"14" + "p_code":"11", + "code":"15" }, { "desc":"DLI allows you to submit Spark jobs compiled as JAR files, which contain the necessary code and dependency information for executing the job. These files are used for spe", "product_code":"dli", - "title":"Using DLI to Submit a Spark Jar Job", + "title":"Submitting a Spark Jar Job Using DLI", "uri":"dli_01_0375.html", "doc_type":"usermanual", - "p_code":"10", - "code":"15" + "p_code":"11", + "code":"16" }, { "desc":"This chapter walks you through on how to develop a DLI job.To manage fine-grained permissions for your DLI resources using IAM, create an IAM user and grant them permissi", @@ -141,7 +150,7 @@ "uri":"dli_01_0001.html", "doc_type":"usermanual", "p_code":"", - "code":"16" + "code":"17" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -150,25 +159,25 @@ "uri":"dli_01_0611.html", "doc_type":"usermanual", "p_code":"", - "code":"17" + "code":"18" }, { - "desc":"To use DLI, you must first configure permissions.This section applies to the following scenarios:If you use DLI for the first time, configure DLI agency permissions by re", + "desc":"Before using DLI, configure DLI agency permissions. This section describes the scenarios and steps for configuring DLI agency permissions (dli_management_agency).If you u", "product_code":"dli", "title":"Configuring DLI Agency Permissions", "uri":"dli_01_0618.html", "doc_type":"usermanual", - "p_code":"17", - "code":"18" + "p_code":"18", + "code":"19" }, { - "desc":"You can use Identity and Access Management (IAM) to implement fine-grained permissions control on DLI resources. For details, see Overview.If your cloud account does not ", + "desc":"You can use Identity and Access Management (IAM) to implement fine-grained permissions management for your DLI resources. For details, see Overview.If your cloud account ", "product_code":"dli", "title":"Creating an IAM User and Granting Permissions", "uri":"dli_01_0418.html", "doc_type":"usermanual", - "p_code":"17", - "code":"19" + "p_code":"18", + "code":"20" }, { "desc":"Before using DLI, you need to configure a DLI job bucket. The bucket is used to store temporary data generated during DLI job running, such as job logs and results.Config", @@ -176,17 +185,17 @@ "title":"Configuring a DLI Job Bucket", "uri":"dli_01_0536.html", "doc_type":"usermanual", - "p_code":"17", - "code":"20" + "p_code":"18", + "code":"21" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dli", - "title":"Creating an Elastic Resource Pool and Queues Within It", + "title":"Creating an Elastic Resource Pool and Creating Queues Within It", "uri":"dli_01_0508.html", "doc_type":"usermanual", "p_code":"", - "code":"21" + "code":"22" }, { "desc":"DLI compute resources are the foundation to run jobs. This section describes the modes of DLI compute resources and queue types.Before we dive into the compute resource m", @@ -194,8 +203,8 @@ "title":"Overview of DLI Elastic Resource Pools and Queues", "uri":"dli_01_0504.html", "doc_type":"usermanual", - "p_code":"21", - "code":"22" + "p_code":"22", + "code":"23" }, { "desc":"An elastic resource pool offers compute resources (CPU and memory) required for running DLI jobs, which can adapt to the changing demands of services.You can create multi", @@ -203,8 +212,8 @@ "title":"Creating an Elastic Resource Pool and Creating Queues Within It", "uri":"dli_01_0505.html", "doc_type":"usermanual", - "p_code":"21", - "code":"23" + "p_code":"22", + "code":"24" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -212,17 +221,17 @@ "title":"Managing Elastic Resource Pools", "uri":"dli_01_0529.html", "doc_type":"usermanual", - "p_code":"21", - "code":"24" + "p_code":"22", + "code":"25" }, { "desc":"After creating an elastic resource pool, you can check and manage it on the management console.This section describes how to check basic information about an elastic reso", "product_code":"dli", - "title":"Viewing Basic Information", + "title":"Checking Basic Information", "uri":"dli_01_0622.html", "doc_type":"usermanual", - "p_code":"24", - "code":"25" + "p_code":"25", + "code":"26" }, { "desc":"Administrators can assign permissions of different operation scopes to users for each elastic resource pool.The administrator and elastic resource pool owner have all per", @@ -230,8 +239,8 @@ "title":"Managing Permissions", "uri":"dli_01_0526.html", "doc_type":"usermanual", - "p_code":"24", - "code":"26" + "p_code":"25", + "code":"27" }, { "desc":"If you want a queue to use resources in an elastic resource pool, bind the queue to the pool.You can click Associate Queue on the Resource Pool page to bind a queue to an", @@ -239,35 +248,35 @@ "title":"Binding a Queue", "uri":"dli_01_0530.html", "doc_type":"usermanual", - "p_code":"24", - "code":"27" + "p_code":"25", + "code":"28" }, { - "desc":"CU settings are used to control the maximum and minimum CU ranges for elastic resource pools to avoid unlimited resource scaling.For example, an elastic resource pool has", + "desc":"Scaling out or in an elastic resource pool essentially means adjusting the actual CUs of the resource pool.In an elastic resource pool:Actual CUs: actual size of resource", + "product_code":"dli", + "title":"Scaling Out or In an Elastic Resource Pool", + "uri":"dli_01_0686.html", + "doc_type":"usermanual", + "p_code":"25", + "code":"29" + }, + { + "desc":"CU settings are used to control the maximum and minimum CU ranges for elastic resource pool scaling to prevent unlimited resource expansion risks.For example, if the curr", "product_code":"dli", "title":"Setting CUs", "uri":"dli_01_0507.html", "doc_type":"usermanual", - "p_code":"24", - "code":"28" + "p_code":"25", + "code":"30" }, { - "desc":"If the current specifications of your elastic resource pool do not meet your service needs, you can modify them using the change yearly/monthly CUs function.In the naviga", - "product_code":"dli", - "title":"Modifying Specifications", - "uri":"dli_01_0524.html", - "doc_type":"usermanual", - "p_code":"24", - "code":"29" - }, - { - "desc":"A tag is a key-value pair that you can customize to identify cloud resources. It helps you to classify and search for cloud resources. A tag consists of a tag key and a t", + "desc":"A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value.If you use ", "product_code":"dli", "title":"Managing Tags", "uri":"dli_01_0525.html", "doc_type":"usermanual", - "p_code":"24", - "code":"30" + "p_code":"25", + "code":"31" }, { "desc":"Multiple queues can be added to an elastic resource pool. For how to add a queue, see Creating an Elastic Resource Pool and Creating Queues Within It. You can configure t", @@ -275,8 +284,8 @@ "title":"Adjusting Scaling Policies for Queues in an Elastic Resource Pool", "uri":"dli_01_0506.html", "doc_type":"usermanual", - "p_code":"24", - "code":"31" + "p_code":"25", + "code":"32" }, { "desc":"If you added a queue to or deleted one from an elastic resource pool, or you scaled an added queue, the CU quantity of the elastic resource pool may be changed. You can v", @@ -284,8 +293,8 @@ "title":"Viewing Scaling History", "uri":"dli_01_0532.html", "doc_type":"usermanual", - "p_code":"24", - "code":"32" + "p_code":"25", + "code":"33" }, { "desc":"You can create enterprise projects matching the organizational structure of your enterprises to centrally manage cloud resources across regions by project. Then you can c", @@ -293,8 +302,8 @@ "title":"Allocating to an Enterprise Project", "uri":"dli_01_0566.html", "doc_type":"usermanual", - "p_code":"24", - "code":"33" + "p_code":"25", + "code":"34" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -302,8 +311,8 @@ "title":"Managing Queues", "uri":"dli_01_0528.html", "doc_type":"usermanual", - "p_code":"21", - "code":"34" + "p_code":"22", + "code":"35" }, { "desc":"This section walks you through how to view basic information about a queue on the management console, including the engine type and version.Log in to the DLI management c", @@ -311,8 +320,8 @@ "title":"Viewing Basic Information About a Queue", "uri":"dli_01_0663.html", "doc_type":"usermanual", - "p_code":"34", - "code":"35" + "p_code":"35", + "code":"36" }, { "desc":"Administrators and queue owners have full operation permissions on queues. They can grant operation permissions to other users based on service needs. This ensures that u", @@ -320,8 +329,8 @@ "title":"Queue Permission Management", "uri":"dli_01_0015.html", "doc_type":"usermanual", - "p_code":"34", - "code":"36" + "p_code":"35", + "code":"37" }, { "desc":"You can create enterprise projects matching the organizational structure of your enterprises to centrally manage cloud resources across regions by project. Then you can c", @@ -329,8 +338,8 @@ "title":"Allocating a Queue to an Enterprise Project", "uri":"dli_01_0565.html", "doc_type":"usermanual", - "p_code":"34", - "code":"37" + "p_code":"35", + "code":"38" }, { "desc":"Once you have created an SMN topic, you can easily subscribe to it by going to the Topic Management > Topics page of the SMN console. You can choose to receive notificati", @@ -338,35 +347,44 @@ "title":"Creating an SMN Topic", "uri":"dli_01_0421.html", "doc_type":"usermanual", - "p_code":"34", - "code":"38" + "p_code":"35", + "code":"39" }, { - "desc":"A tag is a key-value pair that you can customize to identify cloud resources. It helps you to classify and search for cloud resources. A tag consists of a tag key and a t", + "desc":"A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value.If you use ", "product_code":"dli", "title":"Managing Queue Tags", "uri":"dli_01_0022.html", "doc_type":"usermanual", - "p_code":"34", - "code":"39" + "p_code":"35", + "code":"40" }, { - "desc":"DLI allows you to set properties for queues.You can set Spark driver parameters to improve the scheduling efficiency of queues.This section describes how to set queue pro", + "desc":"DLI allows you to set properties for queues.You can currently set the following property parameters:Spark driver parameters: Set them to improve the scheduling efficiency", "product_code":"dli", "title":"Setting Queue Properties", "uri":"dli_01_0563.html", "doc_type":"usermanual", - "p_code":"34", - "code":"40" + "p_code":"35", + "code":"41" + }, + { + "desc":"Spark Native is a core component of Apache Spark designed to enhance the performance of Spark SQL computations. By utilizing vectorized C++ acceleration libraries, it acc", + "product_code":"dli", + "title":"Enabling Spark Native Operator Optimization", + "uri":"dli_01_0685.html", + "doc_type":"usermanual", + "p_code":"35", + "code":"42" }, { "desc":"DLI's address connectivity testing feature can be used to verify network connectivity between DLI queues and destination addresses.This feature is typically utilized for ", "product_code":"dli", - "title":"Testing Address Connectivity", + "title":"Testing the Network Connectivity Between a Queue and a Data Source", "uri":"dli_01_0489.html", "doc_type":"usermanual", - "p_code":"34", - "code":"41" + "p_code":"35", + "code":"43" }, { "desc":"You can delete a queue based on actual conditions.This operation will fail if there are jobs in the Submitting or Running state on this queue.Deleting a queue does not ca", @@ -374,35 +392,35 @@ "title":"Deleting a Queue", "uri":"dli_01_0016.html", "doc_type":"usermanual", - "p_code":"34", - "code":"42" + "p_code":"35", + "code":"44" }, { - "desc":"Newly created queues need to run jobs before they can be scaled in or out.The operations described in this section only apply to standard queues.Queues with 16 CUs do not", + "desc":"Newly created queues need to run jobs before they can be scaled in or out.The operations described in this section only apply to queues in non-elastic resource pools.Queu", "product_code":"dli", - "title":"Auto Scaling of Standard Queues", + "title":"Enabling Elastic Scaling for a Queue in a Non-Elastic Resource Pool", "uri":"dli_01_0487.html", "doc_type":"usermanual", - "p_code":"34", - "code":"43" + "p_code":"35", + "code":"45" }, { "desc":"When services are busy, you might need to use more compute resources to process services in a period. After this period, you do not require the same amount of resources. ", "product_code":"dli", - "title":"Setting a Scheduled Auto Scaling Task for a Standard Queue", + "title":"Creating a Scheduled Elastic Scaling Task for a Queue in a Non-Elastic Resource Pool", "uri":"dli_01_0488.html", "doc_type":"usermanual", - "p_code":"34", - "code":"44" + "p_code":"35", + "code":"46" }, { "desc":"If the CIDR block of the DLI queue conflicts with that of the user data source, you can change the CIDR block of the queue.If the queue whose CIDR block is to be modified", "product_code":"dli", - "title":"Changing the CIDR Block for a Standard Queue", + "title":"Changing the CIDR Block of a Queue in a Non-Elastic Resource Pool", "uri":"dli_01_0443.html", "doc_type":"usermanual", - "p_code":"34", - "code":"45" + "p_code":"35", + "code":"47" }, { "desc":"This section walks you through the procedure of adding a queue to an elastic resource pool and binding an enhanced datasource connection to the elastic resource pool.Proc", @@ -410,8 +428,8 @@ "title":"Example Use Case: Creating an Elastic Resource Pool and Running Jobs", "uri":"dli_01_0515.html", "doc_type":"usermanual", - "p_code":"21", - "code":"46" + "p_code":"22", + "code":"48" }, { "desc":"A company has multiple departments that perform data analysis in different periods during a day.Department A requires a large number of compute resources from 00:00 a.m. ", @@ -419,26 +437,26 @@ "title":"Example Use Case: Configuring Scaling Policies for Queues in an Elastic Resource Pool", "uri":"dli_01_0516.html", "doc_type":"usermanual", - "p_code":"21", - "code":"47" + "p_code":"22", + "code":"49" }, { "desc":"Queues in the non-elastic resource pool mode are the previous-gen of resource management for DLI. It involved purchasing and releasing resources based on usage demands, r", "product_code":"dli", - "title":"Creating a Non-Elastic Resource Pool Queue (Discarded and Not Recommended)", + "title":"Creating a Non-Elastic Resource Pool Queue (Deprecated, Not Recommended)", "uri":"dli_01_0363.html", "doc_type":"usermanual", - "p_code":"21", - "code":"48" + "p_code":"22", + "code":"50" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dli", - "title":"Creating Databases and Tables", + "title":"Creating a Data Directory, Database, and Table", "uri":"dli_01_0390.html", "doc_type":"usermanual", "p_code":"", - "code":"49" + "code":"51" }, { "desc":"Databases and tables are the basis for developing SQL and Spark jobs. Before running a job, you need to define databases and tables based on your service scenarios.Flink ", @@ -446,26 +464,44 @@ "title":"Understanding Data Catalogs, Databases, and Tables", "uri":"dli_01_0228.html", "doc_type":"usermanual", - "p_code":"49", - "code":"50" + "p_code":"51", + "code":"52" }, { - "desc":"A database, built on the computer storage device, is a data warehouse where data is organized, stored, and managed based on its structure.The table is an important part o", + "desc":"A database is a repository of data organized, stored, and managed on computer storage devices according to data structures.A table is one of the most essential components", "product_code":"dli", - "title":"Creating a Database and Table on the DLI Console", + "title":"Creating a Data Catalog, Database, and Table on the DLI Console", "uri":"dli_01_0005.html", "doc_type":"usermanual", - "p_code":"49", - "code":"51" + "p_code":"51", + "code":"53" }, { - "desc":"Metadata is used to define data types. It describes information about the data, including the source, size, format, and other data features. In database fields, metadata ", + "desc":"Metadata is data used to define the type of data. It primarily describes information about the data itself, including its source, size, format, or other characteristics. ", "product_code":"dli", "title":"Viewing Table Metadata", "uri":"dli_01_0008.html", "doc_type":"usermanual", - "p_code":"49", - "code":"52" + "p_code":"51", + "code":"54" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dli", + "title":"Managing Data Catalogs on the DLI Console", + "uri":"dli_01_0671.html", + "doc_type":"usermanual", + "p_code":"51", + "code":"55" + }, + { + "desc":"DLI data catalogs support authorization on the DLI console or authentication through IAM. By setting permissions, you can grant varying data catalog permissions to differ", + "product_code":"dli", + "title":"Configuring Data Catalog Permissions on the DLI Console", + "uri":"dli_01_0672.html", + "doc_type":"usermanual", + "p_code":"55", + "code":"56" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -473,8 +509,8 @@ "title":"Managing Database Resources on the DLI Console", "uri":"dli_01_0004.html", "doc_type":"usermanual", - "p_code":"49", - "code":"53" + "p_code":"51", + "code":"57" }, { "desc":"By setting permissions, you can assign varying database permissions to different users.The administrator and database owner have all permissions, which cannot be set or m", @@ -482,17 +518,17 @@ "title":"Configuring Database Permissions on the DLI Console", "uri":"dli_01_0447.html", "doc_type":"usermanual", - "p_code":"53", - "code":"54" + "p_code":"57", + "code":"58" }, { - "desc":"You can delete databases as needed.You are not allowed to delete databases or tables that are being used for running jobs.The administrator, database owner, and users wit", + "desc":"You can delete an unused database from the DLI console: when a database is no longer needed, such as after a test database has completed testing; if a database has errors", "product_code":"dli", "title":"Deleting a Database on the DLI Console", "uri":"dli_01_0011.html", "doc_type":"usermanual", - "p_code":"53", - "code":"55" + "p_code":"57", + "code":"59" }, { "desc":"In practical use, developers create databases and tables, which are then handed over to testers for testing. Once testing is complete, the databases and tables are handed", @@ -500,17 +536,17 @@ "title":"Changing the Database Owner on the DLI Console", "uri":"dli_01_0376.html", "doc_type":"usermanual", - "p_code":"53", - "code":"56" + "p_code":"57", + "code":"60" }, { - "desc":"A tag is a key-value pair that you can customize to identify cloud resources. It helps you to classify and search for cloud resources. A tag consists of a tag key and a t", + "desc":"A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value. If you use", "product_code":"dli", - "title":"Managing Tags", + "title":"Managing Tags for Database Tables", "uri":"dli_01_0552.html", "doc_type":"usermanual", - "p_code":"53", - "code":"57" + "p_code":"57", + "code":"61" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -518,8 +554,8 @@ "title":"Managing Table Resources on the DLI Console", "uri":"dli_01_0625.html", "doc_type":"usermanual", - "p_code":"49", - "code":"58" + "p_code":"51", + "code":"62" }, { "desc":"By setting permissions, you can assign varying table permissions to different users.The administrator and table owner have all permissions, which cannot be set or modifie", @@ -527,17 +563,17 @@ "title":"Configuring Table Permissions on the DLI Console", "uri":"dli_01_0448.html", "doc_type":"usermanual", - "p_code":"58", - "code":"59" + "p_code":"62", + "code":"63" }, { - "desc":"You can delete tables as needed.Databases or tables that are being used for running jobs cannot be deleted.Only administrators, table owners, and users with table deletio", + "desc":"You can delete an unused data table from the DLI console: when a data table is no longer needed, such as after a test data table has completed testing; if a data table ha", "product_code":"dli", "title":"Deleting a Table on the DLI Console", "uri":"dli_01_0626.html", "doc_type":"usermanual", - "p_code":"58", - "code":"60" + "p_code":"62", + "code":"64" }, { "desc":"In practical use, developers create databases and tables, which are then handed over to testers for testing. Once testing is complete, the databases and tables are handed", @@ -545,17 +581,17 @@ "title":"Changing the Table Owner on the DLI Console", "uri":"dli_01_0627.html", "doc_type":"usermanual", - "p_code":"58", - "code":"61" + "p_code":"62", + "code":"65" }, { - "desc":"This section describes how to import data stored in OBS to a table on the DLI console.Only one path can be specified during data import. The path cannot contain commas (,", + "desc":"This section describes how to import data stored in OBS to a table on the DLI console. Data can be imported to both DLI tables (table type: MANAGED) and OBS tables (table", "product_code":"dli", - "title":"Importing OBS Data to DLI", + "title":"Importing OBS Data to a DLI Table", "uri":"dli_01_0253.html", "doc_type":"usermanual", - "p_code":"58", - "code":"62" + "p_code":"62", + "code":"66" }, { "desc":"You can export data from a DLI table to OBS. During the export, a folder is created in OBS or the content in the existing folder is overwritten.The exported file can be i", @@ -563,8 +599,8 @@ "title":"Exporting DLI Table Data to OBS", "uri":"dli_01_0010.html", "doc_type":"usermanual", - "p_code":"58", - "code":"63" + "p_code":"62", + "code":"67" }, { "desc":"The Preview page displays the first 10 records in the table.You can preview data on either the Data Management page or the SQL Editor page.To preview data on the Data Man", @@ -572,17 +608,17 @@ "title":"Previewing Table Data on the DLI Console", "uri":"dli_01_0007.html", "doc_type":"usermanual", - "p_code":"58", - "code":"64" + "p_code":"62", + "code":"68" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dli", - "title":"Data Migration and Transmission", + "title":"Data Import and Migration", "uri":"dli_01_0661.html", "doc_type":"usermanual", "p_code":"", - "code":"65" + "code":"69" }, { "desc":"DLI enables direct access to data stored in OBS for query and analysis, eliminating the need for data migration.To begin using DLI for data analysis, just import your loc", @@ -590,8 +626,35 @@ "title":"Overview", "uri":"dli_01_0662.html", "doc_type":"usermanual", - "p_code":"65", - "code":"66" + "p_code":"69", + "code":"70" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dli", + "title":"Migrating Data from External Data Sources to DLI", + "uri":"dli_01_0631.html", + "doc_type":"usermanual", + "p_code":"69", + "code":"71" + }, + { + "desc":"To centrally analyze and manage scattered data from various systems, you can utilize migration tools like Cloud Data Migration (CDM) to migrate the data to DLI. Once the ", + "product_code":"dli", + "title":"Overview of Data Migration Scenarios", + "uri":"dli_01_0632.html", + "doc_type":"usermanual", + "p_code":"71", + "code":"72" + }, + { + "desc":"On its GUI, CDM enables you to create data migration tasks from multiple data sources to a data lake.This section describes how to use CDM to migrate data from data sourc", + "product_code":"dli", + "title":"Using CDM to Migrate Data to DLI", + "uri":"dli_01_0633.html", + "doc_type":"usermanual", + "p_code":"71", + "code":"73" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -599,8 +662,8 @@ "title":"Configuring DLI to Read and Write Data from and to External Data Sources", "uri":"dli_01_0634.html", "doc_type":"usermanual", - "p_code":"65", - "code":"67" + "p_code":"", + "code":"74" }, { "desc":"To read and write external data sources when running DLI jobs, two conditions must be met:Establish network connectivity between DLI and the external data source to ensur", @@ -608,8 +671,8 @@ "title":"Configuring DLI to Read and Write External Data Sources", "uri":"dli_01_0635.html", "doc_type":"usermanual", - "p_code":"67", - "code":"68" + "p_code":"74", + "code":"75" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -617,17 +680,17 @@ "title":"Configuring the Network Connection Between DLI and Data Sources (Enhanced Datasource Connection)", "uri":"dli_01_0426.html", "doc_type":"usermanual", - "p_code":"67", - "code":"69" + "p_code":"74", + "code":"76" }, { - "desc":"In cross-source data analysis scenarios, DLI needs to connect to external data sources. However, due to the different VPCs between the data source and DLI, the network ca", + "desc":"Imagine DLI elastic resource pools and data sources as two isolated islands surrounded by water.To enable traffic between these two islands, you need to first construct a", "product_code":"dli", "title":"Overview of Enhanced Datasource Connections", "uri":"dli_01_0003.html", "doc_type":"usermanual", - "p_code":"69", - "code":"70" + "p_code":"76", + "code":"77" }, { "desc":"Create an enhanced datasource connection for DLI to access, import, query, and analyze data of other data sources.For example, to connect DLI to the MRS, RDS, CSS, Kafka,", @@ -635,8 +698,8 @@ "title":"Creating an Enhanced Datasource Connection", "uri":"dli_01_0006.html", "doc_type":"usermanual", - "p_code":"69", - "code":"71" + "p_code":"76", + "code":"78" }, { "desc":"If DLI needs to access external data sources, you need to establish enhanced datasource connections to enable the network between DLI and the data sources, and then devel", @@ -644,17 +707,26 @@ "title":"Common Development Methods for DLI Cross-Source Analysis", "uri":"dli_01_0410.html", "doc_type":"usermanual", - "p_code":"69", - "code":"72" + "p_code":"76", + "code":"79" }, { - "desc":"When using DLI to submit jobs that involve reading and writing data from external sources, it is crucial to securely access these sources by properly storing their access", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dli", - "title":"Using DEW to Manage Access Credentials for Data Sources", + "title":"Managing Data Source Access Credentials Using DEW", "uri":"dli_01_0636.html", "doc_type":"usermanual", - "p_code":"67", - "code":"73" + "p_code":"74", + "code":"80" + }, + { + "desc":"When submitting Flink or Spark jobs through DLI to access external data sources (such as OBS and Kafka), there is a risk of plaintext exposure if AK/SK, usernames/passwor", + "product_code":"dli", + "title":"Overview", + "uri":"dli_01_0687.html", + "doc_type":"usermanual", + "p_code":"80", + "code":"81" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -662,8 +734,8 @@ "title":"Using DLI Datasource Authentication to Manage Access Credentials for Data Sources", "uri":"dli_01_0422.html", "doc_type":"usermanual", - "p_code":"67", - "code":"74" + "p_code":"74", + "code":"82" }, { "desc":"When analyzing across multiple sources, you are advised not to configure authentication information directly in a job as it can lead to password leakage. Instead, you are", @@ -671,8 +743,8 @@ "title":"Overview", "uri":"dli_01_0561.html", "doc_type":"usermanual", - "p_code":"74", - "code":"75" + "p_code":"82", + "code":"83" }, { "desc":"Create a CSS datasource authentication on the DLI console to store the authentication information of the CSS security cluster to DLI. This will allow you to access to the", @@ -680,8 +752,8 @@ "title":"Creating a CSS Datasource Authentication", "uri":"dli_01_0427.html", "doc_type":"usermanual", - "p_code":"74", - "code":"76" + "p_code":"82", + "code":"84" }, { "desc":"Create a Kerberos datasource authentication on the DLI console to store the authentication information of the data source to DLI. This will allow you to access to the dat", @@ -689,8 +761,8 @@ "title":"Creating a Kerberos Datasource Authentication", "uri":"dli_01_0558.html", "doc_type":"usermanual", - "p_code":"74", - "code":"77" + "p_code":"82", + "code":"85" }, { "desc":"Create a Kafka_SSL datasource authentication on the DLI console to store the Kafka authentication information to DLI. This will allow you to access to Kafka instances wit", @@ -698,8 +770,8 @@ "title":"Creating a Kafka_SSL Datasource Authentication", "uri":"dli_01_0560.html", "doc_type":"usermanual", - "p_code":"74", - "code":"78" + "p_code":"82", + "code":"86" }, { "desc":"Create a password datasource authentication on the DLI console to store passwords of the GaussDB(DWS), RDS, DCS, and DDS data sources to DLI. This will allow you to acces", @@ -707,8 +779,8 @@ "title":"Creating a Password Datasource Authentication", "uri":"dli_01_0559.html", "doc_type":"usermanual", - "p_code":"74", - "code":"79" + "p_code":"82", + "code":"87" }, { "desc":"Grant permissions on a datasource authentication to users so multiple user jobs can use the datasource authentication without affecting each other.The administrator and t", @@ -716,8 +788,8 @@ "title":"Datasource Authentication Permission Management", "uri":"dli_01_0480.html", "doc_type":"usermanual", - "p_code":"74", - "code":"80" + "p_code":"82", + "code":"88" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -725,8 +797,8 @@ "title":"Managing Enhanced Datasource Connections", "uri":"dli_01_0509.html", "doc_type":"usermanual", - "p_code":"67", - "code":"81" + "p_code":"74", + "code":"89" }, { "desc":"After creating an enhanced datasource connection, you can view and manage it on the management console.This section describes how to view basic information about an enhan", @@ -734,8 +806,8 @@ "title":"Viewing Basic Information About an Enhanced Datasource Connection", "uri":"dli_01_0623.html", "doc_type":"usermanual", - "p_code":"81", - "code":"82" + "p_code":"89", + "code":"90" }, { "desc":"Enhanced connections support user authorization by project. After authorization, users in the project have the permission to perform operations on the enhanced connection", @@ -743,35 +815,44 @@ "title":"Enhanced Connection Permission Management", "uri":"dli_01_0018.html", "doc_type":"usermanual", - "p_code":"81", - "code":"83" + "p_code":"89", + "code":"91" }, { - "desc":"Bind an elastic resource pool to a queue to connect the queue to a target data source. When an enhanced datasource connection is no longer needed, unbind the queue that w", + "desc":"To connect other resource pools to data sources through enhanced datasource connections, bind enhanced datasource connections to resource pools on the Enhanced tab page.T", "product_code":"dli", - "title":"Binding or Unbinding an Enhanced Datasource Connection to a Queue", - "uri":"dli_01_0514.html", + "title":"Binding an Enhanced Datasource Connection to an Elastic Resource Pool", + "uri":"dli_01_0009.html", "doc_type":"usermanual", - "p_code":"81", - "code":"84" + "p_code":"89", + "code":"92" }, { - "desc":"A route is configured with the destination, next hop type, and next hop to determine where the network traffic is directed. Routes are classified into system routes and c", + "desc":"Unbind an enhanced datasource connection from an elastic resource pool that does not need to access a data source through an enhanced datasoruce connection.If the status ", + "product_code":"dli", + "title":"Unbinding an Enhanced Datasource Connection from an Elastic Resource Pool", + "uri":"dli_01_0555.html", + "doc_type":"usermanual", + "p_code":"89", + "code":"93" + }, + { + "desc":"Enhanced datasource connections establish peering connections between DLI elastic resource pools and data sources to interconnect two VPC networks. If we liken these peer", "product_code":"dli", "title":"Adding a Route for an Enhanced Datasource Connection", "uri":"dli_01_0014.html", "doc_type":"usermanual", - "p_code":"81", - "code":"85" + "p_code":"89", + "code":"94" }, { - "desc":"Delete a route that is no longer used.A custom route table cannot be deleted if it is associated with a subnet.Log in to the DLI management console.In the left navigation", + "desc":"Delete a route that is no longer used.A custom route table cannot be deleted if it is associated with a subnet.Log in to the DLI management console.In the navigation pane", "product_code":"dli", "title":"Deleting the Route for an Enhanced Datasource Connection", "uri":"dli_01_0556.html", "doc_type":"usermanual", - "p_code":"81", - "code":"86" + "p_code":"89", + "code":"95" }, { "desc":"Host information is the mapping between host IP addresses and domain names. After you configure host information, jobs can only use the configured domain names to access ", @@ -779,26 +860,26 @@ "title":"Modifying Host Information in an Elastic Resource Pool", "uri":"dli_01_0013.html", "doc_type":"usermanual", - "p_code":"81", - "code":"87" + "p_code":"89", + "code":"96" }, { - "desc":"A tag is a key-value pair customized by users and used to identify cloud resources. It helps users to classify and search for cloud resources. A tag consists of a tag key", + "desc":"A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value.If you use ", "product_code":"dli", "title":"Enhanced Datasource Connection Tag Management", "uri":"dli_01_0019.html", "doc_type":"usermanual", - "p_code":"81", - "code":"88" + "p_code":"89", + "code":"97" }, { - "desc":"Delete an enhanced datasource connection that is no longer used on the console.Log in to the DLI management console.In the left navigation pane, choose Datasource Connect", + "desc":"Delete an enhanced datasource connection that is no longer used on the console.Log in to the DLI management console.In the navigation pane on the left, choose Datasource ", "product_code":"dli", "title":"Deleting an Enhanced Datasource Connection", "uri":"dli_01_0553.html", "doc_type":"usermanual", - "p_code":"81", - "code":"89" + "p_code":"89", + "code":"98" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -807,7 +888,7 @@ "uri":"dli_01_0486.html", "doc_type":"usermanual", "p_code":"", - "code":"90" + "code":"99" }, { "desc":"Cloud services often interact with each other, with some of which dependent on other services. You can create an agency to delegate DLI to use other cloud services and pe", @@ -815,8 +896,8 @@ "title":"DLI Agency Overview", "uri":"dli_01_0419.html", "doc_type":"usermanual", - "p_code":"90", - "code":"91" + "p_code":"99", + "code":"100" }, { "desc":"When Flink 1.15, Spark 3.3, or a later version is used to execute jobs and the required agency is not included in the DLI system agency dli_management_agency, you need to", @@ -824,8 +905,8 @@ "title":"Creating a Custom DLI Agency", "uri":"dli_01_0616.html", "doc_type":"usermanual", - "p_code":"90", - "code":"92" + "p_code":"99", + "code":"101" }, { "desc":"This section provides agency permission policies for common scenarios, which can be used to configure agency permission policies when you customize your permissions. The ", @@ -833,26 +914,26 @@ "title":"Agency Permission Policies in Common Scenarios", "uri":"dli_01_0617.html", "doc_type":"usermanual", - "p_code":"90", - "code":"93" + "p_code":"99", + "code":"102" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dli", - "title":"Submitting a SQL Job Using DLI", + "title":"Submitting a SQL Job on the DLI Management Console", "uri":"dli_01_0402.html", "doc_type":"usermanual", "p_code":"", - "code":"94" + "code":"103" }, { - "desc":"The SQL Editor allows you to execute data query operations using SQL statements.It supports SQL:2003 and is compatible with Spark SQL.To access the SQL editor, choose SQL", + "desc":"DLI offers a SQL editor for executing data query operations using SQL statements.This section describes how to create and submit a SQL job using the DLI SQL editor.Before", "product_code":"dli", "title":"Creating and Submitting a SQL Job", "uri":"dli_01_0320.html", "doc_type":"usermanual", - "p_code":"94", - "code":"95" + "p_code":"103", + "code":"104" }, { "desc":"Store the data results of analyzed SQL jobs in a specified location in the desired format.By default, DLI stores SQL job results in its job bucket. You can also download ", @@ -860,8 +941,17 @@ "title":"Exporting SQL Job Results", "uri":"dli_01_0621.html", "doc_type":"usermanual", - "p_code":"94", - "code":"96" + "p_code":"103", + "code":"105" + }, + { + "desc":"There are numerous SQL engines in the big data field, which bring diversity to the solutions but also expose some issues such as varying quality of SQL input statements, ", + "product_code":"dli", + "title":"Creating a SQL Inspection Rule", + "uri":"dli_01_0612.html", + "doc_type":"usermanual", + "p_code":"103", + "code":"106" }, { "desc":"In actual job running, it is necessary to prioritize and ensure the normal running of important and urgent tasks due to their varying levels of importance and urgency. Th", @@ -869,8 +959,8 @@ "title":"Setting the Priority for a SQL Job", "uri":"dli_01_0535.html", "doc_type":"usermanual", - "p_code":"94", - "code":"97" + "p_code":"103", + "code":"107" }, { "desc":"DLI job buckets are used to store temporary data generated during DLI job running, such as job logs and results.This section describes how to configure a bucket for DLI j", @@ -878,8 +968,8 @@ "title":"Querying Logs for SQL Jobs", "uri":"dli_01_0637.html", "doc_type":"usermanual", - "p_code":"94", - "code":"98" + "p_code":"103", + "code":"108" }, { "desc":"The SQL Jobs page displays all SQL jobs, which may span multiple pages if there are many jobs. You can navigate to a specific page as needed. DLI allows you to view jobs ", @@ -887,8 +977,8 @@ "title":"Managing SQL Jobs", "uri":"dli_01_0017.html", "doc_type":"usermanual", - "p_code":"94", - "code":"99" + "p_code":"103", + "code":"109" }, { "desc":"A SQL execution plan is a logical flowchart of a database query that shows how a database management system executes a specific SQL query. The execution plan details the ", @@ -896,8 +986,8 @@ "title":"Viewing a SQL Execution Plan", "uri":"dli_01_0638.html", "doc_type":"usermanual", - "p_code":"94", - "code":"100" + "p_code":"103", + "code":"110" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -905,17 +995,17 @@ "title":"Creating and Managing SQL Job Templates", "uri":"dli_01_05110.html", "doc_type":"usermanual", - "p_code":"94", - "code":"101" + "p_code":"103", + "code":"111" }, { - "desc":"To facilitate SQL operation execution, DLI allows you to customize query templates or save the SQL statements in use as templates. After templates are saved, you do not n", + "desc":"DLI allows you to create custom templates or save currently used SQL statements as templates for quick and convenient SQL operations. Once a template is saved, you can ex", "product_code":"dli", "title":"Creating a SQL Job Template", "uri":"dli_01_0021.html", "doc_type":"usermanual", - "p_code":"101", - "code":"102" + "p_code":"111", + "code":"112" }, { "desc":"DLI allows you to create custom templates or save currently used SQL statements as templates for quick and convenient SQL operations. Once a template is saved, you can ex", @@ -923,8 +1013,8 @@ "title":"Developing and Submitting a SQL Job Using a SQL Job Template", "uri":"dli_01_0639.html", "doc_type":"usermanual", - "p_code":"101", - "code":"103" + "p_code":"111", + "code":"113" }, { "desc":"TPC-H is a test set developed by the Transaction Processing Performance Council (TPC) to simulate decision-making support applications. It is widely used in academia and ", @@ -932,17 +1022,17 @@ "title":"TPC-H Sample Data in the SQL Templates Preset on DLI", "uri":"dli_01_05111.html", "doc_type":"usermanual", - "p_code":"101", - "code":"104" + "p_code":"111", + "code":"114" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dli", - "title":"Submitting a Flink Job Using DLI", + "title":"Submitting a Flink Job on the DLI Management Console", "uri":"dli_01_0389.html", "doc_type":"usermanual", "p_code":"", - "code":"105" + "code":"115" }, { "desc":"DLI supports two types of Flink jobs:Flink OpenSource SQL job:It is fully compatible with Flink of the community edition, ensuring that jobs can run smoothly on these Fli", @@ -950,8 +1040,8 @@ "title":"Flink Job Overview", "uri":"dli_01_0403.html", "doc_type":"usermanual", - "p_code":"105", - "code":"106" + "p_code":"115", + "code":"116" }, { "desc":"This section describes how to create a Flink OpenSource SQL job.DLI Flink OpenSource SQL jobs are fully compatible with the syntax of Flink provided by the community. In ", @@ -959,8 +1049,8 @@ "title":"Creating a Flink OpenSource SQL Job", "uri":"dli_01_0498.html", "doc_type":"usermanual", - "p_code":"105", - "code":"107" + "p_code":"115", + "code":"117" }, { "desc":"A Flink Jar job involves developing a custom application Jar package based on Flink's capabilities and submitting it to a DLI queue for execution.To create a Flink Jar jo", @@ -968,8 +1058,8 @@ "title":"Creating a Flink Jar Job", "uri":"dli_01_0457.html", "doc_type":"usermanual", - "p_code":"105", - "code":"108" + "p_code":"115", + "code":"118" }, { "desc":"You can isolate Flink jobs allocated to different users by setting permissions to ensure data query performance.The administrator and job creator have all permissions, wh", @@ -977,8 +1067,8 @@ "title":"Configuring Flink Job Permissions", "uri":"dli_01_0479.html", "doc_type":"usermanual", - "p_code":"105", - "code":"109" + "p_code":"115", + "code":"119" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -986,8 +1076,8 @@ "title":"Managing Flink Jobs", "uri":"dli_01_0377.html", "doc_type":"usermanual", - "p_code":"105", - "code":"110" + "p_code":"115", + "code":"120" }, { "desc":"After creating a Flink job, you can check the basic information, job details, task list, and execution plan of the job on the DLI console.This section describes how to ch", @@ -995,8 +1085,8 @@ "title":"Viewing Flink Job Details", "uri":"dli_01_0462.html", "doc_type":"usermanual", - "p_code":"110", - "code":"111" + "p_code":"120", + "code":"121" }, { "desc":"In actual job running, it is necessary to prioritize and ensure the normal running of important and urgent tasks due to their varying levels of importance and urgency. Th", @@ -1004,8 +1094,8 @@ "title":"Setting the Priority for a Flink Job", "uri":"dli_01_0650.html", "doc_type":"usermanual", - "p_code":"110", - "code":"112" + "p_code":"120", + "code":"122" }, { "desc":"In actual job operations, the compute resources required by a job vary depending on the data volume. As a result, compute resources are wasted when the volume is small an", @@ -1013,8 +1103,8 @@ "title":"Enabling Dynamic Scaling for Flink Jobs", "uri":"dli_01_0534.html", "doc_type":"usermanual", - "p_code":"110", - "code":"113" + "p_code":"120", + "code":"123" }, { "desc":"DLI job buckets are used to store temporary data generated during DLI job running, such as job logs and results.This section describes how to configure a bucket for DLI j", @@ -1022,8 +1112,8 @@ "title":"Querying Logs for Flink Jobs", "uri":"dli_01_0651.html", "doc_type":"usermanual", - "p_code":"110", - "code":"114" + "p_code":"120", + "code":"124" }, { "desc":"After creating a job, you can manage it by performing various operations such as editing its basic information, starting or stopping it, and importing or exporting it.You", @@ -1031,8 +1121,8 @@ "title":"Common Operations of Flink Jobs", "uri":"dli_01_0461.html", "doc_type":"usermanual", - "p_code":"110", - "code":"115" + "p_code":"120", + "code":"125" }, { "desc":"Flink templates include sample templates and custom templates. You can modify an existing sample template to meet the actual job logic requirements and save time for edit", @@ -1040,35 +1130,35 @@ "title":"Managing Flink Job Templates", "uri":"dli_01_0464.html", "doc_type":"usermanual", - "p_code":"105", - "code":"116" + "p_code":"115", + "code":"126" }, { - "desc":"A tag is a key-value pair customized by users and used to identify cloud resources. It helps users to classify and search for cloud resources. A tag consists of a tag key", + "desc":"A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value.DLI allows ", "product_code":"dli", "title":"Adding Tags to a Flink Job", "uri":"dli_01_0463.html", "doc_type":"usermanual", - "p_code":"105", - "code":"117" + "p_code":"115", + "code":"127" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dli", - "title":"Submitting a Spark Job Using DLI", + "title":"Submitting a Spark Job on the DLI Management Console", "uri":"dli_01_0465.html", "doc_type":"usermanual", "p_code":"", - "code":"118" + "code":"128" }, { - "desc":"DLI provides fully-managed Spark computing services by allowing you to execute Spark jobs.On the Overview page, click Create Job in the upper right corner of the Spark Jo", + "desc":"DLI Spark jobs provide fully managed Spark computing services.On the Overview page, click Create Job in the upper right corner of the Spark Jobs tab or click Create Job i", "product_code":"dli", "title":"Creating a Spark Job", "uri":"dli_01_0384.html", "doc_type":"usermanual", - "p_code":"118", - "code":"119" + "p_code":"128", + "code":"129" }, { "desc":"In actual job running, it is necessary to prioritize and ensure the normal running of important and urgent tasks due to their varying levels of importance and urgency. Th", @@ -1076,8 +1166,8 @@ "title":"Setting the Priority for a Spark Job", "uri":"dli_01_0652.html", "doc_type":"usermanual", - "p_code":"118", - "code":"120" + "p_code":"128", + "code":"130" }, { "desc":"DLI job buckets are used to store temporary data generated during DLI job running, such as job logs and results.This section describes how to configure a bucket for DLI j", @@ -1085,8 +1175,8 @@ "title":"Querying Logs for Spark Jobs", "uri":"dli_01_0379.html", "doc_type":"usermanual", - "p_code":"118", - "code":"121" + "p_code":"128", + "code":"131" }, { "desc":"On the Overview page, click Spark Jobs to go to the SQL job management page. Alternatively, you can click Job Management > Spark Jobs. The page displays all Spark jobs. I", @@ -1094,8 +1184,8 @@ "title":"Managing Spark Jobs", "uri":"dli_01_0385.html", "doc_type":"usermanual", - "p_code":"118", - "code":"122" + "p_code":"128", + "code":"132" }, { "desc":"You can modify a sample template to meet the Spark job requirements, saving time for editing SQL statements.Currently, the cloud platform does not provide preset Spark te", @@ -1103,53 +1193,17 @@ "title":"Managing Spark Job Templates", "uri":"dli_01_0551.html", "doc_type":"usermanual", - "p_code":"118", - "code":"123" + "p_code":"128", + "code":"133" }, { "desc":"This section describes metrics reported by DLI to Cloud Eye as well as their namespaces and dimensions. You can use the management console or APIs provided by Cloud Eye t", "product_code":"dli", - "title":"Using Cloud Eye to Monitor DLI", + "title":"Monitoring DLI Using Cloud Eye", "uri":"dli_01_0445.html", "doc_type":"usermanual", "p_code":"", - "code":"124" - }, - { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "product_code":"dli", - "title":"Using AOM to Monitor DLI", - "uri":"dli_01_0664.html", - "doc_type":"usermanual", - "p_code":"", - "code":"125" - }, - { - "desc":"AOM's Prometheus Monitoring is a comprehensive solution that integrates with the open source Prometheus ecosystem. It supports monitoring of various types of components, ", - "product_code":"dli", - "title":"Connecting DLI to AOM's Prometheus Monitoring", - "uri":"dli_01_0665.html", - "doc_type":"usermanual", - "p_code":"125", - "code":"126" - }, - { - "desc":"When connecting DLI to AOM's Prometheus Monitoring, the system automatically configures the parameters listed in table 1 in Configuration Items for Connecting DLI to AOM'", - "product_code":"dli", - "title":"Configuration Items for Connecting DLI to AOM's Prometheus Monitoring", - "uri":"dli_01_0666.html", - "doc_type":"usermanual", - "p_code":"125", - "code":"127" - }, - { - "desc":"Table 1 lists the basic monitoring metrics that are reported by DLI to Prometheus. AOM Prometheus can store these basic metrics for free.", - "product_code":"dli", - "title":"Basic Monitoring Metrics Reported by DLI to Prometheus", - "uri":"dli_01_0667.html", - "doc_type":"usermanual", - "p_code":"125", - "code":"128" + "code":"134" }, { "desc":"With CTS, you can log operations related to DLI, making it easier to search, audit, and trace in the future.", @@ -1158,61 +1212,115 @@ "uri":"dli_01_0318.html", "doc_type":"usermanual", "p_code":"", - "code":"129" + "code":"135" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dli", - "title":"Permissions Management", + "title":"DLI Permission Management", "uri":"dli_01_0408.html", "doc_type":"usermanual", "p_code":"", - "code":"130" + "code":"136" }, { - "desc":"DLI has a comprehensive permission control mechanism and supports fine-grained authentication through Identity and Access Management (IAM). You can create policies in IAM", + "desc":"DLI features two sets of permission systems. These two permission control mechanisms are used in conjunction, with their permissions overlapping and complementing each ot", "product_code":"dli", - "title":"Overview", + "title":"Overview of the DLI Permission System", "uri":"dli_01_0440.html", "doc_type":"usermanual", - "p_code":"130", - "code":"131" + "p_code":"136", + "code":"137" }, { - "desc":"Custom policies can be created as a supplement to the system policies of DLI. You can add actions to custom policies. For the actions supported for custom policies, see \"", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dli", - "title":"Creating a Custom Policy", - "uri":"dli_01_0451.html", + "title":"DLI Permission Management", + "uri":"dli_01_0689.html", "doc_type":"usermanual", - "p_code":"130", - "code":"132" + "p_code":"136", + "code":"138" }, { - "desc":"A resource is an object that exists within a service. You can select DLI resources by specifying their paths.", + "desc":"The permission management function of DLI itself primarily applies to the permission control of internal DLI resources, rather than relying on the unified identity authen", "product_code":"dli", - "title":"DLI Resources", - "uri":"dli_01_0417.html", + "title":"Overview", + "uri":"dli_01_0690.html", "doc_type":"usermanual", - "p_code":"130", - "code":"133" + "p_code":"138", + "code":"139" }, { - "desc":"Request conditions are useful in determining when a custom policy takes effect. A request condition consists of a condition key and operator. Condition keys are either gl", + "desc":"For details about authorization through the DLI console, see Managing Permissions.For details about authorization through the DLI console, see Queue Permission Management", "product_code":"dli", - "title":"DLI Request Conditions", + "title":"DLI Permissions", + "uri":"dli_01_0691.html", + "doc_type":"usermanual", + "p_code":"138", + "code":"140" + }, + { + "desc":"This section describes how to authorize resources on the DLI console.", + "product_code":"dli", + "title":"DLI Authorization Operation Guide", + "uri":"dli_01_0692.html", + "doc_type":"usermanual", + "p_code":"138", + "code":"141" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dli", + "title":"IAM Permission Management", "uri":"dli_01_0475.html", "doc_type":"usermanual", - "p_code":"130", - "code":"134" + "p_code":"136", + "code":"142" }, { - "desc":"Table 1 lists the common operations supported by each system policy of DLI. Choose proper system policies according to this table. For details about the SQL statement per", + "desc":"IAM is a foundational service for permission management, offering functions like user identity authentication, permission allocation, and access control, enabling you to ", "product_code":"dli", - "title":"Common Operations Supported by DLI System Policy", + "title":"Overview", + "uri":"dli_01_0417.html", + "doc_type":"usermanual", + "p_code":"142", + "code":"143" + }, + { + "desc":"In IAM, authorization entities are primarily categorized into users and user groups. Integration with enterprise projects enables resource isolation by group and facilita", + "product_code":"dli", + "title":"IAM Authorization Entity", + "uri":"dli_01_0693.html", + "doc_type":"usermanual", + "p_code":"142", + "code":"144" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dli", + "title":"IAM Permissions", "uri":"dli_01_0441.html", "doc_type":"usermanual", - "p_code":"130", - "code":"135" + "p_code":"142", + "code":"145" + }, + { + "desc":"The role/policy-based authorization model provided by Identity and Access Management (IAM) lets you control access to DLI resources. With IAM, you can:Based on the organi", + "product_code":"dli", + "title":"Using IAM Roles or Policies to Grant Access to DLI", + "uri":"dli_01_0451.html", + "doc_type":"usermanual", + "p_code":"142", + "code":"146" + }, + { + "desc":"An e-commerce company conducts data analysis operations in region A. The marketing department's employees, user 1 and user 2, along with the technical department's employ", + "product_code":"dli", + "title":"Example Use Case: Creating a User Group and Granting Permissions for Using DLI Elastic Resource Pools and Databases", + "uri":"dli_01_0695.html", + "doc_type":"usermanual", + "p_code":"136", + "code":"147" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1221,16 +1329,16 @@ "uri":"dli_01_0567.html", "doc_type":"usermanual", "p_code":"", - "code":"136" + "code":"148" }, { "desc":"To enhance the functions and performance of Spark and Flink jobs, you can create custom images by downloading the base images provided by DLI and adding dependencies (fil", "product_code":"dli", - "title":"Using a Custom Image to Enhance the Job Running Environment", + "title":"Enhancing the Job Runtime Environment Using a Custom Image", "uri":"dli_01_0494.html", "doc_type":"usermanual", - "p_code":"136", - "code":"137" + "p_code":"148", + "code":"149" }, { "desc":"DLI allows you to set variables that are frequently used during job development as global variables on the DLI management console. This avoids repeated definitions during", @@ -1238,8 +1346,8 @@ "title":"Managing DLI Global Variables", "uri":"dli_01_0476.html", "doc_type":"usermanual", - "p_code":"136", - "code":"138" + "p_code":"148", + "code":"150" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1247,8 +1355,8 @@ "title":"Managing Program Packages of Jar Jobs", "uri":"dli_01_0366.html", "doc_type":"usermanual", - "p_code":"136", - "code":"139" + "p_code":"148", + "code":"151" }, { "desc":"Before running DLI jobs, UDF JAR files or Jar job packages need to be uploaded to the cloud platform for unified management and maintenance.There are two ways to manage p", @@ -1256,8 +1364,8 @@ "title":"Package Management Overview", "uri":"dli_01_0407.html", "doc_type":"usermanual", - "p_code":"139", - "code":"140" + "p_code":"151", + "code":"152" }, { "desc":"DLI allows you to submit program packages in batches to the general-use queue for running.If you need to update a package, you can use the same package or file to upload ", @@ -1265,8 +1373,8 @@ "title":"Creating a DLI Package", "uri":"dli_01_0367.html", "doc_type":"usermanual", - "p_code":"139", - "code":"141" + "p_code":"151", + "code":"153" }, { "desc":"By configuring permissions, you can grant different package groups or packages to various users, ensuring that job efficiency remains unaffected and job performance is ma", @@ -1274,8 +1382,8 @@ "title":"Configuring DLI Package Permissions", "uri":"dli_01_0477.html", "doc_type":"usermanual", - "p_code":"139", - "code":"142" + "p_code":"151", + "code":"154" }, { "desc":"DLI allows you to change the owner of a package group or package.Log in to the DLI management console and choose Data Management > Package Management.On the Package Manag", @@ -1283,8 +1391,8 @@ "title":"Changing the DLI Package Owner", "uri":"dli_01_0478.html", "doc_type":"usermanual", - "p_code":"139", - "code":"143" + "p_code":"151", + "code":"155" }, { "desc":"Tags are key-value pairs that you can define to identify cloud resources. They assist you in categorizing and searching for cloud resources. A tag consists of a key and a", @@ -1292,8 +1400,8 @@ "title":"Managing DLI Package Tags", "uri":"dli_01_0369.html", "doc_type":"usermanual", - "p_code":"139", - "code":"144" + "p_code":"151", + "code":"156" }, { "desc":"DLI built-in dependencies are provided by the platform by default. In case of conflicts, you do not need to upload them when packaging JAR packages of Spark or Flink Jar ", @@ -1301,8 +1409,8 @@ "title":"DLI Built-in Dependencies", "uri":"dli_01_0397.html", "doc_type":"usermanual", - "p_code":"139", - "code":"145" + "p_code":"151", + "code":"157" }, { "desc":"A quota limits the quantity of a resource available to users, thereby preventing spikes in the usage of the resource.You can also request for an increased quota if your e", @@ -1310,8 +1418,8 @@ "title":"Managing DLI Resource Quotas", "uri":"dli_01_0550.html", "doc_type":"usermanual", - "p_code":"136", - "code":"146" + "p_code":"148", + "code":"158" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1320,7 +1428,7 @@ "uri":"dli_01_0539.html", "doc_type":"usermanual", "p_code":"", - "code":"147" + "code":"159" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1328,8 +1436,8 @@ "title":"DLI Basics", "uri":"dli_03_0001.html", "doc_type":"usermanual", - "p_code":"147", - "code":"148" + "p_code":"159", + "code":"160" }, { "desc":"Both DLI and MRS support Spark, but there are some differences in service mode, interface, application scenarios, and performance characteristics.The Spark component of D", @@ -1337,8 +1445,8 @@ "title":"What Are the Differences Between MRS Spark and DLI Spark?", "uri":"dli_03_0115.html", "doc_type":"usermanual", - "p_code":"148", - "code":"149" + "p_code":"160", + "code":"161" }, { "desc":"Supported data formats:ParquetCSVORCJSONAvroOBS: Data used by SQL jobs, Spark jobs, and Flink jobs can be stored in OBS, reducing storage costs.DLI: The column-based Parq", @@ -1346,8 +1454,8 @@ "title":"Where Can Data Be Stored in DLI?", "uri":"dli_03_0029.html", "doc_type":"usermanual", - "p_code":"148", - "code":"150" + "p_code":"160", + "code":"162" }, { "desc":"DLI supports importing data from OBS buckets shared by IAM users under the same tenant, but not from OBS buckets shared by other tenants.This ensures data security and is", @@ -1355,8 +1463,8 @@ "title":"Can I Import OBS Bucket Data Shared by Other Tenants into DLI?", "uri":"dli_03_0129.html", "doc_type":"usermanual", - "p_code":"148", - "code":"151" + "p_code":"160", + "code":"163" }, { "desc":"No, a global variable can only be used by the user who created it. Global variables can be used to simplify complex parameters. For example, long and difficult variables ", @@ -1364,8 +1472,8 @@ "title":"Can a Member Account Use Global Variables Created by Other Member Accounts?", "uri":"dli_03_0263.html", "doc_type":"usermanual", - "p_code":"148", - "code":"152" + "p_code":"160", + "code":"164" }, { "desc":"No.The spark.acls.enable configuration item is not used in DLI. The Apache Spark command injection vulnerability (CVE-2022-33891) does not exist in DLI.This vulnerability", @@ -1373,8 +1481,8 @@ "title":"Is DLI Affected by the Apache Spark Command Injection Vulnerability (CVE-2022-33891)?", "uri":"dli_03_0260.html", "doc_type":"usermanual", - "p_code":"148", - "code":"153" + "p_code":"160", + "code":"165" }, { "desc":"To manage a large number of DLI jobs, you can use the following methods:Manage jobs by group.Group tens of thousands of jobs by type and run each group on a queue.Group t", @@ -1382,8 +1490,8 @@ "title":"How Do I Manage Jobs Running on DLI?", "uri":"dli_03_0126.html", "doc_type":"usermanual", - "p_code":"148", - "code":"154" + "p_code":"160", + "code":"166" }, { "desc":"DLI does not support directly changing the field names of a table. However, you can solve this issue by migrating the table data using the following steps:Create a table:", @@ -1391,8 +1499,8 @@ "title":"How Do I Change the Field Names of an Existing Table on DLI?", "uri":"dli_03_0162.html", "doc_type":"usermanual", - "p_code":"148", - "code":"155" + "p_code":"160", + "code":"167" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1400,8 +1508,8 @@ "title":"DLI Elastic Resource Pools and Queues", "uri":"dli_03_0049.html", "doc_type":"usermanual", - "p_code":"147", - "code":"156" + "p_code":"159", + "code":"168" }, { "desc":"In daily big data analysis work, it is important to allocate and manage compute resources properly to provide a good job execution environment.You can allocate resources ", @@ -1409,8 +1517,8 @@ "title":"How Can I Check the Actual and Used CUs for an Elastic Resource Pool as Well as the Required CUs for a Job?", "uri":"dli_03_0276.html", "doc_type":"usermanual", - "p_code":"156", - "code":"157" + "p_code":"168", + "code":"169" }, { "desc":"You need to check the large number of jobs in the Submitting and Running states on the queue.Use Cloud Eye to view jobs in different states on the queue. The procedure is", @@ -1418,8 +1526,8 @@ "title":"How Do I Check for a Backlog of Jobs in the Current DLI Queue?", "uri":"dli_03_0183.html", "doc_type":"usermanual", - "p_code":"156", - "code":"158" + "p_code":"168", + "code":"170" }, { "desc":"To check the running status of the DLI queue and determine whether to run more jobs on that queue, you need to check the queue load.Search for Cloud Eye on the console.In", @@ -1427,8 +1535,8 @@ "title":"How Do I View the Load of a DLI Queue?", "uri":"dli_03_0095.html", "doc_type":"usermanual", - "p_code":"156", - "code":"159" + "p_code":"168", + "code":"171" }, { "desc":"DLI allows you to subscribe to an SMN topic for failed jobs.Log in to the DLI console.In the navigation pane on the left, choose Queue Management.On the Queue Management ", @@ -1436,8 +1544,8 @@ "title":"How Do I Monitor Job Exceptions on a DLI Queue?", "uri":"dli_03_0098.html", "doc_type":"usermanual", - "p_code":"156", - "code":"160" + "p_code":"168", + "code":"172" }, { "desc":"Currently, DLI provides two types of queues, For SQL and For general use. SQL queues are used to run SQL jobs. General-use queues are compatible with Spark queues of earl", @@ -1445,8 +1553,8 @@ "title":"How Do I Migrate an Old Version Spark Queue to a General-Purpose Queue?", "uri":"dli_03_0065.html", "doc_type":"usermanual", - "p_code":"156", - "code":"161" + "p_code":"168", + "code":"173" }, { "desc":"After a SQL job was submitted to the default queue, the job runs abnormally. The job log reported that the execution timed out. The exception logs are as follows:[ERROR] ", @@ -1454,8 +1562,8 @@ "title":"How Do I Do If I Encounter a Timeout Exception When Executing DLI SQL Statements on the default Queue?", "uri":"dli_03_0171.html", "doc_type":"usermanual", - "p_code":"156", - "code":"162" + "p_code":"168", + "code":"174" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1463,8 +1571,8 @@ "title":"DLI Databases and Tables", "uri":"dli_03_0211.html", "doc_type":"usermanual", - "p_code":"147", - "code":"163" + "p_code":"159", + "code":"175" }, { "desc":"A DLI table exists but cannot be queried on the DLI console.If a table exists but cannot be queried, there is a high probability that the current user does not have the p", @@ -1472,8 +1580,8 @@ "title":"Why Am I Unable to Query a Table on the DLI Console?", "uri":"dli_03_0184.html", "doc_type":"usermanual", - "p_code":"163", - "code":"164" + "p_code":"175", + "code":"176" }, { "desc":"When submitting a job to import data into a DLI table, if the compression rate of the Parquet/ORC file corresponding to the OBS table is high, exceeding 5 times the compr", @@ -1481,8 +1589,8 @@ "title":"How Do I Do If the Compression Rate of an OBS Table Is High?", "uri":"dli_03_0013.html", "doc_type":"usermanual", - "p_code":"163", - "code":"165" + "p_code":"175", + "code":"177" }, { "desc":"To avoid garbled characters caused by inconsistent character encoding, you are advised to unify the encoding format of your data source when executing jobs in DLI.DLI onl", @@ -1490,8 +1598,8 @@ "title":"How Do I Do If Inconsistent Character Encoding Leads to Garbled Characters?", "uri":"dli_03_0009.html", "doc_type":"usermanual", - "p_code":"163", - "code":"166" + "p_code":"175", + "code":"178" }, { "desc":"User A created the testTable table in a database through a SQL job and granted user B the permission to insert and delete table data. User A deleted the testTable table a", @@ -1499,8 +1607,8 @@ "title":"Do I Need to to Regrant Permissions to Users and Projects After Deleting and Recreating a Table With the Same Name?", "uri":"dli_03_0175.html", "doc_type":"usermanual", - "p_code":"163", - "code":"167" + "p_code":"175", + "code":"179" }, { "desc":"A CSV file is imported to a DLI partitioned table, but the imported file data does not contain the data in the partitioning column. The partitioning column needs to be sp", @@ -1508,8 +1616,8 @@ "title":"How Do I Do If Files Imported Into a DLI Partitioned Table Lack Data for the Partition Columns, Causing Query Failures After the Import Is Completed?", "uri":"dli_03_0177.html", "doc_type":"usermanual", - "p_code":"163", - "code":"168" + "p_code":"175", + "code":"180" }, { "desc":"When an OBS foreign table is created, a field in the specified OBS file contains a carriage return line feed (CRLF) character. As a result, the data is incorrect.The stat", @@ -1517,8 +1625,8 @@ "title":"How Do I Fix Incorrect Data in an OBS Foreign Table Caused by Newline Characters in OBS File Fields?", "uri":"dli_03_0181.html", "doc_type":"usermanual", - "p_code":"163", - "code":"169" + "p_code":"175", + "code":"181" }, { "desc":"The on clause was not added to the SQL statement for joining tables. As a result, the Cartesian product query occurs due to multi-table association, and the queue resourc", @@ -1526,8 +1634,8 @@ "title":"How Do I Prevent a Cartesian Product Query and Resource Overload Due to Missing \"ON\" Conditions in Table Joins?", "uri":"dli_03_0187.html", "doc_type":"usermanual", - "p_code":"163", - "code":"170" + "p_code":"175", + "code":"182" }, { "desc":"Partition data is manually uploaded to a partition of an OBS table. However, the data cannot be queried using DLI SQL editor.After manually adding partition data, you nee", @@ -1535,8 +1643,8 @@ "title":"How Do I Do If I Can't Query Data After Manually Adding It to the Partition Directory of an OBS Table?", "uri":"dli_03_0190.html", "doc_type":"usermanual", - "p_code":"163", - "code":"171" + "p_code":"175", + "code":"183" }, { "desc":"When using the INSERT OVERWRITE statement to overwrite data in a partitioned table, if you find that it overwrites all data instead of the expected partitioned data, it m", @@ -1544,8 +1652,8 @@ "title":"Why Does the \"insert overwrite\" Operation Affect All Data in a Partitioned Table Instead of Just the Targeted Partition?", "uri":"dli_03_0212.html", "doc_type":"usermanual", - "p_code":"163", - "code":"172" + "p_code":"175", + "code":"184" }, { "desc":"Spark does not have the datetime type and uses the TIMESTAMP type instead.You can use a function to convert data types.The following is an example.select cast(create_date", @@ -1553,8 +1661,8 @@ "title":"Why Does the \"create_date\" Field in an RDS Table (Datetime Data Type) Appear as a Timestamp in DLI Queries?", "uri":"dli_03_0214.html", "doc_type":"usermanual", - "p_code":"163", - "code":"173" + "p_code":"175", + "code":"185" }, { "desc":"Changing a table name immediately after executing a SQL job may result in an incorrect data size for the table.This is because DLI updates the metadata of the table when ", @@ -1562,8 +1670,8 @@ "title":"How Do I Do If Renaming a Table After a SQL Job Causes Incorrect Data Size?", "uri":"dli_03_0215.html", "doc_type":"usermanual", - "p_code":"163", - "code":"174" + "p_code":"175", + "code":"186" }, { "desc":"When DLI is used to insert data into an OBS temporary table, only part of data is imported.Possible causes are as follows:The amount of data read during job execution is ", @@ -1571,8 +1679,17 @@ "title":"How Can I Resolve Data Inconsistencies When Importing Data from DLI to OBS?", "uri":"dli_03_0231.html", "doc_type":"usermanual", - "p_code":"163", - "code":"175" + "p_code":"175", + "code":"187" + }, + { + "desc":"The Hudi table created using Flink SQL statements is not displayed on the DLI console, making it impossible to manage or perform query operations on the table through the", + "product_code":"dli", + "title":"Why Is a Hudi Table Not Displayed on the DLI Console?", + "uri":"dli_03_0277.html", + "doc_type":"usermanual", + "p_code":"175", + "code":"188" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1580,8 +1697,8 @@ "title":"Enhanced Datasource Connections", "uri":"dli_03_0022.html", "doc_type":"usermanual", - "p_code":"147", - "code":"176" + "p_code":"159", + "code":"189" }, { "desc":"The outbound rule had been configured for the security group of the queue associated with the enhanced datasource connection. The datasource authentication used a passwor", @@ -1589,8 +1706,8 @@ "title":"How Do I Resolve a Failure in Connecting DLI to GaussDB(DWS) Through an Enhanced Datasource Connection?", "uri":"dli_03_0238.html", "doc_type":"usermanual", - "p_code":"176", - "code":"177" + "p_code":"189", + "code":"190" }, { "desc":"A datasource connection is created and bound to a queue. The connectivity test fails and the following error information is displayed:failed to connect to specified addre", @@ -1598,8 +1715,8 @@ "title":"How Do I Do If the Datasource Connection Is Successfully Created but the Network Connectivity Test Fails?", "uri":"dli_03_0179.html", "doc_type":"usermanual", - "p_code":"176", - "code":"178" + "p_code":"189", + "code":"191" }, { "desc":"Configuring the Connection Between a DLI Queue and a Data Source in a Private NetworkIf your DLI job needs to connect to a data source, for example, MRS, RDS, CSS, Kafka,", @@ -1607,8 +1724,8 @@ "title":"How Do I Configure Network Connectivity Between a DLI Queue and a Data Source?", "uri":"dli_03_0186.html", "doc_type":"usermanual", - "p_code":"176", - "code":"179" + "p_code":"189", + "code":"192" }, { "desc":"The main reason for creating a VPC peering connection for DLI's enhanced datasource connection is to establish network connectivity between DLI and data sources in differ", @@ -1616,8 +1733,8 @@ "title":"Why Is Creating a VPC Peering Connection Necessary for Enhanced Datasource Connections in DLI?", "uri":"dli_03_0128.html", "doc_type":"usermanual", - "p_code":"176", - "code":"180" + "p_code":"189", + "code":"193" }, { "desc":"The possible causes and solutions are as follows:If you have created a queue, do not bind it to a datasource connection immediately. Wait for 5 to 10 minutes. After the c", @@ -1625,8 +1742,8 @@ "title":"How Do I Do If Creating a Datasource Connection in DLI Gets Stuck in the \"Creating\" State When Binding It to a Queue?", "uri":"dli_03_0257.html", "doc_type":"usermanual", - "p_code":"176", - "code":"181" + "p_code":"189", + "code":"194" }, { "desc":"The network connectivity is abnormal. Check whether the security group is correctly selected and whether the VPC is correctly configured.Example: When you create an RDS d", @@ -1634,8 +1751,8 @@ "title":"How Do I Resolve the \"communication link failure\" Error When Using a Newly Created Datasource Connection That Appears to Be Activated?", "uri":"dli_03_0047.html", "doc_type":"usermanual", - "p_code":"176", - "code":"182" + "p_code":"189", + "code":"195" }, { "desc":"If you have not added the cluster host information to the datasource connection, it can lead to KRB authentication failure, resulting in a connection timeout. In this cas", @@ -1643,8 +1760,8 @@ "title":"How Do I Troubleshoot a Connection Timeout Issue That Isn't Recorded in Logs When Accessing MRS HBase Through a Datasource Connection?", "uri":"dli_03_0080.html", "doc_type":"usermanual", - "p_code":"176", - "code":"183" + "p_code":"189", + "code":"196" }, { "desc":"A datasource RDS table was created in the DataArts Studio, and the insert overwrite statement was executed to write data into RDS. DLI.0999: BatchUpdateException: Incorre", @@ -1652,8 +1769,8 @@ "title":"How Do I Do If I Encounter the \"Incorrect string value\" Error When Executing insert overwrite on a Datasource RDS Table?", "uri":"dli_03_0239.html", "doc_type":"usermanual", - "p_code":"176", - "code":"184" + "p_code":"189", + "code":"197" }, { "desc":"The system failed to create a datasource RDS table, and null pointer error was reported.The following table creation statement was used:The RDS database is in a PostGre c", @@ -1661,8 +1778,8 @@ "title":"How Do I Resolve the Null Pointer Error When Creating an RDS Datasource Table?", "uri":"dli_03_0250.html", "doc_type":"usermanual", - "p_code":"176", - "code":"185" + "p_code":"189", + "code":"198" }, { "desc":"The system failed to execute insert overwrite on the datasource GaussDB(DWS) table, and org.postgresql.util.PSQLException: ERROR: tuple concurrently updated was displayed", @@ -1670,8 +1787,8 @@ "title":"Error Message \"org.postgresql.util.PSQLException: ERROR: tuple concurrently updated\" Is Displayed When the System Executes insert overwrite on a Datasource GaussDB(DWS) Table", "uri":"dli_03_0251.html", "doc_type":"usermanual", - "p_code":"176", - "code":"186" + "p_code":"189", + "code":"199" }, { "desc":"A datasource table was used to import data to a CloudTable HBase table. This HBase table contains a column family and a rowkey for 100 million simulating data records. Th", @@ -1679,8 +1796,8 @@ "title":"RegionTooBusyException Is Reported When Data Is Imported to a CloudTable HBase Table Through a Datasource Table", "uri":"dli_03_0252.html", "doc_type":"usermanual", - "p_code":"176", - "code":"187" + "p_code":"189", + "code":"200" }, { "desc":"A table was created on GaussDB(DWS) and then a datasource connection was created on DLI to read and write data. An error message was displayed during data writing, indica", @@ -1688,8 +1805,8 @@ "title":"How Do I Do If A Null Value Is Written Into a Non-Null Field When Using a DLI Datasource Connection to Connect to a GaussDB(DWS) Table?", "uri":"dli_03_0253.html", "doc_type":"usermanual", - "p_code":"176", - "code":"188" + "p_code":"189", + "code":"201" }, { "desc":"A datasource GaussDB(DWS) table and the datasource connection were created in DLI, and the schema of the source table in GaussDB(DWS) were updated. During the job executi", @@ -1697,8 +1814,8 @@ "title":"How Do I Do If an Insert Operation Failed After the Schema of the GaussDB(DWS) Source Table Is Updated?", "uri":"dli_03_0254.html", "doc_type":"usermanual", - "p_code":"176", - "code":"189" + "p_code":"189", + "code":"202" }, { "desc":"When creating an associated RDS table in DLI, if the RDS table contains an auto-increment primary key or other auto-populated fields, you can take the following measures ", @@ -1706,8 +1823,8 @@ "title":"How Do I Insert Data into an RDS Table with an Auto-Increment Primary Key Using DLI?", "uri":"dli_03_0028.html", "doc_type":"usermanual", - "p_code":"176", - "code":"190" + "p_code":"189", + "code":"203" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1715,8 +1832,8 @@ "title":"SQL Jobs", "uri":"dli_03_0020.html", "doc_type":"usermanual", - "p_code":"147", - "code":"191" + "p_code":"159", + "code":"204" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1724,8 +1841,8 @@ "title":"SQL Job Development", "uri":"dli_03_0204.html", "doc_type":"usermanual", - "p_code":"191", - "code":"192" + "p_code":"204", + "code":"205" }, { "desc":"A temporary table is used to store intermediate results. When a transaction or session ends, the data in the temporary table can be automatically deleted. For example, in", @@ -1733,8 +1850,8 @@ "title":"SQL Jobs", "uri":"dli_03_0200.html", "doc_type":"usermanual", - "p_code":"192", - "code":"193" + "p_code":"205", + "code":"206" }, { "desc":"If a large number of small files are generated during SQL execution, job execution and table query will take a long time. In this case, you should merge small files.You a", @@ -1742,17 +1859,17 @@ "title":"How Do I Merge Small Files?", "uri":"dli_03_0086.html", "doc_type":"usermanual", - "p_code":"192", - "code":"194" + "p_code":"205", + "code":"207" }, { - "desc":"When creating an OBS table, you must specify a table path in the database. The path format is as follows: obs://xxx/database name/table name.If the specified path is akdc", + "desc":"When creating an OBS table, you must specify a table path in the database.The path format is as follows: obs://xxx/database name/table name.If the specified path is akdc.", "product_code":"dli", "title":"How Do I Specify an OBS Path When Creating an OBS Table?", "uri":"dli_03_0092.html", "doc_type":"usermanual", - "p_code":"192", - "code":"195" + "p_code":"205", + "code":"208" }, { "desc":"To associate JSON data nested in an OBS bucket, you can create a table in asynchronous mode.The following is an example of a table creation statement that shows how to us", @@ -1760,8 +1877,8 @@ "title":"How Do I Create a Table Using JSON Data in an OBS Bucket?", "uri":"dli_03_0108.html", "doc_type":"usermanual", - "p_code":"192", - "code":"196" + "p_code":"205", + "code":"209" }, { "desc":"The correct method for using the count function to perform aggregation is as follows:OrIf an incorrect method is used, an error will be reported.", @@ -1769,8 +1886,8 @@ "title":"How Can I Use the count Function to Perform Aggregation?", "uri":"dli_03_0069.html", "doc_type":"usermanual", - "p_code":"192", - "code":"197" + "p_code":"205", + "code":"210" }, { "desc":"You can use the cross-region replication function of OBS. The procedure is as follows:Export the DLI table data in region 1 to the user-defined OBS bucket.Use the OBS cro", @@ -1778,8 +1895,8 @@ "title":"How Do I Synchronize DLI Table Data Across Regions?", "uri":"dli_03_0072.html", "doc_type":"usermanual", - "p_code":"192", - "code":"198" + "p_code":"205", + "code":"211" }, { "desc":"If you need to insert data into a table but only want to specify certain fields, you can use the INSERT INTO statement combined with the SELECT clause.However, DLI curren", @@ -1787,8 +1904,8 @@ "title":"How Do I Insert Table Data into Specific Fields of a Table Using a SQL Job?", "uri":"dli_03_0191.html", "doc_type":"usermanual", - "p_code":"192", - "code":"199" + "p_code":"205", + "code":"212" }, { "desc":"If the job runs slowly, perform the following steps to find the causes and rectify the fault:Check whether the problem is caused by FullGC.Log in to the DLI console. In t", @@ -1796,8 +1913,8 @@ "title":"How Do I Troubleshoot Slow SQL Jobs?", "uri":"dli_03_0196.html", "doc_type":"usermanual", - "p_code":"192", - "code":"200" + "p_code":"205", + "code":"213" }, { "desc":"You can view SQL job logs for routine O&M.Obtain the ID of the DLI job executed on the DataArts Studio console.Job IDOn the DLI console, choose Job Management > SQL Jobs.", @@ -1805,8 +1922,8 @@ "title":"How Do I View DLI SQL Logs?", "uri":"dli_03_0091.html", "doc_type":"usermanual", - "p_code":"192", - "code":"201" + "p_code":"205", + "code":"214" }, { "desc":"You can view the job execution records when a job is running.Log in to the DLI management console.In the navigation pane on the left, choose Job Management > SQL Jobs.Ent", @@ -1814,8 +1931,8 @@ "title":"How Do I View SQL Execution Records in DLI?", "uri":"dli_03_0116.html", "doc_type":"usermanual", - "p_code":"192", - "code":"202" + "p_code":"205", + "code":"215" }, { "desc":"Data skew is a common issue during the execution of SQL jobs. When data is unevenly distributed, some compute nodes process significantly more data than others, which can", @@ -1823,8 +1940,8 @@ "title":"How Do I Do When Data Skew Occurs During the Execution of a SQL Job?", "uri":"dli_03_0093.html", "doc_type":"usermanual", - "p_code":"192", - "code":"203" + "p_code":"205", + "code":"216" }, { "desc":"A SQL job contains join operations. After the job is submitted, it is stuck in the Running state and no result is returned.When a Spark SQL job has join operations on sma", @@ -1832,8 +1949,8 @@ "title":"Why Does a SQL Job That Has Join Operations Stay in the Running State?", "uri":"dli_03_0182.html", "doc_type":"usermanual", - "p_code":"192", - "code":"204" + "p_code":"205", + "code":"217" }, { "desc":"The possible causes and solutions are as follows:After you purchase a DLI queue and submit a SQL job for the first time, wait for 5 to 10 minutes. After the cluster is st", @@ -1841,8 +1958,8 @@ "title":"Why Is a SQL Job Stuck in the Submitting State?", "uri":"dli_03_0213.html", "doc_type":"usermanual", - "p_code":"192", - "code":"205" + "p_code":"205", + "code":"218" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1850,8 +1967,8 @@ "title":"SQL Job O&M", "uri":"dli_03_0206.html", "doc_type":"usermanual", - "p_code":"191", - "code":"206" + "p_code":"204", + "code":"219" }, { "desc":"This message indicates that you are exporting data to an existing OBS path.Solution:Create an OBS directory.You can create an OBS directory that does not exist to store t", @@ -1859,8 +1976,8 @@ "title":"Why Is Error \"path obs://xxx already exists\" Reported When Data Is Exported to OBS?", "uri":"dli_03_0014.html", "doc_type":"usermanual", - "p_code":"206", - "code":"207" + "p_code":"219", + "code":"220" }, { "desc":"This message indicates that the two tables to be joined contain the same column, but the owner of the column is not specified when the command is executed.For example, ta", @@ -1868,8 +1985,8 @@ "title":"Why Is Error \"SQL_ANALYSIS_ERROR: Reference 't.id' is ambiguous, could be: t.id, t.id.;\" Displayed When Two Tables Are Joined?", "uri":"dli_03_0066.html", "doc_type":"usermanual", - "p_code":"206", - "code":"208" + "p_code":"219", + "code":"221" }, { "desc":"This message indicates that your operation is restricted because your account is in arrears or there is insufficient balance in your account.Solution:Check the account st", @@ -1877,8 +1994,8 @@ "title":"Why Is Error \"The current account does not have permission to perform this operation,the current account was restricted. Restricted for no budget.\" Reported when a SQL Statement Is Executed?", "uri":"dli_03_0071.html", "doc_type":"usermanual", - "p_code":"206", - "code":"209" + "p_code":"219", + "code":"222" }, { "desc":"When you query the partitioned table XX.YYY, the partition column is not specified in the search criteria.A partitioned table can be queried only when the query condition", @@ -1886,8 +2003,8 @@ "title":"Why Is Error \"There should be at least one partition pruning predicate on partitioned table XX.YYY\" Reported When a Query Statement Is Executed?", "uri":"dli_03_0145.html", "doc_type":"usermanual", - "p_code":"206", - "code":"210" + "p_code":"219", + "code":"223" }, { "desc":"The following error message is displayed when the LOAD DATA command is executed by a Spark SQL job to import data to a DLI table:In some cases ,the following error messag", @@ -1895,8 +2012,8 @@ "title":"Why Is Error \"IllegalArgumentException: Buffer size too small. size\" Reported When Data Is Loaded to an OBS Foreign Table?", "uri":"dli_03_0169.html", "doc_type":"usermanual", - "p_code":"206", - "code":"211" + "p_code":"219", + "code":"224" }, { "desc":"An error is reported during SQL job execution:Please contact DLI service. DLI.0002: FileNotFoundException: getFileStatus on obs://xxx: status [404]Check whether there is ", @@ -1904,8 +2021,8 @@ "title":"Why Is Error \"DLI.0002 FileNotFoundException\" Reported During SQL Job Running?", "uri":"dli_03_0189.html", "doc_type":"usermanual", - "p_code":"206", - "code":"212" + "p_code":"219", + "code":"225" }, { "desc":"Currently, DLI supports the creation of TEXTFILE, SEQUENCEFILE, RCFILE, ORC, AVRO, and PARQUET tables using the Hive syntax.If you create a table using CTAS statements, s", @@ -1913,8 +2030,8 @@ "title":"Why Is a Schema Parsing Error Reported When I Create a Hive Table Using CTAS?", "uri":"dli_03_0046.html", "doc_type":"usermanual", - "p_code":"206", - "code":"213" + "p_code":"219", + "code":"226" }, { "desc":"When you run a DLI SQL script on DataArts Studio, the log shows that the statements fail to be executed. The error information is as follows:DLI.0999: RuntimeException: o", @@ -1922,8 +2039,8 @@ "title":"Why Is Error \"org.apache.hadoop.fs.obs.OBSIOException\" Reported When I Run DLI SQL Scripts on DataArts Studio?", "uri":"dli_03_0173.html", "doc_type":"usermanual", - "p_code":"206", - "code":"214" + "p_code":"219", + "code":"227" }, { "desc":"Error message \"File not Found\" is displayed when a SQL job is accessed.The system may not be able to locate the specified file path or file due to an incorrect file path ", @@ -1931,8 +2048,8 @@ "title":"Why Is Error \"File not Found\" Reported When I Access a SQL Job?", "uri":"dli_03_0207.html", "doc_type":"usermanual", - "p_code":"206", - "code":"215" + "p_code":"219", + "code":"228" }, { "desc":"Error message \"DLI.0003: AccessControlException XXX\" is reported when a SQL job is accessed.Check the permissions of the OBS bucket to ensure that the account has access ", @@ -1940,8 +2057,8 @@ "title":"Why Is Error \"DLI.0003: AccessControlException XXX\" Reported When I Access a SQL Job?", "uri":"dli_03_0208.html", "doc_type":"usermanual", - "p_code":"206", - "code":"216" + "p_code":"219", + "code":"229" }, { "desc":"Error message \"DLI.0001: org.apache.hadoop.security.AccessControlException: verifyBucketExists on {{bucket name}}: status [403]\" is reported when a SQL job is Accessed.Ch", @@ -1949,8 +2066,8 @@ "title":"Why Is Error \"DLI.0001: org.apache.hadoop.security.AccessControlException: verifyBucketExists on {{bucket name}}: status [403]\" Reported When I Access a SQL Job?", "uri":"dli_03_0209.html", "doc_type":"usermanual", - "p_code":"206", - "code":"217" + "p_code":"219", + "code":"230" }, { "desc":"Error message \"The current account does not have permission to perform this operation,the current account was restricted.\" is reported during SQL statement execution.Chec", @@ -1958,8 +2075,8 @@ "title":"Why Am I Seeing the Error Message \"The current account does not have permission to perform this operation,the current account was restricted. Restricted for no budget\" When Executing a SQL Statement?", "uri":"dli_03_0210.html", "doc_type":"usermanual", - "p_code":"206", - "code":"218" + "p_code":"219", + "code":"231" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1967,8 +2084,8 @@ "title":"Flink Jobs", "uri":"dli_03_0037.html", "doc_type":"usermanual", - "p_code":"147", - "code":"219" + "p_code":"159", + "code":"232" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1976,8 +2093,8 @@ "title":"Flink Job Consulting", "uri":"dli_03_0137.html", "doc_type":"usermanual", - "p_code":"219", - "code":"220" + "p_code":"232", + "code":"233" }, { "desc":"A sub-user can view queues but cannot view Flink jobs. You can authorize the sub-user using DLI or IAM.Authorization on DLILog in to the DLI console using a tenant accoun", @@ -1985,8 +2102,8 @@ "title":"How Do I Authorize a Subuser to View Flink Jobs?", "uri":"dli_03_0139.html", "doc_type":"usermanual", - "p_code":"220", - "code":"221" + "p_code":"233", + "code":"234" }, { "desc":"DLI Flink jobs are highly available. You can enable the automatic restart function to automatically restart your jobs after short-time faults of peripheral services are r", @@ -1994,8 +2111,8 @@ "title":"How Do I Configure Auto Restart upon Exception for a Flink Job?", "uri":"dli_03_0090.html", "doc_type":"usermanual", - "p_code":"220", - "code":"222" + "p_code":"233", + "code":"235" }, { "desc":"When you create a Flink SQL job or Flink Jar job, you can select Save Job Log on the job editing page to save job running logs to OBS.To set the OBS bucket for storing th", @@ -2003,8 +2120,8 @@ "title":"How Do I Save Logs for Flink Jobs?", "uri":"dli_03_0099.html", "doc_type":"usermanual", - "p_code":"220", - "code":"223" + "p_code":"233", + "code":"236" }, { "desc":"Choose Job Management > Flink Jobs. In the Operation column of the target job, choose More > Permissions. When a new user is authorized, No such user. userName:xxxx. is d", @@ -2012,8 +2129,8 @@ "title":"Why Is Error \"No such user. userName:xxxx.\" Reported on the Flink Job Management Page When I Grant Permission to a User?", "uri":"dli_03_0160.html", "doc_type":"usermanual", - "p_code":"220", - "code":"224" + "p_code":"233", + "code":"237" }, { "desc":"Checkpoint was enabled when a Flink job is created, and the OBS bucket for storing checkpoints was specified. I am not sure how to restore a Flink job from a specific che", @@ -2021,8 +2138,8 @@ "title":"How Do I Restore a Flink Job from a Specific Checkpoint After Manually Stopping the Job?", "uri":"dli_03_0180.html", "doc_type":"usermanual", - "p_code":"220", - "code":"225" + "p_code":"233", + "code":"238" }, { "desc":"When you set running parameters of a DLI Flink job, you can enable Alarm Generation upon Job Exception to receive alarms when the job runs abnormally or is in arrears.If ", @@ -2030,8 +2147,8 @@ "title":"Why Is a Message Displayed Indicating That the SMN Topic Does Not Exist When I Use the SMN Topic in DLI?", "uri":"dli_03_0036.html", "doc_type":"usermanual", - "p_code":"220", - "code":"226" + "p_code":"233", + "code":"239" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2039,8 +2156,8 @@ "title":"Flink SQL Jobs", "uri":"dli_03_0131.html", "doc_type":"usermanual", - "p_code":"219", - "code":"227" + "p_code":"232", + "code":"240" }, { "desc":"When using a Flink SQL job, you need to create an OBS partition table for subsequent batch processing.In the following example, the day field is used as the partition fie", @@ -2048,8 +2165,8 @@ "title":"How Do I Map an OBS Table to a DLI Partitioned Table?", "uri":"dli_03_0089.html", "doc_type":"usermanual", - "p_code":"227", - "code":"228" + "p_code":"240", + "code":"241" }, { "desc":"You used Flink 1.10 to run a Flink Opensource SQL job. You set the number of Kafka partitions for the job a small value at the beginning and need to increase the number n", @@ -2057,8 +2174,8 @@ "title":"How Do I Change the Number of Kafka Partitions in a Flink SQL Job Without Stopping It?", "uri":"dli_03_0120.html", "doc_type":"usermanual", - "p_code":"227", - "code":"229" + "p_code":"240", + "code":"242" }, { "desc":"When I run the creation statement with an EL expression in the table name in a Flink SQL job, the following error message is displayed:DLI.0005: AnalysisException: t_user", @@ -2066,8 +2183,8 @@ "title":"How Do I Fix the DLI.0005 Error When Using EL Expressions to Create a Table in a Flink SQL Job?", "uri":"dli_03_0167.html", "doc_type":"usermanual", - "p_code":"227", - "code":"230" + "p_code":"240", + "code":"243" }, { "desc":"After data is written to OBS through the Flink job output stream, data cannot be queried from the DLI table created in the OBS file path.For example, use the following Fl", @@ -2075,8 +2192,8 @@ "title":"Why Is No Data Queried in the DLI Table Created Using the OBS File Path When Data Is Written to OBS by a Flink Job Output Stream?", "uri":"dli_03_0168.html", "doc_type":"usermanual", - "p_code":"227", - "code":"231" + "p_code":"240", + "code":"244" }, { "desc":"After a Flink SQL job is submitted on DLI, the job fails to be executed. The following error information is displayed in the job log:connect to DIS failed java.lang.Illeg", @@ -2084,8 +2201,8 @@ "title":"Why Does a Flink SQL Job Fails to Be Executed, and Is \"connect to DIS failed java.lang.IllegalArgumentException: Access key cannot be null\" Displayed in the Log?", "uri":"dli_03_0174.html", "doc_type":"usermanual", - "p_code":"227", - "code":"232" + "p_code":"240", + "code":"245" }, { "desc":"After a Flink SQL job consumed Kafka and sent data to the Elasticsearch cluster, the job was successfully executed, but no data is available.Possible causes are as follow", @@ -2093,8 +2210,8 @@ "title":"Data Writing Fails After a Flink SQL Job Consumed Kafka and Sank Data to the Elasticsearch Cluster", "uri":"dli_03_0232.html", "doc_type":"usermanual", - "p_code":"227", - "code":"233" + "p_code":"240", + "code":"246" }, { "desc":"You used Flink 1.10 to run a Flink Opensource SQL job. The job failed after the following error was reported when Flink Sink wrote data to Kafka.The CPU usage is too high", @@ -2102,8 +2219,8 @@ "title":"How Do I Configure Connection Retries for Kafka Sink If it is Disconnected?", "uri":"dli_03_0121.html", "doc_type":"usermanual", - "p_code":"227", - "code":"234" + "p_code":"240", + "code":"247" }, { "desc":"In a Flink job, you can use CREATE statements to define source and sink tables, and specify their connector types and related attributes.If you need to write data to diff", @@ -2111,8 +2228,8 @@ "title":"How Do I Write Data to Different Elasticsearch Clusters in a Flink Job?", "uri":"dli_03_0048.html", "doc_type":"usermanual", - "p_code":"227", - "code":"235" + "p_code":"240", + "code":"248" }, { "desc":"To rectify this fault, perform the following steps:Log in to the DIS management console. In the navigation pane, choose Stream Management. View the Flink job SQL statemen", @@ -2120,8 +2237,8 @@ "title":"Why Does DIS Stream Not Exist During Job Semantic Check?", "uri":"dli_03_0040.html", "doc_type":"usermanual", - "p_code":"227", - "code":"236" + "p_code":"240", + "code":"249" }, { "desc":"If the Flink JobManager prompts \"Timeout expired while fetching topic metadata\", it means that the Flink job timed out while trying to fetch metadata for the Kafka topic.", @@ -2129,8 +2246,8 @@ "title":"Why Is Error \"Timeout expired while fetching topic metadata\" Repeatedly Reported in Flink JobManager Logs?", "uri":"dli_03_0265.html", "doc_type":"usermanual", - "p_code":"227", - "code":"237" + "p_code":"240", + "code":"250" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2138,8 +2255,8 @@ "title":"Flink Jar Jobs", "uri":"dli_03_0132.html", "doc_type":"usermanual", - "p_code":"219", - "code":"238" + "p_code":"232", + "code":"251" }, { "desc":"You can upload configuration files for custom jobs (Jar).Upload the configuration file to DLI through Package Management.In the Other Dependencies area of the Flink Jar j", @@ -2147,8 +2264,8 @@ "title":"Can I Upload Configuration Files for Flink Jar Jobs?", "uri":"dli_03_0044.html", "doc_type":"usermanual", - "p_code":"238", - "code":"239" + "p_code":"251", + "code":"252" }, { "desc":"The dependency of your Flink job conflicts with a built-in dependency of the DLI Flink platform. As a result, the job submission fails.Check whether there are conflicting", @@ -2156,8 +2273,8 @@ "title":"Why Does a Flink Jar Package Conflict Result in Job Submission Failure?", "uri":"dli_03_0119.html", "doc_type":"usermanual", - "p_code":"238", - "code":"240" + "p_code":"251", + "code":"253" }, { "desc":"When a Flink Jar job is submitted to access GaussDB(DWS), an error message is displayed indicating that the job fails to be started. The job log contains the following er", @@ -2165,8 +2282,8 @@ "title":"Why Does a Flink Jar Job Fail to Access GaussDB(DWS) and a Message Is Displayed Indicating Too Many Client Connections?", "uri":"dli_03_0161.html", "doc_type":"usermanual", - "p_code":"238", - "code":"241" + "p_code":"251", + "code":"254" }, { "desc":"The storage path of the Flink Jar job checkpoints was set to an OBS bucket. The job failed to be submitted, and an error message indicating an invalid OBS bucket name was", @@ -2174,8 +2291,8 @@ "title":"Why Is Error Invalid OBS Bucket Name Reported After a Flink Job Submission Failed?", "uri":"dli_03_0233.html", "doc_type":"usermanual", - "p_code":"238", - "code":"242" + "p_code":"251", + "code":"255" }, { "desc":"Flink Job submission failed. The exception information is as follows:Flink JAR files conflicted. The submitted Flink JAR file conflicted with the HDFS JAR file of the DLI", @@ -2183,8 +2300,8 @@ "title":"Why Does the Flink Submission Fail Due to Hadoop JAR File Conflict?", "uri":"dli_03_0234.html", "doc_type":"usermanual", - "p_code":"238", - "code":"243" + "p_code":"251", + "code":"256" }, { "desc":"On the Flink job management page, hover the cursor on the status of the job that fails to be submitted to view the brief information about the failure.The possible causes", @@ -2192,8 +2309,8 @@ "title":"How Do I Locate a Flink Job Submission Error?", "uri":"dli_03_0103.html", "doc_type":"usermanual", - "p_code":"238", - "code":"244" + "p_code":"251", + "code":"257" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2201,8 +2318,8 @@ "title":"Flink Job Performance Tuning", "uri":"dli_03_0133.html", "doc_type":"usermanual", - "p_code":"219", - "code":"245" + "p_code":"232", + "code":"258" }, { "desc":"Data Stacking in a Consumer GroupThe accumulated data of a consumer group can be calculated by the following formula: Total amount of data to be consumed by the consumer ", @@ -2210,8 +2327,8 @@ "title":"Flink Job Performance Tuning", "uri":"dli_03_0106.html", "doc_type":"usermanual", - "p_code":"245", - "code":"246" + "p_code":"258", + "code":"259" }, { "desc":"The DLI Flink checkpoint/savepoint mechanism is complete and reliable. You can use this mechanism to prevent data loss when a job is manually restarted or restarted due t", @@ -2219,8 +2336,8 @@ "title":"How Do I Prevent Data Loss After Flink Job Restart?", "uri":"dli_03_0096.html", "doc_type":"usermanual", - "p_code":"245", - "code":"247" + "p_code":"258", + "code":"260" }, { "desc":"On the Flink job management, click Edit in the Operation column of the target job. On the displayed page, check whether Save Job Log in the Running Parameters tab is enab", @@ -2228,8 +2345,8 @@ "title":"How Do I Locate a Flink Job Running Error?", "uri":"dli_03_0105.html", "doc_type":"usermanual", - "p_code":"245", - "code":"248" + "p_code":"258", + "code":"261" }, { "desc":"Flink's checkpointing is a fault tolerance and recovery mechanism. This mechanism ensures that real-time programs can self-recover in case of exceptions or machine issues", @@ -2237,8 +2354,8 @@ "title":"How Can I Check if a Flink Job Can Be Restored From a Checkpoint After Restarting It?", "uri":"dli_03_0136.html", "doc_type":"usermanual", - "p_code":"245", - "code":"249" + "p_code":"258", + "code":"262" }, { "desc":"Mode for storing generated job logs when a DLI Flink job fails to be submitted or executed. The options are as follows:If the submission fails, a submission log is genera", @@ -2246,8 +2363,8 @@ "title":"Why Are Logs Not Written to the OBS Bucket After a DLI Flink Job Fails to Be Submitted for Running?", "uri":"dli_03_0064.html", "doc_type":"usermanual", - "p_code":"245", - "code":"250" + "p_code":"258", + "code":"263" }, { "desc":"JobManager and TaskManager heartbeats timed out. As a result, the Flink job is abnormal.Check whether the network is intermittently disconnected and whether the cluster l", @@ -2255,8 +2372,8 @@ "title":"Why Is the Flink Job Abnormal Due to Heartbeat Timeout Between JobManager and TaskManager?", "uri":"dli_03_0236.html", "doc_type":"usermanual", - "p_code":"245", - "code":"251" + "p_code":"258", + "code":"264" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2264,8 +2381,8 @@ "title":"Spark Jobs", "uri":"dli_03_0021.html", "doc_type":"usermanual", - "p_code":"147", - "code":"252" + "p_code":"159", + "code":"265" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2273,8 +2390,8 @@ "title":"Spark Job Development", "uri":"dli_03_0217.html", "doc_type":"usermanual", - "p_code":"252", - "code":"253" + "p_code":"265", + "code":"266" }, { "desc":"DLI Spark does not support job scheduling. You can use other services, such as DataArts Studio, or use APIs or SDKs to customize job schedule.The Spark SQL syntax does no", @@ -2282,8 +2399,8 @@ "title":"Spark Jobs", "uri":"dli_03_0201.html", "doc_type":"usermanual", - "p_code":"253", - "code":"254" + "p_code":"266", + "code":"267" }, { "desc":"To use Spark to write data into a DLI table, configure the following parameters:fs.obs.access.keyfs.obs.secret.keyfs.obs.implfs.obs.endpointThe following is an example:", @@ -2291,8 +2408,8 @@ "title":"How Do I Use Spark to Write Data into a DLI Table?", "uri":"dli_03_0107.html", "doc_type":"usermanual", - "p_code":"253", - "code":"255" + "p_code":"266", + "code":"268" }, { "desc":"To obtain the AK/SK, set the parameters as follows:Create a SparkContext using code.val sc: SparkContext = new SparkContext()\nsc.hadoopConfiguration.set(\"fs.obs.access.ke", @@ -2300,8 +2417,8 @@ "title":"How Do I Set Up AK/SK So That a General Queue Can Access Tables Stored in OBS?", "uri":"dli_03_0017.html", "doc_type":"usermanual", - "p_code":"253", - "code":"256" + "p_code":"266", + "code":"269" }, { "desc":"Log in to the DLI console. In the navigation pane, choose Job Management > Spark Jobs. In the job list, locate the target job and click next to Job ID to view the parame", @@ -2309,8 +2426,8 @@ "title":"How Do I View the Resource Usage of DLI Spark Jobs?", "uri":"dli_03_0102.html", "doc_type":"usermanual", - "p_code":"253", - "code":"257" + "p_code":"266", + "code":"270" }, { "desc":"If the pymysql module is missing, check whether the corresponding EGG package exists. If the package does not exist, upload the pyFile package on the Package Management p", @@ -2318,8 +2435,8 @@ "title":"How Do I Use Python Scripts to Access the MySQL Database If the pymysql Module Is Missing from the Spark Job Results Stored in MySQL?", "uri":"dli_03_0076.html", "doc_type":"usermanual", - "p_code":"253", - "code":"258" + "p_code":"266", + "code":"271" }, { "desc":"DLI natively supports PySpark.For most cases, Python is preferred for data analysis, and PySpark is the best choice for big data analysis. Generally, JVM programs are pac", @@ -2327,8 +2444,8 @@ "title":"How Do I Run a Complex PySpark Program in DLI?", "uri":"dli_03_0082.html", "doc_type":"usermanual", - "p_code":"253", - "code":"259" + "p_code":"266", + "code":"272" }, { "desc":"When shuffle statements, such as GROUP BY and JOIN, are executed in Spark jobs, data skew occurs, which slows down the job execution.To solve this problem, you can config", @@ -2336,8 +2453,8 @@ "title":"How Do I Use JDBC to Set the spark.sql.shuffle.partitions Parameter to Improve the Task Concurrency?", "uri":"dli_03_0068.html", "doc_type":"usermanual", - "p_code":"253", - "code":"260" + "p_code":"266", + "code":"273" }, { "desc":"You can use SparkFiles to read the file submitted using –-file form a local path: SparkFiles.get(\"Name of the uploaded file\").The file path in the Driver is different fro", @@ -2345,8 +2462,17 @@ "title":"How Do I Read Uploaded Files for a Spark Jar Job?", "uri":"dli_03_0118.html", "doc_type":"usermanual", - "p_code":"253", - "code":"261" + "p_code":"266", + "code":"274" + }, + { + "desc":"When running a job with Spark 3.3.1, certain fields have empty default attribute values when queried in the view attribute on the client. In contrast, when using Spark 3.", + "product_code":"dli", + "title":"Why Are View Attributes Empty in Spark 3.3.1 Client?", + "uri":"dli_03_0279.html", + "doc_type":"usermanual", + "p_code":"266", + "code":"275" }, { "desc":"I cannot find the specified Python environment after adding the Python 3 package.Set spark.yarn.appMasterEnv.PYSPARK_PYTHON to python3 in the conf file to specify the Pyt", @@ -2354,8 +2480,8 @@ "title":"Why Can't I Find the Specified Python Environment After Adding the Python Package?", "uri":"dli_03_0077.html", "doc_type":"usermanual", - "p_code":"253", - "code":"262" + "p_code":"266", + "code":"276" }, { "desc":"The remaining CUs in the queue may be insufficient. As a result, the job cannot be submitted.To view the remaining CUs of a queue, perform the following steps:Check the C", @@ -2363,8 +2489,8 @@ "title":"Why Is a Spark Jar Job Stuck in the Submitting State?", "uri":"dli_03_0220.html", "doc_type":"usermanual", - "p_code":"253", - "code":"263" + "p_code":"266", + "code":"277" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2372,8 +2498,8 @@ "title":"Spark Job O&M", "uri":"dli_03_0218.html", "doc_type":"usermanual", - "p_code":"252", - "code":"264" + "p_code":"265", + "code":"278" }, { "desc":"The following error is reported when a Spark job accesses OBS data:Set the AK/SK to enable Spark jobs to access OBS data.For details, see How Do I Set Up AK/SK So That a ", @@ -2381,8 +2507,8 @@ "title":"Why Do I Get \"ResponseCode: 403\" and \"ResponseStatus: Forbidden\" Errors When a Spark Job Accesses OBS Data?", "uri":"dli_03_0156.html", "doc_type":"usermanual", - "p_code":"264", - "code":"265" + "p_code":"278", + "code":"279" }, { "desc":"This error message may be due to the OBS bucket being set as the DLI log bucket, which cannot be used for other purposes.You can follow these steps to check:Check if the ", @@ -2390,8 +2516,8 @@ "title":"Why Do I Encounter the Error \"verifyBucketExists on XXXX: status [403]\" When Using a Spark Job to Access an OBS Bucket That I Have Permission to Access?", "uri":"dli_03_0164.html", "doc_type":"usermanual", - "p_code":"264", - "code":"266" + "p_code":"278", + "code":"280" }, { "desc":"When running large amounts of data in a Spark job, if a timeout exception error occurs, it is usually due to insufficient resource configuration, data skew, network issue", @@ -2399,8 +2525,8 @@ "title":"Why Does a Job Running Timeout Occur When Processing a Large Amount of Data with a Spark Job?", "uri":"dli_03_0157.html", "doc_type":"usermanual", - "p_code":"264", - "code":"267" + "p_code":"278", + "code":"281" }, { "desc":"Spark jobs cannot access SFTP. Upload the files you want to access to OBS and then you can analyze the data using Spark jobs.Upload data to an OBS bucket: Upload data sto", @@ -2408,8 +2534,8 @@ "title":"Why Does a Spark Job Fail to Execute with an Abnormal Access Directory Error When Accessing Files in SFTP?", "uri":"dli_03_0188.html", "doc_type":"usermanual", - "p_code":"264", - "code":"268" + "p_code":"278", + "code":"282" }, { "desc":"When a Spark job is running, an error message is displayed, indicating that the user does not have the database permission. The error information is as follows:org.apache", @@ -2417,8 +2543,8 @@ "title":"Why Does the Job Fail to Be Executed Due to Insufficient Database and Table Permissions?", "uri":"dli_03_0192.html", "doc_type":"usermanual", - "p_code":"264", - "code":"269" + "p_code":"278", + "code":"283" }, { "desc":"I cannot find the global_temp database in the Spark 3.x job log.The global_temp database is the default built-in database of Spark 3.x and is Spark's global temporary vie", @@ -2426,8 +2552,8 @@ "title":"Why Is the global_temp Database Missing in the Job Log of Spark 3.x?", "uri":"dli_03_0272.html", "doc_type":"usermanual", - "p_code":"264", - "code":"270" + "p_code":"278", + "code":"284" }, { "desc":"I failed to use the DataSource syntax to create an OBS table in Avro format when selecting Spark to access metadata.Spark 2.3.x does not support creating OBS tables in Av", @@ -2435,8 +2561,26 @@ "title":"Why Does Using DataSource Syntax to Create an OBS Table of Avro Type Fail When Accessing Metadata With Spark 2.3.x?", "uri":"dli_03_0275.html", "doc_type":"usermanual", - "p_code":"264", - "code":"271" + "p_code":"278", + "code":"285" + }, + { + "desc":"When the rand function is used in SQL statements of Spark 3.3.1, the error message \"Input argument to rand must be a constant\" is displayed.In Spark 3.3.1, the rand funct", + "product_code":"dli", + "title":"How Do I Resolve the \"Input argument to rand must be a constant\" Error in Spark 3.3.1 SQL Statements?", + "uri":"dli_03_0278.html", + "doc_type":"usermanual", + "p_code":"278", + "code":"286" + }, + { + "desc":"When using Spark 3.3.1 client to create a subquery view with aggregate functions, an error occurs when attempting to write the data, stating \"Not allowed to create a perm", + "product_code":"dli", + "title":"When Using Spark 3.3.1 Client to Create a View and Perform a Join Query, an Error Occurs Stating \"Not allowed to create a permanent view\" When Attempting to Write the Data", + "uri":"dli_03_0273.html", + "doc_type":"usermanual", + "p_code":"278", + "code":"287" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2444,8 +2588,8 @@ "title":"DLI Resource Quotas", "uri":"dli_03_0053.html", "doc_type":"usermanual", - "p_code":"147", - "code":"272" + "p_code":"159", + "code":"288" }, { "desc":"Log in to the management console.Click in the upper left corner and select a region and a project.Click the My Quota icon in the upper right corner of the page.The Serv", @@ -2453,8 +2597,8 @@ "title":"How Do I View My Quotas?", "uri":"dli_03_0031.html", "doc_type":"usermanual", - "p_code":"272", - "code":"273" + "p_code":"288", + "code":"289" }, { "desc":"The system does not support online quota adjustment. To increase a resource quota, dial the hotline or send an email to the customer service. We will process your applica", @@ -2462,8 +2606,8 @@ "title":"How Do I Apply for a Higher Quota?", "uri":"dli_03_0032.html", "doc_type":"usermanual", - "p_code":"272", - "code":"274" + "p_code":"288", + "code":"290" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2471,8 +2615,8 @@ "title":"DLI Permissions Management", "uri":"dli_03_0054.html", "doc_type":"usermanual", - "p_code":"147", - "code":"275" + "p_code":"159", + "code":"291" }, { "desc":"You are unable to perform permission operations on the partition columns of partitioned tables.However, when you grant the permission of any non-partition column in a par", @@ -2480,8 +2624,8 @@ "title":"What Is Column-Level Authorization for DLI Partitioned Tables?", "uri":"dli_03_0008.html", "doc_type":"usermanual", - "p_code":"275", - "code":"276" + "p_code":"291", + "code":"292" }, { "desc":"When the user update an existing program package, the following error information is displayed:\"error_code\"*DLI.0003\",\"error_msg\":\"Permission denied for resource 'resourc", @@ -2489,8 +2633,8 @@ "title":"How Do I Do If I Encounter Insufficient Permissions While Updating Packages?", "uri":"dli_03_0195.html", "doc_type":"usermanual", - "p_code":"275", - "code":"277" + "p_code":"291", + "code":"293" }, { "desc":"When the SQL query statement is executed, the system displays a message indicating that the user does not have the permission to query resources.Error information: DLI.00", @@ -2498,8 +2642,8 @@ "title":"Why Is Error \"DLI.0003: Permission denied for resource...\" Reported When I Run a SQL Statement?", "uri":"dli_03_0227.html", "doc_type":"usermanual", - "p_code":"275", - "code":"278" + "p_code":"291", + "code":"294" }, { "desc":"If you have already granted authorization to a table and a test query was successful, but you encounter an error when trying to query it again after some time, you should", @@ -2507,8 +2651,8 @@ "title":"How Do I Do If I Can't Query Table Data After Being Granted Table Permissions?", "uri":"dli_03_0228.html", "doc_type":"usermanual", - "p_code":"275", - "code":"279" + "p_code":"291", + "code":"295" }, { "desc":"If a table inherits database permissions, you do not need to regrant the inherited permissions to the table.Re-authorizing may cause confusion in table permission managem", @@ -2516,8 +2660,8 @@ "title":"Will Granting Duplicate Permissions to a Table After Inheriting Database Permissions Cause an Error?", "uri":"dli_03_0057.html", "doc_type":"usermanual", - "p_code":"275", - "code":"280" + "p_code":"291", + "code":"296" }, { "desc":"User A created Table1.User B created View1 based on Table1.After the Select Table permission on Table1 is granted to user C, user C fails to query View1.User B does not h", @@ -2525,8 +2669,8 @@ "title":"Why Can't I Query a View After I'm Granted the Select Table Permission on the View?", "uri":"dli_03_0067.html", "doc_type":"usermanual", - "p_code":"275", - "code":"281" + "p_code":"291", + "code":"297" }, { "desc":"Despite configuring a job bucket and authorizing DLI to access it, I still receive an error message stating that DLI is not authorized to access the bucket when attemptin", @@ -2534,8 +2678,8 @@ "title":"How Do I Do If I Receive a Message Saying I Don't Have Sufficient Permissions to Submit My Jobs to the Job Bucket?", "uri":"dli_03_0225.html", "doc_type":"usermanual", - "p_code":"275", - "code":"282" + "p_code":"291", + "code":"298" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2543,8 +2687,8 @@ "title":"DLI APIs", "uri":"dli_03_0056.html", "doc_type":"usermanual", - "p_code":"147", - "code":"283" + "p_code":"159", + "code":"299" }, { "desc":"In the REST API provided by DLI, the request header can be added to the request URI, for example, Content-Type.Content-Type indicates the request body type or format. The", @@ -2552,8 +2696,8 @@ "title":"Why Is Error \"unsupported media Type\" Reported When I Subimt a SQL Job?", "uri":"dli_03_0060.html", "doc_type":"usermanual", - "p_code":"283", - "code":"284" + "p_code":"299", + "code":"300" }, { "desc":"When the API call for submitting a SQL job times out, and the following error information is displayed:There are currently no resources tracked in the state, so there is ", @@ -2561,8 +2705,8 @@ "title":"What Can I Do If an Error Is Reported When the Execution of the API for Creating a SQL Job Times Out?", "uri":"dli_03_0178.html", "doc_type":"usermanual", - "p_code":"283", - "code":"285" + "p_code":"299", + "code":"301" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2571,6 +2715,6 @@ "uri":"dli_01_00006.html", "doc_type":"usermanual", "p_code":"", - "code":"286" + "code":"302" } ] \ No newline at end of file diff --git a/docs/dli/umn/dli_01_00006.html b/docs/dli/umn/dli_01_00006.html index 6cff00ac0..6c20f8be5 100644 --- a/docs/dli/umn/dli_01_00006.html +++ b/docs/dli/umn/dli_01_00006.html @@ -8,11 +8,16 @@ -

2025-02-08

+

2025-09-25

+ +

Modified the following sections:

+ + + +

2025-02-08

Modified the following sections:

- +

2024-07-11

@@ -24,7 +29,7 @@

2024-04-28

Added the following section:

- +

2024-02-27

@@ -44,13 +49,13 @@

2023-10-08

Modified the following content:

- +

2023-09-07

Added the following sections:

- +

Deleted the following section:

  • Deleted the content related to Flink job debugging.

Modified the following section:

diff --git a/docs/dli/umn/dli_01_0001.html b/docs/dli/umn/dli_01_0001.html index 4ea540017..f251d8bc4 100644 --- a/docs/dli/umn/dli_01_0001.html +++ b/docs/dli/umn/dli_01_0001.html @@ -6,15 +6,16 @@

Creating Compute Resources and Metadata Required for Running Jobs

-

Importing Data to DLI

  • DLI allows you to analyze and query data stored in OBS without the need to migrate it. Simply upload your data to OBS and use DLI for data analysis.
  • Cross-source access can reduce data duplication and latency when real-time access and processing of data from different sources is required for service needs.

    The prerequisites for cross-source access are that DLI can communicate with the data source network and DLI can obtain the access credentials to the data source.

    +

    Importing Data to DLI

    @@ -64,7 +65,7 @@

Using Cloud Eye to Monitor DLI

You can query DLI monitoring metrics and alarms through Cloud Eye management console or APIs.

-

For example, you can monitor the resource usage and job status of a DLI queue. For details about DLI metrics, see Using Cloud Eye to Monitor DLI.

+

For example, you can monitor the resource usage and job status of a DLI queue. For details about DLI metrics, see Monitoring DLI Using Cloud Eye.

Using CTS to Audit DLI

With CTS, you can log operations related to DLI, making it easier to search, audit, and trace in the future. For the supported operations, see Using CTS to Audit DLI.

diff --git a/docs/dli/umn/dli_01_0002.html b/docs/dli/umn/dli_01_0002.html index 6f2b56e17..c5415bad0 100644 --- a/docs/dli/umn/dli_01_0002.html +++ b/docs/dli/umn/dli_01_0002.html @@ -1,12 +1,12 @@ -

Using DLI to Submit a SQL Job to Query OBS Data

+

Submitting a SQL Job to Query OBS Data Using DLI

Scenario

DLI can query data stored in OBS. This section describes how to use DLI to submit a SQL job to query OBS data.

-

To illustrate, create a new file called sampledata.csv and upload it to an OBS bucket. Then, create an elastic resource pool, create queues within it, and use DLI to create a database and table. Finally, use DLI's SQL editor to query 1,000 data records from the table.

+

To illustrate, create a file called sampledata.csv and upload it to an OBS bucket. Then, create an elastic resource pool, create queues within it, and use DLI to create a database and table. Finally, use DLI's SQL editor to query 1,000 data records from the table.

Procedure

Table 1 shows the process for submitting a SQL job to query OBS data.

-
Table 1 Procedure for using DLI to submit a SQL job to query OBS data

Procedure

+
@@ -17,7 +17,7 @@ - @@ -42,7 +42,7 @@

Step 1: Upload Data to OBS

Upload data files to OBS.

-
  1. Log in to the OBS management console.
  2. Create a bucket. In this example, the bucket name is obs1.
    1. Click Create Bucket in the upper right corner.
    2. On the displayed Create Bucket page, enter the Bucket Name. Retain the default values for other parameters or adjust them as needed.

      Select a region that matches the location of the DLI console.

      +
      1. Log in to the OBS management console.
      2. Create a bucket. In this example, the bucket name is obs1.
        1. Click Create Bucket in the upper right corner.
        2. On the displayed Create Bucket page, set Bucket Name. Retain the default values for other parameters or adjust them as needed.

          Select a region that matches the location of the DLI console.

        3. Click Create Now.
      3. Click obs1 to access its Objects tab page.
      4. Click Upload Object. In the displayed dialog box, drag a desired file or folder, for example, sampledata.csv to the Upload Object area. Then, click Upload.

        You can create a sampledata.txt file, copy the following content separated by commas (,), and save the file as sampledata.csv.

        @@ -51,11 +51,11 @@ 22,book_2 29,book_9

        After the file is uploaded successfully, the file path is obs://obs1/sampledata.csv.

        -

        For more operations on the OBS console, see the Object Storage Service User Guide.

        +

        For more operations on the OBS console, see Object Storage Service User Guide.

      -

      Step 2: Create an Elastic Resource Pool and Add Queues to the Pool

      In this example, the elastic resource pool dli_resource_pool and queue dli_queue_01 are created.
      1. Log in to the DLI management console.
      2. In the navigation pane on the left, choose Resources > Resource Pool.
      3. On the displayed page, click Buy Resource Pool in the upper right corner.
      4. On the displayed page, set the parameters.
        Table 2 describes the parameters. -
Table 1 Procedure for using DLI to submit a SQL job to query OBS data

Step

Description

Upload data files to OBS.

Step 2: Create an Elastic Resource Pool and Add Queues to the Pool

+

Step 2: Create an Elastic Resource Pool and Create Queues Within It

Create compute resources required for submitting jobs.
Table 2 Parameters

Parameter

+

Step 2: Create an Elastic Resource Pool and Create Queues Within It

In this example, the elastic resource pool dli_resource_pool and queue dli_queue_01 are created.
  1. Log in to the DLI management console.
  2. In the navigation pane on the left, choose Resources > Resource Pool.
  3. On the displayed page, click Buy Resource Pool in the upper right corner.
  4. On the displayed page, set the parameters.
    Table 2 describes the parameters. +
    @@ -137,7 +137,8 @@ -
    Table 2 Parameter descriptions

    Parameter

    Description

    Type of the queue

    • To execute SQL jobs, select For SQL.
    • To execute Flink or Spark jobs, select For general purpose.

    _

    +

    For SQL jobs, select For SQL.

    +

    For other scenarios, select For general purpose.

    Enterprise Project

    @@ -197,9 +198,9 @@

    Step 3: Create a Database

    Before querying data, create a database, for example, db1.

    -

    The default database is a built-in database. You cannot create the default. database.

    +

    default is the database built in DLI. You cannot create a database named default.

    -
    1. In the left navigation pane of the DLI management console, choose SQL Editor.
    2. In the editing window on the right of the SQL Editor page, enter the following SQL statement and click Execute. Read and agree to the privacy agreement, and click OK.
      create database db1;
      +
      1. In the navigation pane on the left of the DLI management console, choose SQL Editor.
      2. In the editing window on the right of the SQL Editor page, enter the following SQL statement and click Execute. Read and agree to the privacy agreement, and click OK.
        create database db1;

        After the database is successfully created, click in the middle pane to refresh the database list. The new database db1 is displayed in the list.

    diff --git a/docs/dli/umn/dli_01_0003.html b/docs/dli/umn/dli_01_0003.html index 67edbadd3..3744d1fde 100644 --- a/docs/dli/umn/dli_01_0003.html +++ b/docs/dli/umn/dli_01_0003.html @@ -1,40 +1,45 @@

    Overview of Enhanced Datasource Connections

    -

    Why Create Enhanced Datasource Connections?

    In cross-source data analysis scenarios, DLI needs to connect to external data sources. However, due to the different VPCs between the data source and DLI, the network cannot be connected, which results in DLI being unable to read data from the data source. DLI's enhanced datasource connection feature enables network connectivity between DLI and the data source.

    -

    This section will introduce a solution for cross-VPC data source network connectivity:

    -
    • Creating an enhanced datasource connection: Establish a VPC peering connection to connect DLI and the data source's VPC network.
    • Testing network connectivity: Verify the connectivity between the queue and the data source's network.
    -

    For details about the data sources that support cross-source access, see Common Development Methods for DLI Cross-Source Analysis.

    -

    In cross-source development scenarios, there is a risk of password leakage if datasource authentication information is directly configured. You are advised to use Data Encryption Workshop (DEW) to store authentication information of data sources when Spark 3.3.1 or later and Flink 1.15 or later jobs access data sources using datasource connections. This will help you address issues related to data security, key security, and complex key management. For details, see Using DEW to Manage Access Credentials for Data Sources.

    -
    +

    How to Establish Network Connectivity Between a DLI Elastic Resource Pool and Data Sources?

    Imagine DLI elastic resource pools and data sources as two isolated islands surrounded by water.

    +

    To enable traffic between these two islands, you need to first construct a bridge and then set up signs at both ends of this bridge.

    +

    DLI enhanced datasource connections serve as your construction team, enabling you to complete the building of both the bridge and the signs in one go.

    +

    By using VPC peering to establish the bridge and defining system routes for direction guidance, you can further enhance navigation with additional custom routes.

    +

    If both DLI elastic resource pools and the CIDR block of data sources have IPv6 enabled, you have the option to designate this bridge to utilize the IPv6 network for communication. Moreover, you can create IPv6 routes.

    +
    Figure 1 Using an enhanced datasource connection to establish network communication between a DLI elastic resource pool and a data source
    +
    +

    Procedure

    This part introduces the network connectivity solution for connecting a DLI elastic resource pool to a data source of a VPC using an enhanced datasource connection.

    +
    1. Creating an enhanced datasource connection: Establish a VPC peering connection to connect DLI and the data source's VPC network. For details, see Creating an Enhanced Datasource Connection.
    2. Configure routing rules: After an enhanced datasource connection is created, the CIDR block is automatically associated with the system default route without additional operations.

      Besides the system default route, you can add custom routing rules as needed to forward traffic destined for the target address to the specified next-hop address. For details, see Adding a Route for an Enhanced Datasource Connection.

      +
    3. Testing network connectivity: Verify the connectivity between the queue and the data source's network. See Testing the Network Connectivity Between a Queue and a Data Source.
    +
    Figure 2 Using an enhanced datasource connection to establish network communication between a DLI elastic resource pool and a data source

    Notes and Constraints

    -
    Table 1 Notes and constraints on enhanced datasource connections

    Item

    +
    - - - - - - - - - @@ -43,9 +48,6 @@
    Table 1 Notes and constraints on enhanced datasource connections

    Item

    Description

    +

    Description

    Use case

    +

    Use case

    • Datasource connections cannot be created for the default queue.
    • Flink jobs can directly access DIS, OBS, and SMN data sources without using datasource connections.
    +
    • Datasource connections cannot be created for the default queue.
    • Flink jobs can directly access DIS, OBS, and SMN data sources without using datasource connections.

    Permission

    +

    Permission

    • VPC Administrator permissions are required for enhanced connections to use VPCs, subnets, routes, VPC peering connections.
    +
    • VPC Administrator permissions are required for enhanced connections to use VPCs, subnets, routes, VPC peering connections.

    Usage

    +

    Usage

    • If you use an enhanced datasource connection, the CIDR block of the elastic resource pool or queue cannot overlap with that of the data source.
    • Only queues bound with datasource connections can access datasource tables.
    • Datasource tables do not support the preview function.
    +
    • If you use an enhanced datasource connection, the CIDR block of the elastic resource pool or queue cannot overlap with that of the data source.
    • Only queues bound with datasource connections can access datasource tables.
    • Datasource tables do not support the preview function.

    Connectivity check

    +

    Connectivity check

    • When checking the connectivity of datasource connections, the notes and constraints on IP addresses are:
      • The IP address must be valid, which consists of four decimal numbers separated by periods (.). The value ranges from 0 to 255.
      • During the test, you can add a port after the IP address and separate them with colons (:). The port can contain a maximum of five digits. The value ranges from 0 to 65535.

        For example, 192.168.xx.xx or 192.168.xx.xx:8181.

        +
    • When checking the connectivity of datasource connections, the notes and constraints on IP addresses are:
      • The IP address must be valid, which consists of four decimal digits separated by periods (.). The value ranges from 0 to 255.
      • During the test, you can add a port after the IP address and separate them with colons (:). The port can contain a maximum of five digits. The value ranges from 0 to 65535.

        For example, 192.168.xx.xx or 192.168.xx.xx:8181.

      -
    • When checking the connectivity of datasource connections, the notes and constraints on domain names are:
      • The domain name can contain 1 to 255 characters. Only letters, numbers, underscores (_), and hyphens (-) are allowed.
      • The top-level domain name must contain at least two letters, for example, .com, .net, and .cn.
      • During the test, you can add a port after the domain name and separate them with colons (:). The port can contain a maximum of five digits. The value ranges from 0 to 65535.

        Example: example.com:8080

        +
      • When checking the connectivity of datasource connections, the notes and constraints on domain names are:
        • The domain name can contain 1 to 255 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed.
        • The top-level domain name must contain at least two letters, for example, .com, .net, and .cn.
        • During the test, you can add a port after the domain name and separate them with colons (:). The port can contain a maximum of five digits. The value ranges from 0 to 65535.

          Example: example.com:8080

    -

    Cross-Source Analysis Process

    To use DLI for cross-source analysis, you need to create a datasource connection to connect DLI to the data source, and then develop jobs to access the data source.

    -
    Figure 1 Cross-source analysis flowchart
    -
    @@ -53,3 +55,10 @@
    + + \ No newline at end of file diff --git a/docs/dli/umn/dli_01_0004.html b/docs/dli/umn/dli_01_0004.html index 1f4245345..fe01438aa 100644 --- a/docs/dli/umn/dli_01_0004.html +++ b/docs/dli/umn/dli_01_0004.html @@ -10,12 +10,12 @@
  5. Changing the Database Owner on the DLI Console
    6. -
  6. Managing Tags
    +
  7. Managing Tags for Database Tables
    8. -
    Parent topic: Creating Databases and Tables
    +
    Parent topic: Creating a Data Directory, Database, and Table
    diff --git a/docs/dli/umn/dli_01_0005.html b/docs/dli/umn/dli_01_0005.html index 35dd222c2..ef2c0e7dd 100644 --- a/docs/dli/umn/dli_01_0005.html +++ b/docs/dli/umn/dli_01_0005.html @@ -1,19 +1,19 @@ -

    Creating a Database and Table on the DLI Console

    -

    A database, built on the computer storage device, is a data warehouse where data is organized, stored, and managed based on its structure.

    -

    The table is an important part of the database. It consists of rows and columns. Each column functions as a field. Each value in a field (column) represents a type of data.

    -

    The database is a framework and the table contains data content. A database has one or more tables.

    -

    You can create databases and tables on the management console or using SQL statements. This section describes how to create a database and a table on the management console.

    -

    A view can be created only by using SQL statements. You cannot create a view on the Create Table page.

    +

    Creating a Data Catalog, Database, and Table on the DLI Console

    +
    • A database is a repository of data organized, stored, and managed on computer storage devices according to data structures.
    • A table is one of the most essential components of a database. It is composed of rows and columns, with each column regarded as a field. The values within each field represent a specific type of data.

      A database is a framework, and tables are its essential content. A database contains one or more tables.

      +
    +

    You can create databases and tables on the management console or using SQL statements.

    +

    +

    +

    This section describes how to create a data catalog, database, and table on the management console.

    +
    • Views can be created only by using SQL statements, not through the Create Table page.
    • For Hudi tables created using SQL statements, you need to configure Hive synchronization parameters before they can be checked in the databases and tables on the DLI management console.
    -

    Precautions

    • If a folder and a file have the same name in the OBS directory, the file path is preferred as the path of the OBS table to be created.
    -
    -

    Creating a Database

    1. You can create a database on either the Data Management page or the SQL Editor page.

      • To create a database on the Data Management page:
        1. On the left of the management console, choose Data Management > Databases and Tables.
        2. In the upper right corner of the Databases and Tables page, click Create Database to create a database.
        -
      • To create a database on the SQL Editor page:
        1. On the left of the management console, click SQL Editor.
        2. In the navigation pane on the left, click next to Databases.
        +

        Creating a Database

        1. You can create a database on either the Data Management page or the SQL Editor page.

          • To create a database on the Data Management page:
            1. In the navigation pane on the left of the console, choose Data Management > Databases and Tables.
            2. In the upper right corner of the Databases and Tables page, click Create Database to create a database.
            +
          • To create a database on the SQL Editor page:
            1. In the navigation pane on the left of the management console, choose SQL Editor.
            2. In the navigation pane on the left, click next to Databases.

        2. In the displayed Create Database dialog box, specify Name and Description by referring to Table 1.

          -

          Table 1 Description

          Parameter

          +
          @@ -21,7 +21,7 @@ - @@ -36,10 +36,10 @@ @@ -51,174 +51,177 @@

          Creating a Table

          Before creating a table, ensure that a database has been created.

          -
          1. You can create a table on either the Databases and Tables page or the SQL Editor page.

            Datasource connection tables, such as View tables, HBase (MRS) tables, OpenTSDB (MRS) tables, GaussDB(DWS) tables, RDS tables, and CSS tables, cannot be created. You can use SQL to create views and datasource connection tables. For details, see sections Creating a View and Creating a Datasource Connection Table in the Data Lake Insight SQL Syntax Reference.

            +
            1. You can create a table on either the Databases and Tables page or the SQL Editor page.

              Datasource connection tables, such as View tables, HBase (MRS) tables, OpenTSDB (MRS) tables, GaussDB(DWS) tables, RDS tables, and CSS tables, cannot be created. You can use SQL to create views and datasource connection tables. For details, see "Creating a View" and "Creating a Datasource Connection Table" in Data Lake Insight SQL Syntax Reference.

              -
              • To create a table on the Data Management page:
                1. On the left of the management console, choose Data Management > Databases and Tables.
                2. On the Databases and Tables page, select the database for which you want to create a table. In the Operation column, click More > Create Table to create a table in the current database.
                -
              • To create a table on the SQL Editor page:
                1. On the left of the management console, click SQL Editor.
                2. In the navigation pane of the displayed SQL Editor page, click Databases. You can create a table in either of the following ways:
                  • Click a database name. In the Tables area, click on the right to create a table in the current database.
                  • Click on the right of the database and choose Create Table from the shortcut menu to create a table in the current database.
                  +
                  • To create a table on the Data Management page:
                    1. In the navigation pane on the left of the console, choose Data Management > Databases and Tables.
                    2. On the Databases and Tables page, select the database for which you want to create a table. In the Operation column, click More > Create Table to create a table in the current database.
                    +
                  • To create a table on the SQL Editor page:
                    1. In the navigation pane on the left of the management console, choose SQL Editor.
                    2. In the navigation pane of the displayed SQL Editor page, click Databases. You can create a table in either of the following ways:
                      • Click a database name. In the Tables area, click on the right to create a table in the current database.
                      • Click on the right of the database and choose Create Table from the shortcut menu to create a table in the current database.
                  -

                3. In the displayed Create Table dialog box, set parameters as required.

                  • If you set Data Location to DLI, set related parameters by referring to Table 2.
                  • If you set Data Location to OBS, set related parameters by referring to Table 2 and Table 3. -
          Table 1 Parameter descriptions

          Parameter

          Description

          Database Name

          • Only numbers, letters, and underscores (_) are allowed. The value cannot contain only numbers or start with an underscore (_).
          • The database name is case insensitive and cannot be left blank.
          • The value can contain a maximum of 128 characters.
          +
          • Only digits, letters, and underscores (_) are allowed. The value cannot contain only digits or start with an underscore (_).
          • The database name is case insensitive and cannot be left blank.
          • The value can contain a maximum of 128 characters.
          NOTE:

          The default database is a built-in database. You cannot create the default. database.

          Tags used to identify cloud resources. A tag includes the tag key and tag value. If you want to use the same tag to identify multiple cloud resources, that is, to select the same tag from the drop-down list box for all services, you are advised to create predefined tags on the Tag Management Service (TMS).

          NOTE:
          • A maximum of 20 tags can be added.
          • Only one tag value can be added to a tag key.
          • The key name in each resource must be unique.
          -
          • Tag key: Enter a tag key name in the text box.
            NOTE:

            A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.

            +
            • Tag key: Enter a tag key name in the text box.
              NOTE:

              A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.

            -
            • Tag value: Enter a tag value in the text box.
              NOTE:

              A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.

              +
              • Tag value: Enter a tag value in the text box.
                NOTE:

                A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.
          Table 2 Common parameters

          Parameter

          +

        3. In the displayed Create Table dialog box, set parameters as required.

          • If you set Data Location to DLI, set related parameters by referring to Table 2.
          • If you set Data Location to OBS, set related parameters by referring to Table 2 and Table 3.

            When there are both a folder and a file with the same name in the OBS directory, creating an OBS table pointing to that path will prioritize the file over the folder.

            + +
            - - - - - - - - - - - - - - - - - - - - - - - - - -
            Table 2 Common parameters

            Parameter

            Description

            +

            Description

            Example

            +

            Example

            Table Name

            +

            Table Name

            • Only numbers, letters, and underscores (_) are allowed. The value cannot contain only numbers or start with an underscore (_).
            • The table name is case insensitive and cannot be left unspecified.
            • The table name can contain the dollar sign ($). An example value is $test.
            • The value can contain a maximum of 128 characters.
            +
            • Only digits, letters, and underscores (_) are allowed. The value cannot contain only digits or start with an underscore (_).
            • The table name is case insensitive and cannot be left unspecified.
            • The table name can contain the dollar sign ($). An example value is $test.
            • The value can contain a maximum of 128 characters.

            table01

            +

            table01

            Data Location

            +

            Data Location

            Data storage location. Currently, DLI and OBS are supported.

            +

            Data storage location. Currently, DLI and OBS are supported.

            DLI

            +

            DLI

            Description

            +

            Description

            Description of the table.

            +

            Description of the table.

            -

            +

            -

            Column Type

            +

            Column Type

            Available values: Normal or Partition

            +

            Available values: Normal or Partition

            Normal

            +

            Normal

            Column

            +

            Column

            Name of a column in a table. The column name must contain at least one letter and can contain underscores (_). It cannot contain only numbers.

            +

            Name of a column in a table. The column name must contain at least one letter and can contain underscores (_). It cannot contain only digits.

            You can select Normal or Partition. Partition columns are dedicated to partition tables. User data is partitioned to improve query efficiency.

            NOTE:

            The column name is case-insensitive and must be unique.

            name

            +

            name

            Type

            +

            Type

            Data type of a column. This parameter corresponds to Column Name.

            -
            • string: The data is of the string type.
            • int: Each integer is stored on four bytes.
            • date: The value ranges from 0000-01-01 to 9999-12-31.
            • double: Each number is stored on eight bytes.
            • boolean: Each value is stored on one byte.
            • decimal: The valid bits are positive integers between 1 to 38, including 1 and 38. The decimal digits are integers less than 10.
            • smallint/short: The number is stored on two bytes.
            • bigint/long: The number is stored on eight bytes.
            • timestamp: The data indicates a date and time. The value can be accurate to six decimal points.
            • float: Each number is stored on four bytes.
            • tinyint: Each number is stored on one byte. Only OBS tables support this data type.
            +

            Data type of a column. This parameter corresponds to Column Name.

            +
            • string: The data is of the string type.
            • int: Each integer is stored on four bytes.
            • date: The value ranges from 0000-01-01 to 9999-12-31.
            • double: Each number is stored on eight bytes.
            • boolean: Each value is stored on one byte.
            • decimal: The valid bits are positive integers between 1 to 38, including 1 and 38. The decimal digits are integers less than 10.
            • smallint/short: The number is stored on two bytes.
            • bigint/long: The number is stored on eight bytes.
            • timestamp: The data indicates a date and time. The value can be accurate to six decimal points.
            • float: Each number is stored on four bytes.
            • tinyint: Each number is stored on one byte. Only OBS tables support this data type.

            string

            +

            string

            Column Description

            +

            Column Description

            Description of a column.

            +

            Description of a column.

            -

            +

            -

            Operation

            +

            Operation

            • Add Column
            • Delete
              NOTE:

              If the table to be created includes a great number of columns, you are advised to use SQL statements to create the table or import column information from the local EXCEL file.

              +
            • Add Column
            • Delete
              NOTE:

              If the table to be created includes a great number of columns, you are advised to use SQL statements to create the table or import column information from the local EXCEL file.

            -

            +

            -
            -
            - @@ -40,45 +40,108 @@
            Table 3 Parameter description when Data Location is set to OBS

            Parameter

            +
            - - - - - - - - - - - - - - - - - - - - - - - - - -
            Table 3 Parameter descriptions when Data Location is set to OBS

            Parameter

            Description

            +

            Description

            Example

            +

            Example

            Data Format

            +

            Data Format

            DLI supports the following data formats:

            -
            • Parquet: DLI can read non-compressed data or data that is compressed using Snappy and gzip.
            • CSV: DLI can read non-compressed data or data that is compressed using gzip.
            • ORC: DLI can read non-compressed data or data that is compressed using Snappy.
            • JSON: DLI can read non-compressed data or data that is compressed using gzip.
            • Avro: DLI can read uncompressed Avro data.
            +

            DLI supports the following data formats:

            +
            • Parquet: DLI can read non-compressed data or data that is compressed using Snappy and gzip.
            • CSV: DLI can read non-compressed data or data that is compressed using gzip.
            • ORC: DLI can read non-compressed data or data that is compressed using Snappy.
            • JSON: DLI can read non-compressed data or data that is compressed using gzip.
            • Avro: DLI can read uncompressed Avro data.

            CSV

            +

            CSV

            Storage Path

            +

            Storage Path

            Enter or select an OBS path. The path can be a folder or a path.

            -
            NOTE:

            If you need to import data stored in OBS to the OBS table, set this parameter to the path of a folder. If the table creation path is a file, data fails to be imported.

            -
            +

            Enter or select an OBS path. The path can be a file or folder.

            +
            • When creating an OBS table, you must specify a folder as the path. If a file is specified, data cannot be imported.
            • When there are both a folder and a file with the same name in the OBS directory, importing data pointing to that path will prioritize the file over the folder.

            obs://obs1/sampledata.csv

            +

            obs://obs1/sampledata.csv

            Table Header: No/Yes

            +

            Table Header: No/Yes

            This parameter is valid only when Data Format is set to CSV. Whether the data source to be imported contains the table header.

            +

            This parameter is valid only when Data Format is set to CSV. Whether the data source to be imported contains the table header.

            Click Advanced Settings and select the checkbox next to Table Header: No. If the checkbox is selected, the table header is displayed. If the checkbox is deselected, no table header is displayed.

            -

            +

            -

            User-defined Delimiter

            +

            User-defined Delimiter

            This parameter is valid only when Data Format is set to CSV and you select User-defined Delimiter.

            +

            This parameter is valid only when Data Format is set to CSV and you select User-defined Delimiter.

            The following delimiters are supported:

            • Comma (,)
            • Vertical bar (|)
            • Tab character (\t)
            • Others: Enter a user-defined delimiter.

            Comma (,)

            +

            Comma (,)

            User-defined Quotation Character

            +

            User-defined Quotation Character

            This parameter is valid only when Data Format is set to CSV and you select User-defined Quotation Character.

            +

            This parameter is valid only when Data Format is set to CSV and you select User-defined Quotation Character.

            The following quotation characters are supported:

            • Single quotation mark (')
            • Double quotation marks (")
            • Others: Enter a user-defined quotation character.

            Single quotation mark (')

            +

            Single quotation mark (')

            User-defined Escape Character

            +

            User-defined Escape Character

            This parameter is valid only when Data Format is set to CSV and you select User-defined Escape Character.

            +

            This parameter is valid only when Data Format is set to CSV and you select User-defined Escape Character.

            The following escape characters are supported:

            • Backslash (\)
            • Others: Enter a user-defined escape character.

            Backslash (\)

            +

            Backslash (\)

            Date Format

            +

            Date Format

            This parameter is valid only when Data Format is set to CSV or JSON.

            +

            This parameter is valid only when Data Format is set to CSV or JSON.

            This parameter specifies the format of the date in the table and is valid only Advanced Settings is selected. The default value is yyyy-MM-dd. For definition of characters involved in the date pattern, see Table 3 in .

            2000-01-01

            +

            2000-01-01

            Timestamp Format

            +

            Timestamp Format

            This parameter is valid only when Data Format is set to CSV or JSON.

            +

            This parameter is valid only when Data Format is set to CSV or JSON.

            This parameter specifies the format of the timestamp in the table and is valid only Advanced Settings is selected. The default value is yyyy-MM-dd HH:mm:ss. For definition of characters involved in the time pattern, see Table 3 in .

            2000-01-01 09:00:00

            +

            2000-01-01 09:00:00
            -

          • Click OK.

            After a table is created, you can view and select the table for use on the Data Management page or SQL Editor page.

            -

          • (Optional) After a DLI table is created, you can decide whether to directly import data to the table.
            • +

          • Click OK.

            After a table is created, you can view and select the table for use on the Data Management page or SQL Editor page.

            +

            • + +

            Related Operations

            After a table is created, you can import data from other OBS buckets to the table.

            +

            For details about how to import data, see Importing OBS Data to a DLI Table.

            diff --git a/docs/dli/umn/dli_01_0006.html b/docs/dli/umn/dli_01_0006.html index 9fe5f682f..96c36cb4e 100644 --- a/docs/dli/umn/dli_01_0006.html +++ b/docs/dli/umn/dli_01_0006.html @@ -29,9 +29,9 @@

            Connectivity check

            • When checking the connectivity of datasource connections, the notes and constraints on IP addresses are:
              • The IP address must be valid, which consists of four decimal numbers separated by periods (.). The value ranges from 0 to 255.
              • During the test, you can add a port after the IP address and separate them with colons (:). The port can contain a maximum of five digits. The value ranges from 0 to 65535.

                For example, 192.168.xx.xx or 192.168.xx.xx:8181.

                +
            • When checking the connectivity of datasource connections, the notes and constraints on IP addresses are:
              • The IP address must be valid, which consists of four decimal digits separated by periods (.). The value ranges from 0 to 255.
              • During the test, you can add a port after the IP address and separate them with colons (:). The port can contain a maximum of five digits. The value ranges from 0 to 65535.

                For example, 192.168.xx.xx or 192.168.xx.xx:8181.

              -
            • When checking the connectivity of datasource connections, the notes and constraints on domain names are:
              • The domain name can contain 1 to 255 characters. Only letters, numbers, underscores (_), and hyphens (-) are allowed.
              • The top-level domain name must contain at least two letters, for example, .com, .net, and .cn.
              • During the test, you can add a port after the domain name and separate them with colons (:). The port can contain a maximum of five digits. The value ranges from 0 to 65535.

                Example: example.com:8080

                +
              • When checking the connectivity of datasource connections, the notes and constraints on domain names are:
                • The domain name can contain 1 to 255 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed.
                • The top-level domain name must contain at least two letters, for example, .com, .net, and .cn.
                • During the test, you can add a port after the domain name and separate them with colons (:). The port can contain a maximum of five digits. The value ranges from 0 to 65535.

                  Example: example.com:8080

            -

            Process

            Figure 1 Enhanced datasource connection creation flowchart
            +

            Procedure

            This part introduces the network connectivity solution for connecting a DLI elastic resource pool to a data source of a VPC using an enhanced datasource connection.

            +
            1. Creating an enhanced datasource connection: Establish a VPC peering connection to connect DLI and the data source's VPC network. For details, see Creating an Enhanced Datasource Connection.
            2. Configure routing rules: After an enhanced datasource connection is created, the CIDR block is automatically associated with the system default route without additional operations.

              Besides the system default route, you can add custom routing rules as needed to forward traffic destined for the target address to the specified next-hop address. For details, see Adding a Route for an Enhanced Datasource Connection.

              +
            3. Testing network connectivity: Verify the connectivity between the queue and the data source's network. See Testing the Network Connectivity Between a Queue and a Data Source.
            +

            For details about the data sources that support datasource connections, see Common Development Methods for DLI Cross-Source Analysis.

            +
            Figure 1 Using an enhanced datasource connection to establish network communication between a DLI elastic resource pool and a data source
            -

            Prerequisites

            • An elastic resource pool or queue has been created.
            • You have obtained the VPC, subnet, private IP address, port, and security group information of the external data source.
            • The security group of the external data source has allowed access from the CIDR block of the elastic resource pool or queue.
            +

            Prerequisites

            -

            Procedure

            1. Create an Enhanced Datasource Connection

              1. Log in to the DLI management console.
              2. In the navigation pane on the left, choose Datasource Connections.
              3. On the displayed Enhanced tab, click Create.

                Set parameters based on Table 2.

                +

                Preparation: Allow the CIDR Block of the Elastic Resource Pool to Pass Through the Security Group Where the Data Source Is

                1. On the DLI management console, obtain the CIDR block of the elastic resource pool.

                  In the navigation pane on the left, choose Resources > Resource Pool. On the displayed page, locate your desired elastic resource pool, click to expand its details, and find its CIDR block.

                  +
                2. Log in to the VPC console and find the VPC the data source belongs to.
                3. On the network console, choose Virtual Private Cloud > Network Interfaces. On the Network Interfaces tab page displayed, search for the security group name, click More in the Operation column, and select Change Security Group.
                4. In the navigation pane on the left, choose Access Control > Security Groups.
                5. Click the name of the security group to which the external data source belongs.
                6. On the Inbound Rules tab, add a rule to allow access from the queue network segment.

                  Configure the inbound rule parameters according to Table 2.

                  -
                  Table 2 Parameters

                  Parameter

                  +
                  - + - - + - - + + + + + + + + + + + + + + + + + + + +
                  Table 2 Inbound rule parameters

                  Parameter

                  Description

                  +

                  Description

                  +

                  Example Value

                  Connection Name

                  +

                  Priority

                  Name of the created datasource connection.

                  -
                  • Only letters, numbers, and underscores (_) are allowed. The parameter must be specified.
                  • A maximum of 64 characters are allowed.
                  +

                  Priority of a security group rule.

                  +

                  The priority value ranges from 1 to 100. The default value is 1, indicating the highest priority. A smaller value indicates a higher priority of a security group rule.

                  +

                  1

                  Resource Pool

                  +

                  Action

                  It binds an elastic resource pool or queue that uses a datasource connection. This parameter is optional.

                  -

                  In regions where this function is available, an elastic resource pool with the same name is created by default for the queue created in "Creating a Queue."

                  -
                  NOTE:

                  Before using an enhanced datasource connection, you must bind a queue and ensure that the VPC peering connection is in the Active state.

                  +

                  Action of the security group rule.

                  +

                  Allow

                  +

                  Protocol & Port

                  +
                  • Network protocol. The value can be All, TCP, UDP, ICMP, or GRE.
                  • Port: Port or port range over which the traffic can reach your instance. The port ranges from 1 to 65535.
                  +

                  In this example, select TCP. Leave the port blank or set it to the data source port.

                  +

                  Type

                  +

                  Type of IP addresses.

                  +

                  IPv4

                  +

                  Source

                  +

                  Allows access from IP addresses or instances in another security group.

                  +

                  In this example, enter the obtained queue CIDR block.

                  +

                  Description

                  +

                  Supplementary information about the security group rule. This parameter is optional.

                  +

                  _

                  +
                  +
                  + + +

                  Step 1: Create an Enhanced Datasource Connection

                  1. Log in to the DLI management console.
                  2. In the navigation pane on the left, choose Datasource Connections.
                  3. On the displayed Enhanced tab, click Create.

                    Set parameters according to Table 3.

                    + +
                    + + + + + + + + - - - - - - - - @@ -104,70 +167,40 @@
                  4. Click OK.

                    After the creation is complete, the enhanced datasource connection is in the Active state, indicating that the connection is successfully created.

                    5. -

                  5. Security Group Where the Data Source Belongs Allows Access from the CIDR Block of the Elastic Resource Pool

                    1. On the DLI management console, obtain the network segment of the elastic resource pool or queue.

                      Choose Resources > Queue Management from the left navigation pane. On the page displayed, locate the queue on which jobs are running, and click the button next to the queue name to obtain the CIDR block of the queue.

                      -
                    2. Log in to the VPC console and find the VPC the data source belongs to.
                    3. On the network console, choose Virtual Private Cloud > Network Interfaces. On the Network Interfaces tab page displayed, search for the security group name, click More in the Operation column, and select Change Security Group.
                    4. In the navigation pane on the left, choose Access Control > Security Groups.
                    5. Click the name of the security group to which the external data source belongs.
                    6. Click the Inbound Rules tab and add a rule to allow access from the CIDR block of the queue.

                      Configure the inbound rule parameters according to Table 3.

                      + +

                      (Optional) Step 2: Configure a Routing Rule

                      Routing rules determine the direction of network traffic by configuring information such as the destination address, next hop type, and next hop address. Routes are classified into system routes and custom routes.

                      +

                      After an enhanced datasource connection is created, the subnet is automatically associated with the system default route. Besides the system default route, you can add custom routing rules as needed to forward traffic destined for the target address to the specified next-hop address.

                      +
                      1. Log in to the DLI management console.
                      2. In the navigation pane on the left, choose Datasource Connections.
                      3. On the displayed Enhanced tab, locate the enhanced datasource connection where you want to add a route and then add a route.
                        • Method 1:
                          1. On the Enhanced tab, locate the enhanced datasource connection where you want to add a route and click Manage Route in its Operation column.
                          2. On the displayed page, click Add Route.
                          3. In the Add Route dialog box, set the parameters based on Table 4.
                          4. Click OK.
                          +
                        • Method 2:
                          1. On the Enhanced tab, locate the enhanced datasource connection where you want to add a route, click More in its Operation column, and select Add Route.
                          2. In the Add Route dialog box, set the parameters based on Table 4.
                          3. Click OK.
                          +
                        -
                    6. Table 3 Parameter descriptions

                    Parameter

                    +

                    Description

                    +

                    Connection Name

                    +

                    Name of the created datasource connection.

                    +
                    • Only letters, digits, and underscores (_) are allowed. The parameter must be specified.
                    • The value can contain a maximum of 64 characters.
                    +

                    Resource Pool

                    +

                    This parameter is optional when you create an enhanced datasource connection. However, you must bind an elastic resource pool to the enhanced datasource connection before using it.

                    +

                    The status of the enhanced datasource connection's VPC peering connection is active. Used to bind an elastic resource pool or queue that uses a datasource connection.

                    +
                    NOTE:

                    Before using an enhanced datasource connection, ensure that the created VPC peering connection is in the Active state.

                    VPC

                    +

                    VPC

                    VPC used by the data source.

                    +

                    VPC used by the data source.

                    Subnet

                    +

                    Subnet

                    Subnet used by the data source.

                    +

                    Subnet used by the data source.

                    Host Information

                    +

                    Host Information

                    In this text field, you can configure the mapping between host IP addresses and domain names so that jobs can only use the configured domain names to access corresponding hosts. This parameter is optional.

                    +

                    In this text field, you can configure the mapping between host IP addresses and domain names so that jobs can only use the configured domain names to access corresponding hosts. This parameter is optional.

                    For example, when accessing the HBase cluster of MRS, you need to configure the host name (domain name) and IP address of the ZooKeeper instance. Enter one record in each line in the format of IP address Host name/Domain name.

                    Example:

                    192.168.0.22 node-masterxxx1.com

                    @@ -86,15 +149,15 @@

                    For details about how to obtain host information, see How Do I Obtain MRS Host Information?.

                    Tags

                    +

                    Tags

                    Tags used to identify cloud resources. A tag includes the tag key and tag value. If you want to use the same tag to identify multiple cloud resources, that is, to select the same tag from the drop-down list box for all services, you are advised to create predefined tags on the Tag Management Service (TMS).

                    +

                    Tags used to identify cloud resources. A tag includes the tag key and tag value. If you want to use the same tag to identify multiple cloud resources, that is, to select the same tag from the drop-down list box for all services, you are advised to create predefined tags on the Tag Management Service (TMS).

                    NOTE:
                    • A maximum of 20 tags can be added.
                    • Only one tag value can be added to a tag key.
                    • The key name in each resource must be unique.
                    -
                    • Tag key: Enter a tag key name in the text box.
                      NOTE:

                      A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.

                      +
                      • Tag key: Enter a tag key name in the text box.
                        NOTE:

                        A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.

                      -
                      • Tag value: Enter a tag value in the text box.
                        NOTE:

                        A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.

                        +
                        • Tag value: Enter a tag value in the text box.
                          NOTE:

                          A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.
                    Table 3 Inbound rule parameters

                    Parameter

                    +
                    - - - - - - - - - - - - - - - - - - - - - - - -
                    Table 4 Parameters for adding a custom route

                    Parameter

                    Description

                    -

                    Example Value

                    +

                    Description

                    Priority

                    +

                    Route Name

                    Priority of a security group rule.

                    -

                    The priority value ranges from 1 to 100. The default value is 1, indicating the highest priority. A smaller value indicates a higher priority of a security group rule.

                    -

                    1

                    +

                    Name of a custom route, which is unique in the same enhanced datasource connection. The name can contain up to 64 characters. Only digits, letters, underscores (_), and hyphens (-) are allowed.

                    Action

                    +

                    IP Address

                    Action of the security group rule.

                    -

                    Allow

                    -

                    Protocol & Port

                    -
                    • Network protocol. The value can be All, TCP, UDP, ICMP, or GRE.
                    • Port: Port or port range over which the traffic can reach your instance. The port ranges from 1 to 65535.
                    -

                    In this example, select TCP. Leave the port blank or set it to the data source port.

                    -

                    Type

                    -

                    Type of IP addresses.

                    -

                    IPv4

                    -

                    Source

                    -

                    Allows access from IP addresses or instances in another security group.

                    -

                    In this example, enter the obtained queue CIDR block.

                    -

                    Description

                    -

                    Supplementary information about the security group rule. This parameter is optional.

                    -

                    _

                    +

                    Custom route CIDR block. The CIDR blocks of different routes can overlap but cannot be identical.

                    +

                    Do not add the 100.125.xx.xx or 100.64.xx.xx CIDR blocks to avoid conflicts with the internal CIDR blocks of services like SWR, which can cause enhanced datasource connections to fail.
                    +
                  6. After adding a route, you can view the route information on the route details page.
                    7. + +

                    Step 3: Test the Connectivity Between the Queue in the Elastic Resource Pool and the Data Source Address

                    1. Log in to the DLI management console. In the navigation pane on the left, choose Resources > Queue Management.
                    2. On the Queue Management page, locate the row containing the target queue, click More in the Operation column, and select Test Address Connectivity.
                    3. On the Test Address Connectivity page, enter the address to be tested. The domain name and IP address are supported, and the port number can be specified.

                      You can input the data source address in the following formats: IPv4 address; IPv4 address + Port number; Domain name; Domain name + Port number.

                      +
                      • IPv4 address: 192.168.x.x
                      • IPv4 + Port number: 192.168.x.x:8080
                      • Domain name: domain-xxxxxx.com
                      • Domain name + Port number: domain-xxxxxx.com:8080
                      +

                      +
                    4. Click Test.
                      • If the test address is reachable, you will receive a message.
                      • If the test address is unreachable, you will also receive a message. Check the network configurations and retry. Network configurations include the VPC peering and the datasource connection. Check whether they have been activated.
                    -

                  7. Test the Connectivity Between the DLI Queue and the Data Source

                    1. Obtain the private IP address and port number of the data source.

                      Take the RDS data source as an example. On the Instances page, click the target DB instance. On the page displayed, locate the Connection Information pane and view the private IP address. In the Connection Information pane, locate the Database Port to view the port number of the RDS DB instance.

                      -
                    2. In the navigation pane of the DLI management console, choose Resources > Queue Management.
                    3. Locate the queue bound with the enhanced datasource connection, click More in the Operation column, and select Test Address Connectivity.
                    4. Enter the data source connection address and port number to test the network connectivity.

                      Format: IP address:Port number

                      -

                      Before testing the connection, ensure that the security group of the external data source has allowed access from the CIDR block of the queue.

                      -
                      -
                    -

                    8. @@ -176,3 +209,10 @@
                    + + \ No newline at end of file diff --git a/docs/dli/umn/dli_01_0007.html b/docs/dli/umn/dli_01_0007.html index bbf784e8b..ba67d1579 100644 --- a/docs/dli/umn/dli_01_0007.html +++ b/docs/dli/umn/dli_01_0007.html @@ -2,8 +2,8 @@

                    Previewing Table Data on the DLI Console

                    The Preview page displays the first 10 records in the table.

                    -

                    Procedure

                    You can preview data on either the Data Management page or the SQL Editor page.
                    • To preview data on the Data Management page:
                      1. On the left of the management console, choose Data Management > Databases and Tables.
                      2. On the displayed Data Management page, click the name of the database where the target table whose data you want to export resides to switch to the Manage Tables page.
                      3. Click More in the Operation column of the target table and select View Properties.
                      4. Click the Preview tab to preview the table data.
                      -
                    • To preview data on the SQL Editor page:
                      1. On the left of the management console, click SQL Editor.
                      2. In the navigation pane of the displayed SQL Editor page, click Databases.
                      3. Click the corresponding database name to view the tables in the database.
                      4. Click on the right of the corresponding table, choose View Properties from the list menu, and click the Preview tab to preview the data of the table.
                      +

                      Procedure

                      You can preview data on either the Data Management page or the SQL Editor page.
                      • To preview data on the Data Management page:
                        1. In the navigation pane on the left of the console, choose Data Management > Databases and Tables.
                        2. On the displayed Data Management page, click the name of the database where the target table whose data you want to export resides to switch to the Manage Tables page.
                        3. Click More in the Operation column of the target table and select View Properties.
                        4. Click the Preview tab to preview the table data.
                        +
                      • To preview data on the SQL Editor page:
                        1. In the navigation pane on the left of the management console, choose SQL Editor.
                        2. In the navigation pane of the displayed SQL Editor page, click Databases.
                        3. Click the corresponding database name to view the tables in the database.
                        4. Click on the right of the corresponding table, choose View Properties from the list menu, and click the Preview tab to preview the data of the table.
                      diff --git a/docs/dli/umn/dli_01_0008.html b/docs/dli/umn/dli_01_0008.html index 127a8e145..f1a2ba834 100644 --- a/docs/dli/umn/dli_01_0008.html +++ b/docs/dli/umn/dli_01_0008.html @@ -1,17 +1,17 @@

                      Viewing Table Metadata

                      -

                      Metadata Description

                      • Metadata is used to define data types. It describes information about the data, including the source, size, format, and other data features. In database fields, metadata interprets data content in the data warehouse.
                      • When you create a table, metadata is defined, consisting of the column name, type, and description.
                      • The Metadata page displays information about the target table, including Column Name, Column Type, Data Type, and Description.
                      +

                      Metadata Description

                      • Metadata is data used to define the type of data. It primarily describes information about the data itself, including its source, size, format, or other characteristics. In database fields, metadata interprets data content in the data warehouse.
                      • When creating a table, metadata is defined by three columns: column name, type, and column description.
                      • The Metadata page displays information about the target table, including Column Name, Column Type, Data Type, and Description.
                      -

                      Procedure

                      You can view metadata on either the Data Management page or the SQL Editor page.
                      • To view metadata on the Data Management page:
                        1. On the left of the management console, choose Data Management > Databases and Tables.
                        2. On the displayed Data Management page, click the name of the database where the target table whose data you want to export resides to switch to the Manage Tables page.
                        3. Click More in the Operation column of the target table and select View Properties. In the Metadata tab, view the metadata of the table.
                        -
                      • To view metadata on the SQL Editor page:
                        1. On the left of the management console, click SQL Editor.
                        2. In the navigation pane of the displayed SQL Editor page, click Databases.
                        3. Click the corresponding database name to view the tables in the database.
                        4. Click on the right of the table and choose View Properties from the shortcut menu. On the Metadata tab page, view the metadata of the table.
                        +

                        Procedure

                        You can view metadata on either the Data Management page or the SQL Editor page.
                        • To view metadata on the Data Management page:
                          1. In the navigation pane on the left of the console, choose Data Management > Databases and Tables.
                          2. On the displayed Data Management page, click the name of the database where the target table whose data you want to export resides to switch to the Manage Tables page.
                          3. Click More in the Operation column of the target table and select View Properties. In the Metadata tab, view the metadata of the table.
                          +
                        • To view metadata on the SQL Editor page:
                          1. In the navigation pane on the left of the management console, choose SQL Editor.
                          2. In the navigation pane of the displayed SQL Editor page, click Databases.
                          3. Click the corresponding database name to view the tables in the database.
                          4. Click on the right of the table and choose View Properties from the shortcut menu. On the Metadata tab page, view the metadata of the table.
                      diff --git a/docs/dli/umn/dli_01_0009.html b/docs/dli/umn/dli_01_0009.html new file mode 100644 index 000000000..d8efc9cd1 --- /dev/null +++ b/docs/dli/umn/dli_01_0009.html @@ -0,0 +1,24 @@ + + +

                      Binding an Enhanced Datasource Connection to an Elastic Resource Pool

                      +

                      Scenario

                      To connect other resource pools to data sources through enhanced datasource connections, bind enhanced datasource connections to resource pools on the Enhanced tab page.

                      +
                      +

                      Notes and Constraints

                      • The CIDR block of the DLI queue to be bound with a datasource connection cannot overlap with that of the data source.
                      • The default queue preset in the system cannot be bound with a datasource connection.
                      +
                      +

                      Procedure

                      1. Log in to the DLI management console.
                      2. In the navigation pane on the left, choose Datasource Connections.
                      3. On the Enhanced tab page displayed, bind an enhanced datasource connection to an elastic resource pool:
                        1. Locate your desired enhanced datasource connection, click More in the Operation column, and select Bind Resource Pool.
                        2. In the Bind Resource Pool dialog box, select the resource pool to be bound for Resource Pool.
                        3. Click OK.
                        +
                      4. View the connection status on the Enhanced tab page.
                        • After an enhanced datasource connection is created, the status is Active, but it does not indicate that the queue is connected to the data source. Go to the queue management page to check whether the data source is connected. The procedure is as follows:
                          1. In the navigation pane on the left, choose Resources > Queue Management. On the page displayed, locate a desired queue.
                          2. Click More in the Operation column and select Test Address Connectivity.
                          3. Enter the IP address and port number of the data source.
                          +
                        +
                        • On the details page of an enhanced datasource connection, you can view information about the VPC peering connection.
                          • VPC peering ID: ID of the VPC peering connection created in the cluster to which the queue belongs.

                            A VPC peering connection is created for each queue bound to an enhanced datasource connection. The VPC peering connection is used for cross-VPC communication. Ensure that the security group used by the data source allows access from the CIDR block of the DLI queue, and do not delete the VPC peering connection during the datasource connection.

                            +
                          • Status of the VPC peering connection:

                            The status of a datasource connection can be Creating, Active, or Failed.

                            +

                            If the connection status is Failed, click on the left to view the detailed error information.

                            +
                          +
                        +
                      +
                      +
                      + + diff --git a/docs/dli/umn/dli_01_0010.html b/docs/dli/umn/dli_01_0010.html index b64a19cf7..7c4c9e409 100644 --- a/docs/dli/umn/dli_01_0010.html +++ b/docs/dli/umn/dli_01_0010.html @@ -2,13 +2,13 @@

                      Exporting DLI Table Data to OBS

                      You can export data from a DLI table to OBS. During the export, a folder is created in OBS or the content in the existing folder is overwritten.

                      -

                      Precautions

                      • The exported file can be in JSON format, and the text format can only be UTF-8.
                      • Only the data in the DLI table (the table type is Managed) can be exported to the OBS bucket, and the export path must be specified to the folder level.
                      • Data can be exported across accounts. That is, after account B authorizes account A, account A can export data to the OBS path of account B if account A has the permission to read the metadata and permission information about the OBS bucket of account B and read and write the path.
                      +

                      Precautions

                      • The exported file can be in JSON format, and the text format can only be UTF-8.
                      • Data in DLI tables (table type: MANAGED) can only be exported to OBS buckets, and the export path must be a folder.
                      • Data can be exported across accounts. That is, after account B authorizes account A, account A can export data to the OBS path of account B if account A has the permission to read the metadata and permission information about the OBS bucket of account B and read and write the path.
                      -

                      Procedure

                      1. You can export data on either the Data Management page or the SQL Editor page.

                        • To export data on the Data Management page:
                          1. On the left of the management console, choose Data Management > Databases and Tables.
                          2. Click the name of the database corresponding to the table where data is to be exported to switch to the Manage Tables page.
                          3. Select the corresponding table (DLI table) and choose More > Export in the Operation column. The Export Data page is displayed.
                          -
                        • To export data on the SQL Editor page:
                          1. On the left of the management console, click SQL Editor.
                          2. In the navigation tree on the left, click Databases to see all databases. Click the database name corresponding to the table to which data is to be exported. The tables are displayed.
                          3. Click on the right of the managed table (DLI table) whose data is to be exported, and choose Export from the shortcut menu.
                          +

                          Procedure

                          1. You can export data on either the Data Management page or the SQL Editor page.

                            • To export data on the Data Management page:
                              1. In the navigation pane on the left of the console, choose Data Management > Databases and Tables.
                              2. Click the name of the database corresponding to the table where data is to be exported to switch to the Manage Tables page.
                              3. Select the corresponding table (DLI table) and choose More > Export in the Operation column. The Export Data page is displayed.
                              +
                            • To export data on the SQL Editor page:
                              1. In the navigation pane on the left of the management console, choose SQL Editor.
                              2. In the navigation tree on the left, click Databases to see all databases. Click the database name corresponding to the table to which data is to be exported. The tables are displayed.
                              3. Click on the right of the managed table (DLI table) whose data is to be exported, and choose Export from the shortcut menu.

                          2. In the displayed Export Data dialog box, specify parameters by referring to Table 1.

                            -
                            Table 1 Parameter description

                            Parameter

                            +
                            diff --git a/docs/dli/umn/dli_01_0011.html b/docs/dli/umn/dli_01_0011.html index 9edb98166..75e9be254 100644 --- a/docs/dli/umn/dli_01_0011.html +++ b/docs/dli/umn/dli_01_0011.html @@ -1,12 +1,13 @@

                            Deleting a Database on the DLI Console

                            -

                            You can delete databases as needed.

                            -

                            Precautions

                            • You are not allowed to delete databases or tables that are being used for running jobs.
                            • The administrator, database owner, and users with the database deletion permission can delete the database.

                              If a database or table is deleted, it cannot be recovered. Exercise caution when performing this operation.

                              +

                              You can delete an unused database from the DLI console: when a database is no longer needed, such as after a test database has completed testing; if a database has errors or anomalies that cannot be fixed; when there is a need to reorganize the data structure, such as by modifying table designs; or if a database is idle and has no practical use.

                              +

                              This section describes how to delete a database on the DLI management console.

                              +

                              Precautions

                              • Databases or tables that are being used for running jobs cannot be deleted.
                              • The administrator, database owner, and users with the database deletion permission can delete the database.

                                If a database or table is deleted, it cannot be recovered. Exercise caution when performing this operation.

                              -

                              Deleting a Database

                              1. On the left of the management console, choose Data Management > Databases and Tables.
                              2. Locate the row where the target database locates and click More > Drop Database in the Operation column.

                                You cannot delete databases that contain tables. To delete a database containing tables, delete the tables first.

                                +

                                Deleting a Database

                                1. In the navigation pane on the left of the console, choose Data Management > Databases and Tables.
                                2. Locate the row where the target database locates and click More > Drop Database in the Operation column.

                                  You cannot delete databases that contain tables. To delete a database containing tables, delete the tables first.

                                3. In the displayed dialog box, click Yes.
                                diff --git a/docs/dli/umn/dli_01_0013.html b/docs/dli/umn/dli_01_0013.html index dad68476b..c8cbe17b5 100644 --- a/docs/dli/umn/dli_01_0013.html +++ b/docs/dli/umn/dli_01_0013.html @@ -4,9 +4,9 @@

                                Scenario

                                Host information is the mapping between host IP addresses and domain names. After you configure host information, jobs can only use the configured domain names to access corresponding hosts. After a datasource connection is created, you can modify the host information.

                                When accessing the HBase cluster of MRS, you need to configure the host name (domain name) and IP address of the instance.

                                -

                                Constraints

                                You have obtained the MRS host information by referring to How Do I Obtain MRS Host Information?

                                +

                                Notes and Constraints

                                You have obtained the MRS host information by referring to How Do I Obtain MRS Host Information?

                                -

                                Modifying Host Information

                                1. Log in to the DLI management console.
                                2. In the left navigation pane, choose Datasource Connections.
                                3. On the Enhanced tab page displayed, locate the enhanced datasource connection to be modified, click More in the Operation column, and select Modify Host.
                                4. In the Modify Host dialog box displayed, enter the obtained host information.

                                  Enter host information in the format of Host IP address Host name. Information about multiple hosts is separated by line breaks.

                                  +

                                  Modifying Host Information

                                  1. Log in to the DLI management console.
                                  2. In the navigation pane on the left, choose Datasource Connections.
                                  3. On the Enhanced tab page displayed, locate the enhanced datasource connection to be modified, click More in the Operation column, and select Modify Host.
                                  4. In the Modify Host dialog box displayed, enter the obtained host information.

                                    Enter host information in the format of Host IP address Host name. Information about multiple hosts is separated by line breaks.

                                    Example:

                                    192.168.0.22 node-masterxxx1.com

                                    192.168.0.23 node-masterxxx2.com

                                    @@ -18,7 +18,7 @@

                                    If the MRS cluster has multiple IP addresses, enter any service IP address when creating a datasource connection.

                                  5. Method 2: Obtain MRS host information from the /etc/hosts file on an MRS node.
                                    1. Log in to any MRS node as user root.
                                    2. Run the following command to obtain MRS hosts information. Copy and save the information.

                                      cat /etc/hosts

                                      -
                                      Figure 1 Obtaining hosts information
                                      +
                                      Figure 1 Obtaining hosts information
                                    3. Modify host information by referring to Modifying Host Information.
                            @@ -29,3 +29,10 @@
                            + + \ No newline at end of file diff --git a/docs/dli/umn/dli_01_0014.html b/docs/dli/umn/dli_01_0014.html index c3b0062ed..6afc8a5ed 100644 --- a/docs/dli/umn/dli_01_0014.html +++ b/docs/dli/umn/dli_01_0014.html @@ -1,13 +1,14 @@

                            Adding a Route for an Enhanced Datasource Connection

                            -

                            Scenario

                            A route is configured with the destination, next hop type, and next hop to determine where the network traffic is directed. Routes are classified into system routes and custom routes.

                            -

                            After an enhanced connection is created, the subnet is automatically associated with the default route. You can add custom routes as needed to forward traffic destined for the destination to the specified next hop.

                            -
                            • When an enhanced connection is created, the associated route table is the one associated with the subnet of the data source.
                            • The route to be added in the Add Route dialog box must be one in the route table associated with the subnet of the resource pool.
                            • The subnet of the data source must be different from that used by the resource pool. Otherwise, a network segment conflict occurs.
                            +

                            Scenario

                            Enhanced datasource connections establish peering connections between DLI elastic resource pools and data sources to interconnect two VPC networks. If we liken these peering connections to exclusive bridges linking elastic resource pools and data sources, then routing serves as directional signage guiding the flow of network traffic.

                            +

                            Routing rules determine the direction of network traffic by configuring information such as the destination address, next hop type, and next hop address. Routes are classified into system routes and custom routes.

                            +

                            After an enhanced datasource connection is created, the subnet is automatically associated with the system default route. Besides the system default route, you can add custom routing rules as needed to forward traffic destined for the target address to the specified next-hop address.

                            +
                            • When an enhanced connection is created, the associated route table is the one associated with the subnet of the data source.
                            • The route to be added in the Add Route dialog box must be one in the route table associated with the subnet of the resource pool.
                            • The data source subnet and the elastic resource pool subnet must be different subnets to avoid network segment conflicts.
                            -

                            Procedure

                            1. Log in to the DLI management console.
                            2. In the left navigation pane, choose Datasource Connections.
                            3. On the Enhanced tab page displayed, locate the row containing the enhanced connection to which a route needs to be added, and add the route.
                              • Method 1:
                                1. On the Enhanced tab page displayed, locate the enhanced datasource connection to which a route needs to be added and click Manage Route in the Operation column.
                                2. Click Add Route.
                                3. In the Add Route dialog box, enter the route information. For details about the parameters, see Table 1.
                                4. Click OK.
                                -
                              • Method 2:
                                1. On the Enhanced tab page displayed, locate the enhanced datasource connection to which a route needs to be added, click More in the Operation column, and select Add Route.
                                2. In the Add Route dialog box, enter the route information. For details about the parameters, see Table 1.
                                3. Click OK.
                                +

                                Procedure

                                1. Log in to the DLI management console.
                                2. In the navigation pane on the left, choose Datasource Connections.
                                3. On the displayed Enhanced tab, locate the enhanced datasource connection where you want to add a route and then add a route.
                                  • Method 1:
                                    1. On the Enhanced tab, locate the enhanced datasource connection where you want to add a route and click Manage Route in its Operation column.
                                    2. On the displayed page, click Add Route.
                                    3. In the Add Route dialog box, set the parameters based on Table 1.
                                    4. Click OK.
                                    +
                                  • Method 2:
                                    1. On the Enhanced tab, locate the enhanced datasource connection where you want to add a route, click More in its Operation column, and select Add Route.
                                    2. In the Add Route dialog box, set the parameters based on Table 1.
                                    3. Click OK.
                            Table 1 Parameter descriptions

                            Parameter

                            Description
                            - - diff --git a/docs/dli/umn/dli_01_0015.html b/docs/dli/umn/dli_01_0015.html index 9c512a3e9..380ba1b32 100644 --- a/docs/dli/umn/dli_01_0015.html +++ b/docs/dli/umn/dli_01_0015.html @@ -7,10 +7,10 @@

                            -

                            Operations

                            1. On the top menu bar of the DLI management console, click Resources > Queue Management.
                            2. Select the queue to be configured and choose Manage Permissions in the Operation column. The User Permission Info area displays the list of users who have permissions on the queue.

                              You can grant queue permissions to new users, modify permissions for users who have some permissions on a queue, and revoke all permissions for a user on a queue.

                              -
                              • Grant permissions to a new user.
                                A new user does not have permissions on the queue.
                                1. Click Set Permission on the right of User Permissions page. The Set Permission dialog box is displayed.
                                2. Specify Username and select corresponding permissions.
                                3. Click OK.

                                  Table 1 describes the related parameters.

                                  +

                                  Operations

                                  1. In the navigation pane on the left of the DLI management console, choose Resources > Queue Management.
                                  2. Select the queue to be configured and choose Manage Permissions in the Operation column. The User Permission Info area displays the list of users who have permissions on the queue.

                                    You can grant queue permissions to new users, modify permissions for users who have some permissions on a queue, and revoke all permissions for a user on a queue.

                                    +
                                    • Grant permissions to a new user.
                                      A new user does not have permissions on the queue.
                                      1. Click Grant Permission on the right of User Permissions page. The Grant Permission dialog box is displayed.
                                      2. Specify Username and select corresponding permissions.
                                      3. Click OK.

                                        Table 1 describes the related parameters.

                                        -
                            Table 1 Parameters for adding a custom route

                            Parameter

                            @@ -18,13 +19,13 @@

                            Route Name

                            Name of a custom route, which is unique in the same enhanced datasource scenario. The name can contain 1 to 64 characters. Only digits, letters, underscores (_), and hyphens (-) are allowed.

                            +

                            Name of a custom route, which is unique in the same enhanced datasource connection. The name can contain up to 64 characters. Only digits, letters, underscores (_), and hyphens (-) are allowed.

                            IP Address

                            Custom route CIDR block. The CIDR block of different routes can overlap but cannot be the same.

                            -

                            Do not add the CIDR blocks 100.125.xx.xx and 100.64.xx.xx to prevent conflicts with the internal CIDR blocks of services such as SWR. This can lead to failure of the enhanced datasource connection.

                            +

                            Custom route CIDR block. The CIDR blocks of different routes can overlap but cannot be identical.

                            +

                            Do not add the 100.125.xx.xx or 100.64.xx.xx CIDR blocks to avoid conflicts with the internal CIDR blocks of services like SWR, which can cause enhanced datasource connections to fail.
                            Table 1 Parameter description

                            Parameter

                            +
                            @@ -18,8 +18,8 @@ - @@ -33,9 +33,9 @@ -
                          3. To grant or revoke permissions for a user who already has certain permissions on a queue, perform the following steps:
                            1. In the list under User Permission Info for a queue, select the user whose permissions need to be modified and click Set Permission in the Operation column.
                            2. In the displayed Set Permission dialog box, modify the permissions of the current user. Table 1 lists the detailed permission descriptions.

                              If all options under Set Permission are gray, you are not allowed to change permissions on this queue. You can apply to the administrator, queue owner, or other authorized users for queue permission granting and revoking.

                              +
                            3. To grant or revoke permissions for a user who already has certain permissions on a queue, perform the following steps:
                              1. In the list under User Permissions for a queue, select the user whose permissions need to be modified and click Set Permission in the Operation column.
                              2. In the displayed Set Permission dialog box, modify the permissions of the current user. Table 1 lists the detailed permission descriptions.

                                If all options under Set Permission are gray, you are not allowed to change permissions on this queue. You can apply to the administrator, queue owner, or other authorized users for queue permission granting and revoking.

                              3. Click OK.
                              -
                            4. To revoke all permissions for a user on a queue, perform the following steps:

                              In the user list under Permission Info, select the user whose permission needs to be revoked and click Revoke Permission under Operation. In the Revoke Permission dialog box, click OK. All permissions on this queue are revoked.

                              +
                            5. To revoke all permissions from a user, perform the following steps:

                              In the user list under Permission Info, select the user whose permission needs to be revoked and click Revoke Permission under Operation. In the Revoke Permission dialog box, click OK. All permissions on this queue are revoked.

                            diff --git a/docs/dli/umn/dli_01_0017.html b/docs/dli/umn/dli_01_0017.html index f609b07a3..4384ae05f 100644 --- a/docs/dli/umn/dli_01_0017.html +++ b/docs/dli/umn/dli_01_0017.html @@ -50,7 +50,7 @@
                            4. @@ -30,7 +29,7 @@ diff --git a/docs/dli/umn/dli_01_0020.html b/docs/dli/umn/dli_01_0020.html index 03c857a7f..96cab4a97 100644 --- a/docs/dli/umn/dli_01_0020.html +++ b/docs/dli/umn/dli_01_0020.html @@ -1,12 +1,12 @@ -

                            Using DLI to Submit a SQL Job to Query RDS for MySQL Data

                            +

                            Submitting a SQL Job to Query RDS for MySQL Data Using DLI

                            Scenario

                            DLI can query data stored in RDS. This section describes how to use DLI to submit a SQL job to query RDS for MySQL data.

                            In this example, we will create an RDS for MySQL DB instance, create a database and table, create a DLI elastic resource pool and add a queue to it, create an enhanced datasource connection to connect the DLI elastic resource pool and the RDS for MySQL DB instance, and submit a SQL job to access the data in the RDS table.

                            Procedure

                            Table 1 shows the process for submitting a SQL job to query RDS for MySQL data.

                            -
                            Table 1 Parameter descriptions

                            Parameter

                            Description

                            Username

                            Name of the authorized user.

                            -
                            NOTE:

                            The username is an existing IAM user name and has logged in to the DLI management console.

                            +

                            Name of the user you want to grant permissions to

                            +
                            NOTE:

                            The username must be an existing IAM username and has been used to log in to the DLI management console.

                            Operation
                            • Edit: Edit the job.
                            • Cancel
                              • You can terminate a job only when the job is in Submitting or Running status.
                              • A job whose status is Finished, Failed, or Canceled cannot be terminated.
                              • If the Cancel button is gray, you are not allowed to perform this operation.
                              -
                            • Re-execute: Execute the job again.
                            • SparkUI: Display the Spark job execution page.
                              NOTE:
                              • When you execute a job on a created queue, the cluster is restarted. It takes about 10 minutes. If you click SparkUI before the cluster is created, an empty projectID will be cached. The SparkUI page cannot be displayed. You are advised to use a dedicated queue so that the cluster will not be released. Alternatively, wait for a while after the job is submitted (the cluster is created), and then check SparkUI.
                              • SparkUI can currently only display the latest 100 jobs.
                              +
                            • Re-execute: Execute the job again.
                            • SparkUI: Display the Spark job execution page.
                              NOTE:
                              • When you execute a job on a created queue, the cluster is restarted. It takes about 10 minutes. If you click SparkUI before the cluster is created, an empty projectID will be cached. The SparkUI page cannot be displayed. You are advised to use a dedicated queue so that the cluster will not be released. Alternatively, wait for a while after the job is submitted (the cluster is created), and then check SparkUI.
                              • You can view only the latest 100 job records on DLI's SparkUI.
                            • In addition to the preceding operations, the following operations are available for QUERY jobs and asynchronous DDL jobs.
                              • View Result: View the job running result.
                              • Export Result: Export the job running result to the created OBS bucket.
                              @@ -78,7 +78,7 @@ diff --git a/docs/dli/umn/dli_01_0018.html b/docs/dli/umn/dli_01_0018.html index 853fd3bfa..4e8a8c99d 100644 --- a/docs/dli/umn/dli_01_0018.html +++ b/docs/dli/umn/dli_01_0018.html @@ -12,7 +12,7 @@

                            After creating a VPC peering connection and route between the enhanced datasource connection of project A and the queue of project B, you can create a job in the queue of project B to access the data source of project A.

                            -

                            Procedure

                            1. Log in to the DLI management console.
                            2. In the left navigation pane, choose Datasource Connections.
                            3. On the Enhanced tab page displayed, locate the desired enhanced connection, click More in the Operation column, and select Manage Permission.
                              • Granting permission
                                1. In the Permissions dialog box displayed, select Grant Permission for Set Permission.
                                2. Enter the project ID.
                                3. Click OK to grant the resource pool operation permission to the project.
                                +

                                Procedure

                                1. Log in to the DLI management console.
                                2. In the navigation pane on the left, choose Datasource Connections.
                                3. On the Enhanced tab page displayed, locate the desired enhanced connection, click More in the Operation column, and select Manage Permission.
                                  • Granting permission
                                    1. In the Permissions dialog box displayed, select Grant Permission for Set Permission.
                                    2. Enter the project ID.
                                    3. Click OK to grant the resource pool operation permission to the project.
                                  • Revoking permission
                                    1. In the Permissions dialog box displayed, select Revoke Permission for Set Permission.
                                    2. Select a project ID.
                                    3. Click OK to revoke the resource pool operation permission from the specified project.
                                diff --git a/docs/dli/umn/dli_01_0019.html b/docs/dli/umn/dli_01_0019.html index a0b962d90..b9fc34744 100644 --- a/docs/dli/umn/dli_01_0019.html +++ b/docs/dli/umn/dli_01_0019.html @@ -1,12 +1,11 @@

                                Enhanced Datasource Connection Tag Management

                                -

                                Scenario

                                A tag is a key-value pair customized by users and used to identify cloud resources. It helps users to classify and search for cloud resources. A tag consists of a tag key and a tag value.

                                +

                                Scenario

                                A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value.

                                If you use tags in other cloud services, you are advised to create the same tag key-value pairs for cloud resources used by the same business to keep consistency.

                                -

                                DLI supports the following two types of tags:

                                -
                                • Resource tags: non-global tags created on DLI.
                                -
                                • Predefined tags: global tags created on Tag Management Service (TMS).

                                  +
                                  DLI supports the following two types of tags:
                                  • Resource tags: indicate non-global tags created on DLI.
                                  • Predefined tags: global tags created on Tag Management Service (TMS).

                                    For details about predefined tags, see Tag Management Service User Guide.

                                  +

                                  DLI allows you to add, modify, or delete tags for datasource connections.

                                Procedure

                                1. In the left navigation pane of the DLI management console, choose Datasource Connections.
                                2. In the Operation column of the link, choose More > Tags.
                                3. The tag management page is displayed, showing the tag information about the current connection.
                                4. Click Add/Edit Tag. The Add/Edit Tag dialog is displayed. Add or edit tag keys and values and click OK. @@ -22,7 +21,7 @@
                                  • Click the text box and select a predefined tag key from the drop-down list.

                                    To add a predefined tag, you need to create one on TMS and then select it from the Tag key drop-down list. You can click View predefined tags to go to the Predefined Tags page of the TMS console. Then, click Create Tag in the upper corner of the page to create a predefined tag.

                                  -
                                  • Enter a tag key in the text box.
                                    NOTE:

                                    A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.

                                    +
                                    • Enter a tag key in the text box.
                                      NOTE:

                                      A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.

                            Tag value

                            You can perform the following operations:

                            -
                            • Click the text box and select a predefined tag value from the drop-down list.
                            • Enter a tag value in the text box.
                              NOTE:

                              A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.

                              +
                              • Click the text box and select a predefined tag value from the drop-down list.
                              • Enter a tag value in the text box.
                                NOTE:

                                A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.
                            Table 1 Procedure for using DLI to submit a SQL job to query RDS for MySQL data

                            Procedure

                            +
                            @@ -22,7 +22,7 @@ - @@ -61,6 +61,7 @@ @@ -68,6 +69,8 @@ @@ -89,6 +92,7 @@ @@ -131,6 +135,7 @@ @@ -138,7 +143,7 @@ @@ -147,7 +152,8 @@ - @@ -169,7 +175,7 @@ - @@ -177,6 +183,9 @@ @@ -223,9 +232,9 @@ DEFAULT CHARACTER SET = utf8mb4; -

                            Step 3: Create an Elastic Resource Pool and Add Queues to the Pool

                            To execute SQL jobs in datasource scenarios, you must use your own SQL queue as the existing default queue cannot be used. In this example, create an elastic resource pool named dli_resource_pool and a queue named dli_queue_01.

                            +

                            Step 3: Create an Elastic Resource Pool and Create Queues Within It

                            To execute SQL jobs in datasource scenarios, you must use your own SQL queue as the existing default queue cannot be used. In this example, create an elastic resource pool named dli_resource_pool and a queue named dli_queue_01.

                            1. Log in to the DLI management console.
                            2. In the navigation pane on the left, choose Resources > Resource Pool.
                            3. On the displayed page, click Buy Resource Pool in the upper right corner.
                            4. On the displayed page, set the parameters.
                              Table 3 describes the parameters. -
                            Table 1 Procedure for using DLI to submit a SQL job to query RDS for MySQL data

                            Step

                            Description

                            Log in to the RDS for MySQL DB instance and create a database and a table.

                            Step 3: Create an Elastic Resource Pool and Add Queues to the Pool

                            +

                            Step 3: Create an Elastic Resource Pool and Create Queues Within It

                            Create compute resources required for submitting jobs.

                            Region

                            Region where you want to create the instance

                            +

                            Products in different regions cannot communicate with each other through a private network. After a DB instance is created, the region cannot be changed. Exercise caution when selecting a region.

                            _

                            DB Instance Name

                            Instance name

                            +

                            The name can contain 4 to 64 characters and must start with a letter. Only letters (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.

                            +

                            If you intend to create multiple DB instances and read replicas at a time, the allowed length for each instance name will change.

                            rds-demo

                            DB Instance Type

                            Primary/standby mode of the instance

                            +
                            • Primary/Standby: An HA architecture. In a primary/standby pair, each instance has the same instance class. When a primary instance is being created, a standby instance is provisioned along with it to provide data redundancy. The standby instance is invisible to you after being created.
                            • Single: A single-node architecture is less expensive than a primary/standby DB pair. It is recommended for development and testing of microsites, and small- and medium-sized enterprises, or for learning about RDS.

                            Single

                            Disk Encryption

                            Determine whether to enable disk encryption.

                            +
                            • Deselected: Encryption is not enabled.
                            • Selected: Selecting it enhances data security but may slightly impact database read and write performance.

                            Disable

                            VPC

                            Select an existing VPC.

                            -

                            For how to recreate a VPC and subnet, refer to "Creating a VPC and Subnet" in the Virtual Private Cloud User Guide.

                            +

                            For how to recreate a VPC and subnet, refer to "Creating a VPC and Subnet" in the Virtual Private Cloud User Guide.

                            NOTE:

                            In datasource scenarios, the CIDR block of the data source cannot overlap that of the elastic resource pool.

                            Database Port

                            Port 3306 is used by default.

                            +

                            The default port is 3306. You can change it after the DB instance is created.

                            +

                            For RDS for MySQL instances, the value ranges from 1024 to 65535, excluding 12017, 33071, and 33062, which are reserved for RDS system use.

                            3306

                            Administrator

                            root

                            +

                            DB administrator. The default username is root.

                            root

                            Administrator Password

                            Administrator password

                            +

                            The password must consist of 8 to 32 characters and contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and the following special characters: ~!@#$%^*-_=+?,()&.| Enter a strong password and change it regularly to enhance security and prevent risks like brute-force attacks.

                            +

                            If the password you provide is considered weak by the system, you will be prompted to provide a stronger password.

                            +

                            Keep this password secure. The system cannot retrieve it.

                            -
                            Table 3 Parameters

                            Parameter

                            +
                            @@ -307,7 +316,8 @@ -
                            Table 3 Parameter descriptions

                            Parameter

                            Description

                            Type of the queue

                            • To execute SQL jobs, select For SQL.
                            • To execute Flink or Spark jobs, select For general purpose.

                            _

                            +

                            For SQL jobs, select For SQL.

                            +

                            For other scenarios, select For general purpose.

                            Enterprise Project

                            @@ -371,11 +381,11 @@

                          4. Create an enhanced datasource connection between RDS for MySQL and DLI.

                            The CIDR block of the elastic resource pool bound to a datasource connection cannot overlap that of the data source.

                            -
                            1. Go to the DLI management console and choose Datasource Connections in the navigation pane on the left.
                            2. On the displayed Enhanced tab, click Create. Set the following parameters:
                              • Connection Name: dlirds
                              • Resource Pool: Select the elastic resource pool created in Step 3: Create an Elastic Resource Pool and Add Queues to the Pool.
                              • VPC: Select the VPC where the RDS for MySQL DB instance is, that is, the VPC selected in Step 2: Create an RDS Database Table.
                              • Subnet: Select the subnet where the RDS for MySQL DB instance is, that is, the subnet selected in Step 2: Create an RDS Database Table.

                                To check the subnet information, go to the RDS console, choose Instances in the navigation pane on the left, click the name of the RDS for MySQL DB instance you created, and find Subnet in the Connection Information area on the displayed page.

                                +
                                1. Go to the DLI management console and choose Datasource Connections in the navigation pane on the left.
                                2. On the displayed Enhanced tab, click Create. Set the following parameters: -
                                3. Click OK.
                                4. In the Enhanced tab, click the created connection dlirds to view its VPC Peering ID and Connection Status. If the connection status is Active, the connection is successful.
                                5. Test if the queue can connect to the RDS for MySQL DB instance.
                                  1. In the navigation pane on the left, choose Resources > Queue Management. On the displayed page, locate the queue added in Step 3: Create an Elastic Resource Pool and Add Queues to the Pool, click More in the Operation column, and select Test Address Connectivity.
                                  2. Enter the floating IP address of the RDS for MySQL DB instance recorded in Step 2: Create an RDS Database Table.

                                    On the Instance Management page, click the target DB instance. On the displayed page, choose Connection Information > Floating IP Address to obtain the floating IP address.

                                    +
                                  3. Click OK.
                                  4. In the Enhanced tab, click the created connection dlirds to view its VPC Peering ID and Connection Status. If the connection status is Active, the connection is successful.
                                  5. Test if the queue can connect to the RDS for MySQL DB instance.
                                    1. In the navigation pane on the left, choose Resources > Queue Management. On the displayed page, locate the queue added in Step 3: Create an Elastic Resource Pool and Create Queues Within It, click More in the Operation column, and select Test Address Connectivity.
                                    2. Enter the floating IP address of the RDS for MySQL DB instance recorded in Step 2: Create an RDS Database Table.

                                      On the Instance Management page, click the target DB instance. On the displayed page, choose Connection Information > Floating IP Address to obtain the floating IP address.

                                      -
                                      • If the IP address is reachable, the DLI queue can connect to the RDS for MySQL DB instance through the created enhanced datasource connection.
                                      • If the IP address is unreachable, check if the security group where the data source is allows access from the IP address of the elastic resource pool. Once the fault is rectified, retest the network connectivity.
                                      +
                                      • If the IP address is reachable, the queue and the DB instance are successfully connected over the network.
                                      • If the IP address is unreachable, check if the security group where the data source is allows access from the IP address of the elastic resource pool. Once the fault is rectified, retest the network connectivity.

                                @@ -398,7 +408,7 @@

                            5. Authentication Certificate

                            Name of the datasource authentication to create

                            -
                            • Only numbers, letters, and underscores (_) are allowed. The name cannot contain only numbers or start with an underscore (_).
                            • The value can contain a maximum of 128 characters.
                            +
                            • Only digits, letters, and underscores (_) are allowed. The name cannot contain only digits or start with an underscore (_).
                            • The value can contain a maximum of 128 characters.

                            Username

                            @@ -422,13 +432,15 @@ 'url' = 'jdbc:mysql://{{ip}}:{{port}}', // Private IP address and port of RDS 'driver' = 'com.mysql.jdbc.Driver', 'dbtable' = 'dli_demo.tabletest', // Name of the created DB instance and table name + 'encryption' = 'true', 'passwdauth'="xxxxx" // Name of the datasource authentication of the password type created on DLI. If datasource authentication is used, you do not need to set the username and password for the job. ) insert into rds_test VALUES ('123','abc'); -SELECT * from rds_test; +SELECT * from rds_test; + diff --git a/docs/dli/umn/dli_01_0021.html b/docs/dli/umn/dli_01_0021.html index 7309d5c9e..f974135bb 100644 --- a/docs/dli/umn/dli_01_0021.html +++ b/docs/dli/umn/dli_01_0021.html @@ -1,7 +1,7 @@

                            Creating a SQL Job Template

                            -

                            To facilitate SQL operation execution, DLI allows you to customize query templates or save the SQL statements in use as templates. After templates are saved, you do not need to compile SQL statements. Instead, you can directly perform the SQL operations using the templates.

                            +

                            DLI allows you to create custom templates or save currently used SQL statements as templates for quick and convenient SQL operations. Once a template is saved, you can execute SQL operations directly through the template without the need to write SQL statements.

                            SQL templates include sample templates and custom templates. The default sample template contains 22 standard TPC-H query statements, which can meet most TPC-H test requirements. For details, see TPC-H Sample Data in the SQL Templates Preset on DLI.

                            In the navigation pane on the left, choose Job Templates > SQL Templates. In the upper right corner of the displayed page, click Settings. In the displayed Settings dialog box, choose whether to display templates by group.

                            If you enable Display by Group, the display options are Expand the first group, Expand all, and Collapse all.

                            @@ -9,9 +9,9 @@

                            Creating a SQL Job Template

                            You can create a template on either the Job Templates or the SQL Editor page.

                            • To create a template on the Job Templates page:
                              1. On the left of the management console, choose Job Templates > SQL Templates.
                              2. On the SQL Templates page, click Create Template to create a template.

                                Enter the template name, SQL statement, and description information. For details, see Table 1.

                                -
                                Table 1 Parameter description

                                Parameter

                                +
                                - diff --git a/docs/dli/umn/dli_01_0022.html b/docs/dli/umn/dli_01_0022.html index b3889e91c..b42823575 100644 --- a/docs/dli/umn/dli_01_0022.html +++ b/docs/dli/umn/dli_01_0022.html @@ -1,14 +1,14 @@

                                Managing Queue Tags

                                -

                                Tag Management

                                A tag is a key-value pair that you can customize to identify cloud resources. It helps you to classify and search for cloud resources. A tag consists of a tag key and a tag value.

                                +

                                Tag Management

                                A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value.

                                If you use tags in other cloud services, you are advised to create the same tag (key-value pairs) for cloud resources used by the same business to keep consistency.

                                DLI supports the following two types of tags:

                                • Resource tags: non-global tags created on DLI
                                -
                                • Predefined tags: global tags created on Tag Management Service (TMS).

                                  +
                                  • Predefined tags: global tags created on Tag Management Service (TMS).

                                    For details about predefined tags, see Tag Management Service User Guide.

                                  DLI allows you to add, modify, or delete tags for queues.

                                  -
                                  1. In the navigation pane of the DLI management console, choose Resources > Queue Management.
                                  2. In the Operation column of the queue, choose More > Tags.
                                  3. The tag management page is displayed, showing the tag information about the current queue.
                                  4. Click Add/Edit Tag to switch to the Add/Edit Tag dialog box. Enter a tag and a value, and click Add.

                                    +

                                    1. In the navigation pane on the left of the DLI management console, choose Resources > Queue Management.
                                    2. In the Operation column of the queue, choose More > Tags.
                                    3. The tag management page is displayed, showing the tag information about the current queue.
                                    4. On the page that appears, click Add/Edit Tag in the upper left corner. Enter a tag and a value, and click Add.

                                Table 1 Parameter descriptions

                                Parameter

                                Description

                                +

                                Description
                                diff --git a/docs/dli/umn/dli_01_0220.html b/docs/dli/umn/dli_01_0220.html index b092753a7..041a81df6 100644 --- a/docs/dli/umn/dli_01_0220.html +++ b/docs/dli/umn/dli_01_0220.html @@ -4,15 +4,15 @@
                                diff --git a/docs/dli/umn/dli_01_0228.html b/docs/dli/umn/dli_01_0228.html index dc6c0ddda..414312cbd 100644 --- a/docs/dli/umn/dli_01_0228.html +++ b/docs/dli/umn/dli_01_0228.html @@ -4,9 +4,6 @@
                                Databases and tables are the basis for developing SQL and Spark jobs. Before running a job, you need to define databases and tables based on your service scenarios.

                                Flink allows for dynamic data types, enabling the definition of data structures at runtime without the need for predefined metadata.

                                -

                                Data Catalog

                                A data catalog is a metadata management object that can contain multiple databases.

                                -

                                For how to create a database and a table in a DLI data catalog, see Creating a Database and Table on the DLI Console.

                                -

                                Database

                                A database is a repository of data organized, stored, and managed on computer storage devices according to data structures. Databases are typically used to store, retrieve, and manage structured data, consisting of multiple data tables that are interrelated through keys and indexes.

                                Table

                                Tables are one of the most important components of a database, consisting of rows and columns. Each row represents a data item, while each column represents a property or feature of the data. Tables are used to organize and store specific types of data, making it possible to query and analyze the data effectively.

                                @@ -27,7 +24,7 @@
                              3. View table

                                A view table is a virtual table that does not store actual data. Instead, it dynamically generates data based on the defined query logic. Views are typically used to simplify complex queries or provide customized data views for different users or applications.

                                A view table can be created based on one or multiple tables, providing a flexible way to display data without affecting the storage and organization of the underlying data.

                                In the navigation pane on the left of the DLI console, choose Data Management > Databases and Tables. On the displayed page, click the name of a database. In the displayed table list, tables whose Type is VIEW are view tables.

                                -

                                A view can only be created using SQL statements. You cannot create a view on the Create Table page. Table or view information in a view cannot be modified. Otherwise, the query may fail.

                                +

                                Views can be created only by using SQL statements, not through the Create Table page. Table or view information in a view cannot be modified. Otherwise, the query may fail.

                              4. Datasource table

                                A datasource table is a data table that can be queried and analyzed across multiple data sources. This type of tables can integrate data from varying data sources and provide a unified data view.

                                Datasource tables are typically used in data warehouse and data lake architectures, allowing users to perform complex queries across multiple data sources.

                                @@ -35,31 +32,31 @@

                                5. Notes and Constraints on Databases and Tables

                                -
                                Table 1 Tag parameters

                                Parameter

                                Description

                                @@ -21,7 +21,7 @@
                                • Click the text box and select a predefined tag key from the drop-down list.

                                  To add a predefined tag, you need to create one on TMS and then select it from the Tag key drop-down list. You can click View predefined tags to go to the Predefined Tags page of the TMS console. Then, click Create Tag in the upper corner of the page to create a predefined tag.

                                -
                                • Enter a tag key in the text box.
                                  NOTE:

                                  A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.

                                  +
                                  • Enter a tag key in the text box.
                                    NOTE:

                                    A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.

                                  @@ -29,7 +29,7 @@

                                Tag value

                                You can specify the tag value in either of the following ways:

                                -
                                • Click the text box and select a predefined tag value from the drop-down list.
                                • Enter a tag value in the text box.
                                  NOTE:

                                  A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.

                                  +
                                  • Click the text box and select a predefined tag value from the drop-down list.
                                  • Enter a tag value in the text box.
                                    NOTE:

                                    A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.
                                Table 1 Notes and constraints on DLI resources

                                Item

                                +
                                - - - - - - - - - @@ -72,7 +69,7 @@ diff --git a/docs/dli/umn/dli_01_0253.html b/docs/dli/umn/dli_01_0253.html index d87ef8470..3078505b7 100644 --- a/docs/dli/umn/dli_01_0253.html +++ b/docs/dli/umn/dli_01_0253.html @@ -1,17 +1,17 @@ -

                                Importing OBS Data to DLI

                                -

                                This section describes how to import data stored in OBS to a table on the DLI console.

                                +

                                Importing OBS Data to a DLI Table

                                +

                                This section describes how to import data stored in OBS to a table on the DLI console. Data can be imported to both DLI tables (table type: MANAGED) and OBS tables (table type: EXTERNAL).

                                Precautions

                                • Only one path can be specified during data import. The path cannot contain commas (,).
                                • To import data in CSV format to a partitioned table, place the column to be partitioned in the last column of the data source.
                                • You are advised not to concurrently import data in to a table. If you concurrently import data into a table, there is a possibility that conflicts occur, leading to failed data import.
                                • The imported file can be in CSV, Parquet, ORC, JSON, and Avro format. The encoding format must be UTF-8.

                                Prerequisites

                                The data to be imported has been stored on OBS.

                                -

                                Procedure

                                1. You can import data on either the Data Management page or the SQL Editor page.

                                  • To import data on the Data Management page:
                                    1. On the left of the management console, choose Data Management > Databases and Tables.
                                    2. Click the name of the database corresponding to the table where data is to be imported to switch to the table management page.
                                    3. Locate the row where the target table resides and choose More > Import in the Operation column. The Import dialog box is displayed.
                                    +

                                    Procedure

                                    1. You can import data on either the Data Management page or the SQL Editor page.

                                      • To import data on the Data Management page:
                                        1. In the navigation pane on the left of the console, choose Data Management > Databases and Tables.
                                        2. Click the name of the database corresponding to the table where data is to be imported to switch to the table management page.
                                        3. Locate the row where the target table resides and choose More > Import in the Operation column. The Import dialog box is displayed.
                                      • To import data on the SQL Editor page:
                                        1. On the left of the management console, click SQL Editor.
                                        2. In the navigation tree on the left of SQL Editor, click Databases to see all databases. Click the database where the target table belongs. The table list is displayed.
                                        3. Click on the right of the table and choose Import from the shortcut menu. The Import page is displayed.

                                    2. In the Import dialog box, set the parameters based on Table 1.

                                      -

                                Table 1 Notes and constraints on DLI resources

                                Item

                                Description

                                +

                                Description

                                Database

                                +

                                Database

                                • default is the database built in DLI. You cannot create a database named default.
                                • DLI supports a maximum of 50 databases.
                                +
                                • default is the database built in DLI. You cannot create a database named default.
                                • DLI supports a maximum of 50 databases.

                                Data table

                                +

                                Data table

                                • DLI supports a maximum of 5,000 tables.
                                • DLI supports the following table types:
                                  • MANAGED: Data is stored in a DLI table.
                                  • EXTERNAL: Data is stored in an OBS table.
                                  • View: A view can only be created using SQL statements.
                                  • Datasource table: The table type is also EXTERNAL.
                                  +
                                • DLI supports a maximum of 5,000 tables.
                                • DLI supports the following table types:
                                  • MANAGED: Data is stored in a DLI table.
                                  • EXTERNAL: Data is stored in an OBS table.
                                  • View: A view can only be created using SQL statements.
                                  • Datasource table: The table type is also EXTERNAL.
                                • You cannot specify a storage path when creating a DLI table.

                                Data import

                                +

                                Data import

                                • Only OBS data can be imported to DLI or OBS.
                                • You can import data in CSV, Parquet, ORC, JSON, or Avro format from OBS to tables created on DLI.
                                • To import data in CSV format to a partitioned table, place the partition column in the last column of the data source.
                                • The encoding format of imported data can only be UTF-8.
                                +
                                • Only OBS data can be imported to DLI or OBS.
                                • You can import data in CSV, Parquet, ORC, JSON, or Avro format from OBS to tables created on DLI.
                                • To import data in CSV format to a partitioned table, place the partition column in the last column of the data source.
                                • The encoding format of imported data can only be UTF-8.

                                Data export

                                +

                                Data export

                                • Data in DLI tables (whose table type is MANAGED) can only be exported to OBS buckets, and the export path must contain a folder.
                                • The exported file is in JSON format, and the text format can only be UTF-8.
                                • Data can be exported across accounts. That is, after account B authorizes account A, account A has the permission to read the metadata and permission information of account B's OBS bucket as well as the read and write permissions on the path. Account A can export data to the OBS path of account B.
                                +
                                • Data in DLI tables (whose table type is MANAGED) can only be exported to OBS buckets, and the export path must contain a folder.
                                • The exported file is in JSON format, and the text format can only be UTF-8.
                                • Data can be exported across accounts. That is, after account B authorizes account A, account A has the permission to read the metadata and permission information of account B's OBS bucket as well as the read and write permissions on the path. Account A can export data to the OBS path of account B.
                                Table 1 Description

                                Parameter

                                +
                                @@ -35,7 +35,7 @@ - @@ -50,9 +50,8 @@ diff --git a/docs/dli/umn/dli_01_0318.html b/docs/dli/umn/dli_01_0318.html index 43c46d4e3..e0559b6cd 100644 --- a/docs/dli/umn/dli_01_0318.html +++ b/docs/dli/umn/dli_01_0318.html @@ -39,7 +39,7 @@ - @@ -396,8 +396,51 @@ + + + + + + + + + + + + + + + + + + + + + + + +
                                Table 1 Parameter descriptions

                                Parameter

                                Description

                                Queues

                                Queue where the imported data will be used

                                +

                                Select a queue.

                                -

                                Path

                                You can directly enter a path or click and select an OBS path. If no bucket is available, you can directly switch to the OBS management console and create an OBS bucket.

                                -
                                • When creating an OBS table, you must specify a folder as the directory. If a file is specified, data import may be failed.
                                • If a folder and a file have the same name in the OBS directory, the file path is preferred as the path of the data to be imported.
                                -
                                NOTE:

                                The path can be a file or folder.

                                -
                                +

                                The path can be a file or folder.

                                +
                                • When creating an OBS table, you must specify a folder as the directory. If a file is specified, data import will fail.
                                • When there are both a folder and a file with the same name in the OBS directory, importing data pointing to that path will prioritize the file over the folder.

                                obs://DLI/sampledata.csv

                                createTable

                                Deleting tables

                                +

                                Dropping a table

                                table

                                updateGlobalVariable

                                Querying resources by enterprise project

                                +

                                tms

                                +

                                tmsQueryResources

                                +

                                Creating an elastic resource pool

                                +

                                elasticresourcepool

                                +

                                createElasticResourcePool

                                +

                                Deleting an elastic resource pool

                                +

                                elasticresourcepool

                                +

                                deleteElasticResourcePool

                                +

                                Updating an elastic resource pool

                                +

                                elasticresourcepool

                                +

                                updateElasticResourcePool

                                +

                                Binding a queue to an elastic resource pool

                                +

                                elasticresourcepool

                                +

                                associateQueueToElasticResourcePool

                                +

                                Updating the queue properties of an elastic resource pool

                                +

                                elasticresourcepool

                                +

                                updateElasticResourcePoolQueuePriority

                                +
                                +
                                diff --git a/docs/dli/umn/dli_01_0320.html b/docs/dli/umn/dli_01_0320.html index 003ce509b..b3bf585b8 100644 --- a/docs/dli/umn/dli_01_0320.html +++ b/docs/dli/umn/dli_01_0320.html @@ -1,19 +1,18 @@

                                Creating and Submitting a SQL Job

                                -

                                Introduction

                                The SQL Editor allows you to execute data query operations using SQL statements.

                                -

                                It supports SQL:2003 and is compatible with Spark SQL.

                                -

                                To access the SQL editor, choose SQL Editor in the left navigation pane of the DLI console, or click Create Job in the upper right corner of the Job Management > SQL Jobs page.

                                +

                                Introduction

                                DLI offers a SQL editor for executing data query operations using SQL statements.

                                +

                                +

                                This section describes how to create and submit a SQL job using the DLI SQL editor.

                                -

                                Notes

                                • If you access the SQL editor for the first time, the system prompts you to set a bucket for DLI jobs. The created bucket is used to store temporary data generated by DLI, such as job logs.

                                  You cannot view job logs if you choose not to create the bucket. The bucket name will be set by the system.

                                  -

                                  On the OBS console, you can configure lifecycle rules for a bucket to periodically delete objects in it or change object storage classes.

                                  +

                                  Notes

                                  • Before submitting a SQL job, configure a DLI job bucket. The bucket is used to store job results and temporary data generated by DLI, such as job logs.
                                    • For details about how to configure a job bucket, see Configuring a DLI Job Bucket. The job bucket name is set by default.
                                    • If your SQL queue has been configured to save job results to a DLI job bucket, the system will write the results directly to the specified OBS bucket when executing a SQL job. Ensure the following preparations are completed before submitting the job:
                                      • Configure DLI job bucket information before submitting a SQL job. Otherwise, the SQL job may fail to be submitted.
                                      • Ensure that the user executing the SQL job has read and write permissions for the DLI job bucket. Otherwise, the job results cannot be properly saved or retrieved.

                                        When executing a job, the system accesses the job bucket using the identity credentials of the user who submitted the job. If permissions are insufficient, it results in failure to save or retrieve the job results.

                                        +
                                      +

                                      For details, refer to How Do I Check if Job Result Saving to a DLI Job Bucket Is Enabled for a SQL Queue?

                                      +
                                    • On the OBS management console, you can configure lifecycle rules for a bucket to automatically delete objects within it or change object storage classes on a regular basis.
                                  -
                                  • SQL statements can be executed in batches on the SQL editor page.
                                  -
                                  • Commonly used syntax in the job editing window is highlighted in different colors.
                                  • Both single-line comment and multi-line comment are allowed. Use two consecutive hyphens (--) in each line to comment your statements.
                                  -

                                  Creating and Submitting a SQL Job Using the SQL Editor

                                  1. Log in to the DLI management console. In the navigation pane on the left, choose SQL Editor.

                                    On the SQL editor page, the system prompts you to create an OBS bucket to store temporary data generated by DLI jobs. In the Set Job Bucket dialog box, click Setting. On the page displayed, click the edit button in the upper right corner of the job bucket card. In the displayed Set Job Bucket dialog box, enter the job bucket path and click OK.

                                    -
                                    +

                                    Creating and Submitting a SQL Job Using the SQL Editor

                                    1. Log in to the DLI management console. In the navigation pane on the left, choose SQL Editor.

                                      On the SQL Editor page, the system prompts you to create a temporary DLI data bucket to store temporary data generated by DLI. For details about how to configure a job bucket, see Configuring a DLI Job Bucket.

                                    2. Above the SQL job editing window, set the parameters required for running a SQL job, such as the queue and database. For how to set the parameters, refer to Table 1.
                                      @@ -23,15 +22,20 @@ - -
                                      Table 1 Setting SQL job parameters

                                      Button & Drop-Down List

                                      Queues

                                      Select a queue from the drop-down list box. If there is no queue available, the default queue is displayed. However, this queue is shared among all users for experience only. This may lead to resource contention, preventing you from obtaining the required resources for your jobs. So, you are advised to create your own queue for executing your jobs. For how to create a queue, see Creating an Elastic Resource Pool and Creating Queues Within It.

                                      -

                                      SQL jobs can only be executed on SQL queues.

                                      +

                                      Resource queue used to execute SQL jobs.

                                      +

                                      A queue determines the compute resources accessible to a job during its operation within an elastic resource pool. Every queue is allocated with specific resources, known as CUs, whose configuration significantly impacts the job's performance and execution efficiency.

                                      +

                                      Before submitting a job, assess its resource needs and select an appropriate queue.

                                      +

                                      SQL jobs can only be executed on SQL queues.

                                      +

                                      If no queue is available, you can create a queue or use the default queue.

                                      +

                                      Databases

                                      Select a database from the drop-down list box. If no database is available, the default database is displayed. For how to create a database, see Creating a Database and Table on the DLI Console.

                                      -
                                      NOTE:

                                      If you have specified a database where tables are located in SQL statements, the database you choose here does not apply.

                                      -
                                      +

                                      Select a database from the drop-down list box.

                                      +

                                      If no database is available, the default database is displayed.

                                      +

                                      For how to create a database, see Creating a Data Catalog, Database, and Table on the DLI Console.

                                      +

                                      If you have specified a database where tables are located in SQL statements, the database you choose here does not apply.

                                      Settings

                                      @@ -44,96 +48,97 @@
                                      -
                                    3. Create a database and a table.

                                      Create them in advance by referring to Creating a Database and Table on the DLI Console. For example, create a table named qw.

                                      +
                                    4. Create a database and a table.

                                      Create them in advance by referring to Creating a Data Catalog, Database, and Table on the DLI Console. For example, create a table named qw.

                                    5. In the SQL job editing window, enter the following SQL statement:
                                      1
                                      SELECT * FROM qw.qw LIMIT 10;

                                      Alternatively, you can double-click the table name qw. The query statement is automatically entered in the SQL job editing window.

                                      DLI offers a range of SQL templates that come with use cases, code examples, and usage guides. You can also use these templates to quickly implement your service logic. For more information about templates, see Creating a SQL Job Template.

                                      -
                                    6. On top of the editing window, click More > Verify Syntax to check whether the SQL statement is correct.
                                      1. If the verification fails, check the SQL statement syntax by referring to Data Lake Insight SQL Syntax Reference.
                                      2. If the syntax verification is successful, click Execute. Read and agree to the privacy agreement. Click OK to execute the SQL statement.
                                      +
                                    7. On top of the editing window, click More > Verify Syntax to check whether the SQL statement is correct.
                                      1. If the verification fails, check the SQL statement syntax by referring to Data Lake Insight SQL Syntax Reference.
                                      2. If the syntax verification is successful, click Execute. Read and agree to the privacy agreement. Click OK to execute the SQL statement.

                                      Once successfully executed, you can check the execution result on the View Result tab below the SQL job editing window.

                                      -
                                    8. View job execution results.

                                      On the View Result tab, click to display execution results in a chart. Click to switch back to the table view.

                                      -
                                      You can view a maximum of 1,000 data records on this View Result tab. To view more or full data, click to export the data to OBS.
                                      • If no column of the numeric type is displayed in the execution result, the result cannot be represented in charts.
                                      • You can view the data in a bar chart, line chart, or fan chart.
                                      • In the bar chart and line chart, the X axis can be any column, while the Y axis can only be columns of the numeric type. The fan chart displays the corresponding legends and indicators.
                                      +
                                    9. View job execution results.

                                      On the View Result tab, click to display execution results in a chart. Click to switch back to the table view.

                                      +
                                      You can view a maximum of 1,000 data records on this View Result tab. To view more or full data, click to export the data to OBS.
                                      • If no column of the numeric type is displayed in the execution result, the result cannot be represented in charts.
                                      • You can view the data in a bar chart, line chart, or fan chart.
                                      • In the bar chart and line chart, the X axis can be any column, while the Y axis can only be columns of the numeric type. The fan chart displays the corresponding legends and indicators.
                                    -

                                    Functions of SQL Editor

                                    • Parameter settings for SQL jobs

                                      Click Settings in the upper right corner of the SQL Editor page. You can set parameters and tags for the SQL job.

                                      +

                                      Setting SQL Job Parameters

                                      Click Settings in the upper right corner of the SQL Editor page. You can set parameters and tags for the SQL job.

                                      • Parameter Settings: Assign key-value pairs as parameter settings.

                                      • Tags: Assign key-value pairs as tags to a SQL job.
                                      -
                                      Table 2 Parameters for SQL job running

                                      Parameter

                                      +
                                      - - - - - - - - - - - - - - - - - - - - - - - - - -
                                      Table 2 Parameters for SQL job running

                                      Parameter

                                      Default Value

                                      +

                                      Default Value

                                      Description

                                      +

                                      Description

                                      spark.sql.files.maxRecordsPerFile

                                      +

                                      spark.sql.files.maxRecordsPerFile

                                      0

                                      +

                                      0

                                      Maximum number of records to be written into a single file. If the value is zero or negative, there is no limit.

                                      +

                                      Maximum number of records to be written into a single file. If the value is zero or negative, there is no limit.

                                      spark.sql.autoBroadcastJoinThreshold

                                      +

                                      spark.sql.autoBroadcastJoinThreshold

                                      209715200

                                      +

                                      209715200

                                      Maximum size, in bytes, of the table that displays all working nodes when a connection is executed. You can set this parameter to -1 to disable the display.

                                      +

                                      Maximum size, in bytes, of the table that displays all working nodes when a connection is executed. You can set this parameter to -1 to disable the display.

                                      NOTE:

                                      Currently, only configuration units that store tables analyzed using the ANALYZE TABLE COMPUTE statistics noscan command and file-based data source tables that calculate statistics directly from data files are supported.

                                      spark.sql.shuffle.partitions

                                      +

                                      spark.sql.shuffle.partitions

                                      200

                                      +

                                      200

                                      Default number of partitions used to filter data for join or aggregation.

                                      +

                                      Default number of partitions used to filter data for join or aggregation.

                                      spark.sql.dynamicPartitionOverwrite.enabled

                                      +

                                      spark.sql.dynamicPartitionOverwrite.enabled

                                      false

                                      +

                                      false

                                      When set to false, DLI will delete all partitions that meet the conditions before overwriting them. For example, if there is a partition named 2021-01 in a partitioned table and you use the INSERT OVERWRITE statement to write data to the 2021-02 partition, the data in the 2021-01 partition will also be overwritten.

                                      +

                                      When set to false, DLI will delete all partitions that meet the conditions before overwriting them. For example, if there is a partition named 2021-01 in a partitioned table and you use the INSERT OVERWRITE statement to write data to the 2021-02 partition, the data in the 2021-01 partition will also be overwritten.

                                      When set to true, DLI will not delete partitions in advance, but will overwrite partitions with data written during runtime.

                                      spark.sql.files.maxPartitionBytes

                                      +

                                      spark.sql.files.maxPartitionBytes

                                      134217728

                                      +

                                      134217728

                                      Maximum number of bytes to be packed into a single partition when a file is read.

                                      +

                                      Maximum number of bytes to be packed into a single partition when a file is read.

                                      spark.sql.badRecordsPath

                                      +

                                      spark.sql.badRecordsPath

                                      -

                                      +

                                      -

                                      Path of bad records.

                                      +

                                      Path of bad records.

                                      dli.sql.sqlasync.enabled

                                      +

                                      dli.sql.sqlasync.enabled

                                      true

                                      +

                                      true

                                      Whether DDL and DCL statements are executed asynchronously. The value true indicates that asynchronous execution is enabled.

                                      +

                                      Whether DDL and DCL statements are executed asynchronously. The value true indicates that asynchronous execution is enabled.

                                      dli.sql.job.timeout

                                      +

                                      dli.sql.job.timeout

                                      -

                                      +

                                      -

                                      Job running timeout interval, in seconds. If the job times out, it will be canceled.

                                      +

                                      Job running timeout interval, in seconds. If the job times out, it will be canceled.
                                      -
                                    • Switching to the SparkUI page to view the SQL statement execution process

                                      The SQL editor allows you to switch to the SparkUI to view the SQL statement execution process.

                                      + +

                                      More Common Functions of the SQL Editor

                                      • Switching to the SparkUI page to view the SQL statement execution process

                                        The SQL editor allows you to switch to the SparkUI to view the SQL statement execution process.

                                        • You can view only the latest 100 job records on DLI's SparkUI.
                                        • If a job is running on the default queue or is a synchronization one, you cannot switch to the SparkUI to view the SQL statement execution process.

                                        When you execute a job on a created queue, the cluster is restarted. It takes about 10 minutes. If you click SparkUI before the cluster is created, an empty projectID will be cached. The SparkUI page cannot be displayed. You are advised to use a dedicated queue so that the cluster will not be released. Alternatively, wait for a while after the job is submitted (the cluster is created), and then check SparkUI.

                                        @@ -141,35 +146,35 @@

                                        The View Log button is not available for synchronization jobs and jobs running on the default queue.

                                      • SQL Editor shortcuts -
                                        Table 3 Keyboard shortcuts

                                        Shortcut

                                        +
                                        - - - - - - - - - - - @@ -180,7 +185,14 @@ + + \ No newline at end of file diff --git a/docs/dli/umn/dli_01_0363.html b/docs/dli/umn/dli_01_0363.html index c66e75103..f409712a7 100644 --- a/docs/dli/umn/dli_01_0363.html +++ b/docs/dli/umn/dli_01_0363.html @@ -1,6 +1,6 @@ -

                                        Creating a Non-Elastic Resource Pool Queue (Discarded and Not Recommended)

                                        +

                                        Creating a Non-Elastic Resource Pool Queue (Deprecated, Not Recommended)

                                        Queues in the non-elastic resource pool mode are the previous-gen of resource management for DLI. It involved purchasing and releasing resources based on usage demands, requiring estimation of resource needs before making purchases.

                                        Queues in an elastic resource pool are recommended, as they offer the flexibility to use resources with high utilization as needed. For how to buy an elastic resource pool and create queues within it, see Creating an Elastic Resource Pool and Creating Queues Within It.

                                        • If you use a sub-account to create a queue for the first time, log in to the DLI management console using the main account and keep records in the DLI database before creating a queue.
                                        • It takes 6 to 10 minutes for a job running on a new queue for the first time.
                                        • After a queue is created, if no job is run within one hour, the system releases the queue.
                                        • Queues with 16 CUs do not support scale-out or scale-in.
                                        • Queues with 64 CUs do not support scale-in.
                                        @@ -32,11 +32,11 @@
                                        Table 3 Keyboard shortcuts

                                        Shortcut

                                        Description

                                        +

                                        Description

                                        Ctrl+Enter

                                        +

                                        Ctrl+Enter

                                        Execute SQL statements. You can run SQL statements by pressing Ctrl+R or Ctrl + Enter on the keyboard.

                                        +

                                        Execute SQL statements. You can run SQL statements by pressing Ctrl+R or Ctrl + Enter on the keyboard.

                                        Ctrl+F

                                        +

                                        Ctrl+F

                                        Search for SQL statements. You can press Ctrl+F to search for a required SQL statement.

                                        +

                                        Search for SQL statements. You can press Ctrl+F to search for a required SQL statement.

                                        Shift+Alt+F

                                        +

                                        Shift+Alt+F

                                        Format SQL statements. You can press Shift + Alt + F to format a SQL statement.

                                        +

                                        Format SQL statements. You can press Shift + Alt + F to format a SQL statement.

                                        Ctrl+Q

                                        +

                                        Ctrl+Q

                                        Syntax verification. You can press Ctrl + Q to verify the syntax of SQL statements.

                                        +

                                        Syntax verification. You can press Ctrl + Q to verify the syntax of SQL statements.

                                        F11

                                        +

                                        F11

                                        Full screen. You can press F11 to display the SQL Job Editor window in full screen. Press F11 again to leave the full screen.

                                        +

                                        Full screen. You can press F11 to display the SQL Job Editor window in full screen. Press F11 again to leave the full screen.
                                        -

                                        Procedure

                                        1. You can create a queue on the Overview, SQL Editor, or Queue Management page.
                                          • In the upper right corner of the Overview page, click Create Queue.
                                          • To create a queue on the Queue Management page:
                                            1. In the navigation pane on the left of the DLI management console, choose Resources > Queue Management.
                                            2. In the upper right corner of the Queue Management page, click Create Queue to create a queue.
                                            -
                                          • To create a queue on the SQL Editor page:
                                            1. In the navigation pane of the DLI management console, click SQL Editor.
                                            2. Click Queues. On the tab page displayed, click on the right to create a queue.
                                            +

                                            Procedure

                                            1. You can create a queue on the Overview, SQL Editor, or Queue Management page.
                                              • In the upper right corner of the Overview page, click Create Queue.
                                              • To create a queue on the Queue Management page:
                                                1. In the navigation pane on the left of the DLI management console, choose Resources > Queue Management.
                                                2. In the upper right corner of the Queue Management page, click Create Queue to create a queue.
                                                +
                                              • To create a queue on the SQL Editor page:
                                                1. In the navigation pane on the left of the DLI management console, choose SQL Editor.
                                                2. Click Queues. On the tab page displayed, click on the right to create a queue.
                                              -
                                            2. On the Create Queue page displayed, set the parameters according to Table 2. -
                                              Table 2 Parameters

                                              Parameter

                                              +
                                            3. On the Create Queue page displayed, set the parameters according to Table 2. +
                                              @@ -45,7 +45,7 @@ @@ -81,9 +81,9 @@ @@ -99,7 +99,7 @@ diff --git a/docs/dli/umn/dli_01_0367.html b/docs/dli/umn/dli_01_0367.html index be1da1f56..cfb642ad7 100644 --- a/docs/dli/umn/dli_01_0367.html +++ b/docs/dli/umn/dli_01_0367.html @@ -7,7 +7,7 @@

                                              Prerequisites

                                              All software packages must be uploaded to OBS for storage in advance.

                                              Procedure

                                              1. On the left of the management console, choose Data Management > Package Management.
                                              2. On the Package Management page, click Create in the upper right corner to create a package.
                                              3. In the displayed Create Package dialog box, set related parameters by referring to Table 1. -
                                              Table 2 Parameter descriptions

                                              Parameter

                                              Description

                                              Name

                                              Queue name

                                              -
                                              • Only numbers, letters, and underscores (_) are allowed. The value cannot contain only numbers, start with an underscore (_), or be left unspecified.
                                              • The value can contain a maximum of 128 characters.
                                              +
                                              • Only digits, letters, and underscores (_) are allowed. The value cannot contain only digits, start with an underscore (_), or be left unspecified.
                                              • The value can contain a maximum of 128 characters.
                                              NOTE:

                                              The queue name is case-insensitive. Uppercase letters will be automatically converted to lowercase letters.

                                              Tags used to identify cloud resources. A tag includes the tag key and tag value. If you want to use the same tag to identify multiple cloud resources, that is, to select the same tag from the drop-down list box for all services, you are advised to create predefined tags on the Tag Management Service (TMS).

                                              NOTE:
                                              • A maximum of 20 tags can be added.
                                              • Only one tag value can be added to a tag key.
                                              • The key name in each resource must be unique.
                                              -
                                              • Tag key: Enter a tag key name in the text box.
                                                NOTE:

                                                A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.

                                                +
                                                • Tag key: Enter a tag key name in the text box.
                                                  NOTE:

                                                  A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.

                                                  -
                                                • Tag value: Enter a tag value in the text box.
                                                  NOTE:

                                                  A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.

                                                  +
                                                • Tag value: Enter a tag value in the text box.
                                                  NOTE:

                                                  A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.
                                              Table 1 Parameter description

                                              Parameter

                                              +
                                              @@ -44,10 +44,10 @@ diff --git a/docs/dli/umn/dli_01_0369.html b/docs/dli/umn/dli_01_0369.html index 00cf39928..5aebf6e0b 100644 --- a/docs/dli/umn/dli_01_0369.html +++ b/docs/dli/umn/dli_01_0369.html @@ -13,10 +13,10 @@ @@ -24,7 +24,7 @@ diff --git a/docs/dli/umn/dli_01_0375.html b/docs/dli/umn/dli_01_0375.html index 3a63422e1..7162d0fce 100644 --- a/docs/dli/umn/dli_01_0375.html +++ b/docs/dli/umn/dli_01_0375.html @@ -1,6 +1,6 @@ -

                                              Using DLI to Submit a Spark Jar Job

                                              +

                                              Submitting a Spark Jar Job Using DLI

                                              Scenario

                                              DLI allows you to submit Spark jobs compiled as JAR files, which contain the necessary code and dependency information for executing the job. These files are used for specific data processing tasks such as data query, analysis, and machine learning. Before submitting a Spark Jar job, upload the package to OBS and submit it along with the data and job parameters to run the job.

                                              This example introduces the basic process of submitting a Spark Jar job package through the DLI console. Due to different service requirements, the specific writing of the Jar package may vary. It is recommended that you refer to the sample code provided by DLI and edit and customize it according to your actual business scenario.

                                              @@ -17,12 +17,22 @@
                                              - - + + + + + + @@ -33,15 +43,15 @@

                                              Step 1: Upload Data to OBS

                                              Develop a Spark Jar job program, compile it, and pack it into spark-examples.jar. Perform the following steps to upload the program:

                                              Before submitting Spark Jar jobs, upload data files to OBS.

                                              -
                                              1. Log in to the DLI console.
                                              2. In the service list, click Object Storage Service under Storage.
                                              3. Create a bucket. In this example, name it dli-test-obs01.
                                                1. On the displayed Buckets page, click Create Bucket in the upper right corner.
                                                2. On the displayed Create Bucket page, enter the Bucket Name. Retain the default values for other parameters or set them as required.

                                                  Select a region that matches the location of the DLI console.

                                                  +
                                                  1. Log in to the DLI console.
                                                  2. In the service list, click Object Storage Service under Storage.
                                                  3. Create a bucket. In this example, name it dli-test-obs01.
                                                    1. On the displayed Buckets page, click Create Bucket in the upper right corner.
                                                    2. On the displayed Create Bucket page, set Bucket Name. Retain the default values for other parameters or set them as required.

                                                      Select a region that matches the location of the DLI console.

                                                    3. Click Create Now.
                                                  4. In the bucket list, click the name of the dli-test-obs01 bucket you just created to access its Objects tab.
                                                  5. Click Upload Object. In the dialog box displayed, drag or add files or folders, for example, spark-examples.jar, to the upload area. Then, click Upload.

                                                    In this example, the path after upload is obs://dli-test-obs01/spark-examples.jar.

                                                    -

                                                    For more operations on the OBS console, see the Object Storage Service User Guide.

                                                    +

                                                    For more operations on the OBS console, see Object Storage Service User Guide.

                                                  -

                                                  Step 2: Create an Elastic Resource Pool and Add Queues to the Pool

                                                  In this example, the elastic resource pool dli_resource_pool and queue dli_queue_01 are created.
                                                  1. Log in to the DLI management console.
                                                  2. In the navigation pane on the left, choose Resources > Resource Pool.
                                                  3. On the displayed page, click Buy Resource Pool in the upper right corner.
                                                  4. On the displayed page, set the parameters.
                                                    Table 2 describes the parameters. -
                                              Table 1 Parameter descriptions

                                              Parameter

                                              Description

                                              Tags used to identify cloud resources. A tag includes the tag key and tag value. If you want to use the same tag to identify multiple cloud resources, that is, to select the same tag from the drop-down list box for all services, you are advised to create predefined tags on the Tag Management Service (TMS).

                                              NOTE:
                                              • A maximum of 20 tags can be added.
                                              • Only one tag value can be added to a tag key.
                                              • The key name in each resource must be unique.
                                              -
                                              • Tag key: Enter a tag key name in the text box.
                                                NOTE:

                                                A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.

                                                +
                                                • Tag key: Enter a tag key name in the text box.
                                                  NOTE:

                                                  A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.

                                                -
                                                • Tag value: Enter a tag value in the text box.
                                                  NOTE:

                                                  A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.

                                                  +
                                                  • Tag value: Enter a tag value in the text box.
                                                    NOTE:

                                                    A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.

                                              Tag key

                                              You can specify the tag key in either of the following ways:

                                              -
                                              • Click the text box and select a predefined tag key from the drop-down list.

                                                To add a predefined tag, you need to create one on TMS and then select it from the tag key drop-down list. You can click View predefined tags to go to the Predefined Tags page of the TMS console. Then, click Create Tag in the upper corner of the page to create a predefined tag.

                                                +
                                                • Click the text box and select a predefined tag key from the drop-down list.

                                                  To add a predefined tag, you need to create one on TMS and then select it from the Tag key drop-down list. You can click View predefined tags to go to the Predefined Tags page of the TMS console. Then, click Create Tag in the upper corner of the page to create a predefined tag.

                                                -
                                                • Enter a tag key in the text box.
                                                  NOTE:

                                                  A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.

                                                  +
                                                  • Enter a tag key in the text box.
                                                    NOTE:

                                                    A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.

                                              Tag value

                                              You can specify the tag value in either of the following ways:

                                              -
                                              • Click the text box and select a predefined tag value from the drop-down list.
                                              • Enter a tag value in the text box.
                                                NOTE:

                                                A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.

                                                +
                                                • Click the text box and select a predefined tag value from the drop-down list.
                                                • Enter a tag value in the text box.
                                                  NOTE:

                                                  A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.

                                              Prepare a Spark Jar job package and upload it to OBS.

                                              Step 2: Create an Elastic Resource Pool and Add Queues to the Pool

                                              +

                                              Step 2: Create an Elastic Resource Pool and Create Queues Within It

                                              Create compute resources required for submitting the Spark Jar job.

                                              Step 3: Submit a Spark Job

                                              +

                                              Step 3: Use DEW to Manage Access Credentials

                                              +

                                              In cross-source analysis scenarios, use DEW to manage access credentials of data sources and create an agency that allows DLI to access DEW.

                                              +

                                              Step 4: Create a Custom Agency to Allow DLI to Access DEW and Read Credentials

                                              +

                                              Create an agency to allow DLI to access DEW.

                                              +

                                              Step 5: Submit a Spark Job

                                              Create a Spark Jar job to analyze data.
                                              Table 2 Parameters

                                              Parameter

                                              +

                                              Step 2: Create an Elastic Resource Pool and Create Queues Within It

                                              In this example, the elastic resource pool dli_resource_pool and queue dli_queue_01 are created.
                                              1. Log in to the DLI management console.
                                              2. In the navigation pane on the left, choose Resources > Resource Pool.
                                              3. On the displayed page, click Buy Resource Pool in the upper right corner.
                                              4. On the displayed page, set the parameters.
                                                Table 2 describes the parameters. +
                                                @@ -70,7 +80,7 @@ - @@ -86,7 +96,7 @@ - @@ -102,41 +112,41 @@
                                                Table 2 Parameter descriptions

                                                Parameter

                                                Description

                                                dli_resource_pool

                                                Specifications

                                                +

                                                Type

                                                Specifications of the elastic resource pool

                                                CIDR Block

                                                CIDR block the elastic resource pool belongs to. If you use an enhanced datasource connection, this CIDR block cannot overlap that of the data source. Once set, this CIDR block cannot be changed.

                                                +

                                                CIDR block the elastic resource pool belongs to. If you use an enhanced datasource connection, this CIDR block cannot overlap that of the data source. Once set, this CIDR block cannot be changed.

                                                172.16.0.0/19

                                                -
                                              5. Click Buy.
                                              6. Click Submit.
                                              7. In the elastic resource pool list, locate the pool you just created and click Add Queue in the Operation column.
                                              8. Set the basic parameters listed below. +
                                              9. Click Buy.
                                              10. Click Submit.
                                              11. In the elastic resource pool list, locate the pool you just created and click Add Queue in the Operation column.
                                              12. Set the basic parameters listed below.
                                                - - - - - - - -
                                                Table 3 Basic parameters for adding a queue

                                                Parameter

                                                Description

                                                +

                                                Description

                                                Example Value

                                                +

                                                Example Value

                                                Name

                                                Name of the queue to add

                                                +

                                                Name of the queue to add

                                                dli_queue_01

                                                +

                                                dli_queue_01

                                                Type

                                                Type of the queue

                                                -
                                                • To execute SQL jobs, select For SQL.
                                                • To execute Flink or Spark jobs, select For general purpose.
                                                +

                                                Type of the queue

                                                +
                                                • To execute SQL jobs, select For SQL.
                                                • To execute Flink or Spark jobs, select For general purpose.

                                                _

                                                +

                                                For general purpose

                                                Enterprise Project

                                                Select an enterprise project.

                                                +

                                                Select an enterprise project for the elastic resource pool.

                                                default

                                                +

                                                default
                                                -
                                              13. Click Next and configure scaling policies for the queue.

                                                Click Create to add a scaling policy with varying priority, period, minimum CUs, and maximum CUs.

                                                +
                                              14. Click Next and configure scaling policies for the queue.

                                                Click Create to add a scaling policy with varying priority, period, minimum CUs, and maximum CUs.

                                                - - - - @@ -179,10 +189,41 @@
                                                Table 4 Scaling policy parameters

                                                Parameter

                                                @@ -149,17 +159,17 @@

                                                Priority

                                                Priority of the scaling policy in the current elastic resource pool. A larger value indicates a higher priority. In this example, only one scaling policy is configured, so its priority is set to 1 by default.

                                                +

                                                Priority of the scaling policy in the current elastic resource pool. A larger value indicates a higher priority. In this example, only one scaling policy is configured, so its priority is set to 1 by default.

                                                1

                                                Period

                                                The first scaling policy is the default policy, and its Period parameter configuration cannot be deleted or modified.

                                                +

                                                The first scaling policy is the default policy, and its Period parameter configuration cannot be deleted or modified.

                                                The period for the scaling policy is from 00 to 24.

                                                00–24

                                                +

                                                00-24

                                                Min CU

                                                @@ -171,7 +181,7 @@

                                                Max CU

                                                Maximum number of CUs allowed by the scaling policy

                                                +

                                                Maximum number of CUs allowed by the scaling policy.

                                                64
                                                -
                                              15. Click OK.
                                              +
                                            4. Click OK.
                                              5. -

                                              Step 3: Submit a Spark Job

                                              1. On the DLI management console, choose Job Management > Spark Jobs in the navigation pane on the left. On the displayed page, click Create Job in the upper right corner.
                                              2. Set the following Spark job parameters: +

                                                Step 3: Use DEW to Manage Access Credentials

                                                To write the output data of a Spark Jar job to OBS, AK/SK is required for accessing OBS. To ensure the security of AK/SK data, you can use DEW and CSMS for unified management of AK/SK, effectively avoiding sensitive information leakage and business risks caused by hard-coded or plaintext configuration of programs.

                                                +
                                                This part introduces how to create a shared secret in DEW.
                                                1. Log in to the DEW management console.
                                                2. In the navigation pane on the left, choose Cloud Secret Management Service > Secrets.
                                                3. On the displayed page, click Create Secret. Set basic secret information.

                                                  Set the AK and SK credential key-value pairs.

                                                  +
                                                  • In this example, the key in the first line is the user's access key ID (AK).
                                                  • In this example, the key in the second line is the user's secret access key (SK).
                                                  +
                                                4. Set access credential parameters on the DLI Spark Jar job editing page.
                                                  spark.hadoop.fs.obs.bucket.USER_BUCKET_NAME.dew.access.key= USER_AK_CSMS_KEY_obstest1 
+spark.hadoop.fs.obs.bucket.USER_BUCKET_NAME.dew.secret.key= USER_SK_CSMS_KEY_obstest1
+spark.hadoop.fs.obs.security.provider=com.dli.provider.UserObsBasicCredentialProvider
+spark.hadoop.fs.dew.csms.secretName=obsAkSk
+spark.hadoop.fs.dew.endpoint=kmsendpoint
+spark.hadoop.fs.dew.csms.version=v3
+spark.dli.job.agency.name=agencyname
                                                  +
                                                +
                                                +
                                                +

                                                Step 4: Create a Custom Agency to Allow DLI to Access DEW and Read Credentials

                                                1. Log in to the management console.
                                                2. In the upper right corner of the page, hover over the username and select Identity and Access Management.
                                                3. In the navigation pane of the IAM console, choose Agencies.
                                                4. On the displayed page, click Create Agency.
                                                5. On the Create Agency page, set the following parameters:
                                                  • Agency Name: Enter an agency name, for example, dli_dew_agency_access.
                                                  • Agency Type: Select Cloud service.
                                                  • Cloud Service: This parameter is available only when you select Cloud service for Agency Type. Select Data Lake Insight (DLI) from the drop-down list.
                                                  • Validity Period: Select Unlimited.
                                                  • Description: You can enter Agency with OBS OperateAccess permissions. This parameter is optional.
                                                  +
                                                6. Click Next.
                                                7. Click the agency name. On the displayed page, click the Permissions tab. Click Authorize. On the displayed page, click Create Policy.
                                                8. Configure policy information.
                                                  1. Enter a policy name, for example, dli-dew-agency.
                                                  2. Select JSON.
                                                  3. In the Policy Content area, paste a custom policy.
                                                    {
+    "Version": "1.1",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "csms:secretVersion:get",
+                "csms:secretVersion:list",
+                "kms:dek:decrypt"
+            ]
+        }
+    ]
+}
                                                    +
                                                  4. Enter a policy description as required.
                                                  +
                                                9. Click Next.
                                                10. On the Select Policy/Role page, select Custom policy from the first drop-down list and select the custom policy created in 8.
                                                11. Click Next. On the Select Scope page, set the authorization scope. In this example, select All resources.
                                                12. Click OK.

                                                  It takes 15 to 30 minutes for the authorization to be in effect.

                                                  +
                                                +
                                                +

                                                Step 5: Submit a Spark Job

                                                1. On the DLI management console, choose Job Management > Spark Jobs in the navigation pane on the left. On the displayed page, click Create Job in the upper right corner.
                                                2. Set the following Spark job parameters:

                                                  For other parameters, refer to the description about the Spark job editing page in "Creating a Spark Job" in the Data Lake Insight User Guide.

                                                3. Click Execute in the upper right corner of the Spark job editing window, read and agree to the privacy agreement, and click OK. Submit the job. A message is displayed, indicating that the job is submitted.

                                                4. (Optional) Switch to the Job Management > Spark Jobs page to view the status and logs of the submitted Spark job.
                                                diff --git a/docs/dli/umn/dli_01_0376.html b/docs/dli/umn/dli_01_0376.html index 51151ca9e..aa2e3edeb 100644 --- a/docs/dli/umn/dli_01_0376.html +++ b/docs/dli/umn/dli_01_0376.html @@ -2,7 +2,7 @@

                                                Changing the Database Owner on the DLI Console

                                                In practical use, developers create databases and tables, which are then handed over to testers for testing. Once testing is complete, the databases and tables are handed over to O&M personnel for experience. In this scenario, ownership of the data can be transferred to another owner by changing the database owner.

                                                -

                                                Changing the Database Owner

                                                You can change the owner of a database on either the Data Management page or the SQL Editor page.
                                                • On the Data Management page, change the database owner.
                                                  1. On the left of the management console, choose Data Management > Databases and Tables.
                                                  2. On the Databases and Tables page, locate the database you want and click More > Modify Database in the Operation column.
                                                  3. In the displayed dialog box, enter a new owner name (an existing username) and click OK.
                                                  +

                                                  Changing the Database Owner

                                                  You can change the owner of a database on either the Data Management page or the SQL Editor page.
                                                  • On the Data Management page, change the database owner.
                                                    1. In the navigation pane on the left of the console, choose Data Management > Databases and Tables.
                                                    2. On the Databases and Tables page, locate the database you want and click More > Modify Database in the Operation column.
                                                    3. In the displayed Modify Owner dialog box, enter a new owner name (an existing username) and click OK.
                                                  • Change the database owner on the SQL Editor page.
                                                    1. On the left of the management console, click SQL Editor.
                                                    2. In the navigation tree on the left, click Databases, click on the right of the database you want to modify, and choose Modify Database from the shortcut menu.
                                                    3. In the displayed dialog box, enter a new owner name (an existing username) and click OK.
                                                  diff --git a/docs/dli/umn/dli_01_0377.html b/docs/dli/umn/dli_01_0377.html index c15319069..50b0fd5e6 100644 --- a/docs/dli/umn/dli_01_0377.html +++ b/docs/dli/umn/dli_01_0377.html @@ -21,7 +21,7 @@
                                                -
                                                Parent topic: Submitting a Flink Job Using DLI
                                                +
                                                Parent topic: Submitting a Flink Job on the DLI Management Console
                                                diff --git a/docs/dli/umn/dli_01_0378.html b/docs/dli/umn/dli_01_0378.html index bfc8fba10..810717b70 100644 --- a/docs/dli/umn/dli_01_0378.html +++ b/docs/dli/umn/dli_01_0378.html @@ -2,72 +2,109 @@

                                                What Is Data Lake Insight

                                                DLI Introduction

                                                Data Lake Insight (DLI) is a serverless data processing and analysis service fully compatible with Apache Spark and Apache Flink ecosystems. It frees you from managing any servers.

                                                -

                                                DLI supports standard SQL and is compatible with Spark SQL and Flink SQL. It also supports multiple access modes, and is compatible with mainstream data formats. DLI supports SQL statements and Spark applications for heterogeneous data sources, including CloudTable, RDS, GaussDB(DWS), CSS, OBS, custom databases on ECSs, and offline databases.

                                                +

                                                DLI supports multiple querying methods including standard SQL, Spark SQL, and Flink SQL, with compatibility with mainstream data formats. DLI supports SQL statements and Spark applications for heterogeneous data sources, including CloudTable, RDS, GaussDB(DWS), CSS, OBS, custom databases on ECSs, and offline databases.

                                                -

                                                Functions

                                                You can query and analyze heterogeneous data sources such as RDS, and GaussDB(DWS) on the cloud using access methods, such as visualized interface, RESTful API, JDBC, and Beeline. The data format is compatible with five mainstream data formats: CSV, JSON, Parquet, and ORC.

                                                -
                                                • Basic functions
                                                  • You can use standard SQL statements to query in SQL jobs.
                                                  • Flink jobs support Flink SQL online analysis capabilities: supporting aggregation functions such as Window and Join, using SQL to express service logic, and achieving service implementation conveniently and quickly.
                                                  • For spark jobs, fully-managed Spark computing can be performed. You can submit computing tasks through interactive sessions or in batch to analyze data in the fully managed Spark queues.
                                                  -
                                                • Federated analysis of heterogeneous data sources
                                                  • Spark datasource connection: Data sources such as GaussDB(DWS), RDS, and CSS can be accessed through DLI.
                                                  • Interconnection with multiple cloud services is supported in Flink jobs to form a rich stream ecosystem. The DLI stream ecosystem consists of cloud service ecosystems and open source ecosystems.
                                                    • Cloud service ecosystem: DLI can interconnect with other services in Flink SQL. You can directly use SQL to read and write data from cloud services.
                                                    • Open-source ecosystem: By establishing network connections with other VPCs through enhanced datasource connections, you can access all Flink and Spark-supported data sources and output sources, such as Kafka, Hbase, Elasticsearch, in the tenant-authorized DLI queues.
                                                    -

                                                    -
                                                  -
                                                • Storage-compute decoupling

                                                  DLI is interconnected with OBS for data analysis. In this architecture where storage and compute are decoupled, resources of these two types are charged separately, helping you reduce costs and improving resource utilization.

                                                  -

                                                  You can choose single-AZ or multi-AZ storage when you create an OBS bucket for storing redundant data on the DLI console. The differences between the two storage policies are as follows:

                                                  -
                                                  • Multi-AZ storage means data is stored in multiple AZs, improving data reliability. If the multi-AZ storage is enabled for a bucket, data is stored in multiple AZs in the same region. If one AZ becomes unavailable, data can still be properly accessed from the other AZs. The multi-AZ storage is ideal for scenarios that demand high reliability. You are advised to use this policy.
                                                  • Single-AZ storage means that data is stored in a single AZ, with lower costs.
                                                  -
                                                • Elastic resource pool

                                                  The backend of elastic resource pools adopts a CCE cluster architecture, supporting heterogeneous resources, so you can manage and schedule resources in a unified manner.

                                                  -

                                                  For details, see Creating an Elastic Resource Pool and Queues Within It.

                                                  -

                                                  Elastic resource pools have the following advantages:

                                                  -
                                                  • Unified management
                                                    • You can manage multiple internal clusters and schedule jobs. You can manage millions of cores for compute resources.
                                                    • Elastic resource pools can be deployed across multiple AZs to support high availability.
                                                    -
                                                  • Tenant resource isolation

                                                    Resources of different queues are isolated to reduce the impact on each other.

                                                    -
                                                  • Shared access and flexibility
                                                    • Minute-level scaling helps you to handle request peaks.
                                                    • Queue priorities and CU quotas can be set at different time to improve resource utilization.
                                                    -
                                                  • Job-level isolation (supported in later versions)

                                                    SQL jobs can run on independent Spark instances, reducing mutual impacts between jobs.

                                                    -
                                                  • Automatic scaling (supported in later versions)

                                                    The queue quota is updated in real time based on workload and priority.

                                                    -
                                                  -

                                                  Using elastic resource pools has the following advantages.

                                                  - -

                                                  Advantage

                                                  +

                                                  Core Functions

                                                  +
                                                  - - - - - - - - - - - - - + + + + + + + +
                                                  Table 1 DLI core functions

                                                  Function

                                                  No Elastic Resource Pool

                                                  -

                                                  Use Elastic Resource Pool

                                                  +

                                                  Description

                                                  Efficiency

                                                  +

                                                  DLI is a data processing and analytics service built on the serverless architecture.

                                                  You need to set scaling tasks repeatedly to improve the resource utilization.

                                                  -

                                                  Dynamic scaling can be done in seconds.

                                                  +

                                                  DLI is a serverless big data query and analytics service. With DLI, you only pay for the actual compute resources used, with no need to maintain or manage cloud servers.

                                                  +
                                                  • Auto scaling: DLI ensures you always have enough capacity on hand to deal with any traffic spikes.

                                                  Resource utilization

                                                  -

                                                  +

                                                  DLI supports multiple compute engines.

                                                  Resources cannot be shared among different queues.

                                                  -

                                                  For example, a queue has idle CUs and another queue is heavily loaded. Resources cannot be shared. You can only scale up the second queue.

                                                  -

                                                  Queues added to the same elastic resource pool can share compute resources.

                                                  +

                                                  DLI is fully compatible with ecosystems like Apache Spark and Apache Flink, and supports standard SQL, Spark SQL, and Flink SQL. It is compatible with mainstream data formats such as CSV, JSON, Parquet, and ORC.

                                                  +
                                                  • Spark is a unified analytics engine designed for large-scale data processing, focusing on query, compute, and analysis. DLI has undergone extensive performance optimization and service-oriented enhancements over the open-source Spark, maintaining compatibility with the Apache Spark ecosystem and APIs while boosting performance by 2.5 times, enabling exabyte-scale data queries and analyses within hours.
                                                  • Flink is a distributed compute engine that can be used for batch processing, which involves handling static datasets and historical datasets. It can also be used for stream processing, enabling the real-time processing of live data streams and the immediate generation of data results. DLI has enhanced features and security based on the open-source Flink and offers the Stream SQL feature needed for data processing.

                                                  When you set a data source, you must allocate different network segments to each queue, which requires a large number of VPC network segments.

                                                  +

                                                  DLI supports multiple connection methods.

                                                  You can add multiple general-purpose queues in the same elastic resource pool to one network segment, simplifying the data source configuration.

                                                  +

                                                  DLI provides multiple connection methods to meet diverse user needs and scenarios.

                                                  +

                                                  Connection methods:

                                                  +
                                                  • Web-based console
                                                  • APIs
                                                  • SDKs
                                                  • Client tools
                                                  • Submitting DLI jobs using DataArts Studio
                                                  • Connecting to BI tools for visual analysis

                                                  Resource allocation

                                                  +

                                                  DLI can connect to multiple data sources for cross-source data analysis.

                                                  If resources are insufficient for scale-out tasks of multiple queues, some queues will fail to be scaled out.

                                                  +
                                                  • Spark datasource connection: Data sources such as GaussDB(DWS), RDS, and CSS can be accessed through DLI.
                                                  • Flink supports cross-source connectivity with various cloud services, forming a rich streaming ecosystem. DLI's streaming ecosystem is divided into cloud service ecosystems and open-source ecosystems:
                                                    • Cloud service ecosystem: DLI supports connectivity with other services in Flink SQL. You can directly use SQL to read and write data from these cloud services.
                                                    • Open-source ecosystem: By establishing network connections with other VPCs through enhanced datasource connections, you can access all Flink and Spark-supported data sources and output sources, such as Kafka, Hbase, Elasticsearch, in the tenant-authorized DLI queues.
                                                    +

                                                    +

                                                  You can set the priority for each queue in the elastic resource pool based on the peak hours to ensure proper resource allocation.

                                                  +

                                                  Three basic job types supported by DLI

                                                  +
                                                  • SQL jobs allow you to query data using standard SQL statements.
                                                  • Flink jobs support Flink SQL online analysis capabilities: supporting aggregation functions such as Window and Join, using SQL to express service logic, and achieving service implementation conveniently and quickly.
                                                  • Spark jobs provide fully managed Spark computing features: You can submit computing tasks through interactive sessions and batch processing, and perform data analysis on fully managed Spark queues.
                                                  +

                                                  DLI supports decoupled storage and compute.

                                                  +

                                                  After storing data in OBS, you can connect DLI to OBS for data analysis. Under the decoupled storage and compute architecture, storage resources and compute resources can be requested and billed separately, reducing costs and improving resource utilization.

                                                  +

                                                  You can choose single-AZ or multi-AZ storage when creating an OBS bucket for storing redundant data on the DLI console. The differences between the two storage policies are as follows:

                                                  +
                                                  • Multi-AZ storage means data will be redundantly stored across multiple AZs, offering higher reliability. Buckets with multi-AZ storage will store data in multiple different AZs within the same region. If one AZ becomes unavailable, data can still be accessed normally from other AZs, making it suitable for data storage scenarios requiring high reliability. You are advised to use this policy.
                                                  • Single-AZ storage means data is only stored in a single AZ, but it is more cost-effective compared to multi-AZ storage.
                                                  +

                                                  DLI manages and schedules resources in a unified manner using elastic resource pools.

                                                  +

                                                  The backend of elastic resource pools adopts a CCE cluster architecture, supporting heterogeneous resources, so you can manage and schedule resources in a unified manner.

                                                  +

                                                  For details, see Creating an Elastic Resource Pool and Creating Queues Within It.
                                                  -
                                                  -

                                                  DLI Core Engine: Spark+Flink+Trino

                                                  • Spark is a unified analysis engine that is ideal for large-scale data processing. It focuses on query, compute, and analysis. DLI optimizes performance and reconstructs services based on open-source Spark. It is compatible with the Apache Spark ecosystem and interfaces, and improves performance by 2.5x when compared with open-source Spark. In this way, DLI enables you to perform query and analysis of EB's of data within hours.
                                                  • Flink is a distributed compute engine that is ideal for batch processing, that is, for processing static data sets and historical data sets. You can also use it for stream processing, that is, processing real-time data streams and generating data results in real time. DLI enhances features and security based on the open-source Flink and provides the Stream SQL feature required for data processing.
                                                  +

                                                  DLI Product Architecture

                                                  DLI includes the following core modules:

                                                  + +
                                                  + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                  Table 2 DLI core modules

                                                  Module

                                                  +

                                                  Description

                                                  +

                                                  Ecosystem tools

                                                  +

                                                  DLI leverages its robust serverless architecture and multimodal engine support to fulfill the diverse needs of various industries, driving their digital transformation and fostering innovation.

                                                  +

                                                  Compute engine

                                                  +
                                                  • Spark: supports batch processing and interactive analysis of large-scale data and provides high-performance distributed computing capabilities.
                                                  • Flink: supports real-time stream processing, capable of handling large-scale real-time data streams, with support for event time processing and state management.
                                                  • HetuEngine: supports interactive data analysis, swiftly handles complex SQL queries, and facilitates connections and queries across various data sources.
                                                  +

                                                  Unified resource management

                                                  +
                                                  • Resource decoupling: DLI adopts a decoupled compute and storage architecture, decoupling compute resources from storage resources. This allows for flexible adjustment of the ratio between compute and storage resources based on actual needs, enhancing resource utilization and reducing costs.
                                                  • Elastic scaling: DLI compute resources are based on containerized Kubernetes and possess ultimate elastic scaling capabilities. Resources can be automatically adjusted based on job demands.
                                                  • Multi-tenant support: Compute resources can be isolated by tenant to ensure independence among different tenants. Each tenant can independently manage their own compute resources, enabling fine-grained resource management and facilitating inter-departmental data sharing and permissions management within enterprises.
                                                  • Pay-per-use compute resources: You only pay for the compute resources you actually use, with no need to pre-purchase or manage servers, enhancing usage efficiency.
                                                  +

                                                  Unified metadata management

                                                  +
                                                  • Multi-source metadata integration: DLI supports centralized management of metadata from various data sources, including cloud-based data sources (such as OBS, RDS, GaussDB(DWS), and CSS) and on-premises data sources (such as self-built databases and Redis). You can manage and analyze metadata across different data sources without the need to migrate data to a unified data lake.
                                                  • Metadata synchronization: DLI provides metadata management to ensure the timeliness and consistency of metadata.
                                                  • Metadata query and management: DLI offers standard SQL APIs, enabling you to query and manage metadata using SQL statements. You can add, delete, modify, and query metadata to facilitate data governance and analysis.
                                                  • Data security and permission management: Permissions on data catalogs, databases, and tables can be managed. You can assign different permissions to various tenants and user groups to ensure data security and compliance.
                                                  +

                                                  Storage service

                                                  +

                                                  OBS and databases are used to store structured or unstructured data for data analysis, providing persistent data storage services.

                                                  +

                                                  Data source connection

                                                  +
                                                  • Cloud data sources can be connected. For example, OBS can be used to store and manage unstructured data. Relational database service (RDS) can be used to store and manage structured data. GaussDB(DWS) can be used to efficiently query and analyze data.
                                                  • On-premises data sources, such as self-built databases (MySQL, PostgreSQL, and HDFS), can be connected.
                                                  +

                                                  Data applications

                                                  +

                                                  DLI can connect to mainstream BI tools in the industry to flexibly meet data presentation needs.

                                                  +
                                                  -

                                                  Serverless Architecture

                                                  DLI is a serverless big data query and analysis service. It has the following advantages:

                                                  -
                                                  • Auto scaling: DLI ensures you always have enough capacity on hand to deal with any traffic spikes.

                                                  Accessing DLI

                                                  A web-based service management platform is provided. You can access DLI using the management console or HTTPS-based APIs, or connect to the DLI server through the JDBC client.

                                                  • Using the management console

                                                    You can submit SQL, Spark, or Flink jobs on the DLI management console.

                                                    diff --git a/docs/dli/umn/dli_01_0379.html b/docs/dli/umn/dli_01_0379.html index 14ff1483b..2b1ee718d 100644 --- a/docs/dli/umn/dli_01_0379.html +++ b/docs/dli/umn/dli_01_0379.html @@ -9,7 +9,7 @@

                                                  Prerequisites

                                                  Before the configuration, create an OBS bucket or parallel file system (PFS). In big data scenarios, you are advised to create a PFS. PFS is a high-performance file system provided by OBS, with access latency in milliseconds. PFS can achieve a bandwidth performance of up to TB/s and millions of IOPS, which makes it ideal for processing high-performance computing (HPC) workloads.

                                                  -

                                                  Configuring a Bucket for DLI Jobs

                                                  1. In the navigation pane of the DLI console, choose Global Configuration > Project.
                                                  2. On the Project page, click next to Job Bucket to configure bucket information.
                                                  3. Click to view available buckets.
                                                  4. In the displayed OBS dialog box, click the name of a bucket or search for and click a bucket name and then click OK. In the Set Job Bucket dialog box, click OK.

                                                    Temporary data generated during DLI job running will be stored in the OBS bucket.

                                                    +

                                                    Configuring a Bucket for DLI Jobs

                                                    1. In the navigation pane of the DLI console, choose Global Configuration > Project.
                                                    2. On the Project page, click next to Job Bucket to configure bucket information.
                                                    3. Click to view available buckets.
                                                    4. In the displayed OBS dialog box, click the name of a bucket or search for and click a bucket name and then click OK. In the Set Job Bucket dialog box, click OK.

                                                      Temporary data generated during DLI job running will be stored in the OBS bucket.

                                                    Querying Logs for Spark Jobs

                                                    1. Log in to the DLI console. In the navigation pane on the left, choose Job Management > Spark Jobs.
                                                    2. Select the Spark job whose jobs you want to query, click More in the Operation column, and select View Log.

                                                      The system automatically switches to the log path of the DLI job bucket.

                                                      @@ -18,7 +18,14 @@
                                                    + + \ No newline at end of file diff --git a/docs/dli/umn/dli_01_0384.html b/docs/dli/umn/dli_01_0384.html index 5438fe108..0c2734a93 100644 --- a/docs/dli/umn/dli_01_0384.html +++ b/docs/dli/umn/dli_01_0384.html @@ -1,155 +1,277 @@

                                                    Creating a Spark Job

                                                    -

                                                    DLI provides fully-managed Spark computing services by allowing you to execute Spark jobs.

                                                    +

                                                    DLI Spark jobs provide fully managed Spark computing services.

                                                    On the Overview page, click Create Job in the upper right corner of the Spark Jobs tab or click Create Job in the upper right corner of the Spark Jobs page. The Spark job editing page is displayed.

                                                    On the Spark job editing page, a message is displayed, indicating that a temporary DLI data bucket will be created. The created bucket is used to store temporary data generated by DLI, such as job logs and job results. You cannot view job logs if you choose not to create the bucket. The bucket will be created and the default bucket name is used.

                                                    If you do not need to create a DLI temporary data bucket and do not want to receive this message, select Do not show again and click Cancel.

                                                    -

                                                    Prerequisites

                                                    • You have uploaded the dependencies to the corresponding OBS bucket on the Data Management > Package Management page. For details, see Creating a DLI Package.
                                                    • Before creating a Spark job to access other external data sources, such as OpenTSDB, HBase, Kafka, GaussDB(DWS), RDS, CSS, CloudTable, DCS Redis, and DDS, you need to create a datasource connection to enable the network between the job running queue and external data sources.
                                                      • For details about the external data sources that can be accessed by Spark jobs, see Common Development Methods for DLI Cross-Source Analysis.
                                                      • For how to create a datasource connection, see Configuring the Network Connection Between DLI and Data Sources (Enhanced Datasource Connection).

                                                        On the Resources > Queue Management page, locate the queue you have created, click More in the Operation column, and select Test Address Connectivity to check if the network connection between the queue and the data source is normal. For details, see Testing Address Connectivity.

                                                        +

                                                        Prerequisites

                                                        -

                                                        Procedure

                                                        1. In the left navigation pane of the DLI management console, choose Job Management > Spark Jobs. The Spark Jobs page is displayed.

                                                          Click Create Job in the upper right corner. In the job editing window, you can set parameters in Fill Form mode or Write API mode.

                                                          -

                                                          The following uses the Fill Form as an example. In Write API mode, refer to the Data Lake Insight API Reference for parameter settings.

                                                          -
                                                        1. Select a queue.

                                                          Select the queue you want to use from the drop-down list box.

                                                          -
                                                        2. Select a Spark version. Select a supported Spark version from the drop-down list. The latest version is recommended.

                                                          You are advised not to use Spark/Flink engines of different versions for a long time.

                                                          +

                                                          Procedure

                                                          1. In the left navigation pane of the DLI management console, choose Job Management > Spark Jobs. The Spark Jobs page is displayed.

                                                            Click Create Job in the upper right corner. In the job editing window, you can set parameters in Fill Form mode or Write API mode.

                                                            +

                                                            The following uses the Fill Form as an example. In Write API mode, refer to the Data Lake Insight API Reference for parameter settings.

                                                            +
                                                          1. Select a queue.
                                                            1. Queues: Select a queue from the drop-down list.
                                                            2. Spark Version: Select a Spark version from the drop-down list. The latest version is recommended.

                                                              You are advised not to use Spark of different versions for a long time.

                                                              • Doing so can lead to code incompatibility, which can negatively impact job execution efficiency.
                                                              • Doing so may result in job execution failures due to conflicts in dependencies. Jobs rely on specific versions of libraries or components.
                                                              -
                                                            3. Configure the job.

                                                              Configure job parameters by referring to Table 1.

                                                              -
                                                              -
                                                              Table 1 Job configuration parameters

                                                              Parameter

                                                              + +
                                                            4. Configure the application. +
                                                              - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                                              Table 1 Application configuration parameters

                                                              Parameter

                                                              Description

                                                              +

                                                              Description

                                                              Job Name (--name)

                                                              +

                                                              Application

                                                              Set a job name.

                                                              +

                                                              Select the package to be executed. The value can be .jar or .py.

                                                              +

                                                              There are the following ways to manage JAR files:

                                                              +
                                                              • Upload packages to OBS: Upload JAR files to an OBS bucket in advance and select the corresponding OBS path.
                                                              • Upload packages to DLI: Upload JAR files to an OBS bucket in advance and create a package on the Data Management > Package Management page of the DLI management console. For details, see Creating a DLI Package.
                                                              +

                                                              For Spark 3.3.x or later, you can only select packages in OBS paths.

                                                              Application

                                                              +

                                                              Agency

                                                              Select the package to be executed. The value can be .jar or .py.

                                                              -

                                                              There are the following ways to manage JAR files:

                                                              -
                                                              • Upload packages to OBS: Upload Jar packages to an OBS bucket in advance and select the corresponding OBS path.
                                                              • Upload packages to DLI: Upload JAR files to an OBS bucket in advance and create a package on the Data Management > Package Management page of the DLI management console. For details, see Creating a DLI Package.
                                                              -

                                                              For Spark 3.3.x or later, you can only select packages in OBS paths.

                                                              +

                                                              Before using Spark 3.3.1 or later (Spark general queue scenario) to run jobs, you need to create an agency on the IAM console and add the new agency information. For details, see Customizing DLI Agency Permissions.

                                                              +

                                                              Common scenarios for creating an agency: DLI is allowed to read and write data from and to OBS to transfer logs. DLI is allowed to access DEW to obtain data access credentials and access catalogs to obtain metadata.

                                                              Main Class (--class)

                                                              +

                                                              Main Class (--class)

                                                              Enter the name of the main class. When the application type is .jar, the main class name cannot be empty.

                                                              +

                                                              Enter the name of the main class. When the application type is .jar, the main class name cannot be empty.

                                                              Application Parameters

                                                              +

                                                              Application Parameters

                                                              User-defined parameters. Separate multiple parameters by Enter.

                                                              -

                                                              These parameters can be replaced with global variables. For example, if you create a global variable batch_num on the Global Configuration > Global Variables page, you can use {{batch_num}} to replace a parameter with this variable after the job is submitted.

                                                              -

                                                              Spark Arguments (--conf)

                                                              -

                                                              Enter a parameter in the format of key=value. Press Enter to separate multiple key-value pairs.

                                                              -

                                                              These parameters can be replaced with global variables. For example, if you create a global variable custom_class on the Global Configuration > Global Variables page, you can use "spark.sql.catalog"={{custom_class}} to replace a parameter with this variable after the job is submitted.

                                                              -
                                                              NOTE:
                                                              • The JVM garbage collection algorithm cannot be customized for Spark jobs.
                                                              • If the Spark version is 3.1.1, configure Spark parameters (--conf) to select a dependent module. For details about the example configuration, see Table 2.
                                                              -
                                                              -

                                                              Job Type

                                                              -

                                                              Set this parameter when you select a CCE queue. Type of the Spark image used by a job. The options are as follows:

                                                              -
                                                              • Basic: Base images provided by DLI. Select this option for non-AI jobs.
                                                              • Image: Custom Spark images. Select an existing image name and version on SWR.
                                                              -

                                                              JAR Package Dependencies (--jars)

                                                              -

                                                              JAR file on which the Spark job depends. You can enter the JAR file name or the OBS path of the JAR file in the format of obs://Bucket name/Folder path/JAR file name.

                                                              -

                                                              Python File Dependencies (--py-files)

                                                              -

                                                              py-files on which the Spark job depends. You can enter the Python file name or the corresponding OBS path of the Python file. The format is as follows: obs://Bucket name/Folder name/File name.

                                                              -

                                                              Other Dependencies (--files)

                                                              -

                                                              Other files on which the Spark job depends. You can enter the name of the dependency file or the corresponding OBS path of the dependency file. The format is as follows: obs://Bucket name/Folder name/File name.

                                                              -

                                                              Group Name

                                                              -

                                                              If you select a group when creating a package, you can select all the packages and files in the group. For how to create a package, see Creating a DLI Package.

                                                              -

                                                              Access Metadata

                                                              -

                                                              Whether to access metadata through Spark jobs.

                                                              -

                                                              Retry upon Failure

                                                              -

                                                              Indicates whether to retry a failed job.

                                                              -

                                                              If you select Yes, you need to set the following parameters:

                                                              -

                                                              Maximum Retries: Maximum number of retry times. The maximum value is 100.

                                                              -

                                                              Advanced Settings

                                                              -
                                                              • Skip
                                                              • Configure
                                                                • Select Dependency Resources: For details about the parameters, see Table 3.
                                                                • Configure Resources: For details about the parameters, see Table 4.
                                                                -
                                                              +

                                                              User-defined parameters. Separate multiple parameters by Enter.

                                                              +

                                                              These parameters can be replaced with global variables. For example, if you create a global variable batch_num on the Global Configuration > Global Variables page, you can use {{batch_num}} to replace a parameter with this variable after the job is submitted.
                                                              - - -
                                                              Table 2 Spark Parameter (--conf) configuration

                                                              Datasource

                                                              +
                                                            5. Configure the job. +
                                                              - - - + + + + + + + + + + + +
                                                              Table 2 Job configuration parameters

                                                              Parameter

                                                              Example Value

                                                              +

                                                              Description

                                                              CSS

                                                              +

                                                              Job Name (--name)

                                                              spark.driver.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/css/*

                                                              +

                                                              Set a job name.

                                                              +

                                                              Spark Arguments(--conf)

                                                              +

                                                              Enter a parameter in the format of key=value. Press Enter to separate multiple key-value pairs.

                                                              +

                                                              These parameters can be replaced with global variables. For example, if you create a global variable custom_class on the Global Configuration > Global Variables page, you can use "spark.sql.catalog"={{custom_class}} to replace a parameter with this variable after the job is submitted.

                                                              +
                                                              NOTE:
                                                              • The JVM garbage collection algorithm cannot be customized for Spark jobs.
                                                              • If the Spark version is 3.1.1, configure Spark parameters (--conf) to select a dependency module. For details about the example configuration, see Table 3.
                                                              +
                                                              +

                                                              If you select 3.3.1 for Spark Version, you can configure compute resource specification parameters in Spark Argument(--conf). Note that the configuration priority of Spark Argument(--conf) is higher than that of Resource Specifications(Optional) in Advanced Settings.

                                                              +

                                                              Table 4 describes the parameter mapping.

                                                              +
                                                              NOTE:

                                                              When configuring compute resource specification parameters in Spark Argument(--conf), you can use the unit M, G, or K. If the unit is not specified, the default unit is byte.

                                                              +
                                                              +

                                                              Access Metadata

                                                              +

                                                              Choose whether to enable access to metadata for a Spark job. Set it to Yes if you need to configure the metadata type accessed by the job. DLI metadata is accessed by default.

                                                              +

                                                              When set to Yes, you also need to set Metadata Source.

                                                              +

                                                              Retry upon Failure

                                                              +

                                                              Indicates whether to retry a failed job.

                                                              +

                                                              If you select Yes, you need to set the following parameters:

                                                              +

                                                              Maximum Retries: Maximum number of retry times. The maximum value is 100.

                                                              +
                                                              +
                                                              + +
                                                              + + + + + - - - - - - - - - -
                                                              Table 3 Spark Parameter (--conf) configuration

                                                              Datasource

                                                              +

                                                              Example Value

                                                              +

                                                              CSS

                                                              +

                                                              spark.driver.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/css/*

                                                              spark.executor.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/css/*

                                                              GaussDB(DWS)

                                                              +

                                                              GaussDB(DWS)

                                                              spark.driver.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/dws/*

                                                              +

                                                              spark.driver.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/dws/*

                                                              spark.executor.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/dws/*

                                                              HBase

                                                              +

                                                              HBase

                                                              spark.driver.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/hbase/*

                                                              +

                                                              spark.driver.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/hbase/*

                                                              spark.executor.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/hbase/*

                                                              OpenTSDB

                                                              +

                                                              OpenTSDB

                                                              park.driver.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/opentsdb/*

                                                              +

                                                              spark.driver.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/opentsdb/*

                                                              spark.executor.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/opentsdb/*

                                                              RDS

                                                              +

                                                              RDS

                                                              spark.driver.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/rds/*

                                                              +

                                                              spark.driver.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/rds/*

                                                              spark.executor.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/rds/*

                                                              Redis

                                                              +

                                                              Redis

                                                              spark.driver.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/redis/*

                                                              +

                                                              spark.driver.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/redis/*

                                                              spark.executor.extraClassPath=/usr/share/extension/dli/spark-jar/datasource/redis/*
                                                              -
                                                            6. Set the following parameters in advanced settings:
                                                              • Select Dependency Resources: For details about the parameters, see Table 3.
                                                              • Configure Resources: For details about the parameters, see Table 4.

                                                                The parallelism degree of Spark resources is jointly determined by the number of Executors and the number of Executor CPU cores.

                                                                + +
                                                                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                Table 4 Mapping between compute resource specification parameters on the console and Spark Argument(--conf)

                                                                Console Parameter

                                                                +

                                                                Spark Argument(--conf)

                                                                +

                                                                Description

                                                                +

                                                                Notes and Constraints

                                                                +

                                                                Executor Memory

                                                                +

                                                                Complete executor memory = spark.executor.memory + spark.executor.memoryOverhead

                                                                +

                                                                spark.executor.memory

                                                                +

                                                                Executor memory, which is configurable.

                                                                +

                                                                -

                                                                +

                                                                spark.executor.memoryOverhead

                                                                +

                                                                Amount of off-heap memory for each executor in a Spark application. This parameter is not configurable.

                                                                +

                                                                spark.executor.memoryOverhead=spark.executor.memory * spark.executor.memoryOverheadFactor

                                                                +

                                                                The minimum value is 384 MB.

                                                                +

                                                                That is, when the value of spark.executor.memory multiplied by spark.executor.memoryOverheadFactor is less than 384 MB, the system automatically sets the value to 384 MB.

                                                                +

                                                                spark.executor.memoryOverheadFactor

                                                                +

                                                                This parameter determines the ratio of off-heap memory allocation to on-heap memory allocation. The default value is 0.1 for Spark applications run with the JAR file and 0.4 for those run with Python. This parameter is configurable.

                                                                +

                                                                The priority of spark.executor.memoryOverheadFactor is higher than that of spark.kubernetes.memoryOverheadFactor.

                                                                +

                                                                Executor Cores

                                                                +

                                                                spark.executor.cores

                                                                +

                                                                Number of executor cores, which is configurable.

                                                                +

                                                                -

                                                                +

                                                                Executors

                                                                +

                                                                spark.executor.instances

                                                                +

                                                                Number of executors, which is configurable.

                                                                +

                                                                -

                                                                +

                                                                Driver Cores

                                                                +

                                                                spark.driver.cores

                                                                +

                                                                Number of driver cores, which is configurable.

                                                                +

                                                                -

                                                                +

                                                                Driver Memory

                                                                +

                                                                Complete driver memory = spark.driver.memory + spark.edriver.memoryOverhead

                                                                +

                                                                +

                                                                spark.driver.memory

                                                                +

                                                                Driver memory, which is configurable.

                                                                +

                                                                -

                                                                +

                                                                spark.driver.memoryOverhead

                                                                +

                                                                Amount of off-heap memory for each driver in a Spark application.

                                                                +

                                                                This parameter is not configurable.

                                                                +

                                                                spark.driver.memoryOverhead=

                                                                +

                                                                spark.driver.memory * spark.driver.memoryOverheadFactor

                                                                +

                                                                The minimum value is 384 MB. That is, when the value of spark.driver.memory multiplied by spark.driver.memoryOverheadFactor is less than 384 MB, the system automatically sets the value to 384 MB.

                                                                +

                                                                spark.driver.memoryOverheadFactor

                                                                +

                                                                This parameter determines the ratio of off-heap memory allocation to on-heap memory allocation. The default value is 0.1 for Spark applications run with the JAR file and 0.4 for those run with Python. This parameter is configurable.

                                                                +

                                                                The priority of spark.driver.memoryOverheadFactor is higher than that of spark.kubernetes.memoryOverheadFactor.

                                                                +

                                                                -

                                                                +

                                                                spark.kubernetes.memoryOverheadFactor

                                                                +

                                                                Amount of memory allocated outside the memory assigned to Spark executors. The default value is 0.1 for Spark applications run with the JAR file and 0.4 for those run with Python. This parameter is configurable.

                                                                +

                                                                The priority of spark.executor.memoryOverheadFactor and spark.driver.memoryOverheadFactor is higher than that of spark.kubernetes.memoryOverheadFactor.

                                                                +
                                                                +
                                                                +
                                                              • (Optional) Configure dependencies. +
                                                                + + + + + + + + + + + + + + + + +
                                                                Table 5 Dependency configuration parameters

                                                                Parameter

                                                                +

                                                                Description

                                                                +

                                                                JAR Package Dependencies (--jars)

                                                                +

                                                                JAR file on which the Spark job depends. You can enter the JAR file name or the OBS path of the JAR file in the format of obs://Bucket name/Folder path/JAR file name.

                                                                +

                                                                Python File Dependencies (--py-files)

                                                                +

                                                                py-files on which the Spark job depends. You can enter the Python file name or the corresponding OBS path of the Python file. The format is as follows: obs://Bucket name/Folder name/File name.

                                                                +

                                                                Other Dependencies (--files)

                                                                +

                                                                Other files on which the Spark job depends. You can enter the name of the dependency file or the corresponding OBS path of the dependency file. The format is as follows: obs://Bucket name/Folder name/File name.

                                                                +

                                                                Group Name

                                                                +

                                                                If you select a group when creating a package, you can select all the packages and files in the group. For how to create a package, see Creating a DLI Package.

                                                                +

                                                                Spark 3.3.x or later does not support group information configuration.

                                                                +
                                                                +
                                                                +
                                                              • Set the following parameters in advanced settings:
                                                                • Select Dependency Resources: For details about the parameters, see Table 6.
                                                                • Configure Resources: For details about the parameters, see Table 7.

                                                                  The parallelism degree of Spark resources is jointly determined by the number of Executors and the number of Executor CPU cores.

                                                                  Maximum number of tasks that can be concurrently executed = Number of Executors x Number of Executor CPU cores

                                                                  You can properly plan compute resource specifications based on the compute CUs of the queue you have purchased.

                                                                  Note that Spark tasks need to be jointly executed by multiple roles, such as driver and executor. So, the number of executors multiplied by the number of executor CPU cores must be less than the number of compute CUs of the queue to prevent other roles from failing to start Spark tasks. For more information about roles for Spark tasks, see Apache Spark.

                                                                  @@ -158,78 +280,141 @@
                                                                -
                                                                Table 3 Parameters for selecting dependency resources

                                                                Parameter

                                                                +
                                                                - - - - -
                                                                Table 6 Parameters for selecting dependency resources

                                                                Parameter

                                                                Description

                                                                +

                                                                Description

                                                                modules

                                                                +

                                                                modules

                                                                If the Spark version is 3.1.1, you do not need to select a module. Configure Spark parameters (--conf).

                                                                +

                                                                If the Spark version is 3.1.1, you do not need to select a module. Configure Spark parameters (--conf).

                                                                Dependency modules provided by DLI for executing datasource connection jobs. To access different services, you need to select different modules.
                                                                • MRS HBase: sys.datasource.hbase
                                                                • DDS: sys.datasource.mongo
                                                                • MRS OpenTSDB: sys.datasource.opentsdb
                                                                • DWS: sys.datasource.dws
                                                                • RDS MySQL: sys.datasource.rds
                                                                • RDS PostGre: sys.datasource.rds
                                                                • DCS: sys.datasource.redis
                                                                • CSS: sys.datasource.css

                                                                Resource Package

                                                                +

                                                                Resource Package

                                                                JAR package on which the Spark job depends.

                                                                +

                                                                JAR package on which the Spark job depends.

                                                                +

                                                                Spark 3.3.x or later does not support this parameter. Configure resource package information in jars, pyFiles, and files.
                                                                -
                                                                Table 4 Resource specification parameters

                                                                Parameter

                                                                +
                                                                - - - - - - - - - - - - -
                                                                Table 7 Resource specification parameters

                                                                Parameter

                                                                Description

                                                                +

                                                                Description

                                                                Resource Specifications

                                                                +

                                                                Resource Specifications

                                                                Select a resource specification from the drop-down list box. The system provides three resource specification options for you to choose from.

                                                                +

                                                                Select a resource specification from the drop-down list box. The system provides three resource specification options for you to choose from.

                                                                Resource specifications involve the following parameters:

                                                                • Executor Memory
                                                                • Executor Cores
                                                                • Executors
                                                                • Driver Cores
                                                                • Driver Memory

                                                                If modified, your modified settings of the items are used.

                                                                Executor Memory

                                                                +

                                                                Executor Memory

                                                                Customize the configuration item based on the selected resource specifications.

                                                                +

                                                                Customize the configuration item based on the selected resource specifications.

                                                                Memory of each Executor. It is recommended that the ratio of Executor CPU cores to Executor memory be 1:4.

                                                                Executor Cores

                                                                +

                                                                Executor Cores

                                                                Number of CPU cores of each Executor applied for by Spark jobs, which determines the capability of each Executor to execute tasks concurrently.

                                                                +

                                                                Number of CPU cores of each Executor applied for by Spark jobs, which determines the capability of each Executor to execute tasks concurrently.

                                                                Executors

                                                                +

                                                                Executors

                                                                Number of Executors applied for by a Spark job

                                                                +

                                                                Number of Executors applied for by a Spark job

                                                                Driver Cores

                                                                +

                                                                Driver Cores

                                                                Number of CPU cores of the driver

                                                                +

                                                                Number of CPU cores of the driver

                                                                Driver Memory

                                                                +

                                                                Driver Memory

                                                                Driver memory size. It is recommended that the ratio of the number of driver CPU cores to the driver memory be 1:4.

                                                                +

                                                                Driver memory size. It is recommended that the ratio of the number of driver CPU cores to the driver memory be 1:4.
                                                                +
                                                                • If you select 3.3.1 for Spark Version, you can configure compute resource specification parameters in Spark Argument(--conf). Note that the configuration priority of Spark Argument(--conf) is higher than that of Resource Specifications(Optional) in Advanced Settings.
                                                                  Table 4 describes the parameter mapping.

                                                                  When configuring compute resource specification parameters in Spark Argument(--conf), you can use the unit M, G, or K. If the unit is not specified, the default unit is byte.

                                                                  +
                                                                  +
                                                                  +
                                                                • Spark 3.3.1 or later includes notes and constraints on the compute resource specifications for jobs. For details, see Table 8.

                                                                  If the compute resource specification is set too high, beyond the resource allocation capacity of the cluster or project, the job may fail to run due to resource request failures.

                                                                  +
                                                                  + +
                                                                  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                  Table 8 Value ranges of compute resources specifications

                                                                  Parameter

                                                                  +

                                                                  Elastic Resource Pool of Standard Edition After Modification

                                                                  +

                                                                  Elastic Resource Pool of Basic Edition

                                                                  +

                                                                  Executor Memory

                                                                  +

                                                                  450 MB to 64 GB

                                                                  +

                                                                  450 MB to 16 GB

                                                                  +

                                                                  Executor Cores

                                                                  +

                                                                  0 to 16

                                                                  +

                                                                  0 to 4

                                                                  +

                                                                  Executors

                                                                  +

                                                                  Unlimited

                                                                  +

                                                                  Unlimited

                                                                  +

                                                                  Driver Cores

                                                                  +

                                                                  0 to 16

                                                                  +

                                                                  0 to 4

                                                                  +

                                                                  Driver Memory

                                                                  +

                                                                  450 MB to 64 GB

                                                                  +

                                                                  450 MB to 16 GB

                                                                  +

                                                                  Job CU Quota

                                                                  +

                                                                  Unlimited

                                                                  +

                                                                  Unlimited

                                                                  +
                                                                  +
                                                                  +
                                                              • Click Execute in the upper right corner of the Spark job editing page.

                                                                After the message "Batch processing job submitted successfully" is displayed, you can view the status and logs of the submitted job on the Spark Jobs page.

                                                                +

                                                                During the Spark job submission process, if the job fails to acquire resources successfully for an extended period, the job status will change to Failed after waiting for approximately 3 hours, indicating that the session has exited. For details about Spark job statuses, see Viewing Basic Information.

                                                                +
                                                                • diff --git a/docs/dli/umn/dli_01_0385.html b/docs/dli/umn/dli_01_0385.html index e9aa7d89f..7166d620e 100644 --- a/docs/dli/umn/dli_01_0385.html +++ b/docs/dli/umn/dli_01_0385.html @@ -1,7 +1,7 @@

                                                                Managing Spark Jobs

                                                                -

                                                                Viewing Basic Information

                                                                On the Overview page, click Spark Jobs to go to the SQL job management page. Alternatively, you can click Job Management > Spark Jobs. The page displays all Spark jobs. If there are a large number of jobs, they will be displayed on multiple pages. DLI allows you to view jobs in all statuses.

                                                                +

                                                                Viewing Basic Information

                                                                On the Overview page, click Spark Jobs to go to the SQL job management page. Alternatively, you can click Job Management > Spark Jobs. The page displays all Spark jobs. If there are a large number of jobs, they will be displayed on multiple pages. DLI allows you to view jobs in all statuses.

                                                                @@ -65,7 +65,7 @@ diff --git a/docs/dli/umn/dli_01_0389.html b/docs/dli/umn/dli_01_0389.html index 39c4e5575..59cef6a30 100644 --- a/docs/dli/umn/dli_01_0389.html +++ b/docs/dli/umn/dli_01_0389.html @@ -1,6 +1,6 @@ -

                                                                Submitting a Flink Job Using DLI

                                                                +

                                                                Submitting a Flink Job on the DLI Management Console

                                                                Table 1 Job management parameters

                                                                Parameter
                                                                Table 1 Spark 3.1.1 dependencies

                                                                Dependency

                                                                +

                                                                Spark 3.3.1 Dependencies

                                                                +
                                                                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
                                                                Table 1 Spark 3.3.1 dependencies

                                                                Dependency

                                                                accessors-smart-1.2.jar

                                                                +

                                                                accessors-smart-2.5.0.jar

                                                                hive-shims-scheduler-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hive-jdbc-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                metrics-graphite-4.1.1.jar

                                                                +

                                                                libfb303-0.9.3.jar

                                                                activation-1.1.1.jar

                                                                +

                                                                activation-1.1.1.jar

                                                                hive-spark-client-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hive-llap-common-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                metrics-jmx-4.1.1.jar

                                                                +

                                                                libthrift-0.14.1-ei-311001.jar

                                                                aggdesigner-algorithm-6.0.jar

                                                                +

                                                                aggdesigner-algorithm-6.0.jar

                                                                hive-standalone-metastore-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hive-metastore-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                metrics-json-4.1.1.jar

                                                                +

                                                                listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar

                                                                aircompressor-0.16.jar

                                                                +

                                                                aircompressor-0.27.jar

                                                                hive-storage-api-2.7.2.jar

                                                                +

                                                                hive-serde-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                metrics-jvm-4.1.1.jar

                                                                +

                                                                log4j-1.2-api-2.17.2.jar

                                                                algebra_2.12-2.0.0-M2.jar

                                                                +

                                                                algebra_2.12-2.0.1.jar

                                                                hive-vector-code-gen-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hive-service-rpc-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                minlog-1.3.0.jar

                                                                +

                                                                log4j-api-2.17.2.jar

                                                                annotations-17.0.0.jar

                                                                +

                                                                annotations-17.0.0.jar

                                                                hk2-api-2.6.1.jar

                                                                +

                                                                hive-shims-0.23-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                netty-3.10.6.Final.jar

                                                                +

                                                                log4j-core-2.17.2.jar

                                                                ant-1.10.9.jar

                                                                +

                                                                antlr4-runtime-4.8.jar

                                                                hk2-locator-2.6.1.jar

                                                                +

                                                                hive-shims-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                netty-all-4.1.86.Final.jar

                                                                +

                                                                log4j-slf4j-impl-2.17.2.jar

                                                                ant-launcher-1.10.9.jar

                                                                +

                                                                antlr-runtime-3.5.2.jar

                                                                hk2-utils-2.6.1.jar

                                                                +

                                                                hive-shims-common-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                netty-buffer-4.1.86.Final.jar

                                                                +

                                                                logging-interceptor-3.14.9.jar

                                                                antlr4-runtime-4.8-1.jar

                                                                +

                                                                aopalliance-1.0.jar

                                                                hppc-0.7.2.jar

                                                                +

                                                                hive-shims-scheduler-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                netty-codec-4.1.86.Final.jar

                                                                +

                                                                luxor-agency-manager_2.12-3.0.0-20250717.081951-800.jar

                                                                antlr-runtime-3.5.2.jar

                                                                +

                                                                aopalliance-repackaged-2.6.1.jar

                                                                httpclient-4.5.6.jar

                                                                +

                                                                hive-spark-client-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                netty-codec-dns-4.1.86.Final.jar

                                                                +

                                                                luxor-cluster-quota-manager-transport_2.12-3.0.0-20250717.201943-802.jar

                                                                aopalliance-1.0.jar

                                                                +

                                                                apiguardian-api-1.1.0.jar

                                                                httpcore-4.4.10.jar

                                                                +

                                                                hive-standalone-metastore-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                netty-codec-haproxy-4.1.86.Final.jar

                                                                +

                                                                luxor-encrypt-3.0.0-20250717.201542-806.jar

                                                                aopalliance-repackaged-2.6.1.jar

                                                                +

                                                                arpack-2.2.1.jar

                                                                istack-commons-runtime-3.0.8.jar

                                                                +

                                                                hive-storage-api-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                netty-codec-http2-4.1.86.Final.jar

                                                                +

                                                                luxor-fs3-3.0.0-20250717.201559-806.jar

                                                                apiguardian-api-1.1.0.jar

                                                                +

                                                                arpack_combined_all-0.1.jar

                                                                ivy-2.5.0.jar

                                                                +

                                                                hive-vector-code-gen-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                netty-codec-http-4.1.86.Final.jar

                                                                +

                                                                luxor-hudi-util-3.0.0-20250717.083632-504.jar

                                                                arpack_combined_all-0.1.jar

                                                                +

                                                                arrow-format-7.0.0.jar

                                                                jackson-annotations-2.13.2.jar

                                                                +

                                                                hk2-api-2.6.1.jar

                                                                netty-codec-memcache-4.1.86.Final.jar

                                                                +

                                                                luxor-obs-fs3-3.0.0-20250717.201607-806.jar

                                                                arrow-format-2.0.0.jar

                                                                +

                                                                arrow-memory-core-7.0.0.jar

                                                                jackson-core-2.13.2.jar

                                                                +

                                                                hk2-locator-2.6.1.jar

                                                                netty-codec-mqtt-4.1.86.Final.jar

                                                                +

                                                                luxor-rpc_2.12-3.0.0-20250717.081915-801.jar

                                                                arrow-memory-core-2.0.0.jar

                                                                +

                                                                arrow-memory-netty-7.0.0.jar

                                                                jackson-core-asl-1.9.13-atlassian-4.jar

                                                                +

                                                                hk2-utils-2.6.1.jar

                                                                netty-codec-redis-4.1.86.Final.jar

                                                                +

                                                                luxor-scc-adapter-3.0.0-20250717.201537-806.jar

                                                                arrow-memory-netty-2.0.0.jar

                                                                +

                                                                arrow-vector-7.0.0.jar

                                                                jackson-databind-2.13.2.2.jar

                                                                +

                                                                hppc-0.7.2.jar

                                                                netty-codec-smtp-4.1.86.Final.jar

                                                                +

                                                                lz4-java-1.8.0.jar

                                                                arrow-vector-2.0.0.jar

                                                                +

                                                                asm-9.3.jar

                                                                jackson-dataformat-yaml-2.13.2.jar

                                                                +

                                                                httpasyncclient-4.1.4.jar

                                                                netty-codec-socks-4.1.86.Final.jar

                                                                +

                                                                manager-hadoop-security-crypter-8.3.1-331.r10.jar

                                                                asm-5.0.4.jar

                                                                +

                                                                audience-annotations-0.12.0.jar

                                                                jackson-datatype-jsr310-2.11.2.jar

                                                                +

                                                                httpclient-4.5.13.jar

                                                                netty-codec-stomp-4.1.86.Final.jar

                                                                +

                                                                mapstruct-1.4.2.Final.jar

                                                                audience-annotations-0.5.0.jar

                                                                +

                                                                avatica-core-1.16.0.jar

                                                                jackson-mapper-asl-1.9.13-atlassian-4.jar

                                                                +

                                                                httpcore-4.4.14.jar

                                                                netty-codec-xml-4.1.86.Final.jar

                                                                +

                                                                memory-0.9.0.jar

                                                                automaton-1.11-8.jar

                                                                +

                                                                avatica-metrics-1.16.0.jar

                                                                jackson-module-jaxb-annotations-2.13.2.jar

                                                                +

                                                                sdk-core-3.1.62.jar

                                                                netty-common-4.1.86.Final.jar

                                                                +

                                                                metrics-core-2.2.0.jar

                                                                avatica-1.22.0.jar

                                                                +

                                                                avatica-server-1.16.0.jar

                                                                jackson-module-scala_2.12-2.13.2.jar

                                                                +

                                                                sdk-csms-3.1.62.jar

                                                                netty-handler-4.1.86.Final.jar

                                                                +

                                                                metrics-core-4.2.7.jar

                                                                avatica-core-1.16.0.jar

                                                                +

                                                                avro-1.11.3.jar

                                                                jaeger-client-1.6.0.jar

                                                                +

                                                                hudi-cli-0.11.0-h0.cbu.dli.300.20250328.r1.jar

                                                                netty-handler-proxy-4.1.86.Final.jar

                                                                +

                                                                metrics-graphite-4.2.7.jar

                                                                avatica-metrics-1.16.0.jar

                                                                +

                                                                avro-ipc-1.11.3.jar

                                                                jaeger-core-1.6.0.jar

                                                                +

                                                                hudi-client-common-0.11.0-h0.cbu.dli.300.20250328.r1.jar

                                                                netty-handler-ssl-ocsp-4.1.86.Final.jar

                                                                +

                                                                metrics-jmx-4.2.7.jar

                                                                avatica-server-1.16.0.jar

                                                                +

                                                                avro-mapred-1.11.3.jar

                                                                jaeger-thrift-1.6.0.jar

                                                                +

                                                                hudi-common-0.11.0-h0.cbu.dli.300.20250328.r1.jar

                                                                netty-resolver-4.1.86.Final.jar

                                                                +

                                                                metrics-json-4.2.7.jar

                                                                avro-1.8.2.jar

                                                                +

                                                                xxx-java-sdk-bundle-1.11.901.jar

                                                                jaeger-tracerresolver-1.6.0.jar

                                                                +

                                                                hudi-hadoop-mr-0.11.0-h0.cbu.dli.300.20250328.r1.jar

                                                                netty-resolver-dns-4.1.86.Final.jar

                                                                +

                                                                metrics-jvm-4.2.7.jar

                                                                avro-ipc-1.8.2.jar

                                                                +

                                                                xxx-keyvault-core-1.0.0.jar

                                                                jakarta.activation-api-1.2.1.jar

                                                                +

                                                                hudi-hbase2.4.x-0.11.0-h0.cbu.dli.300.20250328.r1.jar

                                                                netty-resolver-dns-classes-macos-4.1.86.Final.jar

                                                                +

                                                                minlog-1.3.0.jar

                                                                avro-mapred-1.8.2.jar

                                                                +

                                                                xxx-storage-7.0.1.jar

                                                                jakarta.annotation-api-1.3.5.jar

                                                                +

                                                                hudi-hive-sync-0.11.0-h0.cbu.dli.300.20250328.r1.jar

                                                                netty-resolver-dns-native-macos-4.1.86.Final-osx-aarch_64.jar

                                                                +

                                                                mrs-obs-provider-8.3.1-331.r10.jar

                                                                java-sdk-bundle-1.11.856.jar

                                                                +

                                                                bcpkix-jdk15on-1.69.jar

                                                                jakarta.el-3.0.3.jar

                                                                +

                                                                hudi-spark_2.12-0.11.0-h0.cbu.dli.300.20250328.r1.jar

                                                                netty-resolver-dns-native-macos-4.1.86.Final-osx-x86_64.jar

                                                                +

                                                                native

                                                                base64-2.3.8.jar

                                                                +

                                                                bcprov-jdk15on-1.69.jar

                                                                jakarta.el-api-3.0.3.jar

                                                                +

                                                                hudi-spark3.3.x_2.12-0.11.0-h0.cbu.dli.300.20250328.r1.jar

                                                                netty-transport-4.1.86.Final.jar

                                                                +

                                                                netty-all-4.1.74.Final.jar

                                                                bcpkix-jdk15on-1.69.jar

                                                                +

                                                                bcprov-jdk15on-1.70.jar

                                                                jakarta.inject-2.6.1.jar

                                                                +

                                                                hudi-spark3-common-0.11.0-h0.cbu.dli.300.20250328.r1.jar

                                                                netty-transport-classes-epoll-4.1.86.Final.jar

                                                                +

                                                                netty-buffer-4.1.74.Final.jar

                                                                bcprov-jdk15on-1.69.jar

                                                                +

                                                                bcprov-jdk18on-1.76.jar

                                                                jakarta.servlet-api-4.0.3.jar

                                                                +

                                                                hudi-spark-client-0.11.0-h0.cbu.dli.300.20250328.r1.jar

                                                                netty-transport-classes-kqueue-4.1.86.Final.jar

                                                                +

                                                                netty-codec-4.1.74.Final.jar

                                                                bcutil-jdk15on-1.69.jar

                                                                +

                                                                bcutil-jdk15on-1.69.jar

                                                                jakarta.validation-api-2.0.2.jar

                                                                +

                                                                hudi-spark-common_2.12-0.11.0-h0.cbu.dli.300.20250328.r1.jar

                                                                netty-transport-native-epoll-4.1.86.Final-linux-aarch_64.jar

                                                                +

                                                                netty-common-4.1.74.Final.jar

                                                                bonecp-0.8.0.RELEASE.jar

                                                                +

                                                                blas-2.2.1.jar

                                                                jakarta.ws.rs-api-2.1.6.jar

                                                                +

                                                                hudi-sync-common-0.11.0-h0.cbu.dli.300.20250328.r1.jar

                                                                netty-transport-native-epoll-4.1.86.Final-linux-x86_64.jar

                                                                +

                                                                netty-handler-4.1.74.Final.jar

                                                                breeze_2.12-1.0.jar

                                                                +

                                                                bonecp-0.8.0.RELEASE.jar

                                                                jakarta.xml.bind-api-2.3.2.jar

                                                                +

                                                                hudi-timeline-service-0.11.0-h0.cbu.dli.300.20250328.r1.jar

                                                                netty-transport-native-kqueue-4.1.86.Final-osx-aarch_64.jar

                                                                +

                                                                netty-resolver-4.1.74.Final.jar

                                                                breeze-macros_2.12-1.0.jar

                                                                +

                                                                breeze_2.12-1.2.jar

                                                                jamon-runtime-2.4.1.jar

                                                                +

                                                                hudi-utilities_2.12-0.11.0-h0.cbu.dli.300.20250328.r1.jar

                                                                netty-transport-native-kqueue-4.1.86.Final-osx-x86_64.jar

                                                                +

                                                                netty-tcnative-classes-2.0.48.Final.jar

                                                                caffeine-2.8.1.jar

                                                                +

                                                                breeze-macros_2.12-1.2.jar

                                                                janino-3.0.16.jar

                                                                +

                                                                istack-commons-runtime-3.0.8.jar

                                                                netty-transport-native-unix-common-4.1.86.Final.jar

                                                                +

                                                                netty-transport-4.1.74.Final.jar

                                                                calcite-core-1.22.0.jar

                                                                +

                                                                caffeine-2.8.1.jar

                                                                JavaEWAH-0.3.2.jar

                                                                +

                                                                ivy-2.5.0.jar

                                                                netty-transport-rxtx-4.1.86.Final.jar

                                                                +

                                                                netty-transport-classes-epoll-4.1.74.Final.jar

                                                                calcite-druid-1.19.0.jar

                                                                +

                                                                calcite-core-1.22.0.jar

                                                                java-sdk-core-3.0.12.jar

                                                                +

                                                                j2objc-annotations-2.8.jar

                                                                netty-transport-sctp-4.1.86.Final.jar

                                                                +

                                                                netty-transport-classes-kqueue-4.1.74.Final.jar

                                                                calcite-linq4j-1.22.0.jar

                                                                +

                                                                calcite-linq4j-1.22.0.jar

                                                                javassist-3.25.0-GA.jar

                                                                +

                                                                jackson-annotations-2.15.2.jar

                                                                netty-transport-udt-4.1.86.Final.jar

                                                                +

                                                                netty-transport-native-epoll-4.1.74.Final-linux-aarch_64.jar

                                                                cats-kernel_2.12-2.0.0-M4.jar

                                                                +

                                                                cats-kernel_2.12-2.1.1.jar

                                                                javax.activation-api-1.2.0.jar

                                                                +

                                                                jackson-core-2.15.2.jar

                                                                nimbus-jose-jwt-8.19.jar

                                                                +

                                                                netty-transport-native-epoll-4.1.74.Final-linux-x86_64.jar

                                                                checker-qual-3.5.0.jar

                                                                +

                                                                checker-qual-3.33.0.jar

                                                                javax.annotation-api-1.3.2.jar

                                                                +

                                                                jackson-core-asl-1.9.13-atlassian-4.jar

                                                                objenesis-2.5.1.jar

                                                                +

                                                                netty-transport-native-kqueue-4.1.74.Final-osx-aarch_64.jar

                                                                chill_2.12-0.9.5.jar

                                                                +

                                                                chill_2.12-0.10.0.jar

                                                                javax.inject-1.jar

                                                                +

                                                                jackson-databind-2.15.2.jar

                                                                okhttp-3.14.9.jar

                                                                +

                                                                netty-transport-native-kqueue-4.1.74.Final-osx-x86_64.jar

                                                                chill-java-0.9.5.jar

                                                                +

                                                                chill-java-0.10.0.jar

                                                                javax.jdo-3.2.0-m3.jar

                                                                +

                                                                jackson-dataformat-cbor-2.15.2.jar

                                                                okio-1.17.2.jar

                                                                +

                                                                netty-transport-native-unix-common-4.1.74.Final.jar

                                                                classmate-1.5.1.jar

                                                                +

                                                                commons-cli-1.5.0.jar

                                                                java-xmlbuilder-1.1.jar

                                                                +

                                                                jackson-dataformat-yaml-2.15.2.jar

                                                                opencsv-2.3.jar

                                                                +

                                                                objenesis-3.2.jar

                                                                commons-beanutils-1.9.4.jar

                                                                +

                                                                commons-codec-1.15.jar

                                                                javax.servlet-api-3.1.0.jar

                                                                +

                                                                jackson-datatype-jdk8-2.13.4.jar

                                                                opentelemetry-api-1.16.0.jar

                                                                +

                                                                okhttp-3.14.9.jar

                                                                commons-cli-1.2.jar

                                                                +

                                                                commons-collections-3.2.2.jar

                                                                javax.transaction-api-1.3.jar

                                                                +

                                                                jackson-datatype-jsr310-2.15.2.jar

                                                                opentelemetry-context-1.16.0.jar

                                                                +

                                                                okio-1.14.0.jar

                                                                commons-codec-1.15.jar

                                                                +

                                                                commons-collections4-4.4.jar

                                                                javax.ws.rs-api-2.1.1.jar

                                                                +

                                                                jackson-datatype-threetenbp-2.12.5.jar

                                                                opentelemetry-semconv-1.16.0-alpha.jar

                                                                +

                                                                om-common-8.3.1-331.r10.jar

                                                                commons-collections-3.2.2.jar

                                                                +

                                                                commons-compiler-3.1.9.jar

                                                                javolution-5.5.1.jar

                                                                +

                                                                jackson-jaxrs-base-2.12.7.jar

                                                                opentracing-api-0.33.0.jar

                                                                +

                                                                opencsv-2.3.jar

                                                                commons-compiler-3.0.16.jar

                                                                +

                                                                commons-compress-1.26.0.jar

                                                                jaxb-api-2.2.11.jar

                                                                +

                                                                jackson-jaxrs-json-provider-2.12.7.jar

                                                                opentracing-noop-0.33.0.jar

                                                                +

                                                                opentelemetry-api-1.16.0.jar

                                                                commons-compress-1.21.jar

                                                                +

                                                                commons-configuration2-2.10.1.jar

                                                                jaxb-runtime-2.3.2.jar

                                                                +

                                                                jackson-mapper-asl-1.9.13-atlassian-4.jar

                                                                opentracing-tracerresolver-0.1.8.jar

                                                                +

                                                                opentelemetry-context-1.16.0.jar

                                                                commons-configuration2-2.1.1.jar

                                                                +

                                                                commons-crypto-1.0.0-20191105.jar

                                                                jboss-logging-3.4.1.Final.jar

                                                                +

                                                                jackson-module-jaxb-annotations-2.15.2.jar

                                                                opentracing-util-0.33.0.jar

                                                                +

                                                                opentelemetry-semconv-1.16.0-alpha.jar

                                                                commons-crypto-1.0.0-20191105.jar

                                                                +

                                                                commons-daemon-1.0.13.jar

                                                                jboss-threads-2.3.3.Final.jar

                                                                +

                                                                jackson-module-scala_2.12-2.15.2.jar

                                                                orc-core-1.6.8.jar

                                                                +

                                                                opentracing-api-0.33.0.jar

                                                                commons-daemon-1.0.13.jar

                                                                +

                                                                commons-dbcp-1.4.jar

                                                                jcip-annotations-1.0-1.jar

                                                                +

                                                                jaeger-client-1.6.0.jar

                                                                orc-mapreduce-1.6.8.jar

                                                                +

                                                                opentracing-noop-0.33.0.jar

                                                                commons-dbcp-1.4.jar

                                                                +

                                                                commons-dbcp2-2.6.0.jar

                                                                jcl-over-slf4j-1.7.36.jar

                                                                +

                                                                jaeger-core-1.6.0.jar

                                                                orc-shims-1.6.8.jar

                                                                +

                                                                opentracing-tracerresolver-0.1.8.jar

                                                                commons-dbcp2-2.6.0.jar

                                                                +

                                                                commons-digester-2.1.jar

                                                                jcodings-1.0.57.jar

                                                                +

                                                                jaeger-thrift-1.6.0.jar

                                                                orc-tools-1.6.7-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                opentracing-util-0.33.0.jar

                                                                commons-digester-2.1.jar

                                                                +

                                                                commons-io-2.11.0.jar

                                                                jdo-api-3.2.jar

                                                                +

                                                                jaeger-tracerresolver-1.6.0.jar

                                                                oro-2.0.8.jar

                                                                +

                                                                orc-core-1.6.7-h0.cbu.mrs.331.r10.jar

                                                                commons-httpclient-3.1.jar

                                                                +

                                                                commons-lang-2.6.jar

                                                                jersey-client-2.34.jar

                                                                +

                                                                jakarta.activation-api-1.2.1.jar

                                                                osgi-resource-locator-1.0.3.jar

                                                                +

                                                                orc-mapreduce-1.6.7-h0.cbu.mrs.331.r10.jar

                                                                commons-io-2.8.0.jar

                                                                +

                                                                commons-lang3-3.12.0.jar

                                                                jersey-common-2.34.jar

                                                                +

                                                                jakarta.annotation-api-1.3.5.jar

                                                                paranamer-2.8.jar

                                                                +

                                                                orc-shims-1.6.7-h0.cbu.mrs.331.r10.jar

                                                                commons-lang-2.4.jar

                                                                +

                                                                commons-logging-1.1.3.jar

                                                                jersey-container-servlet-2.34.jar

                                                                +

                                                                jakarta.inject-2.6.1.jar

                                                                parquet-column-1.12.2.jar

                                                                +

                                                                oro-2.0.8.jar

                                                                commons-lang-2.6.jar

                                                                +

                                                                commons-math3-3.6.1.jar

                                                                jersey-container-servlet-core-2.34.jar

                                                                +

                                                                jakarta.servlet-api-4.0.3.jar

                                                                parquet-common-1.12.2.jar

                                                                +

                                                                osgi-resource-locator-1.0.3.jar

                                                                commons-lang3-3.10.jar

                                                                +

                                                                commons-net-3.8.0.jar

                                                                jersey-hk2-2.34.jar

                                                                +

                                                                jakarta.validation-api-2.0.2.jar

                                                                parquet-encoding-1.12.2.jar

                                                                +

                                                                paranamer-2.8.jar

                                                                commons-logging-1.2.jar

                                                                +

                                                                commons-pool-1.5.4.jar

                                                                jersey-server-2.34.jar

                                                                +

                                                                jakarta.ws.rs-api-2.1.6.jar

                                                                parquet-format-structures-1.12.2.jar

                                                                +

                                                                parquet-avro-1.12.2.jar

                                                                commons-math3-3.4.1.jar

                                                                +

                                                                commons-text-1.10.0.jar

                                                                jets3t-0.9.4-1.0.0.jar

                                                                +

                                                                jakarta.xml.bind-api-2.3.2.jar

                                                                parquet-hadoop-1.12.2.jar

                                                                +

                                                                parquet-column-1.12.2.jar

                                                                commons-net-3.1.jar

                                                                +

                                                                commons-validator-1.7.jar

                                                                jettison-1.1.jar

                                                                +

                                                                jamon-runtime-2.4.1.jar

                                                                parquet-hadoop-bundle-1.12.0-ei-2.0.jar

                                                                +

                                                                parquet-common-1.12.2.jar

                                                                commons-pool2-2.6.1.jar

                                                                +

                                                                compress-lzf-1.1.jar

                                                                jetty-http-9.4.41.v20210516.jar

                                                                +

                                                                janino-3.1.9.jar

                                                                parquet-jackson-1.12.2.jar

                                                                +

                                                                parquet-encoding-1.12.2.jar

                                                                commons-text-1.10.0.jar

                                                                +

                                                                core-1.1.2.jar

                                                                jetty-io-9.4.41.v20210516.jar

                                                                +

                                                                JavaEWAH-0.3.2.jar

                                                                postgresql-42.3.5.jar

                                                                +

                                                                parquet-format-structures-1.12.2.jar

                                                                commons-validator-1.7.jar

                                                                +

                                                                curator-client-2.13.0.jar

                                                                jetty-rewrite-9.4.43.v20210629.jar

                                                                +

                                                                javassist-3.25.0-GA.jar

                                                                protobuf-java-2.5.0.jar

                                                                +

                                                                parquet-hadoop-1.12.2.jar

                                                                compress-lzf-1.0.3.jar

                                                                +

                                                                curator-framework-2.13.0.jar

                                                                jetty-security-9.4.41.v20210516.jar

                                                                +

                                                                javax.activation-api-1.2.0.jar

                                                                py4j-0.10.9.jar

                                                                +

                                                                parquet-jackson-1.12.2.jar

                                                                core-1.1.2.jar

                                                                +

                                                                curator-recipes-2.13.0.jar

                                                                jetty-server-9.4.41.v20210516.jar

                                                                +

                                                                javax.annotation-api-1.3.2.jar

                                                                pyrolite-4.30.jar

                                                                +

                                                                pickle-1.2.jar

                                                                curator-client-2.13.0.jar

                                                                +

                                                                datanucleus-api-jdo-4.2.4.jar

                                                                jetty-servlet-9.4.41.v20210516.jar

                                                                +

                                                                javax.el-3.0.1-b12.jar

                                                                re2j-1.1.jar

                                                                +

                                                                protobuf-java-2.5.0.jar

                                                                curator-framework-2.13.0.jar

                                                                +

                                                                datanucleus-core-4.1.17.jar

                                                                jetty-util-9.4.41.v20210516.jar

                                                                +

                                                                javax.inject-1.jar

                                                                RoaringBitmap-0.9.0.jar

                                                                +

                                                                py4j-0.10.9.5.jar

                                                                curator-recipes-2.13.0.jar

                                                                +

                                                                datanucleus-rdbms-fi-4.1.19-302022.jar

                                                                jetty-util-ajax-9.4.41.v20210516.jar

                                                                +

                                                                javax.jdo-3.2.0-m3.jar

                                                                scala-collection-compat_2.12-2.1.1.jar

                                                                +

                                                                re2j-1.1.jar

                                                                datanucleus-api-jdo-4.2.4.jar

                                                                +

                                                                delta-core_2.12-2.3.0-h0.cbu.dli.20231023.r1.jar

                                                                jetty-webapp-9.4.41.v20210516.jar

                                                                +

                                                                javax.servlet-api-3.1.0.jar

                                                                scala-compiler-2.12.16.jar

                                                                +

                                                                RoaringBitmap-0.9.25.jar

                                                                datanucleus-core-4.1.17.jar

                                                                +

                                                                delta-storage-2.3.0-h0.cbu.dli.20231023.r1.jar

                                                                jetty-xml-9.4.41.v20210516.jar

                                                                +

                                                                javax.servlet.jsp-2.3.2.jar

                                                                scala-library-2.12.16.jar

                                                                +

                                                                rocksdbjni-6.20.3.jar

                                                                datanucleus-rdbms-fi-4.1.19-302022.jar

                                                                +

                                                                derby-10.14.2.0.jar

                                                                JLargeArrays-1.5.jar

                                                                +

                                                                javax.servlet.jsp-api-2.3.1.jar

                                                                scala-parser-combinators_2.12-1.1.2.jar

                                                                +

                                                                scala-collection-compat_2.12-2.1.1.jar

                                                                derby-10.14.2.0.jar

                                                                +

                                                                disruptor-3.4.2.jar

                                                                jline-3.21.0.jar

                                                                +

                                                                javax.transaction-api-1.3.jar

                                                                scala-reflect-2.12.16.jar

                                                                +

                                                                scala-compiler-2.12.15.jar

                                                                disruptor-3.4.2.jar

                                                                +

                                                                dli-catalog-client-3.0.0-20250709.014415-186-allDep.jar

                                                                joda-time-2.10.5.jar

                                                                +

                                                                javax.ws.rs-api-2.0.1.jar

                                                                scala-xml_2.12-1.2.0.jar

                                                                +

                                                                scala-library-2.12.15.jar

                                                                dli-catalog-client-2.3.7-20240108.090504-101.jar

                                                                +

                                                                dli-catalog-hive3-client-3.0.0-20250709.014429-186.jar

                                                                jodd-core-3.5.2.jar

                                                                +

                                                                javolution-5.5.1.jar

                                                                secComponentApi-1.1.8.jar

                                                                +

                                                                scala-parser-combinators_2.12-1.1.2.jar

                                                                dli-catalog-hive3-client-2.3.7-20240108.090513-100.jar

                                                                +

                                                                dli-catalog-hive-extension-3.0.0-20250709.014434-186.jar

                                                                jodd-util-6.0.0.jar

                                                                +

                                                                jaxb-api-2.2.11.jar

                                                                serializer-2.7.2.jar

                                                                +

                                                                scala-reflect-2.12.15.jar

                                                                dli-catalog-hive-extension-2.3.7-20240108.090517-100.jar

                                                                +

                                                                dli-lakehouse-storage-obs-3.3.1-3.0.0.dli-SNAPSHOT.jar

                                                                joni-2.1.43.jar

                                                                +

                                                                jaxb-runtime-2.3.2.jar

                                                                shapeless_2.12-2.3.3.jar

                                                                +

                                                                scala-xml_2.12-1.2.0.jar

                                                                dnsjava-2.1.7.jar

                                                                +

                                                                dli-spark-gluten-provider-3.3.1-3.0.0.dli-SNAPSHOT.jar

                                                                jpam-1.1.jar

                                                                +

                                                                jcl-over-slf4j-1.7.36.jar

                                                                shims-0.9.0.jar

                                                                +

                                                                scopt_2.12-3.7.1.jar

                                                                dropwizard-metrics-hadoop-metrics2-reporter-0.1.2.jar

                                                                +

                                                                dli-spark-lakehouse-extension-3.3.1-3.0.0.dli-SNAPSHOT.jar

                                                                jsch-0.1.72.jar

                                                                +

                                                                jcodings-1.0.58.jar

                                                                sketches-core-0.9.0.jar

                                                                +

                                                                secComponentApi-1.1.8.jar

                                                                error_prone_annotations-2.18.0.jar

                                                                +

                                                                dnsjava-2.1.7.jar

                                                                json-20210307.jar

                                                                +

                                                                jdo-api-3.2.jar

                                                                slf4j-api-1.7.30.jar

                                                                +

                                                                serializer-2.7.2.jar

                                                                esdk-obs-java-optimised-3.22.10.2.jar

                                                                +

                                                                dropwizard-metrics-hadoop-metrics2-reporter-0.1.2.jar

                                                                json4s-ast_2.12-3.7.0-M5.jar

                                                                +

                                                                jersey-client-2.36.jar

                                                                slf4j-log4j12-1.7.25.jar

                                                                +

                                                                shapeless_2.12-2.3.7.jar

                                                                esri-geometry-api-2.2.0.jar

                                                                +

                                                                error_prone_annotations-2.18.0.jar

                                                                json4s-core_2.12-3.7.0-M5.jar

                                                                +

                                                                jersey-common-2.36.jar

                                                                snakeyaml-1.30.jar

                                                                +

                                                                shims-0.9.25.jar

                                                                fastutil-6.5.6.jar

                                                                +

                                                                esri-geometry-api-2.2.0.jar

                                                                json4s-jackson_2.12-3.7.0-M5.jar

                                                                +

                                                                jersey-container-servlet-2.36.jar

                                                                snappy-java-1.1.8.2.jar

                                                                +

                                                                sketches-core-0.9.0.jar

                                                                flatbuffers-java-1.9.0.jar

                                                                +

                                                                failureaccess-1.0.1.jar

                                                                json4s-scalap_2.12-3.7.0-M5.jar

                                                                +

                                                                jersey-container-servlet-core-2.36.jar

                                                                spark-avro_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                slf4j-api-1.7.36.jar

                                                                generex-1.0.2.jar

                                                                +

                                                                flatbuffers-java-1.12.0.jar

                                                                json-path-2.4.0.jar

                                                                +

                                                                jersey-hk2-2.36.jar

                                                                spark-catalyst_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                snakeyaml-2.0.jar

                                                                glassfish-corba-omgapi-4.2.2.jar

                                                                +

                                                                glassfish-corba-omgapi-4.2.2.jar

                                                                json-smart-2.3.jar

                                                                +

                                                                jersey-server-2.36.jar

                                                                spark-core_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                snakeyaml-engine-2.6.jar

                                                                gson-2.8.9.jar

                                                                +

                                                                gluten_3.3.1-h0.cbu.dli.20250514.r1.jar

                                                                jsr305-3.0.0.jar

                                                                +

                                                                jettison-1.5.4.jar

                                                                spark-graphx_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                snappy-java-1.1.10.4.jar

                                                                gson-fire-1.8.5.jar

                                                                +

                                                                gson-2.8.9.jar

                                                                JTransforms-3.1.jar

                                                                +

                                                                jetty-rewrite-9.4.53.v20231009.jar

                                                                spark-hive_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                spark-avro_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                guava-14.0.1.jar

                                                                +

                                                                guava-32.1.2-jre.jar

                                                                jul-to-slf4j-1.7.36.jar

                                                                +

                                                                jetty-util-ajax-9.4.54.v20240208.jar

                                                                spark-kubernetes_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                spark-catalyst_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                guice-3.0.jar

                                                                +

                                                                guice-4.0.jar

                                                                kafka-clients-2.8.0.jar

                                                                +

                                                                JLargeArrays-1.5.jar

                                                                spark-kvstore_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                spark-core_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                guice-assistedinject-3.0.jar

                                                                +

                                                                guice-servlet-4.0.jar

                                                                kerb-admin-2.0.2.jar

                                                                +

                                                                jline-3.9.0.jar

                                                                spark-launcher_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                spark-graphx_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                guice-servlet-4.0.jar

                                                                +

                                                                hadoop-annotations-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kerb-client-2.0.2.jar

                                                                +

                                                                joda-time-2.10.13.jar

                                                                spark-mllib_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                spark-hadoop-cloud_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-annotations-3.1.1-h0.cbu.mrs.313.r9.jar

                                                                +

                                                                hadoop-archives-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kerb-common-2.0.2.jar

                                                                +

                                                                jodd-core-3.5.2.jar

                                                                spark-mllib-local_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                spark-hbase_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-archives-3.3.1-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hadoop-auth-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kerb-core-2.0.2.jar

                                                                +

                                                                jodd-util-6.0.0.jar

                                                                spark-network-common_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                spark-hbaseV2_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-auth-3.3.1-h0.cbu.mrs.321.r16.jar

                                                                +

                                                                hadoop-xxx-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kerb-crypto-2.0.2.jar

                                                                +

                                                                joni-2.2.1.jar

                                                                spark-network-shuffle_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                spark-hive_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-3.3.1-h0.cbu.mrs.321.r16.jar

                                                                +

                                                                hadoop-xxx-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kerb-identity-2.0.2.jar

                                                                +

                                                                jpam-1.1.jar

                                                                spark-quota-manager_2.12-3.1.1-2.3.7.dli-SNAPSHOT.jar

                                                                +

                                                                spark-hive-thriftserver_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-client-3.1.1-h0.cbu.mrs.313.r9.jar

                                                                +

                                                                hadoop-client-runtime-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kerb-server-2.0.2.jar

                                                                +

                                                                jsch-0.1.72.jar

                                                                spark-repl_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                spark-kubernetes_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-common-3.3.1-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hadoop-common-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kerb-simplekdc-2.0.2.jar

                                                                +

                                                                json-20210307.jar

                                                                spark-sketch_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                spark-kvstore_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-distcp-3.3.1-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hadoop-distcp-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kerb-util-2.0.2.jar

                                                                +

                                                                json4s-ast_2.12-3.7.0-M11.jar

                                                                spark-sql_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                spark-launcher_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-hdfs-3.3.1-h0.cbu.mrs.321.r16.jar

                                                                +

                                                                hadoop-hdfs-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kerby-asn1-2.0.2.jar

                                                                +

                                                                json4s-core_2.12-3.7.0-M11.jar

                                                                spark-streaming_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                spark-mllib_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-hdfs-client-3.3.1-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hadoop-hdfs-client-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kerby-config-2.0.2.jar

                                                                +

                                                                json4s-jackson_2.12-3.7.0-M11.jar

                                                                spark-tags_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                spark-mllib-local_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-3.1.1-52.1.jar

                                                                +

                                                                hadoop-3.1.1-54.5.jar

                                                                kerby-pkix-2.0.2.jar

                                                                +

                                                                json4s-scalap_2.12-3.7.0-M11.jar

                                                                spark-unsafe_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                spark-network-common_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-mapreduce-client-common-3.1.1-h0.cbu.mrs.313.r9.jar

                                                                +

                                                                hadoop-obscommitter-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kerby-util-2.0.2.jar

                                                                +

                                                                json-path-2.7.0.jar

                                                                spark-uquery_2.12-3.1.1-2.3.7.dli-SNAPSHOT.jar

                                                                +

                                                                spark-network-shuffle_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-mapreduce-client-core-3.1.1-h0.cbu.mrs.313.r9.jar

                                                                +

                                                                hadoop-mapreduce-client-core-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kerby-xdr-2.0.2.jar

                                                                +

                                                                json-smart-2.5.0.jar

                                                                spire_2.12-0.17.0-M1.jar

                                                                +

                                                                spark-quota-manager_2.12-3.3.1-3.0.0.dli-20250717.165119-596.jar

                                                                hadoop-mapreduce-client-jobclient-3.1.1-h0.cbu.mrs.313.r9.jar

                                                                +

                                                                hadoop-mapreduce-client-nativetask-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kotlin-stdlib-1.4.21.jar

                                                                +

                                                                jsr305-3.0.0.jar

                                                                spire-macros_2.12-0.17.0-M1.jar

                                                                +

                                                                spark-repl_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-mapreduce-client-nativetask-3.3.1-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hadoop-plugins-8.3.1-331.r10.jar

                                                                kotlin-stdlib-common-1.4.21.jar

                                                                +

                                                                JTransforms-3.1.jar

                                                                spire-platform_2.12-0.17.0-M1.jar

                                                                +

                                                                spark-sketch_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-registry-3.3.1-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hadoop-registry-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kryo-shaded-4.0.2.jar

                                                                +

                                                                jul-to-slf4j-1.7.36.jar

                                                                spire-util_2.12-0.17.0-M1.jar

                                                                +

                                                                spark-sql_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-shaded-guava-1.1.1.jar

                                                                +

                                                                hadoop-shaded-guava-1.1.1.jar

                                                                kubernetes-client-5.4.1-20211025.jar

                                                                +

                                                                kafka-clients-3.6.1-h0.cbu.mrs.331.r10.jar

                                                                sqlline-1.3.0.jar

                                                                +

                                                                spark-streaming_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-shaded-protobuf_3_7-1.1.1.jar

                                                                +

                                                                hadoop-shaded-protobuf_3_7-1.1.1.jar

                                                                kubernetes-model-admissionregistration-5.4.1-20211025.jar

                                                                +

                                                                kerb-core-2.0.3.jar

                                                                ST4-4.0.4.jar

                                                                +

                                                                spark-tags_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-yarn-api-3.1.1-h0.cbu.mrs.313.r9.jar

                                                                +

                                                                hadoop-yarn-api-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-apiextensions-5.4.1-20211025.jar

                                                                +

                                                                kerby-asn1-2.0.3.jar

                                                                stax2-api-4.2.1.jar

                                                                +

                                                                spark-unsafe_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-yarn-client-3.1.1-h0.cbu.mrs.313.r9.jar

                                                                +

                                                                hadoop-yarn-client-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-apps-5.4.1-20211025.jar

                                                                +

                                                                kerby-pkix-2.0.3.jar

                                                                stax-api-1.0.1.jar

                                                                +

                                                                spark-yarn_2.12-3.3.1-h0.cbu.dli.20250506.300.r2.jar

                                                                hadoop-yarn-registry-3.3.1-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hadoop-yarn-common-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-autoscaling-5.4.1-20211025.jar

                                                                +

                                                                kerby-util-2.0.3.jar

                                                                stream-2.9.6.jar

                                                                +

                                                                spire_2.12-0.17.0.jar

                                                                hbase-asyncfs-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hadoop-yarn-registry-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-batch-5.4.1-20211025.jar

                                                                +

                                                                kotlin-stdlib-1.4.21.jar

                                                                streamingClient

                                                                +

                                                                spire-macros_2.12-0.17.0.jar

                                                                hbase-client-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hadoop-yarn-server-web-proxy-3.3.1-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-certificates-5.4.1-20211025.jar

                                                                +

                                                                kotlin-stdlib-common-1.4.21.jar

                                                                streamingClient010

                                                                +

                                                                spire-platform_2.12-0.17.0.jar

                                                                hbase-common-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-asyncfs-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-common-5.4.1-20211025.jar

                                                                +

                                                                kotlin-stdlib-jdk7-1.8.0.jar

                                                                swagger-annotations-2.2.8.jar

                                                                +

                                                                spire-util_2.12-0.17.0.jar

                                                                hbase-hadoop2-compat-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-client-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-coordination-5.4.1-20211025.jar

                                                                +

                                                                kotlin-stdlib-jdk8-1.8.0.jar

                                                                tephra-api-0.6.0.jar

                                                                +

                                                                sqlline-1.3.0.jar

                                                                hbase-hadoop-compat-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-common-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-core-5.4.1-20211025.jar

                                                                +

                                                                kryo-shaded-4.0.2.jar

                                                                tephra-core-0.6.0.jar

                                                                +

                                                                ST4-4.0.4.jar

                                                                hbase-http-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-hadoop2-compat-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-discovery-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-client-6.7.0.jar

                                                                tephra-hbase-compat-1.0-0.6.0.jar

                                                                +

                                                                stax2-api-4.2.1.jar

                                                                hbase-logging-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-hadoop-compat-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-events-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-client-api-6.7.0.jar

                                                                threetenbp-1.3.5.jar

                                                                +

                                                                stax-api-1.0.1.jar

                                                                hbase-metrics-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-http-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-extensions-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-httpclient-okhttp-6.7.0.jar

                                                                threeten-extra-1.5.0.jar

                                                                +

                                                                stream-2.9.6.jar

                                                                hbase-metrics-api-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-logging-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-flowcontrol-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-admissionregistration-6.7.0.jar

                                                                tink-1.6.0.jar

                                                                +

                                                                streamingClient010

                                                                hbase-procedure-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-mapreduce-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-metrics-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-apiextensions-6.7.0.jar

                                                                token-provider-2.0.2.jar

                                                                +

                                                                super-csv-2.2.0.jar

                                                                hbase-protocol-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-metrics-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-networking-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-apps-6.7.0.jar

                                                                tomcat-servlet-api-8.5.61.jar

                                                                +

                                                                threeten-extra-1.5.0.jar

                                                                hbase-protocol-shaded-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-metrics-api-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-node-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-autoscaling-6.7.0.jar

                                                                transaction-api-1.1.jar

                                                                +

                                                                tink-1.7.0.jar

                                                                hbase-replication-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-procedure-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-policy-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-batch-6.7.0.jar

                                                                twill-api-0.6.0-incubating.jar

                                                                +

                                                                token-server-client-1.0.6-h0.cbu.mrs.331.r10.jar

                                                                hbase-server-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-protocol-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-rbac-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-certificates-6.7.0.jar

                                                                twill-common-0.6.0-incubating.jar

                                                                +

                                                                transaction-api-1.1.jar

                                                                hbase-shaded-gson-4.1.4.jar

                                                                +

                                                                hbase-protocol-shaded-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-scheduling-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-common-6.7.0.jar

                                                                twill-core-0.6.0-incubating.jar

                                                                +

                                                                univocity-parsers-2.9.1.jar

                                                                hbase-shaded-jersey-4.1.4.jar

                                                                +

                                                                hbase-replication-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                kubernetes-model-storageclass-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-coordination-6.7.0.jar

                                                                twill-discovery-api-0.6.0-incubating.jar

                                                                +

                                                                us-common-1.0.76.6.jar

                                                                hbase-shaded-jetty-4.1.4.jar

                                                                +

                                                                hbase-rest-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                leveldbjni-all-1.8-20191105.jar

                                                                +

                                                                kubernetes-model-core-6.7.0.jar

                                                                twill-discovery-core-0.6.0-incubating.jar

                                                                +

                                                                velocity-engine-core-2.3.jar

                                                                hbase-shaded-miscellaneous-4.1.4.jar

                                                                +

                                                                hbase-server-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                libfb303-0.9.3.jar

                                                                +

                                                                kubernetes-model-discovery-6.7.0.jar

                                                                twill-zookeeper-0.6.0-incubating.jar

                                                                +

                                                                websocket-api-9.4.40.v20210413.jar

                                                                hbase-shaded-netty-4.1.4.jar

                                                                +

                                                                hbase-shaded-gson-4.1.4.jar

                                                                libthrift-0.14.1-ei-311001.jar

                                                                +

                                                                kubernetes-model-events-6.7.0.jar

                                                                univocity-parsers-2.9.1.jar

                                                                +

                                                                websocket-client-9.4.40.v20210413.jar

                                                                hbase-shaded-protobuf-4.1.4.jar

                                                                +

                                                                hbase-shaded-jersey-4.1.4.jar

                                                                log4j-1.2.17-cloudera1.jar

                                                                +

                                                                kubernetes-model-extensions-6.7.0.jar

                                                                us-common-1.0.66.jar

                                                                +

                                                                websocket-common-9.4.40.v20210413.jar

                                                                hbase-unsafe-4.1.4.jar

                                                                +

                                                                hbase-shaded-jetty-4.1.4.jar

                                                                log4j-api-2.17.1.jar

                                                                +

                                                                kubernetes-model-flowcontrol-6.7.0.jar

                                                                velocity-1.7.jar

                                                                +

                                                                wildfly-openssl-1.1.3.Final.jar

                                                                hbase-zookeeper-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-shaded-miscellaneous-4.1.4.jar

                                                                log4j-rolling-appender-20131024-2017.jar

                                                                +

                                                                kubernetes-model-gatewayapi-6.7.0.jar

                                                                velocity-engine-core-2.3.jar

                                                                +

                                                                woodstox-core-5.4.0.jar

                                                                hibernate-validator-6.2.5.Final.jar

                                                                +

                                                                hbase-shaded-netty-4.1.4.jar

                                                                logging-interceptor-3.14.9.jar

                                                                +

                                                                kubernetes-model-metrics-6.7.0.jar

                                                                wildfly-client-config-1.0.1.Final.jar

                                                                +

                                                                xalan-2.7.2.jar

                                                                HikariCP-2.6.1.jar

                                                                +

                                                                hbase-shaded-protobuf-4.1.4.jar

                                                                luxor-cluster-quota-manager-transport_2.12-2.3.7-20231226.034700-559.jar

                                                                +

                                                                kubernetes-model-networking-6.7.0.jar

                                                                wildfly-common-1.5.2.Final.jar

                                                                +

                                                                xbean-asm9-shaded-4.20.jar

                                                                hive-classification-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-unsafe-4.1.4.jar

                                                                luxor-encrypt-2.3.7-20231226.034423-1046.jar

                                                                +

                                                                kubernetes-model-node-6.7.0.jar

                                                                woodstox-core-5.4.0.jar

                                                                +

                                                                xercesImpl-2.12.2.jar

                                                                hive-common-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hbase-zookeeper-2.4.14-h0.cbu.mrs.331.r10.jar

                                                                luxor-fs3-2.3.7-20231226.034438-1039.jar

                                                                +

                                                                kubernetes-model-policy-6.7.0.jar

                                                                xalan-2.7.2.jar

                                                                +

                                                                xml-apis-1.4.01.jar

                                                                hive-exec-3.1.0-h0.cbu.mrs.321.r10-core.jar

                                                                +

                                                                HikariCP-2.6.1.jar

                                                                luxor-obs-fs3-2.3.7-20231226.034443-1038.jar

                                                                +

                                                                kubernetes-model-rbac-6.7.0.jar

                                                                xbean-asm7-shaded-4.15.jar

                                                                +

                                                                xz-1.8.jar

                                                                hive-llap-client-2.3.3-ei-12-20210120.005053-2.jar

                                                                +

                                                                hive-beeline-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                luxor-rpc_2.12-2.3.7-20231226.034653-560.jar

                                                                +

                                                                kubernetes-model-resource-6.7.0.jar

                                                                xercesImpl-2.12.2.jar

                                                                +

                                                                zjsonpatch-0.3.0.jar

                                                                hive-llap-common-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hive-classification-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                luxor-scc-adapter-2.3.7-20231226.034418-1045.jar

                                                                +

                                                                kubernetes-model-scheduling-6.7.0.jar

                                                                xml-apis-1.4.01.jar

                                                                +

                                                                zookeeper-3.8.1-h0.cbu.mrs.331.r10.jar

                                                                hive-llap-tez-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hive-cli-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                luxor-transport-2.3.7-20231226.034433-1038.jar

                                                                +

                                                                kubernetes-model-storageclass-6.7.0.jar

                                                                xnio-api-3.8.4.Final.jar

                                                                +

                                                                zookeeper-jute-3.8.1-h0.cbu.mrs.331.r10.jar

                                                                hive-metastore-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hive-common-3.1.0-h0.cbu.dli.20240712.r2.jar

                                                                lz4-java-1.7.1.jar

                                                                +

                                                                lapack-2.2.1.jar

                                                                xz-1.5.jar

                                                                +

                                                                zstd-jni-1.5.2-5.jar

                                                                hive-serde-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hive-exec-3.1.0-h0.cbu.dli.20240712.r2-core.jar

                                                                machinist_2.12-0.6.8.jar

                                                                +

                                                                leveldbjni-all-1.8.jar

                                                                zjsonpatch-0.3.0.jar

                                                                +

                                                                -

                                                                hive-service-rpc-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +
                                                                +
                                                                +
                                                                +

                                                                Spark 3.1.1 Dependencies

                                                                +
                                                                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - - - - - - @@ -1076,778 +2121,778 @@

                                                                Spark 2.4.5 Dependencies

                                                                -
                                                                Table 2 Spark 3.1.1 dependencies

                                                                Dependency

                                                                +

                                                                accessors-smart-1.2.jar

                                                                +

                                                                hive-shims-scheduler-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                metrics-graphite-4.1.1.jar

                                                                +

                                                                activation-1.1.1.jar

                                                                +

                                                                hive-spark-client-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                metrics-jmx-4.1.1.jar

                                                                +

                                                                aggdesigner-algorithm-6.0.jar

                                                                +

                                                                hive-standalone-metastore-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                metrics-json-4.1.1.jar

                                                                +

                                                                aircompressor-0.16.jar

                                                                +

                                                                hive-storage-api-2.7.2.jar

                                                                +

                                                                metrics-jvm-4.1.1.jar

                                                                +

                                                                algebra_2.12-2.0.0-M2.jar

                                                                +

                                                                hive-vector-code-gen-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                minlog-1.3.0.jar

                                                                +

                                                                annotations-17.0.0.jar

                                                                +

                                                                hk2-api-2.6.1.jar

                                                                +

                                                                netty-3.10.6.Final.jar

                                                                +

                                                                ant-1.10.9.jar

                                                                +

                                                                hk2-locator-2.6.1.jar

                                                                +

                                                                netty-all-4.1.86.Final.jar

                                                                +

                                                                ant-launcher-1.10.9.jar

                                                                +

                                                                hk2-utils-2.6.1.jar

                                                                +

                                                                netty-buffer-4.1.86.Final.jar

                                                                +

                                                                antlr4-runtime-4.8-1.jar

                                                                +

                                                                hppc-0.7.2.jar

                                                                +

                                                                netty-codec-4.1.86.Final.jar

                                                                +

                                                                antlr-runtime-3.5.2.jar

                                                                +

                                                                httpclient-4.5.6.jar

                                                                +

                                                                netty-codec-dns-4.1.86.Final.jar

                                                                +

                                                                aopalliance-1.0.jar

                                                                +

                                                                httpcore-4.4.10.jar

                                                                +

                                                                netty-codec-haproxy-4.1.86.Final.jar

                                                                +

                                                                aopalliance-repackaged-2.6.1.jar

                                                                +

                                                                istack-commons-runtime-3.0.8.jar

                                                                +

                                                                netty-codec-http2-4.1.86.Final.jar

                                                                +

                                                                apiguardian-api-1.1.0.jar

                                                                +

                                                                ivy-2.5.0.jar

                                                                +

                                                                netty-codec-http-4.1.86.Final.jar

                                                                +

                                                                arpack_combined_all-0.1.jar

                                                                +

                                                                jackson-annotations-2.13.2.jar

                                                                +

                                                                netty-codec-memcache-4.1.86.Final.jar

                                                                +

                                                                arrow-format-2.0.0.jar

                                                                +

                                                                jackson-core-2.13.2.jar

                                                                +

                                                                netty-codec-mqtt-4.1.86.Final.jar

                                                                +

                                                                arrow-memory-core-2.0.0.jar

                                                                +

                                                                jackson-core-asl-1.9.13-atlassian-4.jar

                                                                +

                                                                netty-codec-redis-4.1.86.Final.jar

                                                                +

                                                                arrow-memory-netty-2.0.0.jar

                                                                +

                                                                jackson-databind-2.13.2.2.jar

                                                                +

                                                                netty-codec-smtp-4.1.86.Final.jar

                                                                +

                                                                arrow-vector-2.0.0.jar

                                                                +

                                                                jackson-dataformat-yaml-2.13.2.jar

                                                                +

                                                                netty-codec-socks-4.1.86.Final.jar

                                                                +

                                                                asm-5.0.4.jar

                                                                +

                                                                jackson-datatype-jsr310-2.11.2.jar

                                                                +

                                                                netty-codec-stomp-4.1.86.Final.jar

                                                                +

                                                                audience-annotations-0.5.0.jar

                                                                +

                                                                jackson-mapper-asl-1.9.13-atlassian-4.jar

                                                                +

                                                                netty-codec-xml-4.1.86.Final.jar

                                                                +

                                                                automaton-1.11-8.jar

                                                                +

                                                                jackson-module-jaxb-annotations-2.13.2.jar

                                                                +

                                                                netty-common-4.1.86.Final.jar

                                                                +

                                                                avatica-1.22.0.jar

                                                                +

                                                                jackson-module-scala_2.12-2.13.2.jar

                                                                +

                                                                netty-handler-4.1.86.Final.jar

                                                                +

                                                                avatica-core-1.16.0.jar

                                                                +

                                                                jaeger-client-1.6.0.jar

                                                                +

                                                                netty-handler-proxy-4.1.86.Final.jar

                                                                +

                                                                avatica-metrics-1.16.0.jar

                                                                +

                                                                jaeger-core-1.6.0.jar

                                                                +

                                                                netty-handler-ssl-ocsp-4.1.86.Final.jar

                                                                +

                                                                avatica-server-1.16.0.jar

                                                                +

                                                                jaeger-thrift-1.6.0.jar

                                                                +

                                                                netty-resolver-4.1.86.Final.jar

                                                                +

                                                                avro-1.8.2.jar

                                                                +

                                                                jaeger-tracerresolver-1.6.0.jar

                                                                +

                                                                netty-resolver-dns-4.1.86.Final.jar

                                                                +

                                                                avro-ipc-1.8.2.jar

                                                                +

                                                                jakarta.activation-api-1.2.1.jar

                                                                +

                                                                netty-resolver-dns-classes-macos-4.1.86.Final.jar

                                                                +

                                                                avro-mapred-1.8.2.jar

                                                                +

                                                                jakarta.annotation-api-1.3.5.jar

                                                                +

                                                                netty-resolver-dns-native-macos-4.1.86.Final-osx-aarch_64.jar

                                                                +

                                                                java-sdk-bundle-1.11.856.jar

                                                                +

                                                                jakarta.el-3.0.3.jar

                                                                +

                                                                netty-resolver-dns-native-macos-4.1.86.Final-osx-x86_64.jar

                                                                +

                                                                base64-2.3.8.jar

                                                                +

                                                                jakarta.el-api-3.0.3.jar

                                                                +

                                                                netty-transport-4.1.86.Final.jar

                                                                +

                                                                bcpkix-jdk15on-1.69.jar

                                                                +

                                                                jakarta.inject-2.6.1.jar

                                                                +

                                                                netty-transport-classes-epoll-4.1.86.Final.jar

                                                                +

                                                                bcprov-jdk15on-1.69.jar

                                                                +

                                                                jakarta.servlet-api-4.0.3.jar

                                                                +

                                                                netty-transport-classes-kqueue-4.1.86.Final.jar

                                                                +

                                                                bcutil-jdk15on-1.69.jar

                                                                +

                                                                jakarta.validation-api-2.0.2.jar

                                                                +

                                                                netty-transport-native-epoll-4.1.86.Final-linux-aarch_64.jar

                                                                +

                                                                bonecp-0.8.0.RELEASE.jar

                                                                +

                                                                jakarta.ws.rs-api-2.1.6.jar

                                                                +

                                                                netty-transport-native-epoll-4.1.86.Final-linux-x86_64.jar

                                                                +

                                                                breeze_2.12-1.0.jar

                                                                +

                                                                jakarta.xml.bind-api-2.3.2.jar

                                                                +

                                                                netty-transport-native-kqueue-4.1.86.Final-osx-aarch_64.jar

                                                                +

                                                                breeze-macros_2.12-1.0.jar

                                                                +

                                                                jamon-runtime-2.4.1.jar

                                                                +

                                                                netty-transport-native-kqueue-4.1.86.Final-osx-x86_64.jar

                                                                +

                                                                caffeine-2.8.1.jar

                                                                +

                                                                janino-3.0.16.jar

                                                                +

                                                                netty-transport-native-unix-common-4.1.86.Final.jar

                                                                +

                                                                calcite-core-1.22.0.jar

                                                                +

                                                                JavaEWAH-0.3.2.jar

                                                                +

                                                                netty-transport-rxtx-4.1.86.Final.jar

                                                                +

                                                                calcite-druid-1.19.0.jar

                                                                +

                                                                java-sdk-core-3.0.12.jar

                                                                +

                                                                netty-transport-sctp-4.1.86.Final.jar

                                                                +

                                                                calcite-linq4j-1.22.0.jar

                                                                +

                                                                javassist-3.25.0-GA.jar

                                                                +

                                                                netty-transport-udt-4.1.86.Final.jar

                                                                +

                                                                cats-kernel_2.12-2.0.0-M4.jar

                                                                +

                                                                javax.activation-api-1.2.0.jar

                                                                +

                                                                nimbus-jose-jwt-8.19.jar

                                                                +

                                                                checker-qual-3.5.0.jar

                                                                +

                                                                javax.annotation-api-1.3.2.jar

                                                                +

                                                                objenesis-2.5.1.jar

                                                                +

                                                                chill_2.12-0.9.5.jar

                                                                +

                                                                javax.inject-1.jar

                                                                +

                                                                okhttp-3.14.9.jar

                                                                +

                                                                chill-java-0.9.5.jar

                                                                +

                                                                javax.jdo-3.2.0-m3.jar

                                                                +

                                                                okio-1.17.2.jar

                                                                +

                                                                classmate-1.5.1.jar

                                                                +

                                                                java-xmlbuilder-1.1.jar

                                                                +

                                                                opencsv-2.3.jar

                                                                +

                                                                commons-beanutils-1.9.4.jar

                                                                +

                                                                javax.servlet-api-3.1.0.jar

                                                                +

                                                                opentelemetry-api-1.16.0.jar

                                                                +

                                                                commons-cli-1.2.jar

                                                                +

                                                                javax.transaction-api-1.3.jar

                                                                +

                                                                opentelemetry-context-1.16.0.jar

                                                                +

                                                                commons-codec-1.15.jar

                                                                +

                                                                javax.ws.rs-api-2.1.1.jar

                                                                +

                                                                opentelemetry-semconv-1.16.0-alpha.jar

                                                                +

                                                                commons-collections-3.2.2.jar

                                                                +

                                                                javolution-5.5.1.jar

                                                                +

                                                                opentracing-api-0.33.0.jar

                                                                +

                                                                commons-compiler-3.0.16.jar

                                                                +

                                                                jaxb-api-2.2.11.jar

                                                                +

                                                                opentracing-noop-0.33.0.jar

                                                                +

                                                                commons-compress-1.21.jar

                                                                +

                                                                jaxb-runtime-2.3.2.jar

                                                                +

                                                                opentracing-tracerresolver-0.1.8.jar

                                                                +

                                                                commons-configuration2-2.1.1.jar

                                                                +

                                                                jboss-logging-3.4.1.Final.jar

                                                                +

                                                                opentracing-util-0.33.0.jar

                                                                +

                                                                commons-crypto-1.0.0-20191105.jar

                                                                +

                                                                jboss-threads-2.3.3.Final.jar

                                                                +

                                                                orc-core-1.6.8.jar

                                                                +

                                                                commons-daemon-1.0.13.jar

                                                                +

                                                                jcip-annotations-1.0-1.jar

                                                                +

                                                                orc-mapreduce-1.6.8.jar

                                                                +

                                                                commons-dbcp-1.4.jar

                                                                +

                                                                jcl-over-slf4j-1.7.36.jar

                                                                +

                                                                orc-shims-1.6.8.jar

                                                                +

                                                                commons-dbcp2-2.6.0.jar

                                                                +

                                                                jcodings-1.0.57.jar

                                                                +

                                                                orc-tools-1.6.7-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                commons-digester-2.1.jar

                                                                +

                                                                jdo-api-3.2.jar

                                                                +

                                                                oro-2.0.8.jar

                                                                +

                                                                commons-httpclient-3.1.jar

                                                                +

                                                                jersey-client-2.34.jar

                                                                +

                                                                osgi-resource-locator-1.0.3.jar

                                                                +

                                                                commons-io-2.8.0.jar

                                                                +

                                                                jersey-common-2.34.jar

                                                                +

                                                                paranamer-2.8.jar

                                                                +

                                                                commons-lang-2.4.jar

                                                                +

                                                                jersey-container-servlet-2.34.jar

                                                                +

                                                                parquet-column-1.12.2.jar

                                                                +

                                                                commons-lang-2.6.jar

                                                                +

                                                                jersey-container-servlet-core-2.34.jar

                                                                +

                                                                parquet-common-1.12.2.jar

                                                                +

                                                                commons-lang3-3.10.jar

                                                                +

                                                                jersey-hk2-2.34.jar

                                                                +

                                                                parquet-encoding-1.12.2.jar

                                                                +

                                                                commons-logging-1.2.jar

                                                                +

                                                                jersey-server-2.34.jar

                                                                +

                                                                parquet-format-structures-1.12.2.jar

                                                                +

                                                                commons-math3-3.4.1.jar

                                                                +

                                                                jets3t-0.9.4-1.0.0.jar

                                                                +

                                                                parquet-hadoop-1.12.2.jar

                                                                +

                                                                commons-net-3.1.jar

                                                                +

                                                                jettison-1.1.jar

                                                                +

                                                                parquet-hadoop-bundle-1.12.0-ei-2.0.jar

                                                                +

                                                                commons-pool2-2.6.1.jar

                                                                +

                                                                jetty-http-9.4.41.v20210516.jar

                                                                +

                                                                parquet-jackson-1.12.2.jar

                                                                +

                                                                commons-text-1.10.0.jar

                                                                +

                                                                jetty-io-9.4.41.v20210516.jar

                                                                +

                                                                postgresql-42.3.5.jar

                                                                +

                                                                commons-validator-1.7.jar

                                                                +

                                                                jetty-rewrite-9.4.43.v20210629.jar

                                                                +

                                                                protobuf-java-2.5.0.jar

                                                                +

                                                                compress-lzf-1.0.3.jar

                                                                +

                                                                jetty-security-9.4.41.v20210516.jar

                                                                +

                                                                py4j-0.10.9.jar

                                                                +

                                                                core-1.1.2.jar

                                                                +

                                                                jetty-server-9.4.41.v20210516.jar

                                                                +

                                                                pyrolite-4.30.jar

                                                                +

                                                                curator-client-2.13.0.jar

                                                                +

                                                                jetty-servlet-9.4.41.v20210516.jar

                                                                +

                                                                re2j-1.1.jar

                                                                +

                                                                curator-framework-2.13.0.jar

                                                                +

                                                                jetty-util-9.4.41.v20210516.jar

                                                                +

                                                                RoaringBitmap-0.9.0.jar

                                                                +

                                                                curator-recipes-2.13.0.jar

                                                                +

                                                                jetty-util-ajax-9.4.41.v20210516.jar

                                                                +

                                                                scala-collection-compat_2.12-2.1.1.jar

                                                                +

                                                                datanucleus-api-jdo-4.2.4.jar

                                                                +

                                                                jetty-webapp-9.4.41.v20210516.jar

                                                                +

                                                                scala-compiler-2.12.16.jar

                                                                +

                                                                datanucleus-core-4.1.17.jar

                                                                +

                                                                jetty-xml-9.4.41.v20210516.jar

                                                                +

                                                                scala-library-2.12.16.jar

                                                                +

                                                                datanucleus-rdbms-fi-4.1.19-302022.jar

                                                                +

                                                                JLargeArrays-1.5.jar

                                                                +

                                                                scala-parser-combinators_2.12-1.1.2.jar

                                                                +

                                                                derby-10.14.2.0.jar

                                                                +

                                                                jline-3.21.0.jar

                                                                +

                                                                scala-reflect-2.12.16.jar

                                                                +

                                                                disruptor-3.4.2.jar

                                                                +

                                                                joda-time-2.10.5.jar

                                                                +

                                                                scala-xml_2.12-1.2.0.jar

                                                                +

                                                                dli-catalog-client-2.3.7-20240108.090504-101.jar

                                                                +

                                                                jodd-core-3.5.2.jar

                                                                +

                                                                secComponentApi-1.1.8.jar

                                                                +

                                                                dli-catalog-hive3-client-2.3.7-20240108.090513-100.jar

                                                                +

                                                                jodd-util-6.0.0.jar

                                                                +

                                                                serializer-2.7.2.jar

                                                                +

                                                                dli-catalog-hive-extension-2.3.7-20240108.090517-100.jar

                                                                +

                                                                joni-2.1.43.jar

                                                                +

                                                                shapeless_2.12-2.3.3.jar

                                                                +

                                                                dnsjava-2.1.7.jar

                                                                +

                                                                jpam-1.1.jar

                                                                +

                                                                shims-0.9.0.jar

                                                                +

                                                                dropwizard-metrics-hadoop-metrics2-reporter-0.1.2.jar

                                                                +

                                                                jsch-0.1.72.jar

                                                                +

                                                                sketches-core-0.9.0.jar

                                                                +

                                                                error_prone_annotations-2.18.0.jar

                                                                +

                                                                json-20210307.jar

                                                                +

                                                                slf4j-api-1.7.30.jar

                                                                +

                                                                esdk-obs-java-optimized-3.22.10.2.jar

                                                                +

                                                                json4s-ast_2.12-3.7.0-M5.jar

                                                                +

                                                                slf4j-log4j12-1.7.25.jar

                                                                +

                                                                esri-geometry-api-2.2.0.jar

                                                                +

                                                                json4s-core_2.12-3.7.0-M5.jar

                                                                +

                                                                snakeyaml-1.30.jar

                                                                +

                                                                fastutil-6.5.6.jar

                                                                +

                                                                json4s-jackson_2.12-3.7.0-M5.jar

                                                                +

                                                                snappy-java-1.1.8.2.jar

                                                                +

                                                                flatbuffers-java-1.9.0.jar

                                                                +

                                                                json4s-scalap_2.12-3.7.0-M5.jar

                                                                +

                                                                spark-avro_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                generex-1.0.2.jar

                                                                +

                                                                json-path-2.4.0.jar

                                                                +

                                                                spark-catalyst_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                glassfish-corba-omgapi-4.2.2.jar

                                                                +

                                                                json-smart-2.3.jar

                                                                +

                                                                spark-core_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                gson-2.8.9.jar

                                                                +

                                                                jsr305-3.0.0.jar

                                                                +

                                                                spark-graphx_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                gson-fire-1.8.5.jar

                                                                +

                                                                JTransforms-3.1.jar

                                                                +

                                                                spark-hive_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                guava-14.0.1.jar

                                                                +

                                                                jul-to-slf4j-1.7.36.jar

                                                                +

                                                                spark-kubernetes_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                guice-3.0.jar

                                                                +

                                                                kafka-clients-2.8.0.jar

                                                                +

                                                                spark-kvstore_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                guice-assistedinject-3.0.jar

                                                                +

                                                                kerb-admin-2.0.2.jar

                                                                +

                                                                spark-launcher_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                guice-servlet-4.0.jar

                                                                +

                                                                kerb-client-2.0.2.jar

                                                                +

                                                                spark-mllib_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                hadoop-annotations-3.1.1-h0.cbu.mrs.313.r9.jar

                                                                +

                                                                kerb-common-2.0.2.jar

                                                                +

                                                                spark-mllib-local_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                hadoop-archives-3.3.1-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kerb-core-2.0.2.jar

                                                                +

                                                                spark-network-common_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                hadoop-auth-3.3.1-h0.cbu.mrs.321.r16.jar

                                                                +

                                                                kerb-crypto-2.0.2.jar

                                                                +

                                                                spark-network-shuffle_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                hadoop-3.3.1-h0.cbu.mrs.321.r16.jar

                                                                +

                                                                kerb-identity-2.0.2.jar

                                                                +

                                                                spark-quota-manager_2.12-3.1.1-2.3.7.dli-SNAPSHOT.jar

                                                                +

                                                                hadoop-client-3.1.1-h0.cbu.mrs.313.r9.jar

                                                                +

                                                                kerb-server-2.0.2.jar

                                                                +

                                                                spark-repl_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                hadoop-common-3.3.1-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kerb-simplekdc-2.0.2.jar

                                                                +

                                                                spark-sketch_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                hadoop-distcp-3.3.1-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kerb-util-2.0.2.jar

                                                                +

                                                                spark-sql_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                hadoop-hdfs-3.3.1-h0.cbu.mrs.321.r16.jar

                                                                +

                                                                kerby-asn1-2.0.2.jar

                                                                +

                                                                spark-streaming_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                hadoop-hdfs-client-3.3.1-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kerby-config-2.0.2.jar

                                                                +

                                                                spark-tags_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                hadoop-3.1.1-52.1.jar

                                                                +

                                                                kerby-pkix-2.0.2.jar

                                                                +

                                                                spark-unsafe_2.12-3.1.1-h1.cbu.dli.20230607.r1.jar

                                                                +

                                                                hadoop-mapreduce-client-common-3.1.1-h0.cbu.mrs.313.r9.jar

                                                                +

                                                                kerby-util-2.0.2.jar

                                                                +

                                                                spark-uquery_2.12-3.1.1-2.3.7.dli-SNAPSHOT.jar

                                                                +

                                                                hadoop-mapreduce-client-core-3.1.1-h0.cbu.mrs.313.r9.jar

                                                                +

                                                                kerby-xdr-2.0.2.jar

                                                                +

                                                                spire_2.12-0.17.0-M1.jar

                                                                +

                                                                hadoop-mapreduce-client-jobclient-3.1.1-h0.cbu.mrs.313.r9.jar

                                                                +

                                                                kotlin-stdlib-1.4.21.jar

                                                                +

                                                                spire-macros_2.12-0.17.0-M1.jar

                                                                +

                                                                hadoop-mapreduce-client-nativetask-3.3.1-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kotlin-stdlib-common-1.4.21.jar

                                                                +

                                                                spire-platform_2.12-0.17.0-M1.jar

                                                                +

                                                                hadoop-registry-3.3.1-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kryo-shaded-4.0.2.jar

                                                                +

                                                                spire-util_2.12-0.17.0-M1.jar

                                                                +

                                                                hadoop-shaded-guava-1.1.1.jar

                                                                +

                                                                kubernetes-client-5.4.1-20211025.jar

                                                                +

                                                                sqlline-1.3.0.jar

                                                                +

                                                                hadoop-shaded-protobuf_3_7-1.1.1.jar

                                                                +

                                                                kubernetes-model-admissionregistration-5.4.1-20211025.jar

                                                                +

                                                                ST4-4.0.4.jar

                                                                +

                                                                hadoop-yarn-api-3.1.1-h0.cbu.mrs.313.r9.jar

                                                                +

                                                                kubernetes-model-apiextensions-5.4.1-20211025.jar

                                                                +

                                                                stax2-api-4.2.1.jar

                                                                +

                                                                hadoop-yarn-client-3.1.1-h0.cbu.mrs.313.r9.jar

                                                                +

                                                                kubernetes-model-apps-5.4.1-20211025.jar

                                                                +

                                                                stax-api-1.0.1.jar

                                                                +

                                                                hadoop-yarn-registry-3.3.1-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-autoscaling-5.4.1-20211025.jar

                                                                +

                                                                stream-2.9.6.jar

                                                                +

                                                                hbase-asyncfs-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-batch-5.4.1-20211025.jar

                                                                +

                                                                streamingClient

                                                                +

                                                                hbase-client-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-certificates-5.4.1-20211025.jar

                                                                +

                                                                streamingClient010

                                                                +

                                                                hbase-common-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-common-5.4.1-20211025.jar

                                                                +

                                                                swagger-annotations-2.2.8.jar

                                                                +

                                                                hbase-hadoop2-compat-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-coordination-5.4.1-20211025.jar

                                                                +

                                                                tephra-api-0.6.0.jar

                                                                +

                                                                hbase-hadoop-compat-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-core-5.4.1-20211025.jar

                                                                +

                                                                tephra-core-0.6.0.jar

                                                                +

                                                                hbase-http-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-discovery-5.4.1-20211025.jar

                                                                +

                                                                tephra-hbase-compat-1.0-0.6.0.jar

                                                                +

                                                                hbase-logging-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-events-5.4.1-20211025.jar

                                                                +

                                                                threetenbp-1.3.5.jar

                                                                +

                                                                hbase-metrics-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-extensions-5.4.1-20211025.jar

                                                                +

                                                                threeten-extra-1.5.0.jar

                                                                +

                                                                hbase-metrics-api-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-flowcontrol-5.4.1-20211025.jar

                                                                +

                                                                tink-1.6.0.jar

                                                                +

                                                                hbase-procedure-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-metrics-5.4.1-20211025.jar

                                                                +

                                                                token-provider-2.0.2.jar

                                                                +

                                                                hbase-protocol-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-networking-5.4.1-20211025.jar

                                                                +

                                                                tomcat-servlet-api-8.5.61.jar

                                                                +

                                                                hbase-protocol-shaded-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-node-5.4.1-20211025.jar

                                                                +

                                                                transaction-api-1.1.jar

                                                                +

                                                                hbase-replication-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-policy-5.4.1-20211025.jar

                                                                +

                                                                twill-api-0.6.0-incubating.jar

                                                                +

                                                                hbase-server-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                kubernetes-model-rbac-5.4.1-20211025.jar

                                                                +

                                                                twill-common-0.6.0-incubating.jar

                                                                +

                                                                hbase-shaded-gson-4.1.4.jar

                                                                +

                                                                kubernetes-model-scheduling-5.4.1-20211025.jar

                                                                +

                                                                twill-core-0.6.0-incubating.jar

                                                                +

                                                                hbase-shaded-jersey-4.1.4.jar

                                                                +

                                                                kubernetes-model-storageclass-5.4.1-20211025.jar

                                                                +

                                                                twill-discovery-api-0.6.0-incubating.jar

                                                                +

                                                                hbase-shaded-jetty-4.1.4.jar

                                                                +

                                                                leveldbjni-all-1.8-20191105.jar

                                                                +

                                                                twill-discovery-core-0.6.0-incubating.jar

                                                                +

                                                                hbase-shaded-miscellaneous-4.1.4.jar

                                                                +

                                                                libfb303-0.9.3.jar

                                                                +

                                                                twill-zookeeper-0.6.0-incubating.jar

                                                                +

                                                                hbase-shaded-netty-4.1.4.jar

                                                                +

                                                                libthrift-0.14.1-ei-311001.jar

                                                                +

                                                                univocity-parsers-2.9.1.jar

                                                                +

                                                                hbase-shaded-protobuf-4.1.4.jar

                                                                +

                                                                log4j-1.2.17-cloudera1.jar

                                                                +

                                                                us-common-1.0.66.jar

                                                                +

                                                                hbase-unsafe-4.1.4.jar

                                                                +

                                                                log4j-api-2.17.1.jar

                                                                +

                                                                velocity-1.7.jar

                                                                +

                                                                hbase-zookeeper-2.4.14-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                log4j-rolling-appender-20131024-2017.jar

                                                                +

                                                                velocity-engine-core-2.3.jar

                                                                +

                                                                hibernate-validator-6.2.5.Final.jar

                                                                +

                                                                logging-interceptor-3.14.9.jar

                                                                +

                                                                wildfly-client-config-1.0.1.Final.jar

                                                                +

                                                                HikariCP-2.6.1.jar

                                                                +

                                                                luxor-cluster-quota-manager-transport_2.12-2.3.7-20231226.034700-559.jar

                                                                +

                                                                wildfly-common-1.5.2.Final.jar

                                                                +

                                                                hive-classification-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                luxor-encrypt-2.3.7-20231226.034423-1046.jar

                                                                +

                                                                woodstox-core-5.4.0.jar

                                                                +

                                                                hive-common-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                luxor-fs3-2.3.7-20231226.034438-1039.jar

                                                                +

                                                                xalan-2.7.2.jar

                                                                +

                                                                hive-exec-3.1.0-h0.cbu.mrs.321.r10-core.jar

                                                                +

                                                                luxor-obs-fs3-2.3.7-20231226.034443-1038.jar

                                                                +

                                                                xbean-asm7-shaded-4.15.jar

                                                                +

                                                                hive-llap-client-2.3.3-ei-12-20210120.005053-2.jar

                                                                +

                                                                luxor-rpc_2.12-2.3.7-20231226.034653-560.jar

                                                                +

                                                                xercesImpl-2.12.2.jar

                                                                +

                                                                hive-llap-common-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                luxor-scc-adapter-2.3.7-20231226.034418-1045.jar

                                                                +

                                                                xml-apis-1.4.01.jar

                                                                +

                                                                hive-llap-tez-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                luxor-transport-2.3.7-20231226.034433-1038.jar

                                                                +

                                                                xnio-api-3.8.4.Final.jar

                                                                +

                                                                hive-metastore-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                lz4-java-1.7.1.jar

                                                                +

                                                                xz-1.5.jar

                                                                +

                                                                hive-serde-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                machinist_2.12-0.6.8.jar

                                                                +

                                                                zjsonpatch-0.3.0.jar

                                                                +

                                                                hive-service-rpc-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                macro-compat_2.12-1.1.1.jar

                                                                +

                                                                macro-compat_2.12-1.1.1.jar

                                                                zookeeper-3.5.6-ei-302002.jar

                                                                +

                                                                zookeeper-3.5.6-ei-302002.jar

                                                                hive-shims-0.23-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hive-shims-0.23-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                memarts-ccsdk-1.0.jar

                                                                +

                                                                memarts-ccsdk-1.0.jar

                                                                zookeeper-jute-3.5.6-ei-302002.jar

                                                                +

                                                                zookeeper-jute-3.5.6-ei-302002.jar

                                                                hive-shims-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hive-shims-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                memory-0.9.0.jar

                                                                +

                                                                memory-0.9.0.jar

                                                                zstd-jni-1.4.9-1.jar

                                                                +

                                                                zstd-jni-1.4.9-1.jar

                                                                hive-shims-common-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                +

                                                                hive-shims-common-3.1.0-h0.cbu.mrs.321.r10.jar

                                                                metrics-core-4.1.1.jar

                                                                +

                                                                metrics-core-4.1.1.jar

                                                                -

                                                                +

                                                                -
                                                                Table 2 Spark 2.4.5 dependencies

                                                                Dependency

                                                                +
                                                                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -1855,701 +2900,701 @@

                                                                Spark 2.3.2 Dependencies

                                                                -
                                                                Table 3 Spark 2.4.5 dependencies

                                                                Dependency

                                                                JavaEWAH-1.1.7.jar

                                                                +

                                                                JavaEWAH-1.1.7.jar

                                                                httpclient-4.5.6.jar

                                                                +

                                                                httpclient-4.5.6.jar

                                                                lucene-queryparser-7.7.2.jar

                                                                +

                                                                lucene-queryparser-7.7.2.jar

                                                                RoaringBitmap-0.7.45.jar

                                                                +

                                                                RoaringBitmap-0.7.45.jar

                                                                httpcore-4.4.10.jar

                                                                +

                                                                httpcore-4.4.10.jar

                                                                lucene-sandbox-7.7.2.jar

                                                                +

                                                                lucene-sandbox-7.7.2.jar

                                                                ST4-4.3.1.jar

                                                                +

                                                                ST4-4.3.1.jar

                                                                ivy-2.4.0.jar

                                                                +

                                                                ivy-2.4.0.jar

                                                                luxor-encrypt-2.0.0-20220623.010726-213.jar

                                                                +

                                                                luxor-encrypt-2.0.0-20220623.010726-213.jar

                                                                accessors-smart-1.2.jar

                                                                +

                                                                accessors-smart-1.2.jar

                                                                jackson-annotations-2.11.4.jar

                                                                +

                                                                jackson-annotations-2.11.4.jar

                                                                luxor-fs3-2.0.0-20220623.010750-209.jar

                                                                +

                                                                luxor-fs3-2.0.0-20220623.010750-209.jar

                                                                activation-1.1.1.jar

                                                                +

                                                                activation-1.1.1.jar

                                                                jackson-core-2.11.4.jar

                                                                +

                                                                jackson-core-2.11.4.jar

                                                                luxor-obs-fs3-2.0.0-20220623.010756-209.jar

                                                                +

                                                                luxor-obs-fs3-2.0.0-20220623.010756-209.jar

                                                                aircompressor-0.16.jar

                                                                +

                                                                aircompressor-0.16.jar

                                                                jackson-core-asl-1.9.13-atlassian-4.jar

                                                                +

                                                                jackson-core-asl-1.9.13-atlassian-4.jar

                                                                luxor-rpc_2.11-2.0.0-20220623.010737-182.jar

                                                                +

                                                                luxor-rpc_2.11-2.0.0-20220623.010737-182.jar

                                                                alluxio-2.3.1-luxor-SNAPSHOT-client.jar

                                                                +

                                                                alluxio-2.3.1-luxor-SNAPSHOT-client.jar

                                                                jackson-databind-2.11.4.jar

                                                                +

                                                                jackson-databind-2.11.4.jar

                                                                luxor-transport-2.0.0-20220623.010744-71.jar

                                                                +

                                                                luxor-transport-2.0.0-20220623.010744-71.jar

                                                                annotations-17.0.0.jar

                                                                +

                                                                annotations-17.0.0.jar

                                                                jackson-dataformat-yaml-2.11.4.jar

                                                                +

                                                                jackson-dataformat-yaml-2.11.4.jar

                                                                lz4-java-1.7.1.jar

                                                                +

                                                                lz4-java-1.7.1.jar

                                                                antlr-2.7.7.jar

                                                                +

                                                                antlr-2.7.7.jar

                                                                jackson-datatype-jsr310-2.11.2.jar

                                                                +

                                                                jackson-datatype-jsr310-2.11.2.jar

                                                                machinist_2.11-0.6.1.jar

                                                                +

                                                                machinist_2.11-0.6.1.jar

                                                                antlr-runtime-3.4.jar

                                                                +

                                                                antlr-runtime-3.4.jar

                                                                jackson-jaxrs-base-2.10.3.jar

                                                                +

                                                                jackson-jaxrs-base-2.10.3.jar

                                                                macro-compat_2.11-1.1.1.jar

                                                                +

                                                                macro-compat_2.11-1.1.1.jar

                                                                antlr4-runtime-4.8-1.jar

                                                                +

                                                                antlr4-runtime-4.8-1.jar

                                                                jackson-jaxrs-json-provider-2.10.3.jar

                                                                +

                                                                jackson-jaxrs-json-provider-2.10.3.jar

                                                                metrics-core-3.1.5.jar

                                                                +

                                                                metrics-core-3.1.5.jar

                                                                aopalliance-1.0.jar

                                                                +

                                                                aopalliance-1.0.jar

                                                                jackson-mapper-asl-1.9.13-atlassian-4.jar

                                                                +

                                                                jackson-mapper-asl-1.9.13-atlassian-4.jar

                                                                metrics-graphite-3.1.5.jar

                                                                +

                                                                metrics-graphite-3.1.5.jar

                                                                aopalliance-repackaged-2.4.0-b34.jar

                                                                +

                                                                aopalliance-repackaged-2.4.0-b34.jar

                                                                jackson-module-jaxb-annotations-2.10.3.jar

                                                                +

                                                                jackson-module-jaxb-annotations-2.10.3.jar

                                                                metrics-jmx-4.1.12.1.jar

                                                                +

                                                                metrics-jmx-4.1.12.1.jar

                                                                apache-log4j-extras-1.2.17.jar

                                                                +

                                                                apache-log4j-extras-1.2.17.jar

                                                                jackson-module-paranamer-2.11.4.jar

                                                                +

                                                                jackson-module-paranamer-2.11.4.jar

                                                                metrics-json-3.1.5.jar

                                                                +

                                                                metrics-json-3.1.5.jar

                                                                arpack_combined_all-0.1.jar

                                                                +

                                                                arpack_combined_all-0.1.jar

                                                                jackson-module-scala_2.11-2.11.4.jar

                                                                +

                                                                jackson-module-scala_2.11-2.11.4.jar

                                                                metrics-jvm-3.1.5.jar

                                                                +

                                                                metrics-jvm-3.1.5.jar

                                                                arrow-format-0.12.0.jar

                                                                +

                                                                arrow-format-0.12.0.jar

                                                                jakarta.activation-api-1.2.1.jar

                                                                +

                                                                jakarta.activation-api-1.2.1.jar

                                                                minlog-1.3.0.jar

                                                                +

                                                                minlog-1.3.0.jar

                                                                arrow-memory-0.12.0.jar

                                                                +

                                                                arrow-memory-0.12.0.jar

                                                                jakarta.xml.bind-api-2.3.2.jar

                                                                +

                                                                jakarta.xml.bind-api-2.3.2.jar

                                                                mssql-jdbc-6.2.1.jre7.jar

                                                                +

                                                                mssql-jdbc-6.2.1.jre7.jar

                                                                arrow-vector-0.12.0.jar

                                                                +

                                                                arrow-vector-0.12.0.jar

                                                                janino-3.0.9.jar

                                                                +

                                                                janino-3.0.9.jar

                                                                netty-all-4.1.51.Final.jar

                                                                +

                                                                netty-all-4.1.51.Final.jar

                                                                asm-5.0.4.jar

                                                                +

                                                                asm-5.0.4.jar

                                                                java-util-1.9.0.jar

                                                                +

                                                                java-util-1.9.0.jar

                                                                nimbus-jose-jwt-8.19.jar

                                                                +

                                                                nimbus-jose-jwt-8.19.jar

                                                                audience-annotations-0.5.0.jar

                                                                +

                                                                audience-annotations-0.5.0.jar

                                                                java-xmlbuilder-1.1.jar

                                                                +

                                                                java-xmlbuilder-1.1.jar

                                                                objenesis-2.5.1.jar

                                                                +

                                                                objenesis-2.5.1.jar

                                                                automaton-1.11-8.jar

                                                                +

                                                                automaton-1.11-8.jar

                                                                javassist-3.18.1-GA.jar

                                                                +

                                                                javassist-3.18.1-GA.jar

                                                                okhttp-3.14.9.jar

                                                                +

                                                                okhttp-3.14.9.jar

                                                                avro-1.8.2.jar

                                                                +

                                                                avro-1.8.2.jar

                                                                javax.annotation-api-1.2.jar

                                                                +

                                                                javax.annotation-api-1.2.jar

                                                                okio-1.17.2.jar

                                                                +

                                                                okio-1.17.2.jar

                                                                avro-ipc-1.8.2.jar

                                                                +

                                                                avro-ipc-1.8.2.jar

                                                                javax.inject-1.jar

                                                                +

                                                                javax.inject-1.jar

                                                                opencsv-2.3.jar

                                                                +

                                                                opencsv-2.3.jar

                                                                avro-mapred-1.8.2.jar

                                                                +

                                                                avro-mapred-1.8.2.jar

                                                                javax.inject-2.4.0-b34.jar

                                                                +

                                                                javax.inject-2.4.0-b34.jar

                                                                opencsv-4.6.jar

                                                                +

                                                                opencsv-4.6.jar

                                                                java-sdk-bundle-1.11.856.jar

                                                                +

                                                                java-sdk-bundle-1.11.856.jar

                                                                javax.servlet-api-3.1.0.jar

                                                                +

                                                                javax.servlet-api-3.1.0.jar

                                                                opencv-4.3.0-2.jar

                                                                +

                                                                opencv-4.3.0-2.jar

                                                                base64-2.3.8.jar

                                                                +

                                                                base64-2.3.8.jar

                                                                javax.ws.rs-api-2.0.1.jar

                                                                +

                                                                javax.ws.rs-api-2.0.1.jar

                                                                orc-core-1.6.8-nohive.jar

                                                                +

                                                                orc-core-1.6.8-nohive.jar

                                                                bcpkix-jdk15on-1.66.jar

                                                                +

                                                                bcpkix-jdk15on-1.66.jar

                                                                javolution-5.3.1.jar

                                                                +

                                                                javolution-5.3.1.jar

                                                                orc-mapreduce-1.6.8-nohive.jar

                                                                +

                                                                orc-mapreduce-1.6.8-nohive.jar

                                                                bcprov-jdk15on-1.67.jar

                                                                +

                                                                bcprov-jdk15on-1.67.jar

                                                                jaxb-api-2.2.11.jar

                                                                +

                                                                jaxb-api-2.2.11.jar

                                                                orc-shims-1.6.8.jar

                                                                +

                                                                orc-shims-1.6.8.jar

                                                                bonecp-0.8.0.RELEASE.jar

                                                                +

                                                                bonecp-0.8.0.RELEASE.jar

                                                                jcip-annotations-1.0-1.jar

                                                                +

                                                                jcip-annotations-1.0-1.jar

                                                                oro-2.0.8.jar

                                                                +

                                                                oro-2.0.8.jar

                                                                breeze-macros_2.11-0.13.2.jar

                                                                +

                                                                breeze-macros_2.11-0.13.2.jar

                                                                jcl-over-slf4j-1.7.30.jar

                                                                +

                                                                jcl-over-slf4j-1.7.30.jar

                                                                osgi-resource-locator-1.0.1.jar

                                                                +

                                                                osgi-resource-locator-1.0.1.jar

                                                                breeze_2.11-0.13.2.jar

                                                                +

                                                                breeze_2.11-0.13.2.jar

                                                                jdo-api-3.0.1.jar

                                                                +

                                                                jdo-api-3.0.1.jar

                                                                paranamer-2.8.jar

                                                                +

                                                                paranamer-2.8.jar

                                                                calcite-avatica-1.2.0-incubating.jar

                                                                +

                                                                calcite-avatica-1.2.0-incubating.jar

                                                                jersey-client-2.23.1.jar

                                                                +

                                                                jersey-client-2.23.1.jar

                                                                parquet-column-1.12.2.jar

                                                                +

                                                                parquet-column-1.12.2.jar

                                                                chill-java-0.9.3.jar

                                                                +

                                                                chill-java-0.9.3.jar

                                                                jersey-common-2.23.1.jar

                                                                +

                                                                jersey-common-2.23.1.jar

                                                                parquet-common-1.12.2.jar

                                                                +

                                                                parquet-common-1.12.2.jar

                                                                chill_2.11-0.9.3.jar

                                                                +

                                                                chill_2.11-0.9.3.jar

                                                                jersey-container-servlet-2.23.1.jar

                                                                +

                                                                jersey-container-servlet-2.23.1.jar

                                                                parquet-encoding-1.12.2.jar

                                                                +

                                                                parquet-encoding-1.12.2.jar

                                                                commons-beanutils-1.9.4.jar

                                                                +

                                                                commons-beanutils-1.9.4.jar

                                                                jersey-container-servlet-core-2.23.1.jar

                                                                +

                                                                jersey-container-servlet-core-2.23.1.jar

                                                                parquet-format-structures-1.12.2.jar

                                                                +

                                                                parquet-format-structures-1.12.2.jar

                                                                commons-cli-1.2.jar

                                                                +

                                                                commons-cli-1.2.jar

                                                                jersey-guava-2.23.1.jar

                                                                +

                                                                jersey-guava-2.23.1.jar

                                                                parquet-hadoop-1.12.2.jar

                                                                +

                                                                parquet-hadoop-1.12.2.jar

                                                                commons-codec-1.15.jar

                                                                +

                                                                commons-codec-1.15.jar

                                                                jersey-media-jaxb-2.23.1.jar

                                                                +

                                                                jersey-media-jaxb-2.23.1.jar

                                                                parquet-hadoop-bundle-1.6.0.jar

                                                                +

                                                                parquet-hadoop-bundle-1.6.0.jar

                                                                commons-collections-3.2.2.jar

                                                                +

                                                                commons-collections-3.2.2.jar

                                                                jersey-server-2.23.1.jar

                                                                +

                                                                jersey-server-2.23.1.jar

                                                                parquet-jackson-1.12.2.jar

                                                                +

                                                                parquet-jackson-1.12.2.jar

                                                                commons-collections4-4.2.jar

                                                                +

                                                                commons-collections4-4.2.jar

                                                                jets3t-0.9.4.jar

                                                                +

                                                                jets3t-0.9.4.jar

                                                                postgresql-42.2.14.jar

                                                                +

                                                                postgresql-42.2.14.jar

                                                                commons-compiler-3.0.9.jar

                                                                +

                                                                commons-compiler-3.0.9.jar

                                                                jettison-1.1.jar

                                                                +

                                                                jettison-1.1.jar

                                                                protobuf-java-2.5.0.jar

                                                                +

                                                                protobuf-java-2.5.0.jar

                                                                commons-compress-1.4.1.jar

                                                                +

                                                                commons-compress-1.4.1.jar

                                                                jetty-http-9.4.34.v20201102.jar

                                                                +

                                                                jetty-http-9.4.34.v20201102.jar

                                                                py4j-0.10.7.jar

                                                                +

                                                                py4j-0.10.7.jar

                                                                commons-configuration2-2.1.1.jar

                                                                +

                                                                commons-configuration2-2.1.1.jar

                                                                jetty-io-9.4.34.v20201102.jar

                                                                +

                                                                jetty-io-9.4.34.v20201102.jar

                                                                pyrolite-4.13.jar

                                                                +

                                                                pyrolite-4.13.jar

                                                                commons-crypto-1.0.0-20191105.jar

                                                                +

                                                                commons-crypto-1.0.0-20191105.jar

                                                                jetty-security-9.4.34.v20201102.jar

                                                                +

                                                                jetty-security-9.4.34.v20201102.jar

                                                                re2j-1.1.jar

                                                                +

                                                                re2j-1.1.jar

                                                                commons-daemon-1.0.13.jar

                                                                +

                                                                commons-daemon-1.0.13.jar

                                                                jetty-server-9.4.34.v20201102.jar

                                                                +

                                                                jetty-server-9.4.34.v20201102.jar

                                                                scala-compiler-2.11.12.jar

                                                                +

                                                                scala-compiler-2.11.12.jar

                                                                commons-dbcp2-2.7.0.jar

                                                                +

                                                                commons-dbcp2-2.7.0.jar

                                                                jetty-servlet-9.4.34.v20201102.jar

                                                                +

                                                                jetty-servlet-9.4.34.v20201102.jar

                                                                scala-library-2.11.12.jar

                                                                +

                                                                scala-library-2.11.12.jar

                                                                commons-httpclient-3.1.jar

                                                                +

                                                                commons-httpclient-3.1.jar

                                                                jetty-util-9.4.34.v20201102.jar

                                                                +

                                                                jetty-util-9.4.34.v20201102.jar

                                                                scala-parser-combinators_2.11-1.1.2.jar

                                                                +

                                                                scala-parser-combinators_2.11-1.1.2.jar

                                                                commons-io-2.5.jar

                                                                +

                                                                commons-io-2.5.jar

                                                                jetty-util-ajax-9.4.34.v20201102.jar

                                                                +

                                                                jetty-util-ajax-9.4.34.v20201102.jar

                                                                scala-reflect-2.11.12.jar

                                                                +

                                                                scala-reflect-2.11.12.jar

                                                                commons-lang-2.6.jar

                                                                +

                                                                commons-lang-2.6.jar

                                                                jetty-webapp-9.4.34.v20201102.jar

                                                                +

                                                                jetty-webapp-9.4.34.v20201102.jar

                                                                scala-xml_2.11-1.0.5.jar

                                                                +

                                                                scala-xml_2.11-1.0.5.jar

                                                                commons-lang3-3.5.jar

                                                                +

                                                                commons-lang3-3.5.jar

                                                                jetty-xml-9.4.34.v20201102.jar

                                                                +

                                                                jetty-xml-9.4.34.v20201102.jar

                                                                secComponentApi-1.0.6.jar

                                                                +

                                                                secComponentApi-1.0.6.jar

                                                                commons-logging-1.2.jar

                                                                +

                                                                commons-logging-1.2.jar

                                                                joda-time-2.9.3.jar

                                                                +

                                                                joda-time-2.9.3.jar

                                                                shapeless_2.11-2.3.2.jar

                                                                +

                                                                shapeless_2.11-2.3.2.jar

                                                                commons-math3-3.4.1.jar

                                                                +

                                                                commons-math3-3.4.1.jar

                                                                jodd-core-3.5.2.jar

                                                                +

                                                                jodd-core-3.5.2.jar

                                                                shims-0.7.45.jar

                                                                +

                                                                shims-0.7.45.jar

                                                                commons-net-3.1.jar

                                                                +

                                                                commons-net-3.1.jar

                                                                json-20200518.jar

                                                                +

                                                                json-20200518.jar

                                                                slf4j-api-1.7.30.jar

                                                                +

                                                                slf4j-api-1.7.30.jar

                                                                commons-pool2-2.8.0.jar

                                                                +

                                                                commons-pool2-2.8.0.jar

                                                                json-io-2.5.1.jar

                                                                +

                                                                json-io-2.5.1.jar

                                                                slf4j-log4j12-1.7.30.jar

                                                                +

                                                                slf4j-log4j12-1.7.30.jar

                                                                commons-text-1.3.jar

                                                                +

                                                                commons-text-1.3.jar

                                                                json-sanitizer-1.2.1.jar

                                                                +

                                                                json-sanitizer-1.2.1.jar

                                                                snakeyaml-1.26.jar

                                                                +

                                                                snakeyaml-1.26.jar

                                                                compress-lzf-1.0.3.jar

                                                                +

                                                                compress-lzf-1.0.3.jar

                                                                json-smart-2.3.jar

                                                                +

                                                                json-smart-2.3.jar

                                                                snappy-java-1.1.8.2.jar

                                                                +

                                                                snappy-java-1.1.8.2.jar

                                                                core-1.1.2.jar

                                                                +

                                                                core-1.1.2.jar

                                                                json4s-ast_2.11-3.5.3.jar

                                                                +

                                                                json4s-ast_2.11-3.5.3.jar

                                                                solr-core-7.7.2.jar

                                                                +

                                                                solr-core-7.7.2.jar

                                                                crypter-0.0.6.jar

                                                                +

                                                                crypter-0.0.6.jar

                                                                json4s-core_2.11-3.5.3.jar

                                                                +

                                                                json4s-core_2.11-3.5.3.jar

                                                                solr-solrj-7.7.2.jar

                                                                +

                                                                solr-solrj-7.7.2.jar

                                                                curator-client-4.2.0.jar

                                                                +

                                                                curator-client-4.2.0.jar

                                                                json4s-jackson_2.11-3.5.3.jar

                                                                +

                                                                json4s-jackson_2.11-3.5.3.jar

                                                                spark-avro_2.11-2.4.5.0100-2.0.0.dli-20220617.085536-9.jar

                                                                +

                                                                spark-avro_2.11-2.4.5.0100-2.0.0.dli-20220617.085536-9.jar

                                                                curator-framework-4.2.0.jar

                                                                +

                                                                curator-framework-4.2.0.jar

                                                                json4s-scalap_2.11-3.5.3.jar

                                                                +

                                                                json4s-scalap_2.11-3.5.3.jar

                                                                spark-avro_2.11-4.0.0.jar

                                                                +

                                                                spark-avro_2.11-4.0.0.jar

                                                                curator-recipes-2.7.1.jar

                                                                +

                                                                curator-recipes-2.7.1.jar

                                                                jsp-api-2.1.jar

                                                                +

                                                                jsp-api-2.1.jar

                                                                spark-catalyst_2.11-2.4.5.0100-2.0.0.dli-20220617.085405-16.jar

                                                                +

                                                                spark-catalyst_2.11-2.4.5.0100-2.0.0.dli-20220617.085405-16.jar

                                                                datanucleus-api-jdo-3.2.6.jar

                                                                +

                                                                datanucleus-api-jdo-3.2.6.jar

                                                                jsr305-1.3.9.jar

                                                                +

                                                                jsr305-1.3.9.jar

                                                                spark-core_2.11-2.4.5.0100-2.0.0.dli-20220617.085327-16.jar

                                                                +

                                                                spark-core_2.11-2.4.5.0100-2.0.0.dli-20220617.085327-16.jar

                                                                datanucleus-core-3.2.10.jar

                                                                +

                                                                datanucleus-core-3.2.10.jar

                                                                jta-1.1.jar

                                                                +

                                                                jta-1.1.jar

                                                                spark-graphx_2.11-2.4.5.0100-.0.dli-20220617.085336-16.jar

                                                                +

                                                                spark-graphx_2.11-2.4.5.0100-.0.dli-20220617.085336-16.jar

                                                                datanucleus-rdbms-3.2.9.jar

                                                                +

                                                                datanucleus-rdbms-3.2.9.jar

                                                                jtransforms-2.4.0.jar

                                                                +

                                                                jtransforms-2.4.0.jar

                                                                spark-hive_2.11-2.4.5.0100-2.0.0.dli-20220617.085423-16.jar

                                                                +

                                                                spark-hive_2.11-2.4.5.0100-2.0.0.dli-20220617.085423-16.jar

                                                                derby-10.14.2.0.jar

                                                                +

                                                                derby-10.14.2.0.jar

                                                                jts-core-1.16.1.jar

                                                                +

                                                                jts-core-1.16.1.jar

                                                                spark-kubernetes_2.11-2.4.5.0100-2.0.0.dli-20220617.085519-16.jar

                                                                +

                                                                spark-kubernetes_2.11-2.4.5.0100-2.0.0.dli-20220617.085519-16.jar

                                                                dnsjava-2.1.7.jar

                                                                +

                                                                dnsjava-2.1.7.jar

                                                                jul-to-slf4j-1.7.30.jar

                                                                +

                                                                jul-to-slf4j-1.7.30.jar

                                                                spark-kvstore_2.11-2.4.5.0100-2.0.0.dli-20220617.085249-16.jar

                                                                +

                                                                spark-kvstore_2.11-2.4.5.0100-2.0.0.dli-20220617.085249-16.jar

                                                                ecj-3.21.0.jar

                                                                +

                                                                ecj-3.21.0.jar

                                                                junit-4.11.jar

                                                                +

                                                                junit-4.11.jar

                                                                spark-launcher_2.11-2.4.5.0100-2.0.0.dli-20220617.085435-16.jar

                                                                +

                                                                spark-launcher_2.11-2.4.5.0100-2.0.0.dli-20220617.085435-16.jar

                                                                ehcache-3.3.1.jar

                                                                +

                                                                ehcache-3.3.1.jar

                                                                kerb-admin-1.0.1.jar

                                                                +

                                                                kerb-admin-1.0.1.jar

                                                                spark-mllib-local_2.11-2.4.5.0100-2.0.0.dli-20220617.085349-16.jar

                                                                +

                                                                spark-mllib-local_2.11-2.4.5.0100-2.0.0.dli-20220617.085349-16.jar

                                                                expiringmap-0.5.9.jar

                                                                +

                                                                expiringmap-0.5.9.jar

                                                                kerb-client-1.0.1.jar

                                                                +

                                                                kerb-client-1.0.1.jar

                                                                spark-mllib_2.11-2.4.5.0100-2.0.0.dli-20220617.085342-16.jar

                                                                +

                                                                spark-mllib_2.11-2.4.5.0100-2.0.0.dli-20220617.085342-16.jar

                                                                fastutil-8.2.3.jar

                                                                +

                                                                fastutil-8.2.3.jar

                                                                kerb-common-1.0.1.jar

                                                                +

                                                                kerb-common-1.0.1.jar

                                                                spark-network-common_2.11-2.4.5.0100-2.0.0.dli-20220617.085254-16.jar

                                                                +

                                                                spark-network-common_2.11-2.4.5.0100-2.0.0.dli-20220617.085254-16.jar

                                                                flatbuffers-java-1.9.0.jar

                                                                +

                                                                flatbuffers-java-1.9.0.jar

                                                                kerb-core-1.0.1.jar

                                                                +

                                                                kerb-core-1.0.1.jar

                                                                spark-network-shuffle_2.11-2.4.5.0100-2.0.0.dli-20220617.085300-16.jar

                                                                +

                                                                spark-network-shuffle_2.11-2.4.5.0100-2.0.0.dli-20220617.085300-16.jar

                                                                fst-2.50.jar

                                                                +

                                                                fst-2.50.jar

                                                                kerb-crypto-1.0.1.jar

                                                                +

                                                                kerb-crypto-1.0.1.jar

                                                                spark-om_2.11-2.4.5.0100-2.0.0.dli-20220617.085316-16.jar

                                                                +

                                                                spark-om_2.11-2.4.5.0100-2.0.0.dli-20220617.085316-16.jar

                                                                generex-1.0.2.jar

                                                                +

                                                                generex-1.0.2.jar

                                                                kerb-identity-1.0.1.jar

                                                                +

                                                                kerb-identity-1.0.1.jar

                                                                spark-repl_2.11-2.4.5.0100-2.0.0.dli-20220617.085430-16.jar

                                                                +

                                                                spark-repl_2.11-2.4.5.0100-2.0.0.dli-20220617.085430-16.jar

                                                                geronimo-jcache_1.0_spec-1.0-alpha-1.jar

                                                                +

                                                                geronimo-jcache_1.0_spec-1.0-alpha-1.jar

                                                                kerb-server-1.0.1.jar

                                                                +

                                                                kerb-server-1.0.1.jar

                                                                spark-sketch_2.11-2.4.5.0100-2.0.0.dli-20220617.085243-16.jar

                                                                +

                                                                spark-sketch_2.11-2.4.5.0100-2.0.0.dli-20220617.085243-16.jar

                                                                gson-2.2.4.jar

                                                                +

                                                                gson-2.2.4.jar

                                                                kerb-simplekdc-1.0.1.jar

                                                                +

                                                                kerb-simplekdc-1.0.1.jar

                                                                spark-sql_2.11-2.4.5.0100-2.0.0.dli-20220617.085414-16.jar

                                                                +

                                                                spark-sql_2.11-2.4.5.0100-2.0.0.dli-20220617.085414-16.jar

                                                                guava-14.0.1.jar

                                                                +

                                                                guava-14.0.1.jar

                                                                kerb-util-1.0.1.jar

                                                                +

                                                                kerb-util-1.0.1.jar

                                                                spark-streaming_2.11-2.4.5.0100-.0.dli-20220617.085359-16.jar

                                                                +

                                                                spark-streaming_2.11-2.4.5.0100-.0.dli-20220617.085359-16.jar

                                                                guice-4.0.jar

                                                                +

                                                                guice-4.0.jar

                                                                kerby-asn1-1.0.1.jar

                                                                +

                                                                kerby-asn1-1.0.1.jar

                                                                spark-tags_2.11-2.4.5.0100-2.0.0.dli-20220617.085322-16.jar

                                                                +

                                                                spark-tags_2.11-2.4.5.0100-2.0.0.dli-20220617.085322-16.jar

                                                                guice-servlet-4.0.jar

                                                                +

                                                                guice-servlet-4.0.jar

                                                                kerby-config-1.0.1.jar

                                                                +

                                                                kerby-config-1.0.1.jar

                                                                spark-unsafe_2.11-2.4.5.0100-2.0.0.dli-20220617.085311-16.jar

                                                                +

                                                                spark-unsafe_2.11-2.4.5.0100-2.0.0.dli-20220617.085311-16.jar

                                                                hadoop-annotations-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-annotations-3.1.1-ei-302002.jar

                                                                kerby-pkix-1.0.1.jar

                                                                +

                                                                kerby-pkix-1.0.1.jar

                                                                spark-uquery_2.11-2.4.5.0100-2.0.0.dli-SNAPSHOT.jar

                                                                +

                                                                spark-uquery_2.11-2.4.5.0100-2.0.0.dli-SNAPSHOT.jar

                                                                hadoop-auth-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-auth-3.1.1-ei-302002.jar

                                                                kerby-util-1.0.1.jar

                                                                +

                                                                kerby-util-1.0.1.jar

                                                                spark-yarn_2.11-2.4.5.0100-2.0.0.dli-20220617.085531-16.jar

                                                                +

                                                                spark-yarn_2.11-2.4.5.0100-2.0.0.dli-20220617.085531-16.jar

                                                                hadoop-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-3.1.1-ei-302002.jar

                                                                kerby-xdr-1.0.1.jar

                                                                +

                                                                kerby-xdr-1.0.1.jar

                                                                spire-macros_2.11-0.13.0.jar

                                                                +

                                                                spire-macros_2.11-0.13.0.jar

                                                                hadoop-client-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-client-3.1.1-ei-302002.jar

                                                                kryo-shaded-4.0.2.jar

                                                                +

                                                                kryo-shaded-4.0.2.jar

                                                                spire_2.11-0.13.0.jar

                                                                +

                                                                spire_2.11-0.13.0.jar

                                                                hadoop-common-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-common-3.1.1-ei-302002.jar

                                                                kubernetes-client-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-client-5.4.1-20211025.jar

                                                                stax-api-1.0-2.jar

                                                                +

                                                                stax-api-1.0-2.jar

                                                                hadoop-hdfs-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-hdfs-3.1.1-ei-302002.jar

                                                                kubernetes-model-admissionregistration-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-admissionregistration-5.4.1-20211025.jar

                                                                stax2-api-3.1.4.jar

                                                                +

                                                                stax2-api-3.1.4.jar

                                                                hadoop-hdfs-client-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-hdfs-client-3.1.1-ei-302002.jar

                                                                kubernetes-model-apiextensions-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-apiextensions-5.4.1-20211025.jar

                                                                stream-2.7.0.jar

                                                                +

                                                                stream-2.7.0.jar

                                                                hadoop-3.1.1-46.jar

                                                                +

                                                                hadoop-3.1.1-46.jar

                                                                kubernetes-model-apps-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-apps-5.4.1-20211025.jar

                                                                stringtemplate-3.2.1.jar

                                                                +

                                                                stringtemplate-3.2.1.jar

                                                                hadoop-mapreduce-client-common-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-mapreduce-client-common-3.1.1-ei-302002.jar

                                                                kubernetes-model-autoscaling-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-autoscaling-5.4.1-20211025.jar

                                                                threeten-extra-1.5.0.jar

                                                                +

                                                                threeten-extra-1.5.0.jar

                                                                hadoop-mapreduce-client-core-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-mapreduce-client-core-3.1.1-ei-302002.jar

                                                                kubernetes-model-batch-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-batch-5.4.1-20211025.jar

                                                                tink-1.6.0.jar

                                                                +

                                                                tink-1.6.0.jar

                                                                hadoop-mapreduce-client-jobclient-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-mapreduce-client-jobclient-3.1.1-ei-302002.jar

                                                                kubernetes-model-certificates-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-certificates-5.4.1-20211025.jar

                                                                token-provider-1.0.1.jar

                                                                +

                                                                token-provider-1.0.1.jar

                                                                hadoop-minikdc-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-minikdc-3.1.1-ei-302002.jar

                                                                kubernetes-model-common-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-common-5.4.1-20211025.jar

                                                                tomcat-api-9.0.39.jar

                                                                +

                                                                tomcat-api-9.0.39.jar

                                                                hadoop-yarn-api-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-yarn-api-3.1.1-ei-302002.jar

                                                                kubernetes-model-coordination-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-coordination-5.4.1-20211025.jar

                                                                zookeeper-jute-3.5.6-ei-302002.jar

                                                                +

                                                                zookeeper-jute-3.5.6-ei-302002.jar

                                                                hadoop-yarn-client-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-yarn-client-3.1.1-ei-302002.jar

                                                                kubernetes-model-core-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-core-5.4.1-20211025.jar

                                                                tomcat-el-api-9.0.39.jar

                                                                +

                                                                tomcat-el-api-9.0.39.jar

                                                                hadoop-yarn-common-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-yarn-common-3.1.1-ei-302002.jar

                                                                kubernetes-model-discovery-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-discovery-5.4.1-20211025.jar

                                                                tomcat-jasper-9.0.39.jar

                                                                +

                                                                tomcat-jasper-9.0.39.jar

                                                                hadoop-yarn-registry-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-yarn-registry-3.1.1-ei-302002.jar

                                                                kubernetes-model-events-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-events-5.4.1-20211025.jar

                                                                tomcat-jasper-el-9.0.39.jar

                                                                +

                                                                tomcat-jasper-el-9.0.39.jar

                                                                hadoop-yarn-server-applicationhistoryservice-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-yarn-server-applicationhistoryservice-3.1.1-ei-302002.jar

                                                                kubernetes-model-extensions-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-extensions-5.4.1-20211025.jar

                                                                tomcat-jsp-api-9.0.39.jar

                                                                +

                                                                tomcat-jsp-api-9.0.39.jar

                                                                hadoop-yarn-server-common-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-yarn-server-common-3.1.1-ei-302002.jar

                                                                kubernetes-model-flowcontrol-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-flowcontrol-5.4.1-20211025.jar

                                                                tomcat-juli-9.0.39.jar

                                                                +

                                                                tomcat-juli-9.0.39.jar

                                                                hadoop-yarn-server-resourcemanager-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-yarn-server-resourcemanager-3.1.1-ei-302002.jar

                                                                kubernetes-model-metrics-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-metrics-5.4.1-20211025.jar

                                                                tomcat-servlet-api-9.0.39.jar

                                                                +

                                                                tomcat-servlet-api-9.0.39.jar

                                                                hadoop-yarn-server-web-proxy-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-yarn-server-web-proxy-3.1.1-ei-302002.jar

                                                                kubernetes-model-networking-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-networking-5.4.1-20211025.jar

                                                                tomcat-util-9.0.39.jar

                                                                +

                                                                tomcat-util-9.0.39.jar

                                                                hamcrest-core-1.3.jar

                                                                +

                                                                hamcrest-core-1.3.jar

                                                                kubernetes-model-node-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-node-5.4.1-20211025.jar

                                                                tomcat-util-scan-9.0.39.jar

                                                                +

                                                                tomcat-util-scan-9.0.39.jar

                                                                hive-common-1.2.1-2.0.0.dli-20220528.090500-402.jar

                                                                +

                                                                hive-common-1.2.1-2.0.0.dli-20220528.090500-402.jar

                                                                kubernetes-model-policy-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-policy-5.4.1-20211025.jar

                                                                univocity-parsers-2.7.3.jar

                                                                +

                                                                univocity-parsers-2.7.3.jar

                                                                hive-exec-1.2.1-2.0.0.dli-20220528.090521-401.jar

                                                                +

                                                                hive-exec-1.2.1-2.0.0.dli-20220528.090521-401.jar

                                                                kubernetes-model-rbac-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-rbac-5.4.1-20211025.jar

                                                                zstd-jni-1.4.9-1.jar

                                                                +

                                                                zstd-jni-1.4.9-1.jar

                                                                hive-metastore-1.2.1-2.0.0.dli-20220528.090509-402.jar

                                                                +

                                                                hive-metastore-1.2.1-2.0.0.dli-20220528.090509-402.jar

                                                                kubernetes-model-scheduling-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-scheduling-5.4.1-20211025.jar

                                                                validation-api-1.1.0.Final.jar

                                                                +

                                                                validation-api-1.1.0.Final.jar

                                                                hive-shims-0.23-1.2.1-2.0.0.dli-20220528.090445-403.jar

                                                                +

                                                                hive-shims-0.23-1.2.1-2.0.0.dli-20220528.090445-403.jar

                                                                kubernetes-model-storageclass-5.4.1-20211025.jar

                                                                +

                                                                kubernetes-model-storageclass-5.4.1-20211025.jar

                                                                velocity-1.7.jar

                                                                +

                                                                velocity-1.7.jar

                                                                hive-shims-1.2.1-2.0.0.dli-20220528.090455-403.jar

                                                                +

                                                                hive-shims-1.2.1-2.0.0.dli-20220528.090455-403.jar

                                                                leveldbjni-all-1.8-20191105.jar

                                                                +

                                                                leveldbjni-all-1.8-20191105.jar

                                                                woodstox-core-5.0.3.jar

                                                                +

                                                                woodstox-core-5.0.3.jar

                                                                hive-shims-common-1.2.1-2.0.0.dli-20220528.090441-404.jar

                                                                +

                                                                hive-shims-common-1.2.1-2.0.0.dli-20220528.090441-404.jar

                                                                libfb303-0.9.3.jar

                                                                +

                                                                libfb303-0.9.3.jar

                                                                xbean-asm6-shaded-4.8.jar

                                                                +

                                                                xbean-asm6-shaded-4.8.jar

                                                                hive-shims-scheduler-1.2.1-2.0.0.dli-20220528.090450-403.jar

                                                                +

                                                                hive-shims-scheduler-1.2.1-2.0.0.dli-20220528.090450-403.jar

                                                                libthrift-0.12.0.jar

                                                                +

                                                                libthrift-0.12.0.jar

                                                                xercesImpl-2.12.0.jar

                                                                +

                                                                xercesImpl-2.12.0.jar

                                                                hk2-api-2.4.0-b34.jar

                                                                +

                                                                hk2-api-2.4.0-b34.jar

                                                                log4j-1.2.17-cloudera1.jar

                                                                +

                                                                log4j-1.2.17-cloudera1.jar

                                                                xml-apis-1.4.01.jar

                                                                +

                                                                xml-apis-1.4.01.jar

                                                                hk2-locator-2.4.0-b34.jar

                                                                +

                                                                hk2-locator-2.4.0-b34.jar

                                                                log4j-rolling-appender-20131024-2017.jar

                                                                +

                                                                log4j-rolling-appender-20131024-2017.jar

                                                                xz-1.0.jar

                                                                +

                                                                xz-1.0.jar

                                                                hk2-utils-2.4.0-b34.jar

                                                                +

                                                                hk2-utils-2.4.0-b34.jar

                                                                logging-interceptor-3.14.9.jar

                                                                +

                                                                logging-interceptor-3.14.9.jar

                                                                zjsonpatch-0.3.0.jar

                                                                +

                                                                zjsonpatch-0.3.0.jar

                                                                hppc-0.7.2.jar

                                                                +

                                                                hppc-0.7.2.jar

                                                                lucene-analyzers-common-7.7.2.jar

                                                                +

                                                                lucene-analyzers-common-7.7.2.jar

                                                                zookeeper-3.5.6-ei-302002.jar

                                                                +

                                                                zookeeper-3.5.6-ei-302002.jar

                                                                htrace-core4-4.2.0-incubating-1.0.0.jar

                                                                +

                                                                htrace-core4-4.2.0-incubating-1.0.0.jar

                                                                lucene-core-7.7.2.jar

                                                                +

                                                                lucene-core-7.7.2.jar

                                                                -

                                                                +

                                                                -
                                                                Table 3 Spark 2.3.2 dependencies

                                                                Dependency

                                                                +
                                                                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -2562,155 +3607,155 @@

                                                                Flink 1.12 Dependencies

                                                                -
                                                                Table 4 Spark 2.3.2 dependencies

                                                                Dependency

                                                                accessors-smart-1.2.jar

                                                                +

                                                                accessors-smart-1.2.jar

                                                                HikariCP-java7-2.4.12.jar

                                                                +

                                                                HikariCP-java7-2.4.12.jar

                                                                logging-interceptor-3.14.4.jar

                                                                +

                                                                logging-interceptor-3.14.4.jar

                                                                activation-1.1.1.jar

                                                                +

                                                                activation-1.1.1.jar

                                                                hive-common-1.2.1-2.1.0.dli-20201111.064115-91.jar

                                                                +

                                                                hive-common-1.2.1-2.1.0.dli-20201111.064115-91.jar

                                                                luxor-encrypt-2.1.0-20201106.065437-53.jar

                                                                +

                                                                luxor-encrypt-2.1.0-20201106.065437-53.jar

                                                                aircompressor-0.8.jar

                                                                +

                                                                aircompressor-0.8.jar

                                                                hive-exec-1.2.1-2.1.0.dli-20201111.064444-91.jar

                                                                +

                                                                hive-exec-1.2.1-2.1.0.dli-20201111.064444-91.jar

                                                                luxor-fs3-2.1.0-20201106.065612-53.jar

                                                                +

                                                                luxor-fs3-2.1.0-20201106.065612-53.jar

                                                                alluxio-2.3.1-luxor-SNAPSHOT-client.jar

                                                                +

                                                                alluxio-2.3.1-luxor-SNAPSHOT-client.jar

                                                                hive-metastore-1.2.1-2.1.0.dli-20201111.064230-91.jar

                                                                +

                                                                hive-metastore-1.2.1-2.1.0.dli-20201111.064230-91.jar

                                                                luxor-obs-fs3-2.1.0-20201106.065616-53.jar

                                                                +

                                                                luxor-obs-fs3-2.1.0-20201106.065616-53.jar

                                                                antlr-2.7.7.jar

                                                                +

                                                                antlr-2.7.7.jar

                                                                hk2-api-2.4.0-b34.jar

                                                                +

                                                                hk2-api-2.4.0-b34.jar

                                                                luxor-rpc_2.11-2.1.0-20201106.065541-53.jar

                                                                +

                                                                luxor-rpc_2.11-2.1.0-20201106.065541-53.jar

                                                                antlr4-runtime-4.8-1.jar

                                                                +

                                                                antlr4-runtime-4.8-1.jar

                                                                hk2-locator-2.4.0-b34.jar

                                                                +

                                                                hk2-locator-2.4.0-b34.jar

                                                                luxor-rpc-protobuf2-2.1.0-20201106.065551-53.jar

                                                                +

                                                                luxor-rpc-protobuf2-2.1.0-20201106.065551-53.jar

                                                                antlr-runtime-3.4.jar

                                                                +

                                                                antlr-runtime-3.4.jar

                                                                hk2-utils-2.4.0-b34.jar

                                                                +

                                                                hk2-utils-2.4.0-b34.jar

                                                                lz4-java-1.7.1.jar

                                                                +

                                                                lz4-java-1.7.1.jar

                                                                aopalliance-1.0.jar

                                                                +

                                                                aopalliance-1.0.jar

                                                                hppc-0.7.2.jar

                                                                +

                                                                hppc-0.7.2.jar

                                                                machinist_2.11-0.6.1.jar

                                                                +

                                                                machinist_2.11-0.6.1.jar

                                                                aopalliance-repackaged-2.4.0-b34.jar

                                                                +

                                                                aopalliance-repackaged-2.4.0-b34.jar

                                                                htrace-core4-4.2.0-incubating-1.0.0.jar

                                                                +

                                                                htrace-core4-4.2.0-incubating-1.0.0.jar

                                                                macro-compat_2.11-1.1.1.jar

                                                                +

                                                                macro-compat_2.11-1.1.1.jar

                                                                apache-log4j-extras-1.2.17.jar

                                                                +

                                                                apache-log4j-extras-1.2.17.jar

                                                                httpclient-4.5.4.jar

                                                                +

                                                                httpclient-4.5.4.jar

                                                                metrics-core-3.1.5.jar

                                                                +

                                                                metrics-core-3.1.5.jar

                                                                arpack_combined_all-0.1.jar

                                                                +

                                                                arpack_combined_all-0.1.jar

                                                                httpcore-4.4.7.jar

                                                                +

                                                                httpcore-4.4.7.jar

                                                                metrics-graphite-3.1.5.jar

                                                                +

                                                                metrics-graphite-3.1.5.jar

                                                                arrow-format-0.8.0.jar

                                                                +

                                                                arrow-format-0.8.0.jar

                                                                ivy-2.4.0.jar

                                                                +

                                                                ivy-2.4.0.jar

                                                                metrics-jmx-4.1.12.1.jar

                                                                +

                                                                metrics-jmx-4.1.12.1.jar

                                                                arrow-memory-0.8.0.jar

                                                                +

                                                                arrow-memory-0.8.0.jar

                                                                j2objc-annotations-1.3.jar

                                                                +

                                                                j2objc-annotations-1.3.jar

                                                                metrics-json-3.1.5.jar

                                                                +

                                                                metrics-json-3.1.5.jar

                                                                arrow-vector-0.8.0.jar

                                                                +

                                                                arrow-vector-0.8.0.jar

                                                                jackson-annotations-2.10.0.jar

                                                                +

                                                                jackson-annotations-2.10.0.jar

                                                                metrics-jvm-3.1.5.jar

                                                                +

                                                                metrics-jvm-3.1.5.jar

                                                                asm-5.0.4.jar

                                                                +

                                                                asm-5.0.4.jar

                                                                jackson-core-2.10.0.jar

                                                                +

                                                                jackson-core-2.10.0.jar

                                                                minlog-1.3.0.jar

                                                                +

                                                                minlog-1.3.0.jar

                                                                audience-annotations-0.5.0.jar

                                                                +

                                                                audience-annotations-0.5.0.jar

                                                                jackson-core-asl-1.9.13-atlassian-4.jar

                                                                +

                                                                jackson-core-asl-1.9.13-atlassian-4.jar

                                                                mssql-jdbc-6.2.1.jre7.jar

                                                                +

                                                                mssql-jdbc-6.2.1.jre7.jar

                                                                automaton-1.11-8.jar

                                                                +

                                                                automaton-1.11-8.jar

                                                                jackson-databind-2.10.0.jar

                                                                +

                                                                jackson-databind-2.10.0.jar

                                                                netty-3.10.6.Final.jar

                                                                +

                                                                netty-3.10.6.Final.jar

                                                                avro-1.7.7.jar

                                                                +

                                                                avro-1.7.7.jar

                                                                jackson-dataformat-yaml-2.10.0.jar

                                                                +

                                                                jackson-dataformat-yaml-2.10.0.jar

                                                                netty-all-4.1.51.Final.jar

                                                                +

                                                                netty-all-4.1.51.Final.jar

                                                                avro-ipc-1.7.7.jar

                                                                +

                                                                avro-ipc-1.7.7.jar

                                                                jackson-datatype-jsr310-2.10.3.jar

                                                                +

                                                                jackson-datatype-jsr310-2.10.3.jar

                                                                nimbus-jose-jwt-8.19.jar

                                                                +

                                                                nimbus-jose-jwt-8.19.jar

                                                                avro-ipc-1.7.7-tests.jar

                                                                +

                                                                avro-ipc-1.7.7-tests.jar

                                                                jackson-jaxrs-base-2.10.3.jar

                                                                +

                                                                jackson-jaxrs-base-2.10.3.jar

                                                                objenesis-2.1.jar

                                                                +

                                                                objenesis-2.1.jar

                                                                avro-mapred-1.7.7-hadoop2.jar

                                                                +

                                                                avro-mapred-1.7.7-hadoop2.jar

                                                                jackson-jaxrs-json-provider-2.10.3.jar

                                                                +

                                                                jackson-jaxrs-json-provider-2.10.3.jar

                                                                okhttp-3.14.4.jar

                                                                +

                                                                okhttp-3.14.4.jar

                                                                java-sdk-bundle-1.11.271.jar

                                                                +

                                                                java-sdk-bundle-1.11.271.jar

                                                                jackson-mapper-asl-1.9.13-atlassian-4.jar

                                                                +

                                                                jackson-mapper-asl-1.9.13-atlassian-4.jar

                                                                okio-1.17.2.jar

                                                                +

                                                                okio-1.17.2.jar

                                                                base64-2.3.8.jar

                                                                +

                                                                base64-2.3.8.jar

                                                                jackson-module-jaxb-annotations-2.10.3.jar

                                                                +

                                                                jackson-module-jaxb-annotations-2.10.3.jar

                                                                opencsv-2.3.jar

                                                                +

                                                                opencsv-2.3.jar

                                                                bcpkix-jdk15on-1.66.jar

                                                                +

                                                                bcpkix-jdk15on-1.66.jar

                                                                jackson-module-paranamer-2.10.0.jar

                                                                +

                                                                jackson-module-paranamer-2.10.0.jar

                                                                opencsv-4.6.jar

                                                                +

                                                                opencsv-4.6.jar

                                                                bcprov-jdk15on-1.66.jar

                                                                +

                                                                bcprov-jdk15on-1.66.jar

                                                                jackson-module-scala_2.11-2.10.0.jar

                                                                +

                                                                jackson-module-scala_2.11-2.10.0.jar

                                                                opencv-4.3.0-2.jar

                                                                +

                                                                opencv-4.3.0-2.jar

                                                                bonecp-0.8.0.RELEASE.jar

                                                                +

                                                                bonecp-0.8.0.RELEASE.jar

                                                                jakarta.activation-api-1.2.1.jar

                                                                +

                                                                jakarta.activation-api-1.2.1.jar

                                                                orc-core-1.4.4-nohive.jar

                                                                +

                                                                orc-core-1.4.4-nohive.jar

                                                                breeze_2.11-0.13.2.jar

                                                                +

                                                                breeze_2.11-0.13.2.jar

                                                                jakarta.xml.bind-api-2.3.2.jar

                                                                +

                                                                jakarta.xml.bind-api-2.3.2.jar

                                                                orc-mapreduce-1.4.4-nohive.jar

                                                                +

                                                                orc-mapreduce-1.4.4-nohive.jar

                                                                breeze-macros_2.11-0.13.2.jar

                                                                +

                                                                breeze-macros_2.11-0.13.2.jar

                                                                janino-3.0.8.jar

                                                                +

                                                                janino-3.0.8.jar

                                                                oro-2.0.8.jar

                                                                +

                                                                oro-2.0.8.jar

                                                                calcite-avatica-1.2.0-incubating.jar

                                                                +

                                                                calcite-avatica-1.2.0-incubating.jar

                                                                javacpp-1.5.4.jar

                                                                +

                                                                javacpp-1.5.4.jar

                                                                osgi-resource-locator-1.0.1.jar

                                                                +

                                                                osgi-resource-locator-1.0.1.jar

                                                                calcite-core-1.2.0-incubating.jar

                                                                +

                                                                calcite-core-1.2.0-incubating.jar

                                                                javacpp-1.5.4-linux-x86_64.jar

                                                                +

                                                                javacpp-1.5.4-linux-x86_64.jar

                                                                paranamer-2.8.jar

                                                                +

                                                                paranamer-2.8.jar

                                                                calcite-linq4j-1.2.0-incubating.jar

                                                                +

                                                                calcite-linq4j-1.2.0-incubating.jar

                                                                javacv-1.5.4.jar

                                                                +

                                                                javacv-1.5.4.jar

                                                                parquet-column-1.8.3.jar

                                                                +

                                                                parquet-column-1.8.3.jar

                                                                checker-qual-2.11.1.jar

                                                                +

                                                                checker-qual-2.11.1.jar

                                                                JavaEWAH-1.1.7.jar

                                                                +

                                                                JavaEWAH-1.1.7.jar

                                                                parquet-common-1.8.3.jar

                                                                +

                                                                parquet-common-1.8.3.jar

                                                                chill_2.11-0.8.4.jar

                                                                +

                                                                chill_2.11-0.8.4.jar

                                                                javassist-3.18.1-GA.jar

                                                                +

                                                                javassist-3.18.1-GA.jar

                                                                parquet-encoding-1.8.3.jar

                                                                +

                                                                parquet-encoding-1.8.3.jar

                                                                chill-java-0.8.4.jar

                                                                +

                                                                chill-java-0.8.4.jar

                                                                javax.annotation-api-1.2.jar

                                                                +

                                                                javax.annotation-api-1.2.jar

                                                                parquet-format-2.3.1.jar

                                                                +

                                                                parquet-format-2.3.1.jar

                                                                commons-beanutils-1.9.4.jar

                                                                +

                                                                commons-beanutils-1.9.4.jar

                                                                javax.inject-1.jar

                                                                +

                                                                javax.inject-1.jar

                                                                parquet-hadoop-1.8.3.jar

                                                                +

                                                                parquet-hadoop-1.8.3.jar

                                                                commons-cli-1.2.jar

                                                                +

                                                                commons-cli-1.2.jar

                                                                javax.inject-2.4.0-b34.jar

                                                                +

                                                                javax.inject-2.4.0-b34.jar

                                                                parquet-hadoop-bundle-1.6.0.jar

                                                                +

                                                                parquet-hadoop-bundle-1.6.0.jar

                                                                commons-codec-2.0-20130428.202122-59.jar

                                                                +

                                                                commons-codec-2.0-20130428.202122-59.jar

                                                                javax.servlet-api-3.1.0.jar

                                                                +

                                                                javax.servlet-api-3.1.0.jar

                                                                parquet-jackson-1.8.3.jar

                                                                +

                                                                parquet-jackson-1.8.3.jar

                                                                commons-collections-3.2.2.jar

                                                                +

                                                                commons-collections-3.2.2.jar

                                                                javax.ws.rs-api-2.0.1.jar

                                                                +

                                                                javax.ws.rs-api-2.0.1.jar

                                                                parquet-format-2.3.1.jar

                                                                +

                                                                parquet-format-2.3.1.jar

                                                                commons-collections4-4.2.jar

                                                                +

                                                                commons-collections4-4.2.jar

                                                                java-xmlbuilder-1.1.jar

                                                                +

                                                                java-xmlbuilder-1.1.jar

                                                                parquet-hadoop-1.8.3.jar

                                                                +

                                                                parquet-hadoop-1.8.3.jar

                                                                commons-compiler-3.0.8.jar

                                                                +

                                                                commons-compiler-3.0.8.jar

                                                                javolution-5.3.1.jar

                                                                +

                                                                javolution-5.3.1.jar

                                                                parquet-hadoop-bundle-1.6.0.jar

                                                                +

                                                                parquet-hadoop-bundle-1.6.0.jar

                                                                commons-compress-1.4.1.jar

                                                                +

                                                                commons-compress-1.4.1.jar

                                                                jaxb-api-2.2.11.jar

                                                                +

                                                                jaxb-api-2.2.11.jar

                                                                parquet-jackson-1.8.3.jar

                                                                +

                                                                parquet-jackson-1.8.3.jar

                                                                commons-configuration2-2.1.1.jar

                                                                +

                                                                commons-configuration2-2.1.1.jar

                                                                jcip-annotations-1.0-1.jar

                                                                +

                                                                jcip-annotations-1.0-1.jar

                                                                postgresql-42.2.14.jar

                                                                +

                                                                postgresql-42.2.14.jar

                                                                commons-crypto-1.0.0-20191105.jar

                                                                +

                                                                commons-crypto-1.0.0-20191105.jar

                                                                jcl-over-slf4j-1.7.26.jar

                                                                +

                                                                jcl-over-slf4j-1.7.26.jar

                                                                protobuf-java-2.5.0.jar

                                                                +

                                                                protobuf-java-2.5.0.jar

                                                                commons-daemon-1.0.13.jar

                                                                +

                                                                commons-daemon-1.0.13.jar

                                                                jdo-api-3.0.1.jar

                                                                +

                                                                jdo-api-3.0.1.jar

                                                                py4j-0.10.7.jar

                                                                +

                                                                py4j-0.10.7.jar

                                                                commons-dbcp-1.4.jar

                                                                +

                                                                commons-dbcp-1.4.jar

                                                                jersey-client-2.23.1.jar

                                                                +

                                                                jersey-client-2.23.1.jar

                                                                pyrolite-4.13.jar

                                                                +

                                                                pyrolite-4.13.jar

                                                                commons-dbcp2-2.7.0.jar

                                                                +

                                                                commons-dbcp2-2.7.0.jar

                                                                jersey-common-2.23.1.jar

                                                                +

                                                                jersey-common-2.23.1.jar

                                                                re2j-1.1.jar

                                                                +

                                                                re2j-1.1.jar

                                                                commons-httpclient-3.1.jar

                                                                +

                                                                commons-httpclient-3.1.jar

                                                                jersey-container-servlet-2.23.1.jar

                                                                +

                                                                jersey-container-servlet-2.23.1.jar

                                                                RoaringBitmap-0.5.11.jar

                                                                +

                                                                RoaringBitmap-0.5.11.jar

                                                                commons-io-2.5.jar

                                                                +

                                                                commons-io-2.5.jar

                                                                jersey-container-servlet-core-2.23.1.jar

                                                                +

                                                                jersey-container-servlet-core-2.23.1.jar

                                                                scala-compiler-2.11.12.jar

                                                                +

                                                                scala-compiler-2.11.12.jar

                                                                commons-lang-2.6.jar

                                                                +

                                                                commons-lang-2.6.jar

                                                                jersey-guava-2.23.1.jar

                                                                +

                                                                jersey-guava-2.23.1.jar

                                                                scala-library-2.11.12.jar

                                                                +

                                                                scala-library-2.11.12.jar

                                                                commons-lang3-3.5.jar

                                                                +

                                                                commons-lang3-3.5.jar

                                                                jersey-media-jaxb-2.23.1.jar

                                                                +

                                                                jersey-media-jaxb-2.23.1.jar

                                                                scalap-2.11.0.jar

                                                                +

                                                                scalap-2.11.0.jar

                                                                commons-logging-1.2.jar

                                                                +

                                                                commons-logging-1.2.jar

                                                                jersey-server-2.23.1.jar

                                                                +

                                                                jersey-server-2.23.1.jar

                                                                scala-parser-combinators_2.11-1.1.0.jar

                                                                +

                                                                scala-parser-combinators_2.11-1.1.0.jar

                                                                commons-math3-3.4.1.jar

                                                                +

                                                                commons-math3-3.4.1.jar

                                                                jets3t-0.9.4.jar

                                                                +

                                                                jets3t-0.9.4.jar

                                                                scala-reflect-2.11.12.jar

                                                                +

                                                                scala-reflect-2.11.12.jar

                                                                commons-net-2.2.jar

                                                                +

                                                                commons-net-2.2.jar

                                                                jetty-http-9.4.31.v20200723.jar

                                                                +

                                                                jetty-http-9.4.31.v20200723.jar

                                                                scala-xml_2.11-1.0.5.jar

                                                                +

                                                                scala-xml_2.11-1.0.5.jar

                                                                commons-pool-1.5.4.jar

                                                                +

                                                                commons-pool-1.5.4.jar

                                                                jetty-io-9.4.31.v20200723.jar

                                                                +

                                                                jetty-io-9.4.31.v20200723.jar

                                                                secComponentApi-1.0.5c.jar

                                                                +

                                                                secComponentApi-1.0.5c.jar

                                                                commons-pool2-2.8.0.jar

                                                                +

                                                                commons-pool2-2.8.0.jar

                                                                jetty-security-9.4.31.v20200723.jar

                                                                +

                                                                jetty-security-9.4.31.v20200723.jar

                                                                shapeless_2.11-2.3.2.jar

                                                                +

                                                                shapeless_2.11-2.3.2.jar

                                                                commons-text-1.3.jar

                                                                +

                                                                commons-text-1.3.jar

                                                                jetty-server-9.4.31.v20200723.jar

                                                                +

                                                                jetty-server-9.4.31.v20200723.jar

                                                                slf4j-api-1.7.30.jar

                                                                +

                                                                slf4j-api-1.7.30.jar

                                                                compress-lzf-1.0.3.jar

                                                                +

                                                                compress-lzf-1.0.3.jar

                                                                jetty-servlet-9.4.31.v20200723.jar

                                                                +

                                                                jetty-servlet-9.4.31.v20200723.jar

                                                                slf4j-log4j12-1.7.30.jar

                                                                +

                                                                slf4j-log4j12-1.7.30.jar

                                                                core-1.1.2.jar

                                                                +

                                                                core-1.1.2.jar

                                                                jetty-util-9.4.31.v20200723.jar

                                                                +

                                                                jetty-util-9.4.31.v20200723.jar

                                                                snakeyaml-1.24.jar

                                                                +

                                                                snakeyaml-1.24.jar

                                                                curator-client-4.2.0.jar

                                                                +

                                                                curator-client-4.2.0.jar

                                                                jetty-util-ajax-9.4.31.v20200723.jar

                                                                +

                                                                jetty-util-ajax-9.4.31.v20200723.jar

                                                                snappy-java-1.1.7.5.jar

                                                                +

                                                                snappy-java-1.1.7.5.jar

                                                                curator-framework-4.2.0.jar

                                                                +

                                                                curator-framework-4.2.0.jar

                                                                jetty-webapp-9.4.31.v20200723.jar

                                                                +

                                                                jetty-webapp-9.4.31.v20200723.jar

                                                                spark-catalyst_2.11-2.3.2.0101-2.1.0.dli-20201111.073826-143.jar

                                                                +

                                                                spark-catalyst_2.11-2.3.2.0101-2.1.0.dli-20201111.073826-143.jar

                                                                curator-recipes-2.7.1.jar

                                                                +

                                                                curator-recipes-2.7.1.jar

                                                                jetty-xml-9.4.31.v20200723.jar

                                                                +

                                                                jetty-xml-9.4.31.v20200723.jar

                                                                spark-core_2.11-2.3.2.0101-.0.dli-20201111.073836-134.jar

                                                                +

                                                                spark-core_2.11-2.3.2.0101-.0.dli-20201111.073836-134.jar

                                                                datanucleus-api-jdo-3.2.6.jar

                                                                +

                                                                datanucleus-api-jdo-3.2.6.jar

                                                                joda-time-2.9.3.jar

                                                                +

                                                                joda-time-2.9.3.jar

                                                                spark-graphx_2.11-2.3.2.0101-2.1.0.dli-20201111.073847-129.jar

                                                                +

                                                                spark-graphx_2.11-2.3.2.0101-2.1.0.dli-20201111.073847-129.jar

                                                                datanucleus-core-3.2.10.jar

                                                                +

                                                                datanucleus-core-3.2.10.jar

                                                                jodd-core-4.2.0.jar

                                                                +

                                                                jodd-core-4.2.0.jar

                                                                spark-hive_2.11-2.3.2.0101-.0.dli-20201111.073854-132.jar

                                                                +

                                                                spark-hive_2.11-2.3.2.0101-.0.dli-20201111.073854-132.jar

                                                                datanucleus-rdbms-3.2.9.jar

                                                                +

                                                                datanucleus-rdbms-3.2.9.jar

                                                                json-20200518.jar

                                                                +

                                                                json-20200518.jar

                                                                spark-kubernetes_2.11-2.3.2.0101-2.1.0.dli-20201111.073916-85.jar

                                                                +

                                                                spark-kubernetes_2.11-2.3.2.0101-2.1.0.dli-20201111.073916-85.jar

                                                                derby-10.12.1.1.jar

                                                                +

                                                                derby-10.12.1.1.jar

                                                                json4s-ast_2.11-3.2.11.jar

                                                                +

                                                                json4s-ast_2.11-3.2.11.jar

                                                                spark-kvstore_2.11-2.3.2.0101-2.1.0.dli-20201111.073933-127.jar

                                                                +

                                                                spark-kvstore_2.11-2.3.2.0101-2.1.0.dli-20201111.073933-127.jar

                                                                dnsjava-2.1.7.jar

                                                                +

                                                                dnsjava-2.1.7.jar

                                                                json4s-core_2.11-3.2.11.jar

                                                                +

                                                                json4s-core_2.11-3.2.11.jar

                                                                spark-launcher_2.11-2.3.2.0101-2.1.0.dli-20201111.073940-127.jar

                                                                +

                                                                spark-launcher_2.11-2.3.2.0101-2.1.0.dli-20201111.073940-127.jar

                                                                ehcache-3.3.1.jar

                                                                +

                                                                ehcache-3.3.1.jar

                                                                json4s-jackson_2.11-3.2.11.jar

                                                                +

                                                                json4s-jackson_2.11-3.2.11.jar

                                                                spark-mllib_2.11-2.3.2.0101-2.1.0.dli-20201111.073946-127.jar

                                                                +

                                                                spark-mllib_2.11-2.3.2.0101-2.1.0.dli-20201111.073946-127.jar

                                                                eigenbase-properties-1.1.5.jar

                                                                +

                                                                eigenbase-properties-1.1.5.jar

                                                                json-sanitizer-1.2.1.jar

                                                                +

                                                                json-sanitizer-1.2.1.jar

                                                                spark-mllib-local_2.11-2.3.2.0101-2.1.0.dli-20201111.073953-127.jar

                                                                +

                                                                spark-mllib-local_2.11-2.3.2.0101-2.1.0.dli-20201111.073953-127.jar

                                                                error_prone_annotations-2.3.4.jar

                                                                +

                                                                error_prone_annotations-2.3.4.jar

                                                                json-smart-2.3.jar

                                                                +

                                                                json-smart-2.3.jar

                                                                spark-network-common_2.11-2.3.2.0101-2.1.0.dli-20201111.073959-127.jar

                                                                +

                                                                spark-network-common_2.11-2.3.2.0101-2.1.0.dli-20201111.073959-127.jar

                                                                failureaccess-1.0.1.jar

                                                                +

                                                                failureaccess-1.0.1.jar

                                                                jsp-api-2.1.jar

                                                                +

                                                                jsp-api-2.1.jar

                                                                spark-network-shuffle_2.11-2.3.2.0101-2.1.0.dli-20201111.074007-127.jar

                                                                +

                                                                spark-network-shuffle_2.11-2.3.2.0101-2.1.0.dli-20201111.074007-127.jar

                                                                fastutil-8.2.3.jar

                                                                +

                                                                fastutil-8.2.3.jar

                                                                jsr305-3.0.2.jar

                                                                +

                                                                jsr305-3.0.2.jar

                                                                spark-om_2.11-2.3.2.0101-.0.dli-20201111.074019-125.jar

                                                                +

                                                                spark-om_2.11-2.3.2.0101-.0.dli-20201111.074019-125.jar

                                                                ffmpeg-4.3.1-1.5.4.jar

                                                                +

                                                                ffmpeg-4.3.1-1.5.4.jar

                                                                jta-1.1.jar

                                                                +

                                                                jta-1.1.jar

                                                                spark-repl_2.11-2.3.2.0101-2.1.0.dli-20201111.074028-125.jar

                                                                +

                                                                spark-repl_2.11-2.3.2.0101-2.1.0.dli-20201111.074028-125.jar

                                                                ffmpeg-4.3.1-1.5.4-linux-x86_64.jar

                                                                +

                                                                ffmpeg-4.3.1-1.5.4-linux-x86_64.jar

                                                                jtransforms-2.4.0.jar

                                                                +

                                                                jtransforms-2.4.0.jar

                                                                spark-sketch_2.11-2.3.2.0101-2.1.0.dli-20201111.074035-125.jar

                                                                +

                                                                spark-sketch_2.11-2.3.2.0101-2.1.0.dli-20201111.074035-125.jar

                                                                flatbuffers-1.2.0-3f79e055.jar

                                                                +

                                                                flatbuffers-1.2.0-3f79e055.jar

                                                                jul-to-slf4j-1.7.26.jar

                                                                +

                                                                jul-to-slf4j-1.7.26.jar

                                                                spark-sql_2.11-2.3.2.0101-2.1.0.dli-20201111.074041-126.jar

                                                                +

                                                                spark-sql_2.11-2.3.2.0101-2.1.0.dli-20201111.074041-126.jar

                                                                generex-1.0.2.jar

                                                                +

                                                                generex-1.0.2.jar

                                                                junit-4.11.jar

                                                                +

                                                                junit-4.11.jar

                                                                spark-streaming_2.11-2.3.2.0101-2.1.0.dli-20201111.074100-123.jar

                                                                +

                                                                spark-streaming_2.11-2.3.2.0101-2.1.0.dli-20201111.074100-123.jar

                                                                geronimo-jcache_1.0_spec-1.0-alpha-1.jar

                                                                +

                                                                geronimo-jcache_1.0_spec-1.0-alpha-1.jar

                                                                kerb-admin-1.0.1.jar

                                                                +

                                                                kerb-admin-1.0.1.jar

                                                                spark-tags_2.11-2.3.2.0101-2.1.0.dli-20201111.074136-123.jar

                                                                +

                                                                spark-tags_2.11-2.3.2.0101-2.1.0.dli-20201111.074136-123.jar

                                                                gson-2.2.4.jar

                                                                +

                                                                gson-2.2.4.jar

                                                                kerb-client-1.0.1.jar

                                                                +

                                                                kerb-client-1.0.1.jar

                                                                spark-tags_2.11-2.3.2.0101-2.1.0.dli-20201111.074141-124-tests.jar

                                                                +

                                                                spark-tags_2.11-2.3.2.0101-2.1.0.dli-20201111.074141-124-tests.jar

                                                                guava-29.0-jre.jar

                                                                +

                                                                guava-29.0-jre.jar

                                                                kerb-common-1.0.1.jar

                                                                +

                                                                kerb-common-1.0.1.jar

                                                                spark-unsafe_2.11-2.3.2.0101-2.1.0.dli-20201111.074144-123.jar

                                                                +

                                                                spark-unsafe_2.11-2.3.2.0101-2.1.0.dli-20201111.074144-123.jar

                                                                guice-4.0.jar

                                                                +

                                                                guice-4.0.jar

                                                                kerb-core-1.0.1.jar

                                                                +

                                                                kerb-core-1.0.1.jar

                                                                spark-uquery_2.11-2.3.2.0101-2.1.0.dli-20201111.074906-210.jar

                                                                +

                                                                spark-uquery_2.11-2.3.2.0101-2.1.0.dli-20201111.074906-210.jar

                                                                guice-servlet-4.0.jar

                                                                +

                                                                guice-servlet-4.0.jar

                                                                kerb-crypto-1.0.1.jar

                                                                +

                                                                kerb-crypto-1.0.1.jar

                                                                spark-yarn_2.11-2.3.2.0101-2.1.0.dli-20201111.074151-123.jar

                                                                +

                                                                spark-yarn_2.11-2.3.2.0101-2.1.0.dli-20201111.074151-123.jar

                                                                hadoop-annotations-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-annotations-3.1.1-ei-302002.jar

                                                                kerb-identity-1.0.1.jar

                                                                +

                                                                kerb-identity-1.0.1.jar

                                                                spire_2.11-0.13.0.jar

                                                                +

                                                                spire_2.11-0.13.0.jar

                                                                hadoop-auth-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-auth-3.1.1-ei-302002.jar

                                                                kerb-server-1.0.1.jar

                                                                +

                                                                kerb-server-1.0.1.jar

                                                                spire-macros_2.11-0.13.0.jar

                                                                +

                                                                spire-macros_2.11-0.13.0.jar

                                                                hadoop-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-3.1.1-ei-302002.jar

                                                                kerb-simplekdc-1.0.1.jar

                                                                +

                                                                kerb-simplekdc-1.0.1.jar

                                                                ST4-4.3.1.jar

                                                                +

                                                                ST4-4.3.1.jar

                                                                hadoop-client-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-client-3.1.1-ei-302002.jar

                                                                kerb-util-1.0.1.jar

                                                                +

                                                                kerb-util-1.0.1.jar

                                                                stax2-api-3.1.4.jar

                                                                +

                                                                stax2-api-3.1.4.jar

                                                                hadoop-common-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-common-3.1.1-ei-302002.jar

                                                                kerby-asn1-1.0.1.jar

                                                                +

                                                                kerby-asn1-1.0.1.jar

                                                                stax-api-1.0-2.jar

                                                                +

                                                                stax-api-1.0-2.jar

                                                                hadoop-hdfs-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-hdfs-3.1.1-ei-302002.jar

                                                                kerby-config-1.0.1.jar

                                                                +

                                                                kerby-config-1.0.1.jar

                                                                stream-2.7.0.jar

                                                                +

                                                                stream-2.7.0.jar

                                                                hadoop-hdfs-client-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-hdfs-client-3.1.1-ei-302002.jar

                                                                kerby-pkix-1.0.1.jar

                                                                +

                                                                kerby-pkix-1.0.1.jar

                                                                stringtemplate-3.2.1.jar

                                                                +

                                                                stringtemplate-3.2.1.jar

                                                                hadoop-3.1.1-41.jar

                                                                +

                                                                hadoop-3.1.1-41.jar

                                                                kerby-util-1.0.1.jar

                                                                +

                                                                kerby-util-1.0.1.jar

                                                                token-provider-1.0.1.jar

                                                                +

                                                                token-provider-1.0.1.jar

                                                                hadoop-mapreduce-client-common-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-mapreduce-client-common-3.1.1-ei-302002.jar

                                                                kerby-xdr-1.0.1.jar

                                                                +

                                                                kerby-xdr-1.0.1.jar

                                                                univocity-parsers-2.5.9.jar

                                                                +

                                                                univocity-parsers-2.5.9.jar

                                                                hadoop-mapreduce-client-core-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-mapreduce-client-core-3.1.1-ei-302002.jar

                                                                kryo-shaded-3.0.3.jar

                                                                +

                                                                kryo-shaded-3.0.3.jar

                                                                validation-api-1.1.0.Final.jar

                                                                +

                                                                validation-api-1.1.0.Final.jar

                                                                hadoop-mapreduce-client-jobclient-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-mapreduce-client-jobclient-3.1.1-ei-302002.jar

                                                                kubernetes-client-4.9.2-20200804.jar

                                                                +

                                                                kubernetes-client-4.9.2-20200804.jar

                                                                woodstox-core-5.0.3.jar

                                                                +

                                                                woodstox-core-5.0.3.jar

                                                                hadoop-minikdc-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-minikdc-3.1.1-ei-302002.jar

                                                                kubernetes-model-4.9.2-20200804.jar

                                                                +

                                                                kubernetes-model-4.9.2-20200804.jar

                                                                xbean-asm5-shaded-4.4.jar

                                                                +

                                                                xbean-asm5-shaded-4.4.jar

                                                                hadoop-yarn-api-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-yarn-api-3.1.1-ei-302002.jar

                                                                kubernetes-model-common-4.9.2-20200804.jar

                                                                +

                                                                kubernetes-model-common-4.9.2-20200804.jar

                                                                xercesImpl-2.12.0.jar

                                                                +

                                                                xercesImpl-2.12.0.jar

                                                                hadoop-yarn-client-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-yarn-client-3.1.1-ei-302002.jar

                                                                leveldbjni-all-1.8-20191105.jar

                                                                +

                                                                leveldbjni-all-1.8-20191105.jar

                                                                xml-apis-1.4.01.jar

                                                                +

                                                                xml-apis-1.4.01.jar

                                                                hadoop-yarn-common-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-yarn-common-3.1.1-ei-302002.jar

                                                                libfb303-0.9.3.jar

                                                                +

                                                                libfb303-0.9.3.jar

                                                                xz-1.0.jar

                                                                +

                                                                xz-1.0.jar

                                                                hadoop-yarn-registry-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-yarn-registry-3.1.1-ei-302002.jar

                                                                libthrift-0.12.0.jar

                                                                +

                                                                libthrift-0.12.0.jar

                                                                zjsonpatch-0.3.0.jar

                                                                +

                                                                zjsonpatch-0.3.0.jar

                                                                hadoop-yarn-server-common-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-yarn-server-common-3.1.1-ei-302002.jar

                                                                listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar

                                                                +

                                                                listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar

                                                                zookeeper-3.5.6-ei-302002.jar

                                                                +

                                                                zookeeper-3.5.6-ei-302002.jar

                                                                hadoop-yarn-server-web-proxy-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-yarn-server-web-proxy-3.1.1-ei-302002.jar

                                                                log4j-1.2.17-cloudera1.jar

                                                                +

                                                                log4j-1.2.17-cloudera1.jar

                                                                zookeeper-jute-3.5.6-ei-302002.jar

                                                                +

                                                                zookeeper-jute-3.5.6-ei-302002.jar

                                                                hamcrest-core-1.3.jar

                                                                +

                                                                hamcrest-core-1.3.jar

                                                                log4j-rolling-appender-20131024-2017.jar

                                                                +

                                                                log4j-rolling-appender-20131024-2017.jar

                                                                zstd-jni-1.4.4-11.jar

                                                                +

                                                                zstd-jni-1.4.4-11.jar
                                                                Table 4 Flink 1.12 dependencies

                                                                Dependency

                                                                +
                                                                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -2719,120 +3764,120 @@

                                                                Flink 1.10 Dependencies

                                                                Only queues created after December 2020 can use the Flink 1.10 dependencies.

                                                                -
                                                                Table 5 Flink 1.12 dependencies

                                                                Dependency

                                                                bcpkix-jdk15on-1.60.jar

                                                                +

                                                                bcpkix-jdk15on-1.60.jar

                                                                flink-json-1.12.2-ei-313001-dli-2022011002.jar

                                                                +

                                                                flink-json-1.12.2-ei-313001-dli-2022011002.jar

                                                                libtensorflow-1.12.0.jar

                                                                +

                                                                libtensorflow-1.12.0.jar

                                                                bcprov-jdk15on-1.60.jar

                                                                +

                                                                bcprov-jdk15on-1.60.jar

                                                                flink-kubernetes_2.11-1.12.2-ei-313001-dli-2022011002.jar

                                                                +

                                                                flink-kubernetes_2.11-1.12.2-ei-313001-dli-2022011002.jar

                                                                log4j-1.2-api-2.17.1.jar

                                                                +

                                                                log4j-1.2-api-2.17.1.jar

                                                                clickhouse-jdbc-0.3.1-ei-313001-SNAPSHOT.jar

                                                                +

                                                                clickhouse-jdbc-0.3.1-ei-313001-SNAPSHOT.jar

                                                                flink-metrics-prometheus_2.11-1.12.2-ei-313001-dli-2022011002.jar

                                                                +

                                                                flink-metrics-prometheus_2.11-1.12.2-ei-313001-dli-2022011002.jar

                                                                log4j-api-2.17.1.jar

                                                                +

                                                                log4j-api-2.17.1.jar

                                                                commons-codec-1.9.jar

                                                                +

                                                                commons-codec-1.9.jar

                                                                flink-obs-hadoop-fs-2.0.0-20220226.034421-73.jar

                                                                +

                                                                flink-obs-hadoop-fs-2.0.0-20220226.034421-73.jar

                                                                log4j-core-2.17.1.jar

                                                                +

                                                                log4j-core-2.17.1.jar

                                                                commons-configuration-1.7.jar

                                                                +

                                                                commons-configuration-1.7.jar

                                                                flink-s3-fs-hadoop-1.12.2.jar

                                                                +

                                                                flink-s3-fs-hadoop-1.12.2.jar

                                                                log4j-slf4j-impl-2.17.1.jar

                                                                +

                                                                log4j-slf4j-impl-2.17.1.jar

                                                                dataflow-fs-obs-2.0.0-20220226.034402-190.jar

                                                                +

                                                                dataflow-fs-obs-2.0.0-20220226.034402-190.jar

                                                                flink-shaded-zookeeper-3.6.3-ei-313001-SNAPSHOT.jar

                                                                +

                                                                flink-shaded-zookeeper-3.6.3-ei-313001-SNAPSHOT.jar

                                                                luxor-encrypt-2.0.0-20220405.072004-199.jar

                                                                +

                                                                luxor-encrypt-2.0.0-20220405.072004-199.jar

                                                                deeplearning4j-core-0.9.1.jar

                                                                +

                                                                deeplearning4j-core-0.9.1.jar

                                                                flink-sql-avro-1.12.2-ei-313001-dli-2022011002.jar

                                                                +

                                                                flink-sql-avro-1.12.2-ei-313001-dli-2022011002.jar

                                                                luxor-fs3-2.0.0-20220405.072025-195.jar

                                                                +

                                                                luxor-fs3-2.0.0-20220405.072025-195.jar

                                                                deeplearning4j-nlp-0.9.1.jar

                                                                +

                                                                deeplearning4j-nlp-0.9.1.jar

                                                                flink-sql-avro-confluent-registry-1.12.2-ei-313001-dli-2022011002.jar

                                                                +

                                                                flink-sql-avro-confluent-registry-1.12.2-ei-313001-dli-2022011002.jar

                                                                luxor-obs-fs3-2.0.0-20220405.072030-195.jar

                                                                +

                                                                luxor-obs-fs3-2.0.0-20220405.072030-195.jar

                                                                deeplearning4j-nn-0.9.1.jar

                                                                +

                                                                deeplearning4j-nn-0.9.1.jar

                                                                flink-table_2.11-1.12.2-ei-313001-dli-2022011002.jar

                                                                +

                                                                flink-table_2.11-1.12.2-ei-313001-dli-2022011002.jar

                                                                manager-hadoop-security-crypter-8.1.3-313001-SNAPSHOT.jar

                                                                +

                                                                manager-hadoop-security-crypter-8.1.3-313001-SNAPSHOT.jar

                                                                ejml-cdense-0.33.jar

                                                                +

                                                                ejml-cdense-0.33.jar

                                                                flink-table-blink_2.11-1.12.2-ei-313001-dli-2022011002.jar

                                                                +

                                                                flink-table-blink_2.11-1.12.2-ei-313001-dli-2022011002.jar

                                                                manager-wc2frm-8.1.3-313001-SNAPSHOT.jar

                                                                +

                                                                manager-wc2frm-8.1.3-313001-SNAPSHOT.jar

                                                                ejml-core-0.33.jar

                                                                +

                                                                ejml-core-0.33.jar

                                                                guava-18.0.jar

                                                                +

                                                                guava-18.0.jar

                                                                mrs-obs-provider-3.1.1.49.jar

                                                                +

                                                                mrs-obs-provider-3.1.1.49.jar

                                                                ejml-ddense-0.33.jar

                                                                +

                                                                ejml-ddense-0.33.jar

                                                                guava-26.0-jre.jar

                                                                +

                                                                guava-26.0-jre.jar

                                                                nd4j-api-0.9.1.jar

                                                                +

                                                                nd4j-api-0.9.1.jar

                                                                ejml-dsparse-0.33.jar

                                                                +

                                                                ejml-dsparse-0.33.jar

                                                                hadoop-hdfs-client-3.1.1-ei-302002.jar

                                                                +

                                                                hadoop-hdfs-client-3.1.1-ei-302002.jar

                                                                nd4j-native-0.9.1.jar

                                                                +

                                                                nd4j-native-0.9.1.jar

                                                                ejml-experimental-0.33.jar

                                                                +

                                                                ejml-experimental-0.33.jar

                                                                hadoop-3.1.1-46.jar

                                                                +

                                                                hadoop-3.1.1-46.jar

                                                                nd4j-native-api-0.9.1.jar

                                                                +

                                                                nd4j-native-api-0.9.1.jar

                                                                ejml-fdense-0.33.jar

                                                                +

                                                                ejml-fdense-0.33.jar

                                                                hadoop-plugins-8.1.3-313001-SNAPSHOT.jar

                                                                +

                                                                hadoop-plugins-8.1.3-313001-SNAPSHOT.jar

                                                                nd4j-native-platform-0.9.1.jar

                                                                +

                                                                nd4j-native-platform-0.9.1.jar

                                                                ejml-simple-0.33.jar

                                                                +

                                                                ejml-simple-0.33.jar

                                                                httpasyncclient-4.1.2.jar

                                                                +

                                                                httpasyncclient-4.1.2.jar

                                                                okhttp-3.14.8.jar

                                                                +

                                                                okhttp-3.14.8.jar

                                                                ejml-zdense-0.33.jar

                                                                +

                                                                ejml-zdense-0.33.jar

                                                                httpclient-4.5.3.jar

                                                                +

                                                                httpclient-4.5.3.jar

                                                                okio-1.14.0.jar

                                                                +

                                                                okio-1.14.0.jar

                                                                elsa-3.0.0-M7.jar

                                                                +

                                                                elsa-3.0.0-M7.jar

                                                                httpcore-4.4.4.jar

                                                                +

                                                                httpcore-4.4.4.jar

                                                                ranger-obs-client-0.1.1.jar

                                                                +

                                                                ranger-obs-client-0.1.1.jar

                                                                flink-changelog-json-1.12.2-ei-313001-dli-2022011002.jar

                                                                +

                                                                flink-changelog-json-1.12.2-ei-313001-dli-2022011002.jar

                                                                httpcore-nio-4.4.4.jar

                                                                +

                                                                httpcore-nio-4.4.4.jar

                                                                secComponentApi-1.0.5.jar

                                                                +

                                                                secComponentApi-1.0.5.jar

                                                                flink-csv-1.12.2-ei-313001-dli-2022011002.jar

                                                                +

                                                                flink-csv-1.12.2-ei-313001-dli-2022011002.jar

                                                                java-xmlbuilder-1.1.jar

                                                                +

                                                                java-xmlbuilder-1.1.jar

                                                                slf4j-api-1.7.26.jar

                                                                +

                                                                slf4j-api-1.7.26.jar

                                                                flink-dist_2.11-1.12.2-ei-313001-dli-2022011002.jar

                                                                +

                                                                flink-dist_2.11-1.12.2-ei-313001-dli-2022011002.jar

                                                                jna-4.1.0.jar

                                                                +

                                                                jna-4.1.0.jar

                                                                tensorflow-1.12.0.jar

                                                                +

                                                                tensorflow-1.12.0.jar
                                                                Table 5 Flink 1.10 dependencies

                                                                Dependency

                                                                +
                                                                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -2840,120 +3885,120 @@

                                                                Flink 1.7.2 Dependencies

                                                                -
                                                                Table 6 Flink 1.10 dependencies

                                                                Dependency

                                                                bcpkix-jdk15on-1.60.jar

                                                                +

                                                                bcpkix-jdk15on-1.60.jar

                                                                esdk-obs-java-3.20.6.1.jar

                                                                +

                                                                esdk-obs-java-3.20.6.1.jar

                                                                java-xmlbuilder-1.1.jar

                                                                +

                                                                java-xmlbuilder-1.1.jar

                                                                bcprov-jdk15on-1.60.jar

                                                                +

                                                                bcprov-jdk15on-1.60.jar

                                                                flink-cep_2.11-1.10.0.jar

                                                                +

                                                                flink-cep_2.11-1.10.0.jar

                                                                jna-4.1.0.jar

                                                                +

                                                                jna-4.1.0.jar

                                                                commons-codec-1.9.jar

                                                                +

                                                                commons-codec-1.9.jar

                                                                flink-cep-scala_2.11-1.10.0.jar

                                                                +

                                                                flink-cep-scala_2.11-1.10.0.jar

                                                                libtensorflow-1.12.0.jar

                                                                +

                                                                libtensorflow-1.12.0.jar

                                                                commons-configuration-1.7.jar

                                                                +

                                                                commons-configuration-1.7.jar

                                                                flink-dist_2.11-1.10.0.jar

                                                                +

                                                                flink-dist_2.11-1.10.0.jar

                                                                log4j-over-slf4j-1.7.26.jar

                                                                +

                                                                log4j-over-slf4j-1.7.26.jar

                                                                deeplearning4j-core-0.9.1.jar

                                                                +

                                                                deeplearning4j-core-0.9.1.jar

                                                                flink-python_2.11-1.10.0.jar

                                                                +

                                                                flink-python_2.11-1.10.0.jar

                                                                logback-classic-1.2.3.jar

                                                                +

                                                                logback-classic-1.2.3.jar

                                                                deeplearning4j-nlp-0.9.1.jar

                                                                +

                                                                deeplearning4j-nlp-0.9.1.jar

                                                                flink-queryable-state-runtime_2.11-1.10.0.jar

                                                                +

                                                                flink-queryable-state-runtime_2.11-1.10.0.jar

                                                                logback-core-1.2.3.jar

                                                                +

                                                                logback-core-1.2.3.jar

                                                                deeplearning4j-nn-0.9.1.jar

                                                                +

                                                                deeplearning4j-nn-0.9.1.jar

                                                                flink-sql-client_2.11-1.10.0.jar

                                                                +

                                                                flink-sql-client_2.11-1.10.0.jar

                                                                nd4j-api-0.9.1.jar

                                                                +

                                                                nd4j-api-0.9.1.jar

                                                                ejml-cdense-0.33.jar

                                                                +

                                                                ejml-cdense-0.33.jar

                                                                flink-state-processor-api_2.11-1.10.0.jar

                                                                +

                                                                flink-state-processor-api_2.11-1.10.0.jar

                                                                nd4j-native-0.9.1.jar

                                                                +

                                                                nd4j-native-0.9.1.jar

                                                                ejml-core-0.33.jar

                                                                +

                                                                ejml-core-0.33.jar

                                                                flink-table_2.11-1.10.0.jar

                                                                +

                                                                flink-table_2.11-1.10.0.jar

                                                                nd4j-native-api-0.9.1.jar

                                                                +

                                                                nd4j-native-api-0.9.1.jar

                                                                ejml-ddense-0.33.jar

                                                                +

                                                                ejml-ddense-0.33.jar

                                                                flink-table-blink_2.11-1.10.0.jar

                                                                +

                                                                flink-table-blink_2.11-1.10.0.jar

                                                                nd4j-native-platform-0.9.1.jar

                                                                +

                                                                nd4j-native-platform-0.9.1.jar

                                                                ejml-dsparse-0.33.jar

                                                                +

                                                                ejml-dsparse-0.33.jar

                                                                guava-26.0-jre.jar

                                                                +

                                                                guava-26.0-jre.jar

                                                                okhttp-3.14.8.jar

                                                                +

                                                                okhttp-3.14.8.jar

                                                                ejml-experimental-0.33.jar

                                                                +

                                                                ejml-experimental-0.33.jar

                                                                hadoop-3.1.1-41.jar

                                                                +

                                                                hadoop-3.1.1-41.jar

                                                                okio-1.14.0.jar

                                                                +

                                                                okio-1.14.0.jar

                                                                ejml-fdense-0.33.jar

                                                                +

                                                                ejml-fdense-0.33.jar

                                                                httpasyncclient-4.1.2.jar

                                                                +

                                                                httpasyncclient-4.1.2.jar

                                                                secComponentApi-1.0.5.jar

                                                                +

                                                                secComponentApi-1.0.5.jar

                                                                ejml-simple-0.33.jar

                                                                +

                                                                ejml-simple-0.33.jar

                                                                httpclient-4.5.3.jar

                                                                +

                                                                httpclient-4.5.3.jar

                                                                slf4j-api-1.7.26.jar

                                                                +

                                                                slf4j-api-1.7.26.jar

                                                                ejml-zdense-0.33.jar

                                                                +

                                                                ejml-zdense-0.33.jar

                                                                httpcore-4.4.4.jar

                                                                +

                                                                httpcore-4.4.4.jar

                                                                tensorflow-1.12.0.jar

                                                                +

                                                                tensorflow-1.12.0.jar

                                                                elsa-3.0.0-M7.jar

                                                                +

                                                                elsa-3.0.0-M7.jar

                                                                httpcore-nio-4.4.4.jar

                                                                +

                                                                httpcore-nio-4.4.4.jar

                                                                -

                                                                +

                                                                -
                                                                Table 6 Flink 1.7.2 dependencies

                                                                Dependency

                                                                +
                                                                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/dli/umn/dli_01_0402.html b/docs/dli/umn/dli_01_0402.html index f70473ad4..49054fe44 100644 --- a/docs/dli/umn/dli_01_0402.html +++ b/docs/dli/umn/dli_01_0402.html @@ -1,6 +1,6 @@ -

                                                                Submitting a SQL Job Using DLI

                                                                +

                                                                Submitting a SQL Job on the DLI Management Console

                                                                diff --git a/docs/dli/umn/dli_01_0407.html b/docs/dli/umn/dli_01_0407.html index 4df8604a1..bc7d05ab3 100644 --- a/docs/dli/umn/dli_01_0407.html +++ b/docs/dli/umn/dli_01_0407.html @@ -3,9 +3,9 @@

                                                                Package Management Overview

                                                                Before running DLI jobs, UDF JAR files or Jar job packages need to be uploaded to the cloud platform for unified management and maintenance.

                                                                There are two ways to manage packages:

                                                                -
                                                                • (Recommended) Upload packages to OBS: Upload Jar packages to an OBS bucket in advance and select the OBS path when configuring a job.
                                                                • Upload packages to DLI: Upload Jar packages to an OBS bucket in advance, create a package on the Data Management > Package Management page of the DLI management console, and select the DLI package when configuring a job.
                                                                +
                                                                • (Recommended) Upload packages to OBS: Upload Jar packages to an OBS bucket in advance and select the OBS path when configuring a job.
                                                                • The DLI package function will soon be discontinued. Upload packages to DLI: Upload Jar packages to an OBS bucket in advance, create a package on the Data Management > Package Management page of the DLI management console, and select the DLI package when configuring a job.

                                                                This section describes how to upload and manage packages on the DLI management console.

                                                                -
                                                                • When using Spark 3.3.1 or later or Flink1.15 or later to run jobs, you are advised to select packages stored in OBS.
                                                                • When packaging Spark or Flink Jar jobs, do not upload the dependency packages that the platform already has to avoid conflicts with the built-in dependency packages of the platform. Refer to DLI Built-in Dependencies for built-in dependency packages.
                                                                +
                                                                • The DLI package function will soon be discontinued. When using Spark 3.3.1 or later or Flink 1.15 or later to run jobs, you are advised to select packages stored in OBS.
                                                                • When packaging Spark or Flink Jar jobs, do not upload the dependency packages that the platform already has to avoid conflicts with the built-in dependency packages of the platform. Refer to DLI Built-in Dependencies for built-in dependency packages.

                                                                Notes and Constraints

                                                                Table 7 Flink 1.7.2 dependencies

                                                                Dependency

                                                                bcpkix-jdk15on-1.60.jar

                                                                +

                                                                bcpkix-jdk15on-1.60.jar

                                                                esdk-obs-java-3.1.3.jar

                                                                +

                                                                esdk-obs-java-3.1.3.jar

                                                                httpcore-4.4.4.jar

                                                                +

                                                                httpcore-4.4.4.jar

                                                                bcprov-jdk15on-1.60.jar

                                                                +

                                                                bcprov-jdk15on-1.60.jar

                                                                flink-cep_2.11-1.7.0.jar

                                                                +

                                                                flink-cep_2.11-1.7.0.jar

                                                                httpcore-nio-4.4.4.jar

                                                                +

                                                                httpcore-nio-4.4.4.jar

                                                                commons-codec-1.9.jar

                                                                +

                                                                commons-codec-1.9.jar

                                                                flink-cep-scala_2.11-1.7.0.jar

                                                                +

                                                                flink-cep-scala_2.11-1.7.0.jar

                                                                java-xmlbuilder-1.1.jar

                                                                +

                                                                java-xmlbuilder-1.1.jar

                                                                commons-configuration-1.7.jar

                                                                +

                                                                commons-configuration-1.7.jar

                                                                flink-dist_2.11-1.7.0.jar

                                                                +

                                                                flink-dist_2.11-1.7.0.jar

                                                                jna-4.1.0.jar

                                                                +

                                                                jna-4.1.0.jar

                                                                deeplearning4j-core-0.9.1.jar

                                                                +

                                                                deeplearning4j-core-0.9.1.jar

                                                                flink-gelly_2.11-1.7.0.jar

                                                                +

                                                                flink-gelly_2.11-1.7.0.jar

                                                                libtensorflow-1.12.0.jar

                                                                +

                                                                libtensorflow-1.12.0.jar

                                                                deeplearning4j-nlp-0.9.1.jar

                                                                +

                                                                deeplearning4j-nlp-0.9.1.jar

                                                                flink-gelly-scala_2.11-1.7.0.jar

                                                                +

                                                                flink-gelly-scala_2.11-1.7.0.jar

                                                                log4j-over-slf4j-1.7.21.jar

                                                                +

                                                                log4j-over-slf4j-1.7.21.jar

                                                                deeplearning4j-nn-0.9.1.jar

                                                                +

                                                                deeplearning4j-nn-0.9.1.jar

                                                                flink-ml_2.11-1.7.0.jar

                                                                +

                                                                flink-ml_2.11-1.7.0.jar

                                                                logback-classic-1.2.3.jar

                                                                +

                                                                logback-classic-1.2.3.jar

                                                                ejml-cdense-0.33.jar

                                                                +

                                                                ejml-cdense-0.33.jar

                                                                flink-python_2.11-1.7.0.jar

                                                                +

                                                                flink-python_2.11-1.7.0.jar

                                                                logback-core-1.2.3.jar

                                                                +

                                                                logback-core-1.2.3.jar

                                                                ejml-core-0.33.jar

                                                                +

                                                                ejml-core-0.33.jar

                                                                flink-queryable-state-runtime_2.11-1.7.0.jar

                                                                +

                                                                flink-queryable-state-runtime_2.11-1.7.0.jar

                                                                nd4j-api-0.9.1.jar

                                                                +

                                                                nd4j-api-0.9.1.jar

                                                                ejml-ddense-0.33.jar

                                                                +

                                                                ejml-ddense-0.33.jar

                                                                flink-shaded-curator-1.7.0.jar

                                                                +

                                                                flink-shaded-curator-1.7.0.jar

                                                                nd4j-native-0.9.1.jar

                                                                +

                                                                nd4j-native-0.9.1.jar

                                                                ejml-dsparse-0.33.jar

                                                                +

                                                                ejml-dsparse-0.33.jar

                                                                flink-shaded-hadoop2-uber-1.7.0.jar

                                                                +

                                                                flink-shaded-hadoop2-uber-1.7.0.jar

                                                                nd4j-native-api-0.9.1.jar

                                                                +

                                                                nd4j-native-api-0.9.1.jar

                                                                ejml-experimental-0.33.jar

                                                                +

                                                                ejml-experimental-0.33.jar

                                                                flink-table_2.11-1.7.0.jar

                                                                +

                                                                flink-table_2.11-1.7.0.jar

                                                                nd4j-native-platform-0.9.1.jar

                                                                +

                                                                nd4j-native-platform-0.9.1.jar

                                                                ejml-fdense-0.33.jar

                                                                +

                                                                ejml-fdense-0.33.jar

                                                                guava-26.0-jre.jar

                                                                +

                                                                guava-26.0-jre.jar

                                                                okhttp-3.14.8.jar

                                                                +

                                                                okhttp-3.14.8.jar

                                                                ejml-simple-0.33.jar

                                                                +

                                                                ejml-simple-0.33.jar

                                                                hadoop-3.1.1-41-20201014.085840-4.jar

                                                                +

                                                                hadoop-3.1.1-41-20201014.085840-4.jar

                                                                okio-1.14.0.jar

                                                                +

                                                                okio-1.14.0.jar

                                                                ejml-zdense-0.33.jar

                                                                +

                                                                ejml-zdense-0.33.jar

                                                                httpasyncclient-4.1.2.jar

                                                                +

                                                                httpasyncclient-4.1.2.jar

                                                                slf4j-api-1.7.21.jar

                                                                +

                                                                slf4j-api-1.7.21.jar

                                                                elsa-3.0.0-M7.jar

                                                                +

                                                                elsa-3.0.0-M7.jar

                                                                httpclient-4.5.12.jar

                                                                +

                                                                httpclient-4.5.12.jar

                                                                tensorflow-1.12.0.jar

                                                                +

                                                                tensorflow-1.12.0.jar
                                                                Table 1 Notes and constraints on package usage

                                                                Item

                                                                diff --git a/docs/dli/umn/dli_01_0408.html b/docs/dli/umn/dli_01_0408.html index 92875a062..2ed47b89b 100644 --- a/docs/dli/umn/dli_01_0408.html +++ b/docs/dli/umn/dli_01_0408.html @@ -1,18 +1,17 @@ -

                                                                Permissions Management

                                                                -
                                                                +

                                                                DLI Permission Management

                                                                +

                                                                +
                                                                diff --git a/docs/dli/umn/dli_01_0410.html b/docs/dli/umn/dli_01_0410.html index f20ea2504..51ac7cead 100644 --- a/docs/dli/umn/dli_01_0410.html +++ b/docs/dli/umn/dli_01_0410.html @@ -6,7 +6,7 @@

                                                                Notes

                                                                • Flink jobs can directly access DIS, OBS, and SMN data sources without using datasource connections.
                                                                • You are advised to use enhanced datasource connections to connect DLI to data sources.
                                                                -

                                                                DLI Supported Data Sources

                                                                Table 1 lists the data sources supported by DLI. For how to use the data sources, see the Data Lake Insight SQL Syntax Reference.

                                                                +

                                                                DLI Supported Data Sources

                                                                Table 1 lists the data sources supported by DLI. For how to use the data sources, see Data Lake Insight SQL Syntax Reference.

                                                                @@ -64,7 +64,7 @@ - diff --git a/docs/dli/umn/dli_01_0417.html b/docs/dli/umn/dli_01_0417.html index 07c4eb9e3..d458eadea 100644 --- a/docs/dli/umn/dli_01_0417.html +++ b/docs/dli/umn/dli_01_0417.html @@ -1,86 +1,58 @@ -

                                                                DLI Resources

                                                                -

                                                                A resource is an object that exists within a service. You can select DLI resources by specifying their paths.

                                                                +

                                                                Overview

                                                                +

                                                                IAM is a foundational service for permission management, offering functions like user identity authentication, permission allocation, and access control, enabling you to securely manage access to cloud resources and perform fine-grained permission management.

                                                                +

                                                                IAM Authorization Types and Use Cases

                                                                IAM can authorize different enterprise users to access cloud service resources. For example, if there are employees responsible for data analysis within your organization whom you wish to have usage permissions for DLI compute resources but not the permission to perform high-risk operations such as deleting DLI resources, you can use IAM for permission allocation. By granting users the ability to only use DLI resources without allowing them to delete these resources, you can control their access to DLI resources.

                                                                +

                                                                For newly created users, they must first log in to DLI once to record metadata before being able to use DLI.

                                                                -
                                                                Table 1 Supported data sources

                                                                Service

                                                                √

                                                                DMS Kafka

                                                                +

                                                                DMS for Kafka

                                                                x

                                                                Table 1 DLI resources and their paths

                                                                Resource Type

                                                                +
                                                                - - + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                                                Table 1 IAM authorization types

                                                                Type

                                                                Resource Names

                                                                +

                                                                Core Relationship

                                                                Path

                                                                +

                                                                Permission

                                                                +

                                                                Authorization Method

                                                                +

                                                                Use Case

                                                                queue

                                                                +

                                                                Role/Policy-based authorization

                                                                DLI queue

                                                                +

                                                                User-permission-authorization scope

                                                                queues.queuename

                                                                +
                                                                • System-defined role
                                                                • System-defined policy
                                                                • Custom policy

                                                                database

                                                                +

                                                                Assigning roles or policies to principals

                                                                DLI database

                                                                -

                                                                databases.dbname

                                                                -

                                                                table

                                                                -

                                                                DLI table

                                                                -

                                                                databases.dbname.tables.tbname

                                                                -

                                                                column

                                                                -

                                                                DLI column

                                                                -

                                                                databases.dbname.tables.tbname.columns.colname

                                                                -

                                                                jobs

                                                                -

                                                                DLI Flink job

                                                                -

                                                                jobs.flink.jobid

                                                                -

                                                                resource

                                                                -

                                                                DLI package

                                                                -

                                                                resources.resourcename

                                                                -

                                                                group

                                                                -

                                                                DLI package group

                                                                -

                                                                groups.groupname

                                                                -

                                                                datasourceauth

                                                                -

                                                                DLI cross-source authentication information

                                                                -

                                                                datasourceauth.name

                                                                -

                                                                edsconnections

                                                                -

                                                                Enhanced datasource connection

                                                                -

                                                                edsconnections.connection ID

                                                                +

                                                                To authorize a user, you need to add it to a user group first and then specify the scope of authorization. It provides a limited number of condition keys and cannot meet the requirements of fine-grained permissions control. This method is suitable for small- and medium-sized enterprises.
                                                                +

                                                                IAM is free to use, and you only need to pay for the resources in your account.

                                                                +

                                                                If your account does not need individual IAM users for permission management, skip over this section.

                                                                + +

                                                                DLI System Permissions

                                                                Table 2 lists all system-defined permissions for DLI.

                                                                + +
                                                                + + + + + +
                                                                Table 2 DLI system permissions

                                                                Type

                                                                +

                                                                System-defined permissions for role/policy-based authorization

                                                                +
                                                                +
                                                                +
                                                                Permission types: Based on the granularity of authorization, they are divided into roles and policies.
                                                                • Roles: A coarse-grained authorization strategy that defines permissions by job responsibility. This strategy offers limited service-level roles for authorization. Cloud services are interdependent. When you assign permissions using roles, you also need to attach any existing role dependencies. Roles are not suitable for fine-grained authorization and least privilege access.
                                                                • Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This strategy is more flexible and ideal for least privilege access. For example, you can grant IAM users only permissions to manage DLI resources of a certain type.
                                                                +
                                                                +
                                                                -
                                                                Parent topic: Permissions Management
                                                                +
                                                                Parent topic: IAM Permission Management
                                                                diff --git a/docs/dli/umn/dli_01_0418.html b/docs/dli/umn/dli_01_0418.html index 5800d891c..fc7663ce3 100644 --- a/docs/dli/umn/dli_01_0418.html +++ b/docs/dli/umn/dli_01_0418.html @@ -1,19 +1,54 @@

                                                                Creating an IAM User and Granting Permissions

                                                                -

                                                                You can use Identity and Access Management (IAM) to implement fine-grained permissions control on DLI resources. For details, see Overview.

                                                                +

                                                                You can use Identity and Access Management (IAM) to implement fine-grained permissions management for your DLI resources. For details, see Overview.

                                                                If your cloud account does not need individual IAM users, then you may skip over this section.

                                                                This section describes how to create an IAM user and grant DLI permissions to the user. Figure 1 shows the procedure.

                                                                -

                                                                Prerequisites

                                                                Before assigning permissions to user groups, you should learn about system policies and select the policies based on service requirements. For details about system permissions supported by DLI, see DLI System Permissions.

                                                                +

                                                                Prerequisites

                                                                Before granting permissions to a user group, familiarize yourself with the DLI permissions that can be added to the user group and select them as needed.

                                                                +
                                                                +

                                                                Process Flow

                                                                Figure 1 Process for granting DLI permissions
                                                                + +
                                                                + + + + + + + + + + + + + + + + + + + + + +
                                                                Table 1 Procedure

                                                                No.

                                                                +

                                                                Step

                                                                +

                                                                Description

                                                                +

                                                                1

                                                                +

                                                                Create a user group and grant permissions to it.

                                                                +

                                                                Create a user group on the IAM console and grant the DLI ReadOnlyAccess permission to it.

                                                                +

                                                                2

                                                                +

                                                                Create a user and add them to the user group.

                                                                +

                                                                Create a user on the IAM console and add them to the created user group.

                                                                +

                                                                3

                                                                +

                                                                Log in as the IAM user and verify permissions.

                                                                +

                                                                Log in to the console using the newly created user, switch to the authorized region, and verify permissions.

                                                                +
                                                                • Choose Service List > Data Lake Insight. If you can view the elastic resource pool list on the Resources > Resource Pool page but cannot purchase an elastic resource pool by clicking Buy Resource Pool in the upper right corner (assuming the current permission includes only DLI ReadOnlyAccess), the DLI ReadOnlyAccess permission has already taken effect.
                                                                • Choose any other service in Service List. If a message appears indicating that you have insufficient permissions to access the service, the DLI ReadOnlyAccess permission has already taken effect.
                                                                +

                                                                4

                                                                +

                                                                Create a custom policy and associate it with the user group.

                                                                +

                                                                If the predefined DLI permissions in the system do not meet your authorization requirements, you can create custom policies.

                                                                +

                                                                For details about how to create a custom policy, see Creating a Custom Policy.

                                                                +
                                                                -

                                                                Process Flow

                                                                Figure 1 Process for granting DLI permissions
                                                                -

                                                                -

                                                                -
                                                                1. Create a user group and grant the permission to it.

                                                                  Create a user group on the IAM console and grant the DLI ReadOnlyAccess permission to it.

                                                                  -
                                                                2. Create a user and add the user to the user group.

                                                                  Create a user on the IAM console and add the user to the group created in 1.

                                                                  -
                                                                3. Log in and verify the permission.

                                                                  Log in to the management console using the newly created user, and verify that the user's permissions.

                                                                  -
                                                                  • Choose Service List > Data Lake Insight. The DLI management console is displayed. If you can view the queue list on the Queue Management page but cannot buy DLI queues by clicking Buy Queue in the upper right corner (assume that the current permission contains only DLI ReadOnlyAccess), the DLI ReadOnlyAccess permission has taken effect.
                                                                  • Choose any other service in Service List. If a message appears indicating that you have insufficient permissions to access the service, the DLI ReadOnlyAccess permission has already taken effect.
                                                                  -
                                                                @@ -22,3 +57,10 @@
                                                                + + \ No newline at end of file diff --git a/docs/dli/umn/dli_01_0419.html b/docs/dli/umn/dli_01_0419.html index a76418ab3..af99864eb 100644 --- a/docs/dli/umn/dli_01_0419.html +++ b/docs/dli/umn/dli_01_0419.html @@ -3,7 +3,7 @@

                                                                DLI Agency Overview

                                                                What Is an Agency?

                                                                Cloud services often interact with each other, with some of which dependent on other services. You can create an agency to delegate DLI to use other cloud services and perform resource O&M on your behalf.

                                                                For example, the AK/SK required by DLI Flink jobs is stored in DEW. To allow DLI to access DEW data during job execution, you need to provide an IAM agency to delegate the permissions to perform operations on DEW data to DLI.

                                                                -
                                                                Figure 1 DLI service agency
                                                                +
                                                                Figure 1 DLI service agency

                                                                DLI Agencies

                                                                Before using DLI, you are advised to set up DLI agency permissions to ensure the proper functioning of DLI.

                                                                • By default, DLI provides the following agencies: dli_admin_agency, dli_management_agency, and dli_data_clean_agency. The names of these agencies are fixed, but the permissions contained in them can be customized. In other scenarios, you need to create custom agencies. For details about the agencies, see Table 1.
                                                                • DLI upgrades dli_admin_agency to dli_management_agency to meet the demand for fine-grained agency permissions management. The new agency has the necessary permissions for datasource operations, notifications, and user authorization operations. For details, see Configuring DLI Agency Permissions.
                                                                • To use Flink 1.15, Spark 3.3.1 (Spark general queue scenario), or a later version to execute jobs, perform the following operations:
                                                                  Create an agency on the IAM console and add the agency information to the job configuration. For details, see Creating a Custom DLI Agency.
                                                                  • Common scenarios for creating an agency: DLI is allowed to read and write data from and to OBS, dump logs, and read and write Flink checkpoints. DLI is allowed to access DEW to obtain data access credentials and access catalogs to obtain metadata.
                                                                  • You cannot use the default agency names dli_admin_agency, dli_management_agency, or dli_data_clean_agency. It must be unique.
                                                                  @@ -13,7 +13,7 @@
                                                                  • Only the tenant account or a member account of user group admin can authorize the service.
                                                                  • Do not delete the agency created by the system by default.
                                                                  -
                                                                  Table 1 DLI agencies

                                                                  Permission

                                                                  +
                                                                  @@ -25,7 +25,7 @@ - @@ -91,3 +91,10 @@ + + \ No newline at end of file diff --git a/docs/dli/umn/dli_01_0427.html b/docs/dli/umn/dli_01_0427.html index edeeb87fd..da72a3e40 100644 --- a/docs/dli/umn/dli_01_0427.html +++ b/docs/dli/umn/dli_01_0427.html @@ -11,7 +11,7 @@
                                                                • Upload the authentication credential to the OBS bucket.

                                                                • Create a datasource authentication.
                                                                  1. Log in to the DLI management console.
                                                                  2. Choose Datasource Connections. On the page displayed, click Datasource Authentication.
                                                                  3. Click Create.

                                                                    Configure CSS authentication parameters according to Table 1.

                                                                    -
                                                                  • Table 1 DLI agencies

                                                                  Agency

                                                                  Type

                                                                  Default agency

                                                                  This agency has been discarded and is not recommended. Upgrade the agency to dli_management_agency as soon as possible.

                                                                  +

                                                                  This agency has been deprecated and is not recommended. Upgrade the agency to dli_management_agency as soon as possible.

                                                                  For details about how to update an agency, see Configuring DLI Agency Permissions.
                                                                  Table 1 Parameters

                                                                  Parameter

                                                                  +
                                                                  @@ -19,8 +19,8 @@ -
                                                                  Table 1 Parameter descriptions

                                                                  Parameter

                                                                  Description

                                                                  Authentication Certificate

                                                                  Name of the datasource authentication information to be created.

                                                                  -
                                                                  • The name can contain only digits, letters, and underscores (_), but cannot contain only digits or start with an underscore (_).
                                                                  • The length of the database name cannot exceed 128 characters.
                                                                  • It is recommended that the name contain the CSS security cluster name to distinguish security authentication information of different clusters.
                                                                  +

                                                                  Name of the datasource authentication to be created.

                                                                  +
                                                                  • The name can contain only digits, letters, and underscores (_), but cannot contain only digits or start with an underscore (_).
                                                                  • The value can contain a maximum of 128 characters.
                                                                  • It is recommended that the name contain the CSS security cluster name to distinguish security authentication information of different clusters.

                                                                  Type

                                                                  diff --git a/docs/dli/umn/dli_01_0440.html b/docs/dli/umn/dli_01_0440.html index b37f04734..3b2be826f 100644 --- a/docs/dli/umn/dli_01_0440.html +++ b/docs/dli/umn/dli_01_0440.html @@ -1,191 +1,110 @@ -

                                                                  Overview

                                                                  -

                                                                  DLI has a comprehensive permission control mechanism and supports fine-grained authentication through Identity and Access Management (IAM). You can create policies in IAM to manage DLI permissions. You can use both the DLI's permission control mechanism and the IAM service for permission management.

                                                                  -

                                                                  Application Scenarios of IAM Authentication

                                                                  When using DLI on the cloud, enterprise users need to manage DLI resources (queues) used by employees in different departments, including creating, deleting, using, and isolating resources. In addition, data of different departments needs to be managed, including data isolation and sharing.

                                                                  -

                                                                  DLI uses IAM for refined enterprise-level multi-tenant management. IAM provides identity authentication, permissions management, and access control, helping you securely access to your cloud resources.

                                                                  -

                                                                  With IAM, you can use your account to create IAM users for your employees, and assign permissions to the users to control their access to specific resource types. For example, some software developers in your enterprise need to use DLI resources but must not delete them or perform any high-risk operations. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using DLI resources.

                                                                  -

                                                                  For a new user, you need to log in for the system to record the metadata before using DLI.

                                                                  -
                                                                  -

                                                                  IAM is free to use, and you only need to pay for the resources in your account.

                                                                  -

                                                                  If your account does not need individual IAM users for permissions management, skip over this section.

                                                                  -
                                                                  -

                                                                  DLI System Permissions

                                                                  Table 1 lists all the system-defined roles and policies supported by DLI.

                                                                  -
                                                                  Type: There are roles and policies.
                                                                  • Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. Only a limited number of service-level roles are available. When using roles to grant permissions, you also need to assign other roles on which the permissions depend. However, roles are not an ideal choice for fine-grained authorization and secure access control.
                                                                  • Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant DLI users only the permissions for managing a certain type of ECSs.
                                                                  -
                                                                  +

                                                                  Overview of the DLI Permission System

                                                                  +

                                                                  DLI features two sets of permission systems. These two permission control mechanisms are used in conjunction, with their permissions overlapping and complementing each other to provide a more comprehensive level of access control.

                                                                  -
                                                                  Table 1 DLI system permissions

                                                                  Role/Policy Name

                                                                  +
                                                                  - - - - - - - - - - - - - - - - - - - - -
                                                                  Table 1 DLI permission system types and descriptions

                                                                  Type

                                                                  Description

                                                                  +

                                                                  Description

                                                                  Category

                                                                  -

                                                                  Dependency

                                                                  +

                                                                  Reference

                                                                  DLI FullAccess

                                                                  +

                                                                  DLI permission management

                                                                  Full permissions for DLI.

                                                                  +

                                                                  DLI provides the capability to control resource permissions and resource operation permissions for IAM users, allowing different resources and operation permissions to be granted to various IAM users. For example, a specific IAM user can be granted permission only to query tables, while an administrator user may have multiple operational permissions such as querying tables, deleting tables, and accessing table metadata.

                                                                  +
                                                                  • Resource permission control: Various resources within DLI (such as elastic resource pools, queues, databases, and tables) can be configured with different access permissions. These permissions can be finely tuned down to specific read/write operations. For example, an IAM user can be granted the permission to display a table but not the permission to query it.
                                                                  • Resource operation permission control: DLI also controls the operations that users are permitted to perform. For example, an IAM user might be allowed to query a table but not to add columns to it.

                                                                  System-defined policy

                                                                  -

                                                                  This role depends on other roles in the same project.

                                                                  -
                                                                  • Creating a datasource connection: VPC ReadOnlyAccess
                                                                  • Creating a tag: TMS FullAccess and EPS EPS FullAccess
                                                                  • Using OBS for storage: OBS OperateAccess
                                                                  • Creating an agency: Security Administrator
                                                                  +

                                                                  Overview

                                                                  DLI ReadOnlyAccess

                                                                  +

                                                                  IAM permission management

                                                                  Read-only permissions for DLI.

                                                                  -

                                                                  With read-only permissions, you can use DLI resources and perform operations that do not require fine-grained permissions. For example, create global variables, create packages and package groups, submit jobs to the default queue, create tables in the default database, create datasource connections, and delete datasource connections.

                                                                  +

                                                                  IAM offers the capability for fine-grained permission management, allowing you to create and manage detailed permission policies. These policies can precisely define the operation permissions of users or user groups within DLI. For example, you can create a permission that allows the creation of DLI elastic resource pools, then bind this permission to a specific user group. As a result, all users added to that user group will have the permission to create elastic resource pools.

                                                                  System-defined policy

                                                                  -

                                                                  None

                                                                  -

                                                                  Tenant Administrator

                                                                  -

                                                                  Tenant administrator

                                                                  -
                                                                  • Job execution permissions for DLI resources. After a database or a queue is created, the user can use the ACL to assign rights to other users.
                                                                  • Scope: project-level service
                                                                  -

                                                                  System-defined role

                                                                  -

                                                                  None

                                                                  -

                                                                  DLI Service Administrator

                                                                  -

                                                                  DLI administrator.

                                                                  -
                                                                  • Job execution permissions for DLI resources. After a database or a queue is created, the user can use the ACL to assign rights to other users.
                                                                  • Scope: project-level service
                                                                  -

                                                                  System-defined role

                                                                  -

                                                                  None

                                                                  +

                                                                  Overview
                                                                  -

                                                                  For details, see Creating an IAM User and Granting Permissions.

                                                                  +

                                                                  DLI permission management focuses on the fine-grained control over internal resources and operations within DLI, while IAM permission management emphasizes control from the perspective of identity authentication and global permission policies. By combining both, comprehensive permission management can be achieved, spanning from user identities to specific resource operations.

                                                                  +

                                                                  For example, if user A in group A is granted the permission to delete database resources, but other users in group A do not have this permission, then when granting permissions to group A through IAM, the dli:database:dropDatabase permission for deleting databases would not be included. However, using the table permission management provided by the DLI management console, you can precisely grant only user A the permission to delete databases.

                                                                  +

                                                                  This example illustrates that the scope of the DLI permission system and the IAM authorization system are clearly distinguished, ensuring that these two permission control mechanisms operate independently without interfering with each other.

                                                                  +

                                                                  Basic Principles for Permission Management

                                                                  • Priority principle: If there is an explicit denial (Deny) permission, the authorization result should be denied regardless of other permissions.
                                                                  • Default deny: If there is no explicit allowance (Allow) permission, the authorization result should still be denied even if there is no denial permission.
                                                                  • Explicit allowance: The authorization result is only allowed when there is an explicit allowance permission.
                                                                  -

                                                                  DLI Permission Types

                                                                  Table 2 lists the DLI service permissions. For details about the resources that can be controlled by DLI, see Table 4.

                                                                  - -
                                                                  Table 2 DLI permission types

                                                                  Permission Type

                                                                  +

                                                                  How Does the Access Mechanism Work When There Is a Conflict Between Two Permissions?

                                                                  • When no policy grants the Allow permission, the default condition is to have the Deny permission. The Allow permission can take effect only when there is a policy that grants the Allow permission and no other policies deny this permission.

                                                                    For example, if an Allow permission for creating tables already exists in an IAM authentication policy for a specific database DB1, adding another Allow permission for creating views will stack upon the existing permissions, thereby expanding the user's privileges.

                                                                    +

                                                                    If a new policy is added with a Deny permission for adding or deleting databases, the user permissions will be adjusted according to the Deny precedence rule. Even if the operation permission to delete the database is granted through the DLI console, it will ultimately be overridden by the Deny precedence rule, denying the user the permission to delete the database.

                                                                    +
                                                                  • Based on the principle of least privilege, Deny always takes precedence over Allow.

                                                                    For example, if an IAM user is granted permission to create tables in database DB1 on the DLI console, but the dli:database:createTable Deny permission is added in the IAM authentication policy, meaning the user is prohibited from creating data tables, then the user will ultimately be unable to access those data tables.

                                                                    +
                                                                    Figure 1 Two permission mechanisms of DLI
                                                                    +
                                                                  +
                                                                  +

                                                                  Permission Management Methods Supported by Different DLI Resource Types

                                                                  DLI SQL resources are resources that can be created using SQL statements, such as databases and tables. To use SQL resources, you need to have both SQL operation permissions and SQL resource permissions. The SQL operation permissions grant the relevant permissions for using the DLI APIs associated with this type of resource.

                                                                  +
                                                                  • SQL resources: Metadata, databases, tables (including views), and columns.

                                                                    Before submitting a DLI job, you must pre-grant IAM users the necessary permissions to access DLI metadata, databases, tables, and columns. This ensures that the job can smoothly access the required data and resources during execution.

                                                                    +
                                                                  • Other DLI resources: Queues, elastic resource pools, jobs, global variables, packages, enhanced datasource connections, and datasource authentication. +
                                                                    - - - - - - - - + + + - - - - - - - - - - - - - - - - - - - - - - - -
                                                                    Table 2 Permission management methods supported by different DLI resource types

                                                                    Resource Type

                                                                    Subtype

                                                                    +

                                                                    Authorization Type

                                                                    Console Operations

                                                                    +

                                                                    Spark 2.x

                                                                    SQL Syntax

                                                                    +

                                                                    Spark 3.3.x

                                                                    Queue Permissions

                                                                    +

                                                                    SQL resource

                                                                    Queue management permissions

                                                                    +

                                                                    IAM fine-grained authorization (role or policy-based authorization)

                                                                    For details, see Queue Permission Management.

                                                                    +

                                                                    Supported

                                                                    None

                                                                    +

                                                                    Supported

                                                                    Queue usage permission

                                                                    +

                                                                    SQL resource

                                                                    +

                                                                    DLI resource authorization

                                                                    +

                                                                    Supported

                                                                    +

                                                                    Supported

                                                                    Data Permissions

                                                                    +

                                                                    Other DLI resource

                                                                    Database permissions

                                                                    +

                                                                    IAM fine-grained authorization (role or policy-based authorization)

                                                                    For details, see Configuring Database Permissions on the DLI Console and Configuring Table Permissions on the DLI Console.

                                                                    +

                                                                    Supported

                                                                    For details, see SQL Syntax of Batch Jobs > Data Permissions Management > Data Permissions List in the Data Lake Insight SQL Syntax Reference.

                                                                    +

                                                                    Supported

                                                                    Table permissions

                                                                    +

                                                                    Other DLI resource

                                                                    Column permissions

                                                                    +

                                                                    DLI resource authorization

                                                                    Job Permissions

                                                                    +

                                                                    Supported

                                                                    Flink job permissions

                                                                    -

                                                                    For details, see Configuring Flink Job Permissions.

                                                                    -

                                                                    None

                                                                    -

                                                                    Package Permissions

                                                                    -

                                                                    -

                                                                    Package group permissions

                                                                    -

                                                                    For details, see Configuring DLI Package Permissions.

                                                                    -

                                                                    None

                                                                    -

                                                                    Package permissions

                                                                    -

                                                                    Datasource Connection Permissions

                                                                    -

                                                                    Datasource connection permissions

                                                                    -

                                                                    For details, see Datasource Authentication Permission Management.

                                                                    -

                                                                    None

                                                                    +

                                                                    Supported
                                                                    -
                                                                  -

                                                                  Examples

                                                                  An Internet company mainly provides game and music services. DLI is used to analyze user behaviors and assist decision making.

                                                                  -

                                                                  As shown in Figure 1, the Leader of the Basic Platform Team has applied for a Tenant Administrator account to manage and use cloud services. The Leader of the Basic Platform Team creates a subaccount with the DLI Service Administrator permission to manage and use DLI, as the Big Data Platform Team requires DLI for data analysis. The Leader of the Basic Platform Team creates a Queue A and assigns it to Data Engineer A to analyze the gaming data. A Queue B is also assigned to Data Engineer B to analyze the music data. Besides granting the queue usage permission, the Leader of the Basic Platform Team grants data (except the database) management and usage permissions to the two engineers.

                                                                  -
                                                                  Figure 1 Granting permissions
                                                                  -

                                                                  The Data Engineer A creates a table named gameTable for storing game prop data and a table named userTable for storing game user data. The music service is a new service. To explore potential music users among existing game users, the Data Engineer A assigns the query permission on the userTable to the Data Engineer B. In addition, Data Engineer B creates a table named musicTable for storing music copyrights information.

                                                                  -

                                                                  Table 3 describes the queue and data permissions of Data Engineer A and Data Engineer B.

                                                                  - -
                                                                  - - - - - - - - - - - - - - - - -
                                                                  Table 3 Permission description

                                                                  User

                                                                  -

                                                                  Data Engineer A (game data analysis)

                                                                  -

                                                                  Data Engineer B (music data analysis)

                                                                  -

                                                                  Queues

                                                                  -

                                                                  Queue A (queue usage permission)

                                                                  -

                                                                  Queue B (queue usage permission)

                                                                  -

                                                                  Data (Table)

                                                                  -

                                                                  gameTable (table management and usage permission)

                                                                  -

                                                                  musicTable (table management and usage permission)

                                                                  -

                                                                  userTable (table management and usage permission)

                                                                  -

                                                                  userTable (table query permission)

                                                                  -
                                                                  -
                                                                  -

                                                                  The queue usage permission includes job submitting and terminating permissions.

                                                                  -
                                                                  +
                                                                  -
                                                                  Parent topic: Permissions Management
                                                                  +
                                                                  Parent topic: DLI Permission Management
                                                                  + + \ No newline at end of file diff --git a/docs/dli/umn/dli_01_0441.html b/docs/dli/umn/dli_01_0441.html index d649fdf68..8785d87bd 100644 --- a/docs/dli/umn/dli_01_0441.html +++ b/docs/dli/umn/dli_01_0441.html @@ -1,612 +1,955 @@ -

                                                                  Common Operations Supported by DLI System Policy

                                                                  -

                                                                  Table 1 lists the common operations supported by each system policy of DLI. Choose proper system policies according to this table. For details about the SQL statement permission matrix in DLI in terms of permissions on databases, tables, and roles, see SQL Syntax of Batch Jobs > Data Permissions Management > Data Permissions List in the Data Lake Insight SQL Syntax Reference.

                                                                  - -
                                                                  Table 1 Common operations supported by each system permission

                                                                  Resource

                                                                  +

                                                                  IAM Permissions

                                                                  +

                                                                  Elastic Resource Pool

                                                                  +
                                                                  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                                                  Table 1 Elastic resource pool permission set

                                                                  Operation

                                                                  Operation

                                                                  -

                                                                  Description

                                                                  -

                                                                  DLI FullAccess

                                                                  -

                                                                  DLI ReadOnlyAccess

                                                                  -

                                                                  Tenant Administrator

                                                                  -

                                                                  DLI Service Administrator

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  Queue

                                                                  +

                                                                  Creating an elastic resource pool

                                                                  DROP_QUEUE

                                                                  -

                                                                  Deleting a Queue

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  +

                                                                  dli:elasticresourcepool:create

                                                                  SUBMIT_JOB

                                                                  +

                                                                  Querying all elastic resource pools

                                                                  Submitting a job

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  +

                                                                  /

                                                                  CANCEL_JOB

                                                                  +

                                                                  Deleting an elastic resource pool

                                                                  Terminating a Job

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  +

                                                                  dli:elasticresourcepool:drop

                                                                  RESTART

                                                                  +

                                                                  Modifying elastic resource pool information

                                                                  Restarting a queue

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  +

                                                                  dli:elasticresourcepool:update

                                                                  GRANT_PRIVILEGE

                                                                  +

                                                                  Associating a queue with an elastic resource pool

                                                                  Granting permissions to a queue

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  +

                                                                  dli:elasticresourcepool:resourceManagement

                                                                  REVOKE_PRIVILEGE

                                                                  +

                                                                  Querying all queues in an elastic resource pool

                                                                  Revoking permissions to a queue

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  +

                                                                  dli:elasticresourcepool:resourceManagement

                                                                  SHOW_PRIVILEGES

                                                                  +

                                                                  Modifying the scaling policy of a queue associated with an elastic resource pool

                                                                  Viewing the queue permissions of other users

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  +

                                                                  dli:elasticresourcepool:resourceManagement

                                                                  Database

                                                                  +

                                                                  Viewing scaling history of an elastic resource pool

                                                                  DROP_DATABASE

                                                                  -

                                                                  Deleting a database

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  CREATE_TABLE

                                                                  -

                                                                  Creating a table

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  CREATE_VIEW

                                                                  -

                                                                  Creating a view

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  EXPLAIN

                                                                  -

                                                                  Explaining the SQL statement as an execution plan

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  CREATE_ROLE

                                                                  -

                                                                  Creating a role

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  DROP_ROLE

                                                                  -

                                                                  Deleting a role

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  SHOW_ROLES

                                                                  -

                                                                  Displaying a role

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  GRANT_ROLE

                                                                  -

                                                                  Binding a role

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  REVOKE_ROLE

                                                                  -

                                                                  Unbinding a role

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  SHOW_USERS

                                                                  -

                                                                  Displaying the binding relationships between all roles and users

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  GRANT_PRIVILEGE

                                                                  -

                                                                  Granting permissions to the database

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  REVOKE_PRIVILEGE

                                                                  -

                                                                  Revoking permissions to the database

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  SHOW_PRIVILEGES

                                                                  -

                                                                  Viewing database permissions of other users

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  DISPLAY_ALL_TABLES

                                                                  -

                                                                  Displaying tables in a database

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  DISPLAY_DATABASE

                                                                  -

                                                                  Displaying databases

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  CREATE_FUNCTION

                                                                  -

                                                                  Creating a function

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  DROP_FUNCTION

                                                                  -

                                                                  Deleting a function

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  SHOW_FUNCTIONS

                                                                  -

                                                                  Displaying all functions

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  DESCRIBE_FUNCTION

                                                                  -

                                                                  Displaying function details

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  Table

                                                                  -

                                                                  DROP_TABLE

                                                                  -

                                                                  Deleting tables

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  SELECT

                                                                  -

                                                                  Querying tables

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  INSERT_INTO_TABLE

                                                                  -

                                                                  Inserting table data

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  ALTER_TABLE_ADD_COLUMNS

                                                                  -

                                                                  Adding a column

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  INSERT_OVERWRITE_TABLE

                                                                  -

                                                                  Overwriting a table

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  ALTER_TABLE_RENAME

                                                                  -

                                                                  Renaming a table

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  ALTER_TABLE_ADD_PARTITION

                                                                  -

                                                                  Adding partitions to the partition table

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  ALTER_TABLE_RENAME_PARTITION

                                                                  -

                                                                  Renaming a table partition

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  ALTER_TABLE_DROP_PARTITION

                                                                  -

                                                                  Deleting partitions from a partition table

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  SHOW_PARTITIONS

                                                                  -

                                                                  Displaying all partitions

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  ALTER_TABLE_RECOVER_PARTITION

                                                                  -

                                                                  Restoring table partitions

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  ALTER_TABLE_SET_LOCATION

                                                                  -

                                                                  Setting the partition path

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  GRANT_PRIVILEGE

                                                                  -

                                                                  Granting permissions to the table

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  REVOKE_PRIVILEGE

                                                                  -

                                                                  Revoking permissions to the table

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  SHOW_PRIVILEGES

                                                                  -

                                                                  Viewing table permissions of other users

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  DISPLAY_TABLE

                                                                  -

                                                                  Displaying a table

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  DESCRIBE_TABLE

                                                                  -

                                                                  Displaying table information

                                                                  -

                                                                  √

                                                                  -

                                                                  ×

                                                                  -

                                                                  √

                                                                  -

                                                                  √

                                                                  -

                                                                  Enhanced datasource connection

                                                                  -

                                                                  BIND_QUEUE

                                                                  -

                                                                  Binding an enhanced datasource connection to a queue

                                                                  -

                                                                  It is only used to grant permissions across projects.

                                                                  -

                                                                  ×

                                                                  -

                                                                  ×

                                                                  -

                                                                  ×

                                                                  -

                                                                  ×

                                                                  +

                                                                  dli:elasticresourcepool:scale
                                                                  +

                                                                  Queue

                                                                  +
                                                                  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                  Table 2 Queue permission set

                                                                  Operation

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  +

                                                                  Creating a queue

                                                                  +

                                                                  dli:queue:createQueue

                                                                  +

                                                                  Querying all queues

                                                                  +

                                                                  /

                                                                  +

                                                                  Deleting a queue

                                                                  +

                                                                  dli:queue:dropQueue

                                                                  +

                                                                  Modifying the CIDR block of a queue (deprecated)

                                                                  +

                                                                  dli:queue:updateQueue

                                                                  +

                                                                  Querying queue details

                                                                  +

                                                                  /

                                                                  +

                                                                  Restarting, scaling out, and scaling in queues

                                                                  +

                                                                  dli:queue:scaleQueue

                                                                  +

                                                                  Creating an address connectivity test request

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying connectivity test details of a specified address

                                                                  +

                                                                  /

                                                                  +

                                                                  Creating a scheduled CU change (deprecated)

                                                                  +

                                                                  dli:queue:scaleQueue

                                                                  +

                                                                  Viewing a scheduled CU change (deprecated)

                                                                  +

                                                                  dli:queue:scaleQueue

                                                                  +

                                                                  Batch deleting scheduled CU changes (deprecated)

                                                                  +

                                                                  dli:queue:scaleQueue

                                                                  +

                                                                  Modifying a scheduled CU change (deprecated)

                                                                  +

                                                                  dli:queue:scaleQueue

                                                                  +

                                                                  Deleting a scheduled CU change (deprecated)

                                                                  +

                                                                  dli:queue:scaleQueue

                                                                  +

                                                                  Adding queue properties

                                                                  +

                                                                  dli:queue:updateQueue

                                                                  +

                                                                  Querying queue properties

                                                                  +

                                                                  /

                                                                  +

                                                                  Updating queue properties

                                                                  +

                                                                  dli:queue:updateQueue

                                                                  +

                                                                  Deleting queue properties

                                                                  +

                                                                  dli:queue:updateQueue

                                                                  +

                                                                  Setting the queue scale-out range

                                                                  +

                                                                  dli:queue:scaleQueue

                                                                  +
                                                                  +
                                                                  +
                                                                  +

                                                                  Enhanced Datasource Connection

                                                                  +
                                                                  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                  Table 3 Enhanced datasource connection permission set

                                                                  Operation

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  +

                                                                  Creating an enhanced datasource connection

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying the enhanced datasource connection list

                                                                  +

                                                                  /

                                                                  +

                                                                  Deleting an enhanced datasource connection

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying an enhanced datasource connection

                                                                  +

                                                                  /

                                                                  +

                                                                  Modifying the host information of an enhanced datasource connection

                                                                  +

                                                                  /

                                                                  +

                                                                  Binding a queue

                                                                  +

                                                                  /

                                                                  +

                                                                  Unbinding a queue

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying authorization of an enhanced datasource connection

                                                                  +

                                                                  /

                                                                  +

                                                                  Creating a route for an enhanced datasource connection (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Deleting a route from an enhanced datasource connection (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Creating a route for an enhanced datasource connection

                                                                  +

                                                                  /

                                                                  +

                                                                  Deleting a route from an enhanced datasource connection

                                                                  +

                                                                  /

                                                                  +
                                                                  +
                                                                  +
                                                                  +

                                                                  Package and Package Group

                                                                  +
                                                                  + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                  Table 4 Package and package group permission set

                                                                  Operation

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  +

                                                                  Uploading a package group (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying the package group list (deprecated)

                                                                  +

                                                                  dli:resource:listResource

                                                                  +

                                                                  Uploading a JAR package group (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Uploading a file package group (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Uploading a PyFile package group (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying resource packages in a group (deprecated)

                                                                  +

                                                                  dli:resource:getResource

                                                                  +

                                                                  Deleting a resource package from a group (deprecated)

                                                                  +

                                                                  dli:resource:deleteResource

                                                                  +

                                                                  Changing the owner of a group or resource package (deprecated)

                                                                  +

                                                                  dli:resource:updateResource

                                                                  +
                                                                  +
                                                                  +
                                                                  +

                                                                  Global Variable

                                                                  +
                                                                  + + + + + + + + + + + + + + + + +
                                                                  Table 5 Global variable permission set

                                                                  Operation

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  +

                                                                  Creating a global variable

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying global variables

                                                                  +

                                                                  /

                                                                  +

                                                                  Deleting a DLI global variable

                                                                  +

                                                                  dli:variable:delete

                                                                  +

                                                                  Modifying a DLI global variable

                                                                  +

                                                                  dli:variable:update

                                                                  +
                                                                  +
                                                                  +
                                                                  +

                                                                  Datasource Authentication

                                                                  +
                                                                  + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                  Table 6 Datasource authentication permission set

                                                                  Operation

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  +

                                                                  Creating datasource authentication (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying the datasource authentication list (deprecated)

                                                                  +

                                                                  dli:datasourceauth:list

                                                                  +

                                                                  Updating datasource authentication (deprecated)

                                                                  +

                                                                  dli:datasourceauth:update

                                                                  +

                                                                  Deleting datasource authentication (deprecated)

                                                                  +

                                                                  dli:datasourceauth:delete

                                                                  +

                                                                  Creating datasource authentication

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying the datasource authentication list

                                                                  +

                                                                  dli:datasourceauth:listAuth

                                                                  +

                                                                  Updating datasource authentication information

                                                                  +

                                                                  dli:datasourceauth:updateAuth

                                                                  +

                                                                  Deleting datasource authentication information

                                                                  +

                                                                  dli:datasourceauth:dropAuth

                                                                  +
                                                                  +
                                                                  +
                                                                  +

                                                                  SQL Job

                                                                  +
                                                                  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                  Table 7 SQL job permission set

                                                                  Operation

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  +

                                                                  Submitting a SQL job

                                                                  +

                                                                  dli:queue:submitJob

                                                                  +

                                                                  Canceling a job

                                                                  +

                                                                  dli:queue:cancelJob

                                                                  +

                                                                  Querying all SQL jobs

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying all SQL jobs (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Previewing SQL job query results

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying the job status

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying job details

                                                                  +

                                                                  /

                                                                  +

                                                                  Checking SQL syntax

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying the job execution progress

                                                                  +

                                                                  /

                                                                  +

                                                                  Importing table data (deprecated)

                                                                  +

                                                                  dli:table:insertInto

                                                                  +

                                                                  Exporting table data (deprecated)

                                                                  +

                                                                  dli:table:select

                                                                  +

                                                                  Exporting query results (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Submitting a SQL job (deprecated)

                                                                  +

                                                                  dli:queue:submitJob

                                                                  +

                                                                  Canceling a job (deprecated)

                                                                  +

                                                                  dli:queue:cancelJob

                                                                  +

                                                                  Querying job execution results (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Creating a data upload task (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Authenticating a data upload (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Committing final data (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Creating a data download channel

                                                                  +

                                                                  /

                                                                  +

                                                                  Creating a SQL template

                                                                  +

                                                                  /

                                                                  +

                                                                  Viewing all SQL templates

                                                                  +

                                                                  /

                                                                  +

                                                                  Batch deleting SQL templates

                                                                  +

                                                                  /

                                                                  +

                                                                  Updating a SQL template

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying all sample SQL templates

                                                                  +

                                                                  /

                                                                  +
                                                                  +
                                                                  +
                                                                  +

                                                                  Spark Job

                                                                  +
                                                                  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                  Table 8 Spark job permission set

                                                                  Operation

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  +

                                                                  Creating a batch processing job

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying the batch processing job list

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying batch processing job details

                                                                  +

                                                                  /

                                                                  +

                                                                  Canceling a batch processing job

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying the status of a batch processing job

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying batch processing job logs (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Creating a job template

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying the job template list

                                                                  +

                                                                  /

                                                                  +

                                                                  Modifying a job template

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying a job template

                                                                  +

                                                                  /

                                                                  +
                                                                  +
                                                                  +
                                                                  +

                                                                  Flink Job

                                                                  +
                                                                  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                  Table 9 Flink job permission set

                                                                  Operation

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  +

                                                                  Creating a Flink SQL job

                                                                  +

                                                                  dli:jobs:create

                                                                  +

                                                                  Updating a Flink SQL job

                                                                  +

                                                                  dli:jobs:update

                                                                  +

                                                                  Creating a Flink Jar job

                                                                  +

                                                                  dli:jobs:create

                                                                  +

                                                                  Updating a Flink Jar job

                                                                  +

                                                                  dli:jobs:update

                                                                  +

                                                                  Batch running jobs

                                                                  +

                                                                  dli:jobs:start

                                                                  +

                                                                  Batch stopping jobs

                                                                  +

                                                                  dli:jobs:stop

                                                                  +

                                                                  Querying the job list

                                                                  +

                                                                  dli:jobs:listAll

                                                                  +

                                                                  Querying job details

                                                                  +

                                                                  dli:jobs:get

                                                                  +

                                                                  Deleting a job

                                                                  +

                                                                  dli:jobs:delete

                                                                  +

                                                                  Batch deleting jobs

                                                                  +

                                                                  dli:jobs:delete

                                                                  +

                                                                  Exporting a Flink job

                                                                  +

                                                                  dli:jobs:export

                                                                  +

                                                                  Importing a Flink job

                                                                  +

                                                                  dli:jobs:create

                                                                  +

                                                                  Generating a static stream graph for a Flink SQL job

                                                                  +

                                                                  dli:jobs:get

                                                                  +

                                                                  Querying the job execution plan

                                                                  +

                                                                  dli:jobs:get

                                                                  +

                                                                  Importing a savepoint

                                                                  +

                                                                  dli:jobs:update

                                                                  +

                                                                  Creating a savepoint

                                                                  +

                                                                  dli:jobs:update

                                                                  +

                                                                  Checking job existence (protected)

                                                                  +

                                                                  /

                                                                  +

                                                                  Checking Flink SQL syntax (protected)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying jobmanager logs of a running job (protected)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying taskmanager logs of a running job (protected)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying job commit logs (protected)

                                                                  +

                                                                  /

                                                                  +

                                                                  Creating a template

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying the template list

                                                                  +

                                                                  /

                                                                  +

                                                                  Deleting a template

                                                                  +

                                                                  /

                                                                  +

                                                                  Updating a template

                                                                  +

                                                                  /

                                                                  +

                                                                  Checking Flink template existence (Protected)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying the sample Flink system template list (protected)

                                                                  +

                                                                  /

                                                                  +
                                                                  +
                                                                  +
                                                                  +

                                                                  Permission Management

                                                                  +
                                                                  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                  Table 10 Permission set for DLI permission management

                                                                  Operation

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  +

                                                                  Granting data access control to users or projects

                                                                  +

                                                                  /

                                                                  +

                                                                  Checking the permissions granted to a user

                                                                  +

                                                                  /

                                                                  +

                                                                  Granting queue permissions to a user (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying queue users (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Granting data permissions to users (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying database users (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying table users (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying user permissions on a table (deprecated)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying the list of cross-project permissions on a database (protected)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying specific project permissions on a database (protected)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying the list of cross-project permissions on a table (protected)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying specific project permissions on a table (protected)

                                                                  +

                                                                  /

                                                                  +

                                                                  Querying cross-project permissions on a column (protected)

                                                                  +

                                                                  /

                                                                  +

                                                                  Changing a database name (protected)

                                                                  +

                                                                  dli:database:updateDatabase

                                                                  +
                                                                  +
                                                                  +
                                                                  +

                                                                  Quota

                                                                  +
                                                                  + + + + + + + +
                                                                  Table 11 Quota permission set

                                                                  Operation

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  +

                                                                  Querying a user's quota list

                                                                  +

                                                                  /

                                                                  +
                                                                  +
                                                                  +
                                                                  +

                                                                  Data Catalog

                                                                  +
                                                                  + + + + + + + + + + + + + +
                                                                  Table 12 Data catalog permission set

                                                                  Operation

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  +

                                                                  Querying information about all catalogs in a project

                                                                  +

                                                                  dli:catalog:list

                                                                  +

                                                                  Binding or unbinding a catalog mapping

                                                                  +

                                                                  dli:catalog:bind

                                                                  +

                                                                  Describing a catalog

                                                                  +

                                                                  dli:catalog:get

                                                                  +
                                                                  +
                                                                  +
                                                                  +

                                                                  Database

                                                                  +
                                                                  + + + + + + + + + + + + + + + + +
                                                                  Table 13 Database permission set

                                                                  Operation

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  +

                                                                  Querying all databases (deprecated)

                                                                  +

                                                                  dli:database:list

                                                                  +

                                                                  Creating a database (deprecated)

                                                                  +

                                                                  dli:database:create

                                                                  +

                                                                  Changing a database owner (deprecated)

                                                                  +

                                                                  dli:database:update

                                                                  +

                                                                  Deleting a database (deprecated)

                                                                  +

                                                                  dli:database:dropDatabase

                                                                  +
                                                                  +
                                                                  +
                                                                  +

                                                                  Table

                                                                  +
                                                                  + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                                  Table 14 Data table permission set

                                                                  Operation

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  +

                                                                  Querying all tables (deprecated)

                                                                  +

                                                                  dli:database:displayAllTables

                                                                  +

                                                                  Creating a table (deprecated)

                                                                  +

                                                                  dli:database:createTable

                                                                  +

                                                                  Changing a table owner (deprecated)

                                                                  +

                                                                  dli:table:update

                                                                  +

                                                                  Describing a table (deprecated)

                                                                  +

                                                                  dli:table:describe

                                                                  +

                                                                  Deleting a table (deprecated)

                                                                  +

                                                                  dli:table:delete

                                                                  +

                                                                  Previewing a table (deprecated)

                                                                  +

                                                                  dli:table:select

                                                                  +

                                                                  Querying the partition list (deprecated)

                                                                  +

                                                                  dli:table:showPartitions

                                                                  +
                                                                  +
                                                                  +
                                                                  +

                                                                  SQL Inspection Rule

                                                                  +
                                                                  + + + + + + + + + + + + + + + + + + + +
                                                                  Table 15 SQL inspection rule permission set

                                                                  Operation

                                                                  +

                                                                  Permission (service:resource:action)

                                                                  +

                                                                  (Role/Policy-based Authorization)

                                                                  +

                                                                  Creating a SQL inspection rule

                                                                  +

                                                                  dli:sqldefendrule:create

                                                                  +

                                                                  Modifying a SQL inspection rule

                                                                  +

                                                                  dli:sqldefendrule:update

                                                                  +

                                                                  Deleting a SQL inspection rule

                                                                  +

                                                                  dli:sqldefendrule:delete

                                                                  +

                                                                  Querying a SQL inspection rule

                                                                  +

                                                                  dli:sqldefendrule:get

                                                                  +

                                                                  Querying the SQL inspection rule list

                                                                  +

                                                                  dli:sqldefendrule:list

                                                                  +
                                                                  +
                                                                  +
                                                                  +
                                                                  -
                                                                  Parent topic: Permissions Management
                                                                  +
                                                                  Parent topic: IAM Permission Management
                                                                  diff --git a/docs/dli/umn/dli_01_0443.html b/docs/dli/umn/dli_01_0443.html index 7de634b1a..161d5335a 100644 --- a/docs/dli/umn/dli_01_0443.html +++ b/docs/dli/umn/dli_01_0443.html @@ -1,9 +1,9 @@ -

                                                                  Changing the CIDR Block for a Standard Queue

                                                                  +

                                                                  Changing the CIDR Block of a Queue in a Non-Elastic Resource Pool

                                                                  If the CIDR block of the DLI queue conflicts with that of the user data source, you can change the CIDR block of the queue.

                                                                  If the queue whose CIDR block is to be modified has jobs that are being submitted or running, or the queue has been bound to enhanced datasource connections, the CIDR block cannot be modified.

                                                                  -

                                                                  The operations described in this section only apply to standard queues.

                                                                  +

                                                                  The operations described in this section only apply to queues in non-elastic resource pools.

                                                                  Procedure

                                                                  1. In the navigation pane on the left of the DLI management console, choose Resources > Queue Management.
                                                                  2. Select the queue to be modified and click Modify CIDR Block in the Operation column.
                                                                  3. Enter the required CIDR block and click OK. After the CIDR block of the queue is successfully changed, wait for 5 to 10 minutes until the cluster to which the queue belongs is restarted and then run jobs on the queue.
                                                                  diff --git a/docs/dli/umn/dli_01_0445.html b/docs/dli/umn/dli_01_0445.html index d99131da0..c42ff9f6f 100644 --- a/docs/dli/umn/dli_01_0445.html +++ b/docs/dli/umn/dli_01_0445.html @@ -1,387 +1,499 @@ -

                                                                  Using Cloud Eye to Monitor DLI

                                                                  +

                                                                  Monitoring DLI Using Cloud Eye

                                                                  Description

                                                                  This section describes metrics reported by DLI to Cloud Eye as well as their namespaces and dimensions. You can use the management console or APIs provided by Cloud Eye to query the metrics of the monitored object and alarms generated for DLI.

                                                                  Namespace

                                                                  SYS.DLI

                                                                  Metric

                                                                  -
                                                                  Table 1 DLI metrics

                                                                  Metric ID

                                                                  +
                                                                  - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - - + + - - - - - + + - - - - - - + + - - - - - - - + + - - - - - + + - - - - - - - + + - - - - - - + + - - - - - - + + - - - - - + + - - - - - - - + + - - - - - + + - - - - - - - + + diff --git a/docs/dli/umn/dli_01_0447.html b/docs/dli/umn/dli_01_0447.html index 45fe1cf34..59cc8de79 100644 --- a/docs/dli/umn/dli_01_0447.html +++ b/docs/dli/umn/dli_01_0447.html @@ -6,11 +6,11 @@

                                                                  Precautions

                                                                  • Lower-level objects automatically inherit permissions granted to upper-level objects. The hierarchical relationship is database > table > column.
                                                                  • The database owner, table owner, and authorized users can assign permissions on the database and tables.
                                                                  • Columns can only inherit the query permission. For details about Inheritable Permissions, see Configuring Database Permissions on the DLI Console.
                                                                  • The permissions can be revoked only at the initial level to which the permissions are granted. You need to grant and revoke permissions at the same level. You need to grant and revoke permissions at the same level. For example, after you are granted the insertion permission on a database, you can obtain the insertion permission on the tables in the database. Your insertion permission can be revoked only at the database level.
                                                                  • If you create a database with the same name as a deleted database, the database permissions will not be inherited. In this case, you need to grant the database permissions to users or projects.

                                                                    For example, user A is granted with the permission to delete the testdb database. Delete the database and create another one with the same name. You need to grant user A the deletion permission of the testdb database again.

                                                                  -

                                                                  Viewing Database Permissions

                                                                  1. On the left of the management console, choose Data Management > Databases and Tables.
                                                                  2. Locate the row where the target database resides and click Manage Permissions in the Operation column.

                                                                    Permissions can be granted to new users or projects, modified for users or projects with existing permissions, or revoked from a user or project.

                                                                    +

                                                                    Viewing Database Permissions

                                                                    1. In the navigation pane on the left of the console, choose Data Management > Databases and Tables.
                                                                    2. Locate the row where the target database resides and click Manage Permissions in the Operation column.

                                                                      Permissions can be granted to new users or projects, modified for users or projects with existing permissions, or revoked from a user or project.

                                                                    Granting Permissions to a New User or Project

                                                                    Here, the new user or project refers to a user or a project that does not have permissions on the database.
                                                                    1. Click a database you need. In the displayed Database Permission Management page, click Grant Permission in the upper right corner.
                                                                    2. In the displayed dialog box, select User or Project, enter the username or select the project to be authorized, and select the required permissions. For details about the permissions, see Table 1. -
                                                                  Table 1 DLI metrics

                                                                  Metric ID

                                                                  Name

                                                                  +

                                                                  Name

                                                                  Description

                                                                  +

                                                                  Description

                                                                  Value Range

                                                                  +

                                                                  Value Range

                                                                  Monitored Object

                                                                  +

                                                                  Unit

                                                                  Monitoring Period (Raw Data)

                                                                  +

                                                                  Conversion Rule

                                                                  +

                                                                  Monitored Object

                                                                  +

                                                                  Monitoring Period (Raw Data)

                                                                  queue_cu_num

                                                                  +

                                                                  queue_cu_num

                                                                  Queue CU Usage

                                                                  +

                                                                  Queue CU Usage

                                                                  Displays the number of CUs applied by the user queue

                                                                  +

                                                                  Displays the number of CUs applied by the user queue

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Queues

                                                                  +

                                                                  Count

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  5 minutes

                                                                  queue_job_launching_num

                                                                  +

                                                                  queue_job_launching_num

                                                                  Number of Jobs Being Submitted

                                                                  +

                                                                  Number of Jobs Being Submitted

                                                                  Displays the number of jobs in the Submitting state in the user queue.

                                                                  +

                                                                  Displays the number of jobs in the Submitting state in the user queue.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Queues

                                                                  +

                                                                  Count

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  5 minutes

                                                                  queue_job_running_num

                                                                  +

                                                                  queue_job_running_num

                                                                  Number of Running Jobs

                                                                  +

                                                                  Number of Running Jobs

                                                                  Displays the number of running jobs in the user queue.

                                                                  +

                                                                  Displays the number of running jobs in the user queue.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Queues

                                                                  +

                                                                  Count

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  5 minutes

                                                                  queue_job_succeed_num

                                                                  +

                                                                  queue_job_succeed_num

                                                                  Number of Finished Jobs

                                                                  +

                                                                  Number of Finished Jobs

                                                                  Displays the number of completed jobs in the user queue.

                                                                  +

                                                                  Displays the number of completed jobs in the user queue.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Queues

                                                                  +

                                                                  Count

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  5 minutes

                                                                  queue_job_failed_num

                                                                  +

                                                                  queue_job_failed_num

                                                                  Failed Jobs

                                                                  +

                                                                  Failed Jobs

                                                                  Displays the number of failed jobs in the user queue.

                                                                  +

                                                                  Displays the number of failed jobs in the user queue.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Queues

                                                                  +

                                                                  Count

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  5 minutes

                                                                  queue_job_cancelled_num

                                                                  +

                                                                  queue_job_cancelled_num

                                                                  Number of Canceled Jobs

                                                                  +

                                                                  Number of Canceled Jobs

                                                                  Displays the number of canceled jobs in the user queue.

                                                                  +

                                                                  Displays the number of canceled jobs in the user queue.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Queues

                                                                  +

                                                                  Count

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  5 minutes

                                                                  queue_alloc_cu_num

                                                                  +

                                                                  queue_alloc_cu_num

                                                                  Allocated CUs (queue)

                                                                  +

                                                                  Allocated CUs (queue)

                                                                  Displays the CU allocation for user queues.

                                                                  +

                                                                  Displays the CU allocation for user queues.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Queues

                                                                  +

                                                                  Count

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  5 minutes

                                                                  queue_min_cu_num

                                                                  +

                                                                  queue_min_cu_num

                                                                  Minimum CUs for Queue

                                                                  +

                                                                  Minimum CUs for Queue

                                                                  Displays the minimum number of CUs for a user queue.

                                                                  +

                                                                  Displays the minimum number of CUs for a user queue.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Queues

                                                                  +

                                                                  Count

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  5 minutes

                                                                  queue_max_cu_num

                                                                  +

                                                                  queue_max_cu_num

                                                                  Maximum CUs for Queue

                                                                  +

                                                                  Maximum CUs for Queue

                                                                  Displays the maximum number of CUs for a user queue.

                                                                  +

                                                                  Displays the maximum number of CUs for a user queue.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Queues

                                                                  +

                                                                  Count

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  5 minutes

                                                                  queue_priority

                                                                  +

                                                                  queue_priority

                                                                  Queue Priority

                                                                  +

                                                                  Queue Priority

                                                                  Displays the priority of a user queue.

                                                                  +

                                                                  Displays the priority of a user queue.

                                                                  1–100

                                                                  +

                                                                  1–100

                                                                  Queues

                                                                  +

                                                                  N/A

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  5 minutes

                                                                  queue_cpu_usage

                                                                  +

                                                                  queue_cpu_usage

                                                                  Queue CPU Usage

                                                                  +

                                                                  Queue CPU Usage

                                                                  Displays the CPU usage of user queues.

                                                                  -

                                                                  This metric only applies to standard queues.

                                                                  +

                                                                  Displays the CPU usage of user queues.

                                                                  0–100

                                                                  +

                                                                  0–100

                                                                  Queues

                                                                  +

                                                                  %

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  This metric applies only to queues in non-elastic resource pools.

                                                                  +

                                                                  5 minutes

                                                                  queue_disk_usage

                                                                  +

                                                                  queue_disk_usage

                                                                  Queue Disk Usage

                                                                  +

                                                                  Queue Disk Usage

                                                                  Displays the disk usage of user queues.

                                                                  -

                                                                  This metric only applies to standard queues.

                                                                  +

                                                                  Displays the disk usage of user queues.

                                                                  0–100

                                                                  +

                                                                  0–100

                                                                  Queues

                                                                  +

                                                                  %

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  This metric applies only to queues in non-elastic resource pools.

                                                                  +

                                                                  5 minutes

                                                                  queue_disk_used

                                                                  +

                                                                  queue_disk_used

                                                                  Max Disk Usage

                                                                  +

                                                                  Max Disk Usage

                                                                  Displays the maximum disk usage of user queues.

                                                                  -

                                                                  This metric only applies to standard queues.

                                                                  +

                                                                  Displays the maximum disk usage of user queues.

                                                                  0–100

                                                                  +

                                                                  0–100

                                                                  Queues

                                                                  +

                                                                  %

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  This metric applies only to queues in non-elastic resource pools.

                                                                  +

                                                                  5 minutes

                                                                  queue_mem_usage

                                                                  +

                                                                  queue_mem_usage

                                                                  Queue Memory Usage

                                                                  +

                                                                  Queue Memory Usage

                                                                  Displays the memory usage of user queues.

                                                                  -

                                                                  This metric only applies to standard queues.

                                                                  +

                                                                  Displays the memory usage of user queues.

                                                                  0–100

                                                                  +

                                                                  0–100

                                                                  Queues

                                                                  +

                                                                  %

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  This metric applies only to queues in non-elastic resource pools.

                                                                  +

                                                                  5 minutes

                                                                  queue_mem_used

                                                                  +

                                                                  queue_mem_used

                                                                  Used Memory

                                                                  +

                                                                  Used Memory

                                                                  Displays the memory usage rate of the user queues.

                                                                  -

                                                                  This metric only applies to standard queues.

                                                                  +

                                                                  Displays the memory usage rate of the user queues.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Queues

                                                                  +

                                                                  MB

                                                                  5 minutes

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Queues

                                                                  +

                                                                  This metric applies only to queues in non-elastic resource pools.

                                                                  +

                                                                  5 minutes

                                                                  flink_read_records_per_second

                                                                  +

                                                                  flink_read_records_per_second

                                                                  Flink Job Data Read Rate

                                                                  +

                                                                  Flink Job Data Read Rate

                                                                  Displays the data input rate of a Flink job for monitoring and debugging.

                                                                  +

                                                                  Displays the data input rate of a Flink job for monitoring and debugging.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Flink jobs

                                                                  +

                                                                  record/s

                                                                  10 seconds

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Flink jobs

                                                                  +

                                                                  10 seconds

                                                                  flink_write_records_per_second

                                                                  +

                                                                  flink_write_records_per_second

                                                                  Flink Job Data Write Rate

                                                                  +

                                                                  Flink Job Data Write Rate

                                                                  Displays the data output rate of a Flink job for monitoring and debugging.

                                                                  +

                                                                  Displays the data output rate of a Flink job for monitoring and debugging.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Flink jobs

                                                                  +

                                                                  record/s

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Flink jobs

                                                                  10 seconds

                                                                  +

                                                                  10 seconds

                                                                  flink_read_records_total

                                                                  +

                                                                  flink_read_records_total

                                                                  Flink Job Total Data Read

                                                                  +

                                                                  Flink Job Total Data Read

                                                                  Displays the total number of data inputs of a Flink job for monitoring and debugging.

                                                                  +

                                                                  Displays the total number of data inputs of a Flink job for monitoring and debugging.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Flink jobs

                                                                  +

                                                                  record/s

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Flink jobs

                                                                  10 seconds

                                                                  +

                                                                  10 seconds

                                                                  flink_write_records_total

                                                                  +

                                                                  flink_write_records_total

                                                                  Flink Job Total Data Write

                                                                  +

                                                                  Flink Job Total Data Write

                                                                  Displays the total number of output data records of a Flink job for monitoring and debugging.

                                                                  +

                                                                  Displays the total number of output data records of a Flink job for monitoring and debugging.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Flink jobs

                                                                  +

                                                                  record/s

                                                                  10 seconds

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Flink jobs

                                                                  +

                                                                  10 seconds

                                                                  flink_read_bytes_per_second

                                                                  +

                                                                  flink_read_bytes_per_second

                                                                  Flink Job Byte Read Rate

                                                                  +

                                                                  Flink Job Byte Read Rate

                                                                  Displays the number of input bytes per second of a Flink job.

                                                                  +

                                                                  Displays the number of input bytes per second of a Flink job.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Flink jobs

                                                                  +

                                                                  byte/s

                                                                  +

                                                                  1024(IEC)

                                                                  +

                                                                  Flink jobs

                                                                  10 seconds

                                                                  +

                                                                  10 seconds

                                                                  flink_write_bytes_per_second

                                                                  +

                                                                  flink_write_bytes_per_second

                                                                  Flink Job Byte Write Rate

                                                                  +

                                                                  Flink Job Byte Write Rate

                                                                  Displays the number of output bytes per second of a Flink job.

                                                                  +

                                                                  Displays the number of output bytes per second of a Flink job.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Flink jobs

                                                                  +

                                                                  byte/s

                                                                  10 seconds

                                                                  +

                                                                  1024(IEC)

                                                                  +

                                                                  Flink jobs

                                                                  +

                                                                  10 seconds

                                                                  flink_read_bytes_total

                                                                  +

                                                                  flink_read_bytes_total

                                                                  Flink Job Total Read Byte

                                                                  +

                                                                  Flink Job Total Read Byte

                                                                  Displays the total number of input bytes of a Flink job.

                                                                  +

                                                                  Displays the total number of input bytes of a Flink job.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Flink jobs

                                                                  +

                                                                  byte/s

                                                                  10 seconds

                                                                  +

                                                                  1024(IEC)

                                                                  +

                                                                  Flink jobs

                                                                  +

                                                                  10 seconds

                                                                  flink_write_bytes_total

                                                                  +

                                                                  flink_write_bytes_total

                                                                  Flink Job Total Write Byte

                                                                  +

                                                                  Flink Job Total Write Byte

                                                                  Displays the total number of output bytes of a Flink job.

                                                                  +

                                                                  Displays the total number of output bytes of a Flink job.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Flink jobs

                                                                  +

                                                                  byte/s

                                                                  10 seconds

                                                                  +

                                                                  1024(IEC)

                                                                  +

                                                                  Flink jobs

                                                                  +

                                                                  10 seconds

                                                                  flink_cpu_usage

                                                                  +

                                                                  flink_cpu_usage

                                                                  Flink Job CPU Usage

                                                                  +

                                                                  Flink Job CPU Usage

                                                                  Displays the CPU usage of Flink jobs.

                                                                  +

                                                                  Displays the CPU usage of Flink jobs.

                                                                  0–100

                                                                  +

                                                                  0–100

                                                                  Flink jobs

                                                                  +

                                                                  %

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Flink jobs

                                                                  10 seconds

                                                                  +

                                                                  10 seconds

                                                                  flink_mem_usage

                                                                  +

                                                                  flink_mem_usage

                                                                  Flink Job Memory Usage

                                                                  +

                                                                  Flink Job Memory Usage

                                                                  Displays the memory usage of Flink jobs.

                                                                  +

                                                                  Displays the memory usage of Flink jobs.

                                                                  0–100

                                                                  +

                                                                  0–100

                                                                  Flink jobs

                                                                  +

                                                                  %

                                                                  10 seconds

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Flink jobs

                                                                  +

                                                                  10 seconds

                                                                  flink_max_op_latency

                                                                  +

                                                                  flink_max_op_latency

                                                                  Flink Job Max Operator Latency

                                                                  +

                                                                  Flink Job Max Operator Latency

                                                                  Displays the maximum operator delay of a Flink job. The unit is ms.

                                                                  +

                                                                  Displays the maximum operator delay of a Flink job. The unit is ms.

                                                                  ≥ 0

                                                                  +

                                                                  ≥ 0

                                                                  Flink jobs

                                                                  +

                                                                  ms

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Flink jobs

                                                                  10 seconds

                                                                  +

                                                                  10 seconds

                                                                  flink_max_op_backpressure_level

                                                                  +

                                                                  flink_max_op_backpressure_level

                                                                  Flink Job Maximum Operator Backpressure

                                                                  +

                                                                  Flink Job Maximum Operator Backpressure

                                                                  Displays the maximum operator backpressure value of a Flink job. A larger value indicates severer backpressure.

                                                                  +

                                                                  Displays the maximum operator backpressure value of a Flink job. A larger value indicates severer backpressure.

                                                                  0: OK

                                                                  50: low

                                                                  100: high

                                                                  0–100

                                                                  +

                                                                  0–100

                                                                  Flink jobs

                                                                  +

                                                                  N/A

                                                                  10 seconds

                                                                  +

                                                                  N/A

                                                                  +

                                                                  Flink jobs

                                                                  +

                                                                  10 seconds
                                                                  Table 1 Parameters

                                                                  Parameter

                                                                  +
                                                                  @@ -23,7 +23,7 @@ - - @@ -61,7 +61,7 @@

                                                                  Modifying Permissions for an Existing User or Project

                                                                  For a user or project that has some permissions on the database, you can revoke the existing permissions or grant new ones.

                                                                  If the options in Set Permission are gray, the corresponding account does not have the permission to modify the database. You can apply to the administrator, database owner, or other authorized users for granting and revoking permissions of databases.

                                                                  -
                                                                  1. In the User Permission Info list, find the user whose permission needs to be set.
                                                                    • If the user is an IAM user, you can set permissions for it.
                                                                    • If the user is already an administrator, you can only view the permissions information.
                                                                    +
                                                                    1. On the User Permissions page, locate the user you wish to set permissions for.
                                                                      • If the user is an IAM user, you can set permissions for it.
                                                                      • If the user is already an administrator, you can only view the permissions information.

                                                                      In the Project Permission Info list, locate the project for which you want to set permissions and click Set Permission.

                                                                    2. In the Operation column of the IAM user or project, click Set Permission. The Set Permission dialog box is displayed.

                                                                      For details about the permissions of database users or projects, see Table 1.

                                                                    3. Click OK.
                                                                    diff --git a/docs/dli/umn/dli_01_0448.html b/docs/dli/umn/dli_01_0448.html index 8851ae2f9..89453b441 100644 --- a/docs/dli/umn/dli_01_0448.html +++ b/docs/dli/umn/dli_01_0448.html @@ -6,12 +6,12 @@

                                                                    Precautions

                                                                    • If you create a table with the same name as a deleted table, the table permissions will not be inherited. In this case, you need to grant the table permissions to users or projects.

                                                                      For example, user A is granted with the permission to delete the testTable table. Delete the table and create another one with the same name. You need to grant user A the deletion permission of the testTable table again.

                                                                    -

                                                                    Viewing Table Permissions

                                                                    1. On the left of the management console, choose Data Management > Databases and Tables.
                                                                    2. Click the database name in the table whose authority is to be set. The Table Management page of the database is displayed.
                                                                    3. Locate the row where the target table resides and click Manage Permissions in the Operation column.

                                                                      Permissions can be granted to new users or projects, modified for users or projects with existing permissions, or revoked from a user or project.

                                                                      +

                                                                      Viewing Table Permissions

                                                                      1. In the navigation pane on the left of the console, choose Data Management > Databases and Tables.
                                                                      2. Click the database name in the table whose authority is to be set. The Table Management page of the database is displayed.
                                                                      3. Locate the row where the target table resides and click Manage Permissions in the Operation column.

                                                                        Permissions can be granted to new users or projects, modified for users or projects with existing permissions, or revoked from a user or project.

                                                                      -

                                                                      Granting Permissions to a New User or a Project

                                                                      Here, the new user or project refers to a user or a project that does not have permissions on the database.
                                                                      1. Click the table you need. In the displayed table permissions page, click Grant Permission in the upper right corner.
                                                                      2. In the displayed Grant Permission dialog box, select the required permissions.
                                                                        • For details about the DLI table permissions, see Table 1.

                                                                          +

                                                                          Granting Permissions to a New User or Project

                                                                          Here, the new user or project refers to a user or a project that does not have permissions on the database.
                                                                          1. Click the table you need. In the displayed table permissions page, click Grant Permission in the upper right corner.
                                                                          2. In the displayed Grant Permission dialog box, select the required permissions.
                                                                            • For details about the DLI table permissions, see Table 1.

                                                                              -
                                                                  Table 1 Parameter descriptions

                                                                  Parameter

                                                                  Description

                                                                  Username/Project Name

                                                                  • If you select User, enter the IAM username when adding a user to the database.
                                                                    NOTE:

                                                                    The username is an existing IAM user name and has logged in to the DLI management console.

                                                                    +
                                                                  • If you select User, enter the IAM username when adding a user to the database.
                                                                    NOTE:

                                                                    The username must be an existing IAM username and has been used to log in to the DLI management console.

                                                                  • If you select Project, select the project to be authorized in the current region.
                                                                    NOTE:

                                                                    When Project is selected:

                                                                    • If you set Non-inheritable Permissions, you cannot view tables in the corresponding database within the project.
                                                                    • If you set Inheritable Permissions, you can view all tables in the database within the project.
                                                                    @@ -46,10 +46,10 @@

                                                                  Inherited Permissions

                                                                  Select a permission to grant it to the user, or deselect a permission to revoke it.

                                                                  +

                                                                  Selecting a permission grants it to a user, while deselecting a permission revokes it from the user.

                                                                  Inherited permissions are applicable to the current database and all its tables. However, only the query permission is applicable to table columns.

                                                                  The following permissions can be granted to both user and project.

                                                                  -
                                                                  • Drop Table: This permission allows you to delete tables in a database.
                                                                  • Select Table: This permission allows you to query data of the current table.
                                                                  • View Table Information: This permission allows you to view information about the current table.
                                                                  • Insert: This permission allows you to insert data into the current table.
                                                                  • Add Column: This permission allows you to add columns to the current table.
                                                                  • Overwrite: This permission allows you to insert data to overwrite the data in the current table.
                                                                  • Grant Permission: This permission allows you to grant database permissions to other users or projects.
                                                                  • Revoke Permission: This permission allows you to revoke the permissions of the database that other users have but cannot revoke the database owner's permissions.
                                                                  • Add Partition to Partition Table: This permission allows you to add a partition to a partition table.
                                                                  • Delete Partition from Partition Table: This permission allows you to delete existing partitions from a partition table.
                                                                  • Configure Path for Partition: This permission allows you to set the path of a partition in a partition table to a specified OBS path.
                                                                  • Rename Table Partition: This permission allows you to rename partitions in a partition table.
                                                                  • Rename Table: This permission allows you to rename tables.
                                                                  • Restore Table Partition: This permission allows you to export partition information from the file system and save the information to metadata.
                                                                  • View All Partitions: This permission allows you to view all partitions in a partition table.
                                                                  • View Other Users' Permissions: This permission allows you to query other users' permission on the current database.
                                                                  +
                                                                  • Drop Table: This permission allows you to delete tables in a database.
                                                                  • Select Table: This permission allows you to query data of the current table.
                                                                  • View Table Information: This permission allows you to view information about the current table.
                                                                  • Insert: This permission allows you to insert data into the current table.
                                                                  • Add Column: This permission allows you to add columns to the current table.
                                                                  • Overwrite: This permission allows you to insert data to overwrite the data in the current table.
                                                                  • Grant Permission: This permission allows you to grant database permissions to other users or projects.
                                                                  • Revoke Permission: This permission allows you to revoke the permissions of the database that other users have but cannot revoke the database owner's permissions.
                                                                  • Add Partition: This permission allows you to add a partition to a partition table.
                                                                  • Delete Partition: This permission allows you to delete existing partitions from a partition table.
                                                                  • Configure Path for Partition: This permission allows you to set the path of a partition in a partition table to a specified OBS path.
                                                                  • Rename Table Partition: This permission allows you to rename partitions in a partition table.
                                                                  • Rename Table: This permission allows you to rename tables.
                                                                  • Restore Table Partition: This permission allows you to export partition information from the file system and save the information to metadata.
                                                                  • View All Partitions: This permission allows you to view all partitions in a partition table.
                                                                  • View Other Users' Permissions: This permission allows you to query other users' permission on the current database.
                                                                  Table 1 Parameter description

                                                                  Parameter

                                                                  +
                                                                  @@ -24,7 +24,7 @@ -
                                                                  Table 1 Parameter descriptions

                                                                  Parameter

                                                                  Description

                                                                  Username/Project

                                                                  • If you select User, enter the IAM username when granting table permissions to the user.
                                                                    NOTE:

                                                                    The username is an existing IAM user name and has logged in to the DLI management console.

                                                                    +
                                                                  • If you select User, enter the IAM username when granting table permissions to the user.
                                                                    NOTE:

                                                                    The username must be an existing IAM username and has been used to log in to the DLI management console.

                                                                  • If you select Project, select the project to be authorized in the current region.
                                                                    NOTE:

                                                                    If you select Project, you can only view information about the authorized tables and their databases.

                                                                    @@ -47,7 +47,7 @@
                                                                  • For details about the OBS table permissions, see Table 2.

                                                                    -
                                                                    Table 2 Parameter description

                                                                    Parameter

                                                                    +
                                                                    @@ -55,21 +55,21 @@ - - -
                                                                    Table 2 Parameter descriptions

                                                                    Parameter

                                                                    Description

                                                                    Authorization Object

                                                                    Select User or Project.

                                                                    +

                                                                    Select User or Project.

                                                                    Username/Project

                                                                    • If you select User, enter the IAM username when granting table permissions to the user.
                                                                      NOTE:

                                                                      The username is an existing IAM user name and has logged in to the DLI management console.

                                                                      +
                                                                    • If you select User, enter the IAM username when granting table permissions to the user.
                                                                      NOTE:

                                                                      The username must be an existing IAM username and has been used to log in to the DLI management console.

                                                                      -
                                                                    • If you select Project, select the project to be authorized in the current region.
                                                                      NOTE:

                                                                      If you select Project, you can only view information about the authorized tables and their databases.

                                                                      +
                                                                    • If you select Project, select the project to be authorized in the current region.
                                                                      NOTE:

                                                                      If you select Project, you can only view information about the authorized tables and their databases.

                                                                    Non-inheritable Permissions

                                                                    Select a permission to grant it to the user, or deselect a permission to revoke it.
                                                                    • The following permissions are applicable to both user and project authorization:
                                                                      • View Table Creation Statement: This permission allows you to view the statement for creating the current table.
                                                                      • View Table Information: This permission allows you to view information about the current table.
                                                                      • Select Table: This permission allows you to query data of the current table.
                                                                      • Drop Table: This permission allows you to delete the current table.
                                                                      • Rename Table: Rename the current table.
                                                                      • Insert: This permission allows you to insert data into the current table.
                                                                      • Overwrite: This permission allows you to insert data to overwrite the data in the current table.
                                                                      • Add Column: This permission allows you to add columns to the current table.
                                                                      • Grant Permission: This permission allows you to grant table permissions to other users or projects.
                                                                      • Revoke Permission: This permission allows you to revoke the table's permissions that other users or projects have but cannot revoke the table owner's permissions.
                                                                      • View Other Users' Permissions: This permission allows you to query other users' permission on the current table.
                                                                      +
                                                                    Select a permission to grant it to the user, or deselect a permission to revoke it.
                                                                    • The following permissions are applicable to both user and project authorization:
                                                                      • View Table Creation Statement: This permission allows you to view the statement for creating the current table.
                                                                      • View Table Information: This permission allows you to view information about the current table.
                                                                      • Select Table: This permission allows you to query data of the current table.
                                                                      • Drop Table: This permission allows you to delete the current table.
                                                                      • Rename Table: Rename the current table.
                                                                      • Insert: This permission allows you to insert data into the current table.
                                                                      • Overwrite: This permission allows you to insert data to overwrite the data in the current table.
                                                                      • Add Column: This permission allows you to add columns to the current table.
                                                                      • Grant Permission: This permission allows you to grant table permissions to other users or projects.
                                                                      • Revoke Permission: This permission allows you to revoke the table's permissions that other users or projects have but cannot revoke the table owner's permissions.
                                                                      • View Other Users' Permissions: This permission allows you to query other users' permission on the current table.
                                                                      The partition table also has the following permissions:
                                                                      • Add Partition: This permission allows you to add a partition to a partition table.
                                                                      • Delete Partition: This permission allows you to delete existing partitions from a partition table.
                                                                      • Configure Path for Partition: This permission allows you to set the path of a partition in a partition table to a specified OBS path.
                                                                      • Rename Table Partition: This permission allows you to rename partitions in a partition table.
                                                                      • Restore Table Partition: This permission allows you to export partition information from the file system and save the information to metadata.
                                                                      • View All Partitions: This permission allows you to view all partitions in a partition table.
                                                                    @@ -81,10 +81,10 @@
                                                                    -
                                                                  • For details about the view permissions, see Table 3.

                                                                    A view can be created only by using SQL statements. You cannot create a view on the Create Table page.

                                                                    +
                                                                  • For details about the view permissions, see Table 3.

                                                                    Views can be created only by using SQL statements, not through the Create Table page.

                                                                    -
                                                                    Table 3 Parameter description

                                                                    Parameter

                                                                    +
                                                                    @@ -92,12 +92,12 @@ - -
                                                                    Table 3 Parameter descriptions

                                                                    Parameter

                                                                    Description

                                                                    Authorization Object

                                                                    Select User or Project.

                                                                    +

                                                                    Select User or Project.

                                                                    Username/Project

                                                                    • If you select User, enter the IAM username when adding a user to the database.
                                                                      NOTE:

                                                                      The username is an existing IAM user name and has logged in to the DLI management console.

                                                                      +
                                                                    • If you select User, enter the IAM username when adding a user to the database.
                                                                      NOTE:

                                                                      The username must be an existing IAM username and has been used to log in to the DLI management console.

                                                                    • If you select Project, select the project to be authorized in the current region.
                                                                      NOTE:

                                                                      If you select Project, you can only view information about the authorized tables and their databases.

                                                                      @@ -122,7 +122,7 @@

                                                                      Modifying Permissions for an Existing User or Project

                                                                      For a user or project that has some permissions on the database, you can revoke the existing permissions or grant new ones.

                                                                      If all options under Set Permission are gray, you are not allowed to change permissions on this table. You can apply to the administrator, table owner, or other authorized users for granting and revoking table permissions.

                                                                      -
                                                                      1. In the User Permission Info list, find the user whose permission needs to be set.
                                                                        • If the user is an IAM user and is not the owner of the table, you can set permissions.
                                                                        • If the user is an administrator or table owner, you can only view permissions.
                                                                        +
                                                                        1. On the User Permissions page, locate the user you wish to set permissions for.
                                                                          • If the user is an IAM user and is not the owner of the table, you can set permissions.
                                                                          • If the user is an administrator or table owner, you can only view permissions.

                                                                          In the Project Permission Info list, locate the project for which you want to set permissions and click Set Permission.

                                                                        2. In the Operation column of the IAM user or project, click Set Permission. The Set Permission dialog box is displayed.
                                                                          • For details about DLI table user or project permissions, see Table 1.
                                                                          • For details about OBS table user or project permissions, see Table 2.
                                                                          • For details about View table user or project permissions, see Table 3.
                                                                        3. Click OK.
                                                                        diff --git a/docs/dli/umn/dli_01_0451.html b/docs/dli/umn/dli_01_0451.html index b770dde8d..2ed803f45 100644 --- a/docs/dli/umn/dli_01_0451.html +++ b/docs/dli/umn/dli_01_0451.html @@ -1,12 +1,64 @@ -

                                                                        Creating a Custom Policy

                                                                        -

                                                                        Custom policies can be created as a supplement to the system policies of DLI. You can add actions to custom policies. For the actions supported for custom policies, see "Permissions Policies and Supported Actions" in the Elastic Volume Service API Reference.

                                                                        -

                                                                        You can create custom policies in either of the following two ways:

                                                                        -
                                                                        • Visual editor: Select cloud services, actions, resources, and request conditions without the need to know policy syntax.
                                                                        • JSON: Create a policy in the JSON format from scratch or based on an existing policy.
                                                                        -

                                                                        . This section describes common DLI custom policies.

                                                                        -

                                                                        Policy Field Description

                                                                        The following example assumes that the authorized user has the permission to create tables in all databases in all regions:

                                                                        -
                                                                        {
+
                                                                        Using IAM Roles or Policies to Grant Access to DLI
                                                                        
+
                                                                        The role/policy-based authorization model provided by Identity and Access Management (IAM) lets you control access to DLI resources. With IAM, you can:
                                                                        
+
                                                                        • Based on the organizational structure of your enterprise, create IAM users in you master account for employees from different departments within the company. This ensures that each employee has unique security credentials and can use DLI resources.
                                                                        • Grant users the minimum permissions required to perform specific tasks based on their job responsibilities.
                                                                        • Entrust an account or cloud service to perform professional, efficient O&M on your DLI resources.
                                                                        
+
                                                                        If your account does not need individual IAM users, you may skip over this section.
                                                                        
+
                                                                        Process Flow shows the process flow of role/policy-based authorization.
                                                                        
+
                                                                        Prerequisites
                                                                        Before granting permissions to a user group, familiarize yourself with the DLI permissions that can be added to the user group and select them accordingly based on actual needs.
                                                                        
+
                                                                        For details about the system permissions of other services, see Permissions.
                                                                        
+
                                                                        
+
                                                                        Process Flow
                                                                        Figure 1 Process for granting DLI permissions
                                                                        
+
+
                                                                        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                        Table 1 Procedure
                                                                        No.
                                                                        
+
                                                                        Step
                                                                        
+
                                                                        Description
                                                                        
+
                                                                        1
                                                                        
+
                                                                        Create a user group and grant permissions to it.
                                                                        
+
                                                                        Create a user group on the IAM console and grant the DLI ReadOnlyAccess permission to it.
                                                                        
+
                                                                        2
                                                                        
+
                                                                        Create a user and add them to the user group.
                                                                        
+
                                                                        Create a user on the IAM console and add them to the created user group.
                                                                        
+
                                                                        3
                                                                        
+
                                                                        Log in as the IAM user and verify permissions.
                                                                        
+
                                                                        Log in to the console using the newly created user, switch to the authorized region, and verify permissions.
                                                                        
+
                                                                        • Choose Service List > Data Lake Insight. If you can view the elastic resource pool list on the Resources > Resource Pool page but cannot purchase an elastic resource pool by clicking Buy Resource Pool in the upper right corner (assuming the current permission includes only DLI ReadOnlyAccess), the DLI ReadOnlyAccess permission has already taken effect.
                                                                        • Choose any other service in Service List. If a message appears indicating that you have insufficient permissions to access the service, the DLI ReadOnlyAccess permission has already taken effect.
                                                                        
+
                                                                        4
                                                                        
+
                                                                        Create a custom policy and associate it with the user group.
                                                                        
+
                                                                        If the predefined DLI permissions in the system do not meet your authorization requirements, you can create custom policies.
                                                                        
+
                                                                        For details about how to create a custom policy, see Creating a Custom Policy.
                                                                        
+
                                                                        
+
                                                                        
+
                                                                        
+
                                                                        Creating a Custom DLI Policy
                                                                        If the predefined DLI permissions in the system do not meet your authorization requirements, you can create custom policies. For the actions that can be added to custom policies, refer to "Permission Policies and Supported Actions" in Data Lake Insight API Reference.
                                                                        
+
                                                                        You can create custom policies in either of the following two ways:
                                                                        
+
                                                                        • Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
                                                                        • JSON: Create a JSON policy or edit an existing one.
                                                                        
+
                                                                        
+
                                                                        
+
                                                                        Policy Fields
                                                                        In the following example, an IAM user is granted the permission to create tables across all databases in all regions.
                                                                        
+
                                                                        {
     "Version": "1.1",
     "Statement": [
         {
@@ -20,228 +72,257 @@
         }
     ]
 }
                                                                        
-
                                                                        • Version
                                                                          1.1 indicates a fine-grained permission policy that defines permissions required to perform operations on specific cloud resources under certain conditions.
                                                                          
-
                                                                        • Effect
                                                                          The value can be Allow and Deny. If both Allow and Deny are found in statements, the Deny overrides the Allow.
                                                                          
-
                                                                        • Action
                                                                          Specific operation on a resource. A maximum of 100 actions are allowed.
                                                                          
-
                                                                           
                                                                          • The format is Service name:Resource type:Action, for example, dli:queue:submit_job.
                                                                          • Service name: product name, such as dli, evs, and vpc. Only lowercase letters are allowed. Resource types and operations are not case-sensitive. You can use an asterisk (*) to represent all operations.
                                                                          • Resource type: For details, see Table 4.
                                                                          • Action: action registered in IAM.
                                                                          
+
                                                                          • Version
                                                                            Version: 1.1. Policy: A fine-grained authorization strategy that defines the permissions required to perform actions on a specific cloud resource under certain conditions.
                                                                            
+
                                                                          • Effect
                                                                            Function. The value can be Allow and Deny. If both Allow and Deny are found in statements, the Deny overrides the Allow.
                                                                            
+
                                                                          • Action
                                                                            Specific action on a resource. A maximum of 100 actions are allowed.
                                                                            
+
                                                                             
                                                                            • The format is Service name:Resource type:Action, for example, dli:queue:submit_job.
                                                                            • Service name: product name, such as dli, evs, or vpc. Only lowercase letters are allowed. Resource types and actions are not case-sensitive. You can use an asterisk (*) to represent all actions.
                                                                            • Resource type: For details, see Table 5.
                                                                            • Action: action registered with IAM.
                                                                            
 
                                                                            
-
                                                                          • Condition
                                                                            Conditions determine when a policy takes effect. A condition consists of a condition key and operator.
                                                                            
-
                                                                            A condition key is a key in the Condition element of a statement. There are global and service-level condition keys.
                                                                            
-
                                                                            • Global condition keys (prefixed with g:) apply to all actions. For details, see condition key description in Policy Syntax.
                                                                            • Service-level condition keys apply only to operations of the specific service.
                                                                            
-
                                                                            An operator is used together with a condition key to form a complete condition statement. For details, see Table 1.
                                                                            
-
                                                                            IAM provides a set of DLI predefined condition keys. The following table lists the predefined condition keys of DLI.
                                                                            
+
                                                                          • Condition
                                                                            Determines when a policy is in effect. A condition consists of a condition key and a condition operator.
                                                                            
+
                                                                            A key in the Condition element of a statement. There are global and service-specific condition keys.
                                                                            
+
                                                                            • Global-level condition key: The prefix is g:, which applies to all actions. For details, see the condition key description in Policy Syntax.
                                                                            • Service-level condition key: applies only to actions of the specific service.
                                                                            
+
                                                                            An operator must be used together with a condition key to form a complete condition statement. For details, see Table 2.
                                                                            
+
                                                                            IAM provides a set of DLI predefined condition keys. The following table lists the DLI predefined condition keys.
                                                                            
 
-
                                                                            Table 1 DLI request conditions
                                                                            Condition Key
                                                                            
+
                                                                            
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                            Table 2 DLI request conditions
                                                                            Condition Key
                                                                            
 
                                                                            Type
                                                                            
+
                                                                            Type
                                                                            
 
                                                                            Operator
                                                                            
+
                                                                            Operator
                                                                            
 
                                                                            Description
                                                                            
+
                                                                            Description
                                                                            
                                                                             		
 
                                                                            
 
                                                                            g:CurrentTime
                                                                            
+
                                                                            g:CurrentTime
                                                                            
 
                                                                            Global
                                                                            
+
                                                                            Global
                                                                            
 
                                                                            Date and time
                                                                            
+
                                                                            Date and time
                                                                            
 
                                                                            Time when an authentication request is received
                                                                            
-
                                                                             NOTE: 
                                                                            The time is expressed in the format defined by ISO 8601, for example, 2012-11-11T23:59:59Z.
                                                                            
+
                                                                            Time when an authentication request is received
                                                                            
+
                                                                             NOTE: 
                                                                            The time is expressed in the format defined by ISO 8601, for example, 2012-11-11T23:59:59Z.
                                                                            
 
                                                                            
                                                                             		
 
                                                                            g:MFAPresent
                                                                            
+
                                                                            g:MFAPresent
                                                                            
 
                                                                            Global
                                                                            
+
                                                                            Global
                                                                            
 
                                                                            Boolean
                                                                            
+
                                                                            Boolean
                                                                            
 
                                                                            Whether multi-factor authentication is used during user login
                                                                            
+
                                                                            Whether multi-factor authentication is used during user login
                                                                            
                                                                             		
 
                                                                            g:UserId
                                                                            
+
                                                                            g:UserId
                                                                            
 
                                                                            Global
                                                                            
+
                                                                            Global
                                                                            
 
                                                                            String
                                                                            
+
                                                                            String
                                                                            
 
                                                                            ID of the current login user
                                                                            
+
                                                                            ID of the current login user
                                                                            
                                                                             		
 
                                                                            g:UserName
                                                                            
+
                                                                            g:UserName
                                                                            
 
                                                                            Global
                                                                            
+
                                                                            Global
                                                                            
 
                                                                            String
                                                                            
+
                                                                            String
                                                                            
 
                                                                            Current login user
                                                                            
+
                                                                            Current login username
                                                                            
                                                                             		
 
                                                                            g:ProjectName
                                                                            
+
                                                                            g:ProjectName
                                                                            
 
                                                                            Global
                                                                            
+
                                                                            Global
                                                                            
 
                                                                            String
                                                                            
+
                                                                            String
                                                                            
 
                                                                            Project that you have logged in to
                                                                            
+
                                                                            Project that you have logged in to
                                                                            
                                                                             		
 
                                                                            g:DomainName
                                                                            
+
                                                                            g:DomainName
                                                                            
 
                                                                            Global
                                                                            
+
                                                                            Global
                                                                            
 
                                                                            String
                                                                            
+
                                                                            String
                                                                            
 
                                                                            Domain that you have logged in to
                                                                            
+
                                                                            Domain that you have logged in to
                                                                            
                                                                             		
 
                                                                            
                                                                             
 
                                                                            
 
                                                                            
-
                                                                          • Resource
                                                                            The format is Service name:Region:Domain ID:Resource type:Resource path. The wildcard (*) indicates all options. For details about the resource types and path, see Table 4.
                                                                            
-
                                                                            Example:
                                                                            
-
                                                                            dli:*:*:queue:* indicates all queues.
                                                                            
+
                                                                          • Resource
                                                                            The format is Service name:Region:Domain ID:Resource type:Resource path. The wildcard (*) indicates all options. For details about the resource types and path, see Table 5.
                                                                            
+
                                                                            Example:
                                                                            
+
                                                                            dli:*:*:queue:* indicates all queues.
                                                                            
 
                                                                            • 
 
-
                                                                            Creating a Custom Policy
                                                                            You can set actions and resources of different levels based on scenarios.
                                                                            
-
                                                                            1. Define an action.
                                                                              The format is Service name:Resource type:Action. The wildcard is *. Example:
                                                                              
+
                                                                              Creating a Custom Policy
                                                                              You can set actions and resources at varying levels based on scenarios.
                                                                              
+
                                                                              1. Define an action.
                                                                                The format is Service name:Resource type:Action. You can use wildcards *. Example:
                                                                                
 
-
                                                                                Table 2 Action
                                                                                Action
                                                                                
+
                                                                                
-
-
-
-
-
-
-
                                                                                Table 3 Action
                                                                                Action
                                                                                
 
                                                                                Description
                                                                                
+
                                                                                Description
                                                                                
                                                                                 		
 
                                                                                
 
                                                                                dli:queue:submit_job
                                                                                
+
                                                                                dli:queue:submit_job
                                                                                
 
                                                                                Submission operations on a DLI queue
                                                                                
+
                                                                                Submission operations on a DLI queue
                                                                                
                                                                                 		
 
                                                                                dli:queue:*
                                                                                
+
                                                                                dli:queue:*
                                                                                
 
                                                                                All operations on a DLI queue
                                                                                
+
                                                                                All operations on a DLI queue
                                                                                
                                                                                 		
 
                                                                                dli:*:*
                                                                                
+
                                                                                dli:*:*
                                                                                
 
                                                                                All operations on all DLI resource types
                                                                                
+
                                                                                All operations on all DLI resource types
                                                                                
                                                                                 		
 
                                                                                
                                                                                 
 
                                                                                
 
                                                                                
-
                                                                                For more information about the relationship between operations and system permissions, see Common Operations Supported by DLI System Policy.
                                                                                
-
                                                                              2. Define a resource.
                                                                                The format is Service name:Region:Domain ID:Resource type:Resource path. The wildcard (*) indicates all resources. The five fields can be flexibly set. Different levels of permission control can be set for resource paths based on scenario requirements. If you need to set all resources of the service, you do not need to specify this field. For details about the definition of Resource, see Table 3. For details about the resource types and paths in Resource, see Table 4.
                                                                                
+
                                                                              3. Define a resource.
                                                                                The format is Service name:Region:Domain ID:Resource type:Resource path. The wildcard (*) indicates all resources. You can flexibly set these five fields. The Resource path field can be set with varying levels of access control based on the specific scenario. If you need to set permissions for all resources under this service, you can leave this field unspecified.
                                                                                
+
                                                                                For details about how to define a resource, see Table 4.
                                                                                
+
                                                                                For details about the resource types and resource paths, see Table 5.
                                                                                
 
-
                                                                                Table 3 Resource
                                                                                Resource
                                                                                
+
                                                                                
-
-
-
-
-
-
-
-
-
                                                                                Table 4 Resource
                                                                                Resource
                                                                                
 
                                                                                Description
                                                                                
+
                                                                                Description
                                                                                
                                                                                 		
 
                                                                                
 
                                                                                DLI:*:*:table:databases.dbname.tables.*
                                                                                
+
                                                                                DLI:*:*:table:databases.dbname.tables.*
                                                                                
 
                                                                                DLI, any region, any account ID, all table resources of database dbname
                                                                                
+
                                                                                DLI, any region, any account ID, all table resources of database dbname
                                                                                
                                                                                 		
 
                                                                                DLI:*:*:database:databases.dbname
                                                                                
+
                                                                                DLI:*:*:database:databases.dbname
                                                                                
 
                                                                                DLI, any region, any account ID, resource of database dbname
                                                                                
+
                                                                                DLI, any region, any account ID, resource of database dbname
                                                                                
                                                                                 		
 
                                                                                DLI:*:*:queue:queues.*
                                                                                
+
                                                                                DLI:*:*:queue:queues.*
                                                                                
 
                                                                                DLI, any region, any account ID, any queue resource
                                                                                
+
                                                                                DLI, any region, any account ID, any queue resource
                                                                                
                                                                                 		
 
                                                                                DLI:*:*:jobs:jobs.flink.1
                                                                                
+
                                                                                DLI:*:*:jobs:jobs.flink.1
                                                                                
 
                                                                                DLI, any region, any account ID, Flink job whose ID is 1
                                                                                
+
                                                                                DLI, any region, any account ID, Flink job whose ID is 1
                                                                                
                                                                                 		
 
                                                                                
                                                                                 
 
                                                                                
 
                                                                                
 
-
                                                                                Table 4 DLI resources and their paths
                                                                                Resource Type
                                                                                
+
                                                                                
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                Table 5 DLI resources and their paths
                                                                                Type
                                                                                
 
                                                                                Resource Names
                                                                                
+
                                                                                Resource
                                                                                
 
                                                                                Path
                                                                                
+
                                                                                Path
                                                                                
                                                                                 		
 
                                                                                
 
                                                                                queue
                                                                                
+
                                                                                elasticresourcepool
                                                                                
 
                                                                                DLI queue
                                                                                
+
                                                                                DLI elastic resource pool
                                                                                
 
                                                                                queues.queuename
                                                                                
+
                                                                                elasticresourcepools.name
                                                                                
                                                                                 		
 
                                                                                database
                                                                                
+
                                                                                queue
                                                                                
 
                                                                                DLI database
                                                                                
+
                                                                                DLI queue
                                                                                
 
                                                                                databases.dbname
                                                                                
+
                                                                                queues.queuename
                                                                                
                                                                                 		
 
                                                                                table
                                                                                
+
                                                                                database
                                                                                
 
                                                                                DLI table
                                                                                
+
                                                                                DLI database
                                                                                
 
                                                                                databases.dbname.tables.tbname
                                                                                
+
                                                                                databases.dbname
                                                                                
                                                                                 		
 
                                                                                column
                                                                                
+
                                                                                table
                                                                                
 
                                                                                DLI column
                                                                                
+
                                                                                DLI table
                                                                                
 
                                                                                databases.dbname.tables.tbname.columns.colname
                                                                                
+
                                                                                databases.dbname.tables.tbname
                                                                                
                                                                                 		
 
                                                                                jobs
                                                                                
+
                                                                                column
                                                                                
 
                                                                                DLI Flink job
                                                                                
+
                                                                                DLI column
                                                                                
 
                                                                                jobs.flink.jobid
                                                                                
+
                                                                                databases.dbname.tables.tbname.columns.colname
                                                                                
                                                                                 		
 
                                                                                resource
                                                                                
+
                                                                                jobs
                                                                                
 
                                                                                DLI package
                                                                                
+
                                                                                DLI Flink job
                                                                                
 
                                                                                resources.resourcename
                                                                                
+
                                                                                jobs.flink.jobid
                                                                                
                                                                                 		
 
                                                                                group
                                                                                
+
                                                                                resource
                                                                                
 
                                                                                DLI package group
                                                                                
+
                                                                                DLI package
                                                                                
 
                                                                                groups.groupname
                                                                                
+
                                                                                resources.resourcename
                                                                                
                                                                                 		
 
                                                                                datasourceauth
                                                                                
+
                                                                                group
                                                                                
 
                                                                                DLI cross-source authentication information
                                                                                
+
                                                                                DLI package group
                                                                                
 
                                                                                datasourceauth.name
                                                                                
+
                                                                                groups.groupname
                                                                                
                                                                                 		
 
                                                                                edsconnections
                                                                                
+
                                                                                datasourceauth
                                                                                
 
                                                                                Enhanced datasource connection
                                                                                
+
                                                                                DLI datasource authentication information
                                                                                
 
                                                                                edsconnections.connection ID
                                                                                
+
                                                                                datasourceauth.name
                                                                                
+
                                                                                edsconnections
                                                                                
+
                                                                                Enhanced datasource connection
                                                                                
+
                                                                                edsconnections.Connection ID
                                                                                
+
                                                                                variable
                                                                                
+
                                                                                DLI global variable
                                                                                
+
                                                                                variables.name
                                                                                
+
                                                                                sqldefendrule
                                                                                
+
                                                                                SQL inspection rule
                                                                                
+
                                                                                sqldefendes.*
                                                                                
+
                                                                                catalog
                                                                                
+
                                                                                DLI data catalog
                                                                                
+
                                                                                catalogs.name
                                                                                
                                                                                 		
 
                                                                                
                                                                                 
 
                                                                                
 
                                                                                
 
-
                                                                              4. Combine all the preceding fields into a JSON file to form a complete policy. You can set multiple actions and resources. You can also create a policy on the visualized page provided by IAM. For example:
                                                                                Create a policy that grants users the permission to create and delete databases, submit jobs for any queue, and delete tables under any account ID in any region of DLI.
                                                                                
-
                                                                                {
+
                                                                              5. Combine all of the preceding fields into a JSON string to create a complete policy. You can set multiple actions and resources, and you also have the option to create policies through the IAM console. For example:
                                                                                Create a policy that grants users the permission to create and delete databases, submit jobs for any queue, and delete tables under any account ID in any region of DLI.
                                                                                
+
                                                                                {
     "Version": "1.1",
     "Statement": [
         {
@@ -262,7 +343,7 @@
 }
                                                                                
 
                                                                                6. 
 
-
                                                                                Example Custom Policies
                                                                                • Example 1: Allow policies
                                                                                  • Allow users to create tables across all databases in all regions:
                                                                                    {
+
                                                                                    Example Custom Policies
                                                                                    • Example 1: Allow policies
                                                                                      • Allow users to create tables across all databases in all regions.
                                                                                        {
     "Version": "1.1",
     "Statement": [
         {
@@ -276,7 +357,7 @@
         }
     ]
 }
                                                                                        
-
                                                                                      • Allow users to query column col in the table tb of the database db:
                                                                                        {
+
                                                                                      • Allow users to query column col in the table tb of the database db.
                                                                                        {
     "Version": "1.1",
     "Statement": [
         {
@@ -291,9 +372,9 @@
     ]
 }
                                                                                        
 
                                                                                      
-
                                                                                    • Example 2: Deny policies
                                                                                      A deny policy must be used together with other policies. That is, a user can set a deny policy only after being assigned some operation permissions. Otherwise, the deny policy does not take effect.
                                                                                      
-
                                                                                      If the permissions assigned to a user contain both Allow and Deny actions, the Deny actions take precedence over the Allow actions.
                                                                                      
-
                                                                                      • Deny users to create or delete databases, submit jobs (except the default queue), or delete tables.
                                                                                        {
+
                                                                                      • Example 2: Deny policies
                                                                                        A deny policy must be used together with other policies. Users need to be granted some operation permission policies first before a deny policy can be set within those permissions. Otherwise, if the user has no permissions at all, the deny policy has no practical effect.
                                                                                        
+
                                                                                        In the policies granted to a user, if an action has both Allow and Deny, the Deny takes precedence.
                                                                                        
+
                                                                                        • Deny users to create or delete databases, submit jobs (except the default queue), or delete tables.
                                                                                          {
     "Version": "1.1",
     "Statement": [
         {
@@ -312,7 +393,7 @@
         }
     ]
 }
                                                                                          
-
                                                                                        • Deny users to submit jobs in the demo queue.
                                                                                          {
+
                                                                                        • Deny users to submit jobs on the demo queue.
                                                                                          {
     "Version": "1.1",
     "Statement": [
         {
@@ -329,10 +410,195 @@
 
                                                                                        
 
                                                                                      
 
                                                                                    
+
                                                                                    DLI Resources
                                                                                    Resources are objects that exist within a service. In DLI, resources include the following, and you can select specific resources when creating custom policies by specifying the resource path.
                                                                                    
+
+
                                                                                    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                    Table 6 DLI resources and their paths
                                                                                    Type
                                                                                    
+
                                                                                    Resource
                                                                                    
+
                                                                                    Path
                                                                                    
+
                                                                                    elasticresourcepool
                                                                                    
+
                                                                                    DLI elastic resource pool
                                                                                    
+
                                                                                    elasticresourcepools.name
                                                                                    
+
                                                                                    queue
                                                                                    
+
                                                                                    DLI queue
                                                                                    
+
                                                                                    queues.queuename
                                                                                    
+
                                                                                    database
                                                                                    
+
                                                                                    DLI database
                                                                                    
+
                                                                                    databases.dbname
                                                                                    
+
                                                                                    table
                                                                                    
+
                                                                                    DLI table
                                                                                    
+
                                                                                    databases.dbname.tables.tbname
                                                                                    
+
                                                                                    column
                                                                                    
+
                                                                                    DLI column
                                                                                    
+
                                                                                    databases.dbname.tables.tbname.columns.colname
                                                                                    
+
                                                                                    jobs
                                                                                    
+
                                                                                    DLI Flink job
                                                                                    
+
                                                                                    jobs.flink.jobid
                                                                                    
+
                                                                                    resource
                                                                                    
+
                                                                                    DLI package
                                                                                    
+
                                                                                    resources.resourcename
                                                                                    
+
                                                                                    group
                                                                                    
+
                                                                                    DLI package group
                                                                                    
+
                                                                                    groups.groupname
                                                                                    
+
                                                                                    datasourceauth
                                                                                    
+
                                                                                    DLI datasource authentication information
                                                                                    
+
                                                                                    datasourceauth.name
                                                                                    
+
                                                                                    edsconnections
                                                                                    
+
                                                                                    Enhanced datasource connection
                                                                                    
+
                                                                                    edsconnections.Connection ID
                                                                                    
+
                                                                                    variable
                                                                                    
+
                                                                                    DLI global variable
                                                                                    
+
                                                                                    variables.name
                                                                                    
+
                                                                                    sqldefendrule
                                                                                    
+
                                                                                    SQL inspection rule
                                                                                    
+
                                                                                    sqldefendes.*
                                                                                    
+
                                                                                    catalog
                                                                                    
+
                                                                                    DLI data catalog
                                                                                    
+
                                                                                    catalogs.name
                                                                                    
+
                                                                                    
+
                                                                                    
+
                                                                                    
+
                                                                                    DLI Request Condition
                                                                                    Request conditions are useful in determining when a custom policy is in effect. A request condition consists of condition keys and operators. Condition keys are either global or service-level and are used in the Condition element of a policy statement. Global condition keys (starting with g:) are available for operations of all services, while service-level condition keys (starting with a service name such as dli) are available only for operations of a specific service. An operator must be used together with a condition key to form a complete condition statement.
                                                                                    
+
                                                                                    IAM provides a set of DLI predefined condition keys. The following table lists the DLI predefined condition keys.
                                                                                    
+
+
                                                                                    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                    Table 7 DLI request conditions
                                                                                    Condition Key
                                                                                    
+
                                                                                    Type
                                                                                    
+
                                                                                    Operator
                                                                                    
+
                                                                                    Description
                                                                                    
+
                                                                                    g:CurrentTime
                                                                                    
+
                                                                                    Global
                                                                                    
+
                                                                                    Date and time
                                                                                    
+
                                                                                    Time when an authentication request is received
                                                                                    
+
                                                                                     NOTE: 
                                                                                    The time is expressed in the format defined by ISO 8601, for example, 2012-11-11T23:59:59Z.
                                                                                    
+
                                                                                    
+
                                                                                    g:MFAPresent
                                                                                    
+
                                                                                    Global
                                                                                    
+
                                                                                    Boolean
                                                                                    
+
                                                                                    Whether multi-factor authentication is used during user login
                                                                                    
+
                                                                                    g:UserId
                                                                                    
+
                                                                                    Global
                                                                                    
+
                                                                                    String
                                                                                    
+
                                                                                    ID of the current login user
                                                                                    
+
                                                                                    g:UserName
                                                                                    
+
                                                                                    Global
                                                                                    
+
                                                                                    String
                                                                                    
+
                                                                                    Current login username
                                                                                    
+
                                                                                    g:ProjectName
                                                                                    
+
                                                                                    Global
                                                                                    
+
                                                                                    String
                                                                                    
+
                                                                                    Project that you have logged in to
                                                                                    
+
                                                                                    g:DomainName
                                                                                    
+
                                                                                    Global
                                                                                    
+
                                                                                    String
                                                                                    
+
                                                                                    Domain that you have logged in to
                                                                                    
+
                                                                                    
+
                                                                                    
+
                                                                                    
 
                                                                                
 
                                                                                
 
                                                                                
-
                                                                                Parent topic: Permissions Management
                                                                                
+
                                                                                Parent topic: IAM Permission Management
                                                                                
 
                                                                                
 
                                                                                
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_01_0457.html b/docs/dli/umn/dli_01_0457.html
index 73ecc2617..54b5ac2c6 100644
--- a/docs/dli/umn/dli_01_0457.html
+++ b/docs/dli/umn/dli_01_0457.html
@@ -4,46 +4,47 @@
 
                                                                                A Flink Jar job involves developing a custom application Jar package based on Flink's capabilities and submitting it to a DLI queue for execution.
                                                                                
 
                                                                                To create a Flink Jar job, you need to write and build your own application Jar package. This is suitable for users who require stream data processing and are proficient in Flink's secondary development capabilities.
                                                                                
 
                                                                                This section describes how to create a Flink Jar job on the DLI management console.
                                                                                
-
                                                                                Prerequisites
                                                                                • When you use a Flink Jar job to access other external data sources, such as OpenTSDB, HBase, Kafka, GaussDB(DWS), RDS, CSS, CloudTable, DCS Redis, and DDS, you need to create a datasource connection to connect the job running queue to the external data source.
                                                                                  • For details about the external data sources that can be accessed by Flink jobs, see Common Development Methods for DLI Cross-Source Analysis.
                                                                                  • For how to create a datasource connection, see Configuring the Network Connection Between DLI and Data Sources (Enhanced Datasource Connection).
                                                                                    On the Resources > Queue Management page, locate the queue you have created, click More in the Operation column, and select Test Address Connectivity to check if the network connection between the queue and the data source is normal. For details, see Testing Address Connectivity.
                                                                                    
+
                                                                                    Prerequisites
                                                                                    • When you use a Flink Jar job to access other external data sources, such as OpenTSDB, HBase, Kafka, GaussDB(DWS), RDS, CSS, CloudTable, DCS Redis, and DDS, you need to create a datasource connection to connect the job running queue to the external data source.
 
                                                                                    • To run a Flink Jar job, you need to build your custom application code into a JAR file and upload it to the OBS bucket that has already been created.
                                                                                    • Flink dependencies have been built in the DLI server and security hardening has been performed based on the open-source community version. To avoid dependency package compatibility issues or log output and dump issues, be careful to exclude the following files when packaging:
                                                                                      • Built-in dependencies (or set the package dependency scope to provided in Maven or SBT)
                                                                                      • Log configuration files (example, log4j.properties/logback.xml)
                                                                                      • JAR package for log output implementation (example, log4j). 
                                                                                      
 
                                                                                    
 
                                                                                    
+
                                                                                    Precautions
                                                                                    Before creating and submitting jobs, you are advised to enable CTS to record DLI operations for queries, audits, and tracking. To view the DLI operations that can be recorded by CTS, see Using CTS to Audit DLI.
                                                                                    
+
                                                                                    
 
                                                                                    Creating a Flink Jar Job
                                                                                    1. In the left navigation pane of the DLI management console, choose Job Management > Flink Jobs. The Flink Jobs page is displayed.
                                                                                    2. In the upper right corner of the Flink Jobs page, click Create Job.
                                                                                      
 
                                                                                    3. Specify job parameters.
                                                                                      
-
                                                                                      Table 1 Job configuration information
                                                                                      Parameter
                                                                                      
+
                                                                                      
-
-
-
-
-
-
-
-
-
@@ -53,42 +54,50 @@
 
                                                                                    4. Click OK to enter the editing page.
                                                                                    5. Select a queue.
                                                                                    6. Configuring Flink Jar Job parameters
                                                                                      
 
                                                                                      
-
                                                                                      7. Table 1 Job configuration information
                                                                                      Parameter
                                                                                      
 
                                                                                      Description
                                                                                      
+
                                                                                      Description
                                                                                      
                                                                                       		
 
                                                                                      
 
                                                                                      Type
                                                                                      
+
                                                                                      Type
                                                                                      
 
                                                                                      Select Flink Jar.
                                                                                      
+
                                                                                      Select Flink Jar.
                                                                                      
                                                                                       		
 
                                                                                      Name
                                                                                      
+
                                                                                      Name
                                                                                      
 
                                                                                      Job name. Enter 1 to 57 characters. Only letters, numbers, hyphens (-), and underscores (_) are allowed.
                                                                                      
+
                                                                                      Job name. The value can contain up to 57 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
                                                                                      
 
                                                                                       NOTE: 
                                                                                      The job name must be globally unique.
                                                                                      
 
                                                                                      
                                                                                       		
 
                                                                                      Description
                                                                                      
+
                                                                                      Description
                                                                                      
 
                                                                                      Description of a job. It can be up to 512 characters long.
                                                                                      
+
                                                                                      Job description. It can contain up to 512 characters.
                                                                                      
                                                                                       		
 
                                                                                      Tags
                                                                                      
+
                                                                                      Tags
                                                                                      
 
                                                                                      Tags used to identify cloud resources. A tag includes the tag key and tag value. If you want to use the same tag to identify multiple cloud resources, that is, to select the same tag from the drop-down list box for all services, you are advised to create predefined tags on the Tag Management Service (TMS).
                                                                                      
-
                                                                                      For details, see .
                                                                                      
+
                                                                                      Tags used to identify cloud resources. A tag includes the tag key and tag value. If you want to use the same tag to identify multiple cloud resources, that is, to select the same tag from the drop-down list box for all services, you are advised to create predefined tags on the Tag Management Service (TMS).
                                                                                      
 
                                                                                       NOTE: 
                                                                                      • A maximum of 20 tags can be added.
                                                                                      • Only one tag value can be added to a tag key.
                                                                                      • The key name in each resource must be unique.
                                                                                      
 
                                                                                      
-
                                                                                      • Tag key: Enter a tag key name in the text box.
                                                                                         NOTE: 
                                                                                        A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                        
+
                                                                                        • Tag key: Enter a tag key name in the text box.
                                                                                           NOTE: 
                                                                                          A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                          
 
                                                                                          
 
                                                                                        
-
                                                                                        • Tag value: Enter a tag value in the text box.
                                                                                           NOTE: 
                                                                                          A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.
                                                                                          
+
                                                                                          • Tag value: Enter a tag value in the text box.
                                                                                             NOTE: 
                                                                                            A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.
                                                                                            
 
                                                                                            
 
                                                                                          
 
                                                                                      		
 
                                                                                      Table 2 Parameters
                                                                                      Parameter
                                                                                      
+
                                                                                      
-
-
-
-
-
+
+
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@@ -130,67 +136,80 @@
 
                                                                                    7. Set compute resource specification parameters.
                                                                                      
-
                                                                                      8. Table 2 Parameter descriptions
                                                                                      Parameter
                                                                                      
 
                                                                                      Description
                                                                                      
+
                                                                                      Description
                                                                                      
                                                                                       		
 
                                                                                      
 
                                                                                      Queue
                                                                                      
+
                                                                                      Queue
                                                                                      
 
                                                                                      Select a queue where you want to run your job.
                                                                                      
+
                                                                                      Select a queue where you want to run your job.
                                                                                      
                                                                                       		
 
                                                                                      Application
                                                                                      
+
                                                                                      Flink Version
                                                                                      
 
                                                                                      Select a Jar job package.
                                                                                      
+
                                                                                      Flink version used for job running. Flink versions have varying feature support.
                                                                                      
+
                                                                                       NOTE: 
                                                                                      You are advised not to use Flink of different versions for a long time.
                                                                                      
+
                                                                                      • Doing so can lead to code incompatibility, which can negatively impact job execution efficiency.
                                                                                      • Doing so may result in job execution failures due to conflicts in dependencies. Jobs rely on specific versions of libraries or components.
                                                                                      
+
                                                                                      
+
                                                                                      Application
                                                                                      
+
                                                                                      Select a Jar job package.
                                                                                      
 
                                                                                      There are the following ways to manage JAR files:
                                                                                      
 
                                                                                      • Upload packages to OBS: Upload Jar packages to an OBS bucket in advance and select the corresponding OBS path.
                                                                                      • Upload packages to DLI: Upload JAR files to an OBS bucket in advance and create a package on the Data Management > Package Management page of the DLI management console. For details, see Creating a DLI Package.
                                                                                      
 
                                                                                      For Flink 1.15 or later, you can only select packages from OBS, instead of DLI.
                                                                                      
                                                                                       		
 
                                                                                      Main Class
                                                                                      
+
                                                                                      Main Class
                                                                                      
 
                                                                                      The name of the JAR package to be loaded, for example, KafkaMessageStreaming.
                                                                                      
+
                                                                                      The name of the JAR package to be loaded, for example, KafkaMessageStreaming.
                                                                                      
 
                                                                                      • Default: Specified based on the Manifest file in the JAR package.
                                                                                      • Manually assign: You must enter the class name and confirm the class arguments (separated by spaces).
                                                                                      
 
                                                                                       NOTE: 
                                                                                      When a class belongs to a package, the main class path must contain the complete package path, for example, packagePath.KafkaMessageStreaming.
                                                                                      
 
                                                                                      
                                                                                       		
 
                                                                                      Class Arguments
                                                                                      
+
                                                                                      Class Arguments
                                                                                      
 
                                                                                      List of arguments of a specified class. The arguments are separated by spaces.
                                                                                      
+
                                                                                      List of arguments of a specified class. The arguments are separated by spaces.
                                                                                      
 
                                                                                      Flink parameters support replacement of non-sensitive global variables. For example, if you add the global variable windowsize in Global Configuration > Global Variables, you can add the -windowsSize {{windowsize}} parameter for the Flink Jar job.
                                                                                      
                                                                                       		
 
                                                                                      JAR Package Dependencies
                                                                                      
+
                                                                                      JAR Package Dependencies
                                                                                      
 
                                                                                      Select a user-defined package dependency. The dependent program packages are stored in the classpath directory of the cluster.
                                                                                      
+
                                                                                      Select a user-defined package dependency. The dependent program packages are stored in the classpath directory of the cluster.
                                                                                      
 
                                                                                      There are the following ways to manage JAR files:
                                                                                      
 
                                                                                      • Upload packages to OBS: Upload Jar packages to an OBS bucket in advance and select the corresponding OBS path.
                                                                                      • Upload packages to DLI: Upload JAR files to an OBS bucket in advance and create a package on the Data Management > Package Management page of the DLI management console. For details, see Creating a DLI Package.
                                                                                      
 
                                                                                      For Flink 1.15 or later, you can only select packages from OBS, instead of DLI.
                                                                                      
@@ -96,9 +105,9 @@
 
                                                                                      For details about built-in dependency packages, see DLI Built-in Dependencies.
                                                                                      
                                                                                       		
 
                                                                                      Other Dependencies
                                                                                      
+
                                                                                      Other Dependencies
                                                                                      
 
                                                                                      User-defined dependency files. Other dependency files need to be referenced in the code.
                                                                                      
+
                                                                                      User-defined dependency files. Other dependency files need to be referenced in the code.
                                                                                      
 
                                                                                      There are the following ways to manage dependency files:
                                                                                      
 
                                                                                      • Upload packages to OBS: Upload dependency files to an OBS bucket in advance and select the corresponding OBS path.
                                                                                      • Upload packages to DLI: Upload dependency files to an OBS bucket in advance and create a package on the Data Management > Package Management page of the DLI management console. For details, see Creating a DLI Package.
                                                                                      
 
                                                                                      For Flink 1.15 or later, you can only select packages from OBS, instead of DLI.
                                                                                      
@@ -106,23 +115,20 @@
 
                                                                                      ClassName.class.getClassLoader().getResource("userData/fileName")
                                                                                      
                                                                                       		
 
                                                                                      Flink Version
                                                                                      
+
                                                                                      Agency
                                                                                      
 
                                                                                      Set Queue before setting this parameter.
                                                                                      
-
                                                                                       NOTE: 
                                                                                      You are advised not to use Flink of different versions for a long time.
                                                                                      
-
                                                                                      • Doing so can lead to code incompatibility, which can negatively impact job execution efficiency.
                                                                                      • Doing so may result in job execution failures due to conflicts in dependencies. Jobs rely on specific versions of libraries or components.
                                                                                      
-
                                                                                      
+
                                                                                      If you choose Flink 1.15 or later to execute your job, you can create a custom agency to allow DLI to access other services.
                                                                                      
+
                                                                                      For how to create a custom agency, see Creating a Custom DLI Agency.
                                                                                      
                                                                                       		
 
                                                                                      Agency
                                                                                      
+
                                                                                      Runtime Configuration
                                                                                      
 
                                                                                      If you choose Flink 1.15 to execute your job, you can create a custom agency to allow DLI to access other services.
                                                                                      
-
                                                                                      Runtime Configuration
                                                                                      
-
                                                                                      User-defined optimization parameters. The parameter format is key=value.
                                                                                      
+
                                                                                      User-defined optimization parameters. The parameter format is key=value.
                                                                                      
 
                                                                                      Flink optimization parameters support replacement non-sensitive global variable. For example, if you create global variable phase in Global Configuration > Global Variables, optimization parameter table.optimizer.agg-phase.strategy={{phase}} can be added to the Flink Jar job.
                                                                                      
+
                                                                                      Flink 1.15 supports minimal submission of Flink Jar jobs. Enable this by configuring flink.dli.job.jar.minimize-submission.enabled=true in the runtime optimization parameters.
                                                                                      
+
                                                                                       NOTE: 
                                                                                      Minimal submission means Flink only submits the necessary job dependencies, not the entire Flink environment. By setting the scope of non-Connector Flink dependencies (starting with flink-) and third-party libraries (like Hadoop, Hive, Hudi, and MySQL-CDC) to provided, you ensure these dependencies are excluded from the Jar job, avoiding conflicts with Flink core dependencies.
                                                                                      
+
                                                                                      • Only Flink 1.15 supports minimal submission of Flink Jar jobs.
                                                                                      • For Flink-related dependencies, use the provided scope by adding <scope>provided</scope> in the dependencies, especially for non-Connector dependencies under the org.apache.flink group starting with flink-.
                                                                                      • For dependencies related to Hadoop, Hive, Hudi, and MySQL-CDC, also use the provided scope by adding <scope>provided</scope> in the dependencies.
                                                                                      • In the Flink source code, only methods marked with @Public or @PublicEvolving are intended for user invocation. DLI guarantees compatibility with these methods.
                                                                                      
+
                                                                                      
                                                                                       		
 
                                                                                      
                                                                                       
 
 
                                                                                      
-
-
-
@@ -120,164 +120,14 @@
 
                                                                                      Viewing Details
                                                                                      This section describes how to view job details. After you create and save a job, you can click the job name to view job details, including SQL statements and parameter settings. For a Jar job, you can only view its parameter settings.
                                                                                      
-
                                                                                      1. In the left navigation pane of the DLI management console, choose Job Management > Flink Jobs. The Flink Jobs page is displayed.
                                                                                      2. Click the name of the job to be viewed. The Job Detail tab is displayed.
                                                                                        In the Job Details tab, you can view SQL statements, configured parameters.
                                                                                        
-
                                                                                        The following uses a Flink SQL job as an example.
-
                                                                                      Table 3 Parameters
                                                                                      Parameter
                                                                                      
+
                                                                                      
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
-
-
                                                                                      Table 3 Parameter descriptions
                                                                                      Parameter
                                                                                      
 
                                                                                      Description
                                                                                      
+
                                                                                      Description
                                                                                      
                                                                                       		
 
                                                                                      
 
                                                                                      CUs
                                                                                      
+
                                                                                      CUs
                                                                                      
 
                                                                                      One CU consists of one vCPU and 4 GB of memory. The number of CUs ranges from 2 to 10000.
                                                                                      
-
                                                                                       NOTE: 
                                                                                      When Task Manager Config is selected, elastic resource pool queue management is optimized by automatically adjusting CUs to match Actual CUs after setting Slot(s) per TM.
                                                                                      
-
                                                                                      CUs = Actual number of CUs = max[Job Manager CPUs + Task Manager CPU, (Job Manager Memory + Task Manager Memory/4)]
                                                                                      
-
                                                                                      • Job Manager CPUs + Task Manager CPUs = Actual TMs x CU(s) per TM + Job Manager CUs.
                                                                                      • Job Manager Memory + Task Manager Memory = Actual TMs x Memory per TM + Job Manager Memory
                                                                                      • If Slot(s) per TM is set, then: Actual TMs = Parallelism/Slot(s) per TM.
                                                                                      • If Slot(s) per TM is not set, then: Actual TMs = (CUs – Job Manager CUs)/CU(s) per TM.
                                                                                      • If Memory per TM and Job Manager Memory in the optimization parameters are not set, then: Memory per TM = CU(s) per TM x 4. Job Manager Memory = Job Manager CUs x 4.
                                                                                      • The parallelism degree of Spark resources is jointly determined by the number of Executors and the number of Executor CPU cores.
                                                                                      
+
                                                                                      One CU consists of one vCPU and 4 GB of memory. The number of CUs ranges from 2 to 10000.
                                                                                      
+
                                                                                       NOTE: 
                                                                                      When Task Manager Config is selected, elastic resource pool queue management is optimized by automatically adjusting CUs to match Actual CUs after setting Slot(s) per TM.
                                                                                      
+
                                                                                      CUs = Actual number of CUs = max[Job Manager CPU + Task Manager CPU, (Job Manager Memory + Task Manager Memory/4)]
                                                                                      
+
                                                                                      • Job Manager CPU + Task Manager CPU = Actual TMs x CU(s) per TM + Job Manager CUs.
                                                                                      • Job Manager Memory + Task Manager Memory = Actual TMs x Memory per TM + Job Manager Memory
                                                                                      • If Slot(s) per TM is set, then: Actual TMs = Parallelism/Slot(s) per TM.
                                                                                      • If Slot(s) per TM is not set, then: Actual TMs = (CUs – Job Manager CUs)/CU(s) per TM.
                                                                                      • If Memory per TM and Job Manager Memory in the optimization parameters are not set, then: Memory per TM = CU(s) per TM x 4. Job Manager Memory = Job Manager CUs x 4.
                                                                                      • The parallelism degree of Spark resources is jointly determined by the number of Executors and the number of Executor CPU cores.
                                                                                      
 
                                                                                      
                                                                                       		
 
                                                                                      Job Manager CUs
                                                                                      
+
                                                                                      Job Manager CUs
                                                                                      
 
                                                                                      Number of CUs for the job management unit.
                                                                                      
+
                                                                                      Number of management unit CUs.
                                                                                      
                                                                                       		
 
                                                                                      Parallelism
                                                                                      
+
                                                                                      Parallelism
                                                                                      
 
                                                                                      Number of tasks concurrently executed by each operator in a job.
                                                                                      
-
                                                                                       NOTE: 
                                                                                      • The value must be less than or equal to four times the number of compute units (CUs minus the number of job manager CUs).
                                                                                      • Set this parameter to a value greater than that configured in the code to avoid job submission failures.
                                                                                      
+
                                                                                      Number of tasks concurrently executed by each operator in a job.
                                                                                      
+
                                                                                       NOTE: 
                                                                                      • The value must be less than or equal to four times the number of compute units (CUs – Job Manager CUs).
                                                                                      • Set this parameter to a value greater than that configured in the code to avoid job submission failures.
                                                                                      
 
                                                                                      
                                                                                       		
 
                                                                                      Task Manager Config
                                                                                      
+
                                                                                      Task Manager Config
                                                                                      
 
                                                                                      Whether Task Manager resource parameters are set
                                                                                      
-
                                                                                      • If this option is selected, you need to set the following parameters:
                                                                                        • CU(s) per TM: Number of resources occupied by each Task Manager.
                                                                                        • Slot(s) per TM: Number of slots contained in each Task Manager.
                                                                                        
+
                                                                                      Whether TaskManager resource parameters are set
                                                                                      
+
                                                                                      • If this option is selected, you need to set the following parameters:
                                                                                        • CU(s) per TM: Number of resources occupied by each TaskManager.
                                                                                        • Slot(s) per TM: Number of slots contained in each TaskManager.
                                                                                        
 
                                                                                      
 
                                                                                      • If not selected, the system automatically uses the default values.
                                                                                        • CU(s) per TM: The default value is 1.
                                                                                        • Slot(s) per TM: The default value is (Parallelism x CU(s) per TM)/(CUs – Job Manager CUs).
                                                                                        
 
                                                                                      
                                                                                       		
 
                                                                                      Save Job Log
                                                                                      
+
                                                                                      Save Job Log
                                                                                      
 
                                                                                      Whether to save the job running logs to the OBS bucket.
                                                                                      
+
                                                                                      Whether to save the job running logs to the OBS bucket.
                                                                                      
 
                                                                                      If you select this parameter, you also need to set OBS Bucket.
                                                                                      
-
                                                                                       CAUTION: 
                                                                                      You are advised to select this parameter. Otherwise, no run log is generated after the job is executed. If the job is abnormal, the run log cannot be obtained for fault locating.
                                                                                      
+
                                                                                       CAUTION: 
                                                                                      You are advised to select this parameter. Otherwise, no run logs will be generated after the job is executed. If the job runs abnormally later, you will be unable to obtain the run logs for troubleshooting.
                                                                                      
 
                                                                                      
 
                                                                                      		
 
                                                                                      OBS Bucket
                                                                                      
+
                                                                                      Enable Checkpointing
                                                                                      
 
                                                                                      This parameter is mandatory when you select Save Job Log.
                                                                                      
-
                                                                                      Select an OBS bucket to store job logs. If the OBS bucket you select is not authorized, click Authorize.
                                                                                      
+
                                                                                      Checkpoints are used to periodically save the job state. Enabling checkpointing allows for the quick recovery of a specific job state in case of system failure.
                                                                                      
+
                                                                                      There are two ways to enable checkpointing in DLI:
                                                                                      
+
                                                                                      • Configure checkpoint-related parameters in the job code, suitable for Flink 1.15 or earlier.
                                                                                      • Enable checkpointing on the Jar job configuration page of the DLI management console, suitable for Flink 1.15 or later.
                                                                                      
+
                                                                                      For Flink 1.15, do not configure checkpoint-related parameters both in the job code and the Jar job configuration page. The configurations in the job code have higher priority. Duplicate configurations may lead to the use of incorrect checkpoint paths during abnormal restarts, causing recovery failures or data inconsistencies.
                                                                                      
+
                                                                                      After selecting Enable Checkpointing, set the following parameters to enable checkpointing:
                                                                                      • Checkpoint Interval: The interval between checkpoints, in seconds.
                                                                                      • Checkpoint Mode: Select a mode for checkpoints. The options are:
                                                                                        • At least once: Events are processed at least once.
                                                                                        • Exactly once: Events are processed only once.
                                                                                        
+
                                                                                      
+
                                                                                      
+
                                                                                       CAUTION: 
                                                                                      • After selecting Enable Checkpointing, you need to set OBS Bucket to save the checkpoint information. The default checkpoint save path is Bucket name/jobs/checkpoint/Directory with job ID prefix.
                                                                                      • Once checkpointing is enabled, do not set checkpoint parameters in the job code, as the parameters configured in the job code have a higher priority than those configured on the job configuration page. Duplicate configurations may cause the job to use incorrect checkpoint paths during abnormal restarts, resulting in recovery failures or data inconsistencies.
                                                                                      • After enabling checkpointing, if Auto Restart on Exception and Restore Job from Checkpoint are both selected, you do not need to set Checkpoint Path. The system will automatically determine the path based on the Enable Checkpointing configuration.
                                                                                      
+
                                                                                      
                                                                                       		
 
                                                                                      Alarm on Job Exception
                                                                                      
+
                                                                                      OBS Bucket
                                                                                      
 
                                                                                      Whether to notify users of any job exceptions, such as running exceptions or arrears, via SMS or email.
                                                                                      
+
                                                                                      This parameter is mandatory when you select Save Job Log.
                                                                                      
+
                                                                                      Select an OBS bucket to store job logs. If the OBS bucket you selected is unauthorized, click Authorize.
                                                                                      
+
                                                                                      Alarm on Job Exception
                                                                                      
+
                                                                                      Whether to notify users of any job exceptions, such as running exceptions or arrears, via SMS or email.
                                                                                      
 
                                                                                      If this option is selected, you need to set the following parameters:
                                                                                      
 
                                                                                      SMN Topic
                                                                                      
 
                                                                                      Select a custom SMN topic. For how to create a custom SMN topic, see "Creating a Topic" in the Simple Message Notification User Guide.
                                                                                      
                                                                                       		
 
                                                                                      Auto Restart upon Exception
                                                                                      
+
                                                                                      Auto Restart upon Exception
                                                                                      
 
                                                                                      Whether automatic restart is enabled. If enabled, jobs will be automatically restarted and restored when exceptions occur.
                                                                                      
+
                                                                                      Whether automatic restart is enabled. If enabled, jobs will be automatically restarted and restored when exceptions occur.
                                                                                      
 
                                                                                      If this option is selected, you need to set the following parameters:
                                                                                      
 
                                                                                      • Max. Retry Attempts: maximum number of retries upon an exception. The unit is times/hour.
                                                                                        • Unlimited: The number of retries is unlimited.
                                                                                        • Limited: The number of retries is user-defined.
                                                                                        
 
                                                                                      • Restore Job from Checkpoint: Restore the job from the saved checkpoint.
                                                                                        If you select this parameter, you need to set Checkpoint Path.
                                                                                        
@@ -201,14 +220,226 @@
 
                                                                                      
 
                                                                                      
 
                                                                                      
+
                                                                                      DLI offers various resource configuration templates based on different Flink engine versions.
                                                                                      
+
                                                                                      Compared with the v1 template, the v2 template does not support the setting of the number of CUs. The v2 template supports the setting of Job Manager Memory and Task Manager Memory.
                                                                                      
+
                                                                                      v1: applicable to Flink 1.12, 1.13, and 1.15.
                                                                                      
+
                                                                                      v2: applicable to Flink 1.13, 1.15, and 1.17.
                                                                                      
+
                                                                                      You are advised to use the parameter settings of v2.
                                                                                      
+
                                                                                      For details about the parameters of v1, see Table 4.
                                                                                      
+
                                                                                      For details about the parameters of v2, see Table 5.
                                                                                      
+
+
                                                                                      
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                      Table 4 Parameter descriptions of v1
                                                                                      Parameter
                                                                                      
+
                                                                                      Description
                                                                                      
+
                                                                                      CUs
                                                                                      
+
                                                                                      One CU consists of one vCPU and 4 GB of memory. The number of CUs ranges from 2 to 10000.
                                                                                      
+
                                                                                       NOTE: 
                                                                                      When Task Manager Config is selected, elastic resource pool queue management is optimized by automatically adjusting CUs to match Actual CUs after setting Slot(s) per TM.
                                                                                      
+
                                                                                      CUs = Actual number of CUs = max[Job Manager CPU + Task Manager CPU, (Job Manager Memory + Task Manager Memory/4)]
                                                                                      
+
                                                                                      • Job Manager CPU + Task Manager CPU = Actual TMs x CU(s) per TM + Job Manager CUs.
                                                                                      • Job Manager Memory + Task Manager Memory = Actual TMs x Memory per TM + Job Manager Memory
                                                                                      • If Slot(s) per TM is set, then: Actual TMs = Parallelism/Slot(s) per TM.
                                                                                      • If Slot(s) per TM is not set, then: Actual TMs = (CUs – Job Manager CUs)/CU(s) per TM.
                                                                                      • If Memory per TM and Job Manager Memory in the optimization parameters are not set, then: Memory per TM = CU(s) per TM x 4. Job Manager Memory = Job Manager CUs x 4.
                                                                                      • The parallelism degree of Spark resources is jointly determined by the number of Executors and the number of Executor CPU cores.
                                                                                      
+
                                                                                      
+
                                                                                      Job Manager CUs
                                                                                      
+
                                                                                      Number of management unit CUs.
                                                                                      
+
                                                                                      Parallelism
                                                                                      
+
                                                                                      Number of tasks concurrently executed by each operator in a job.
                                                                                      
+
                                                                                       NOTE: 
                                                                                      • The value cannot exceed four times the number of compute units (CUs – Job Manager CUs).
                                                                                      • Set this parameter to a value greater than that configured in the code to avoid job submission failures.
                                                                                      
+
                                                                                      
+
                                                                                      Task Manager Config
                                                                                      
+
                                                                                      Whether TaskManager resource parameters are set
                                                                                      
+
                                                                                      • If this option is selected, you need to set the following parameters:
                                                                                        • CU(s) per TM: Number of resources occupied by each TaskManager.
                                                                                        • Slot(s) per TM: Number of slots contained in each TaskManager.
                                                                                        
+
                                                                                      
+
                                                                                      • If not selected, the system automatically uses the default values.
                                                                                        • CU(s) per TM: The default value is 1.
                                                                                        • Slot(s) per TM: The default value is (Parallelism x CU(s) per TM)/(CUs – Job Manager CUs).
                                                                                        
+
                                                                                      
+
                                                                                      Save Job Log
                                                                                      
+
                                                                                      Whether to save the job running logs to the OBS bucket.
                                                                                      
+
                                                                                       CAUTION: 
                                                                                      You are advised to select this parameter. Otherwise, no run logs will be generated after the job is executed. If the job runs abnormally later, you will be unable to obtain the run logs for troubleshooting.
                                                                                      
+
                                                                                      
+
                                                                                      If this option is selected, you need to set the following parameters:
                                                                                      
+
                                                                                      OBS Bucket: Select an OBS bucket to store job logs. If the selected OBS bucket is not authorized, click Authorize.
                                                                                      
+
                                                                                      Alarm on Job Exception
                                                                                      
+
                                                                                      Whether to notify users of any job exceptions, such as running exceptions or arrears, via SMS or email.
                                                                                      
+
                                                                                      If this option is selected, you need to set the following parameters:
                                                                                      
+
                                                                                      SMN Topic
                                                                                      
+
                                                                                      Select a custom SMN topic. For how to create a custom SMN topic, see "Creating a Topic" in the Simple Message Notification User Guide.
                                                                                      
+
                                                                                      Auto Restart upon Exception
                                                                                      
+
                                                                                      Whether automatic restart is enabled. If enabled, jobs will be automatically restarted and restored when exceptions occur.
                                                                                      
+
                                                                                      If this option is selected, you need to set the following parameters:
                                                                                      
+
                                                                                      • Max. Retry Attempts: maximum number of retries upon an exception. The unit is times/hour.
                                                                                        • Unlimited: The number of retries is unlimited.
                                                                                        • Limited: The number of retries is user-defined.
                                                                                        
+
                                                                                      • Restore Job from Checkpoint: Restore the job from the saved checkpoint.
                                                                                        If you select this parameter, you also need to set Checkpoint Path.
                                                                                        
+
                                                                                        Checkpoint Path: Select a path for storing checkpoints. This path must match that configured in the application package. Each job must have a unique checkpoint path, or, you will not be able to obtain the checkpoint.
                                                                                        
+
                                                                                      
+
                                                                                      
+
                                                                                      
+
+
                                                                                      
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                      Table 5 Parameter descriptions of v2
                                                                                      Parameter
                                                                                      
+
                                                                                      Description
                                                                                      
+
                                                                                      Parallelism
                                                                                      
+
                                                                                      Number of tasks concurrently executed by each operator in a job.
                                                                                      
+
                                                                                       NOTE: 
                                                                                      • The minimum parallelism must not be less than 1. The default value is 1.
                                                                                      • This value cannot be greater than four times the compute units (CUs – Job Manager CUs).
                                                                                      
+
                                                                                      
+
                                                                                      Job Manager CPU
                                                                                      
+
                                                                                      Number of vCPUs available for JobManager.
                                                                                      
+
                                                                                      The default value is 1. The minimum value cannot be less than 0.5.
                                                                                      
+
                                                                                      Job Manager Memory
                                                                                      
+
                                                                                      Memory available for JobManager.
                                                                                      
+
                                                                                      The default value is 4 GB. The minimum size cannot be less than 2 GB (2,048 MB). The default unit is GB, which can be set to GB or MB.
                                                                                      
+
                                                                                      Task Manager CPU
                                                                                      
+
                                                                                      Number of vCPUs available for TaskManager.
                                                                                      
+
                                                                                      The default value is 1. The minimum value cannot be less than 0.5.
                                                                                      
+
                                                                                      Task Manager Memory
                                                                                      
+
                                                                                      Memory available for TaskManager.
                                                                                      
+
                                                                                      The default value is 4 GB. The minimum size cannot be less than 2 GB (2,048 MB). The default unit is GB, which can be set to GB or MB.
                                                                                      
+
                                                                                      Slot(s) per TM
                                                                                      
+
                                                                                      Number of parallel tasks that a single TaskManager can support. Each task slot can execute one task in parallel. Increasing task slots enhances the parallel processing capacity of TaskManager but also increases resource consumption.
                                                                                      
+
                                                                                      The number of task slots is linked to the CPU count of TaskManager since each CPU can offer one task slot.
                                                                                      
+
                                                                                      By default, a single TM slot is set to 1. The minimum parallelism must not be less than 1.
                                                                                      
+
                                                                                      Save Job Log
                                                                                      
+
                                                                                      Whether to save the job running logs to the OBS bucket.
                                                                                      
+
                                                                                       CAUTION: 
                                                                                      You are advised to select this parameter. Otherwise, no run logs will be generated after the job is executed. If the job runs abnormally later, you will be unable to obtain the run logs for troubleshooting.
                                                                                      
+
                                                                                      
+
                                                                                      If this option is selected, you need to set the following parameters:
                                                                                      
+
                                                                                      OBS Bucket: Select an OBS bucket to store job logs. If the selected OBS bucket is not authorized, click Authorize.
                                                                                      
+
                                                                                      OBS Bucket
                                                                                      
+
                                                                                      OBS bucket to store job logs and checkpoint information. If the OBS bucket you selected is unauthorized, click Authorize.
                                                                                      
+
                                                                                      Alarm on Job Exception
                                                                                      
+
                                                                                      Whether to notify users of any job exceptions, such as running exceptions or arrears, via SMS or email.
                                                                                      
+
                                                                                      If this option is selected, you need to set the following parameters:
                                                                                      
+
                                                                                      SMN Topic
                                                                                      
+
                                                                                      Select a custom SMN topic. For how to create a custom SMN topic, see "Creating a Topic" in the Simple Message Notification User Guide.
                                                                                      
+
                                                                                      Auto Restart upon Exception
                                                                                      
+
                                                                                      Whether automatic restart is enabled. If enabled, jobs will be automatically restarted and restored when exceptions occur.
                                                                                      
+
                                                                                      If this option is selected, you need to set the following parameters:
                                                                                      
+
                                                                                      • Max. Retry Attempts: maximum number of retries upon an exception. The unit is times/hour.
                                                                                        • Unlimited: The number of retries is unlimited.
                                                                                        • Limited: The number of retries is user-defined.
                                                                                        
+
                                                                                      • Restore Job from Checkpoint: Restore the job from the saved checkpoint.
                                                                                        If you select this parameter, you also need to set Checkpoint Path.
                                                                                        
+
                                                                                        Checkpoint Path: Select a path for storing checkpoints. This path must match that configured in the application package. Each job must have a unique checkpoint path, or, you will not be able to obtain the checkpoint.
                                                                                        
+
                                                                                      
+
                                                                                      
+
                                                                                      
 
                                                                                      
-
                                                                                    8. Click Save on the upper right of the page.
                                                                                    9. Click Start in the upper right corner. On the displayed Start Flink Job page, confirm the job specifications, and click Start Now to start the job. After the job is started, the system automatically switches to the Flink Jobs page, and the created job is displayed in the job list. You can view the job status in the Status column.
                                                                                      • Once a job is successfully submitted, its status changes from Submitting to Running. After the execution is complete, the status changes to Completed.
                                                                                      • If the job status is Submission failed or Running exception, the job fails to submit or run. In this case, you can hover over the status icon in the Status column of the job list to view the error details. You can click  to copy these details. Rectify the fault based on the error information and resubmit the job.
                                                                                      
+
                                                                                      You can set compute resource specification parameters on the Runtime Configuration tab of Flink jobs, and the parameter values have a higher priority than the specified values.
                                                                                      
+
                                                                                      Table 6 describes the parameter mapping.
                                                                                      
+
                                                                                       
                                                                                      In Flink 1.12, you are advised to set compute resource specification parameters based on the configuration method on the console. Using custom parameter settings may result in discrepancies in actual CU statistics.
                                                                                      
+
                                                                                      
+
+
                                                                                      
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                      Table 6 Mapping between compute resource specification parameters on the console and those in the Runtime Configuration
                                                                                      Runtime Configuration
                                                                                      
+
                                                                                      Compute Resource Specification Parameter of v1
                                                                                      
+
                                                                                      Compute Resource Specification Parameter of v2
                                                                                      
+
                                                                                      Description
                                                                                      
+
                                                                                      kubernetes.jobmanager.cpu
                                                                                      
+
                                                                                      Job Manager CUs
                                                                                      
+
                                                                                      Job Manager CPU
                                                                                      
+
                                                                                      Number of vCPUs available for JobManager.
                                                                                      
+
                                                                                      The default value is 1. The minimum value cannot be less than 0.5.
                                                                                      
+
                                                                                      kubernetes.taskmanager.cpu
                                                                                      
+
                                                                                      CU(s) per TM
                                                                                      
+
                                                                                      Task Manager CPU
                                                                                      
+
                                                                                      Number of vCPUs available for TaskManager.
                                                                                      
+
                                                                                      The default value is 1. The minimum value cannot be less than 0.5.
                                                                                      
+
                                                                                      jobmanager.memory.process.size
                                                                                      
+
                                                                                      -
                                                                                      
+
                                                                                      Job Manager Memory
                                                                                      
+
                                                                                      Memory available for JobManager.
                                                                                      
+
                                                                                      The default value is 4 GB. The minimum size cannot be less than 2 GB (2,048 MB). The default unit is GB, which can be set to GB or MB.
                                                                                      
+
                                                                                      taskmanager.memory.process.size
                                                                                      
+
                                                                                      -
                                                                                      
+
                                                                                      Task Manager Memory
                                                                                      
+
                                                                                      Memory available for TaskManager.
                                                                                      
+
                                                                                      The default value is 4 GB. The minimum size cannot be less than 2 GB (2,048 MB). The default unit is GB, which can be set to GB or MB.
                                                                                      
+
                                                                                      
+
                                                                                      
+
                                                                                    10. Click Save in the upper right of the page.
                                                                                    11. Click Start in the upper right corner. On the displayed Start Flink Job page, confirm the job specifications, and click Start Now to start the job. After the job is started, the system automatically switches to the Flink Jobs page, and the created job is displayed in the job list. You can view the job status in the Status column.
                                                                                      • Once a job is successfully submitted, its status changes from Submitting to Running. After the execution is complete, the status changes to Completed.
                                                                                      • If the job status is Submission failed or Running exception, the job fails to submit or run. In this case, you can hover over the status icon in the Status column of the job list to view the error details. You can click  to copy these details. Rectify the fault based on the error information and resubmit the job.
                                                                                      
 
                                                                                      12. 
 
 
 
 
diff --git a/docs/dli/umn/dli_01_0461.html b/docs/dli/umn/dli_01_0461.html
index 1352ac049..8ebfcc601 100644
--- a/docs/dli/umn/dli_01_0461.html
+++ b/docs/dli/umn/dli_01_0461.html
@@ -17,7 +17,7 @@
 
 
                                                                                      Stopping a Job
                                                                                      You can stop a job in the Running or Submitting state.
                                                                                      
 
                                                                                      1. In the left navigation pane of the DLI management console, choose Job Management > Flink Jobs. The Flink Jobs page is displayed.
                                                                                      2. Stop a job using either of the following methods:
                                                                                        • Stopping a job
                                                                                          Locate the row that contains the job to be stopped, click More in the Operation column, and select Stop.
                                                                                          
-
                                                                                          Alternatively, you can select the row where the job you want to stop locates and click Stop in the upper left of the job list.
                                                                                          
+
                                                                                          Alternatively, you can select the row where the job you want to stop locates and click Stop in the upper left of the job list.
                                                                                          
 
                                                                                        • Batch stopping jobs
                                                                                          Locate the rows containing the jobs you want to stop and click Stop in the upper left of the job list.
                                                                                          
 
                                                                                        
 
                                                                                      3. In the displayed Stop Job dialog box, click OK to stop the job.
                                                                                         
                                                                                        • Before stopping a job, you can trigger a savepoint to save the job status information. When you start the job again, you can choose whether to restore the job from the savepoint.
                                                                                        • If you select Trigger savepoint, a savepoint is created. If Trigger savepoint is not selected, no savepoint is created. By default, the savepoint function is disabled.
                                                                                        • The lifecycle of a savepoint starts when the savepoint is triggered and stops the job, and ends when the job is restarted. The savepoint is automatically deleted after the job is restarted.
                                                                                        
@@ -78,15 +78,15 @@
 
                                                                                      
 
                                                                                      Alarm Generation upon Job Exception
                                                                                      
 
                                                                                      Whether to report job exceptions, for example, abnormal job running or exceptions due to an insufficient balance, to users via SMS or email.
                                                                                      
+
                                                                                      Whether to notify users of any job exceptions, such as running exceptions or arrears, via SMS or email.
                                                                                      
 
                                                                                      If this option is selected, you need to set the following parameters:
                                                                                      
 
                                                                                      SMN Topic
                                                                                      
-
                                                                                      Select a user-defined SMN topic. For how to create a custom SMN topic, see "Creating a Topic" in the Simple Message Notification User Guide.
                                                                                      
+
                                                                                      Select a custom SMN topic. For how to create a custom SMN topic, see "Creating a Topic" in the Simple Message Notification User Guide.
                                                                                      
                                                                                       		
 
                                                                                      
 
                                                                                      Auto Restart upon Exception
                                                                                      
 
                                                                                      Whether to enable automatic restart. If this function is enabled, any job that has become abnormal will be automatically restarted.
                                                                                      
+
                                                                                      Whether automatic restart is enabled. If enabled, jobs will be automatically restarted and restored when exceptions occur.
                                                                                      
 
                                                                                      If this option is selected, you need to set the following parameters:
                                                                                      
 
                                                                                      • Max. Retry Attempts: maximum number of retries upon an exception. The unit is times/hour.
                                                                                        • Unlimited: The number of retries is unlimited.
                                                                                        • Limited: The number of retries is user-defined.
                                                                                        
 
                                                                                      • Restore Job from Checkpoint: Restore the job from the saved checkpoint.
                                                                                         NOTE: 
                                                                                        This parameter cannot be configured for Flink SQL jobs or Flink OpenSource SQL jobs.
                                                                                        
diff --git a/docs/dli/umn/dli_01_0462.html b/docs/dli/umn/dli_01_0462.html
index 3e3423a9a..eb172c484 100644
--- a/docs/dli/umn/dli_01_0462.html
+++ b/docs/dli/umn/dli_01_0462.html
@@ -8,7 +8,7 @@
 
 
                                                                                      Description
                                                                                      
 
                                                                                      Instruction
                                                                                      
+
                                                                                      Helpful Link
                                                                                      
                                                                                       		
 
                                                                                      
                                                                                       
 
 
                                                                                      
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                                      Table 3 Parameter descriptions
                                                                                      Parameter
                                                                                      
-
                                                                                      Description
                                                                                      
-
                                                                                      Type
                                                                                      
-
                                                                                      Job type, for example, Flink SQL
                                                                                      
-
                                                                                      Name
                                                                                      
-
                                                                                      Flink job name
                                                                                      
-
                                                                                      Description
                                                                                      
-
                                                                                      Description of a Flink job
                                                                                      
-
                                                                                      Status
                                                                                      
-
                                                                                      Running status of a job
                                                                                      
-
                                                                                      Running Mode
                                                                                      
-
                                                                                      The dedicated resource mode is used by default.
                                                                                      
-
                                                                                      Flink Version
                                                                                      
-
                                                                                      Version of Flink selected for the job.
                                                                                      
-
                                                                                      Runtime Configuration
                                                                                      
-
                                                                                      Displayed when a user-defined parameter is added to a job
                                                                                      
-
                                                                                      CUs
                                                                                      
-
                                                                                      Number of CUs configured for a job
                                                                                      
-
                                                                                      Job Manager CUs
                                                                                      
-
                                                                                      Number of job manager CUs configured for a job.
                                                                                      
-
                                                                                      Parallelism
                                                                                      
-
                                                                                      Number of jobs that can be concurrently executed by a Flink job
                                                                                      
-
                                                                                      CU(s) per TM
                                                                                      
-
                                                                                      Number of CUs occupied by each Task Manager configured for a job
                                                                                      
-
                                                                                      Slot(s) per TM
                                                                                      
-
                                                                                      Number of Task Manager slots configured for a job
                                                                                      
-
                                                                                      OBS Bucket
                                                                                      
-
                                                                                      OBS bucket name. After Enable Checkpointing and Save Job Log are enabled, checkpoints and job logs are saved in this bucket.
                                                                                      
-
                                                                                      Save Job Log
                                                                                      
-
                                                                                      Whether the job running logs are saved to OBS
                                                                                      
-
                                                                                      Alarm on Job Exception
                                                                                      
-
                                                                                      Whether job exceptions are reported
                                                                                      
-
                                                                                      SMN Topic
                                                                                      
-
                                                                                      Name of the SMN topic. This parameter is displayed when Alarm Generation upon Job Exception is enabled.
                                                                                      
-
                                                                                      Auto Restart upon Exception
                                                                                      
-
                                                                                      Whether automatic restart is enabled.
                                                                                      
-
                                                                                      Max. Retry Attempts
                                                                                      
-
                                                                                      Maximum number of retry times upon an exception. Unlimited means the number is not limited.
                                                                                      
-
                                                                                      Savepoint
                                                                                      
-
                                                                                      OBS path of the savepoint
                                                                                      
-
                                                                                      Enable Checkpointing
                                                                                      
-
                                                                                      Whether checkpointing is enabled
                                                                                      
-
                                                                                      Checkpoint Interval
                                                                                      
-
                                                                                      Interval between storing intermediate job running results to OBS. The unit is second.
                                                                                      
-
                                                                                      Checkpoint Mode
                                                                                      
-
                                                                                      Checkpoint mode. Available values are as follows:
                                                                                      
-
                                                                                      • At least once: Events are processed at least once.
                                                                                      • Exactly once: Events are processed only once.
                                                                                      
-
                                                                                      Idle State Retention Time
                                                                                      
-
                                                                                      Clears intermediate states of operators such as GroupBy, RegularJoin, Rank, and Depulicate that have not been updated after the maximum retention time. The default value is 1 hour.
                                                                                      
-
                                                                                      Dirty Data Policy
                                                                                      
-
                                                                                      Policy for processing dirty data. The value is displayed only when there is a dirty data policy. Available values are as follows:
                                                                                      
-
                                                                                      Ignore
                                                                                      
-
                                                                                      Trigger a job exception
                                                                                      
-
                                                                                      Save
                                                                                      
-
                                                                                      Dirty Data Dump Address
                                                                                      
-
                                                                                      OBS path for storing dirty data when Dirty Data Policy is set to Save.
                                                                                      
-
                                                                                      Created
                                                                                      
-
                                                                                      Time when a job is created
                                                                                      
-
                                                                                      Updated
                                                                                      
-
                                                                                      Time when a job was last updated
                                                                                      
-
                                                                                      
-
                                                                                      
-
+
                                                                                      1. In the left navigation pane of the DLI management console, choose Job Management > Flink Jobs. The Flink Jobs page is displayed.
                                                                                      2. Click the name of your desired job.
                                                                                        On the displayed page, you can view the job details, SQL statements, job configuration information, task list, execution plan, commit logs, run logs, log list, and job tags.
                                                                                        
 
                                                                                      
 
 
                                                                                      Viewing Monitoring Information
                                                                                      You can use Cloud Eye to view details about job data input and output.
                                                                                      
 
                                                                                      1. In the left navigation pane of the DLI management console, choose Job Management > Flink Jobs. The Flink Jobs page is displayed.
                                                                                      2. Click the name of the job you want. The job details are displayed.
                                                                                        Click Job Monitoring in the upper right corner of the page to switch to the Cloud Eye console.
                                                                                        
 
                                                                                        The following table describes monitoring metrics related to Flink jobs.
                                                                                        
 
-
                                                                                        Table 4 Monitoring metrics related to Flink jobs
                                                                                        Name
                                                                                        
+
                                                                                        
@@ -355,7 +205,7 @@
 
                                                                                         
                                                                                        If the value is 0, no data is received from the data source.
                                                                                        
 
                                                                                        1. In the left navigation pane of the DLI management console, choose Job Management > Flink Jobs. The Flink Jobs page is displayed.
                                                                                        2. Click the name of the job you want. The job details are displayed.
                                                                                        3. On Task List and view the node information about the task.
                                                                                          View the operator task list. The following table describes the task parameters.
-
                                                                                        Table 3 Monitoring metrics related to Flink jobs
                                                                                        Name
                                                                                        
                                                                                         		
 
                                                                                        Description
                                                                                        
                                                                                         		
 
                                                                                        Table 5 Parameter descriptions
                                                                                        Parameter
                                                                                        
+
                                                                                        
diff --git a/docs/dli/umn/dli_01_0463.html b/docs/dli/umn/dli_01_0463.html
index 6dd84558d..969de7c5b 100644
--- a/docs/dli/umn/dli_01_0463.html
+++ b/docs/dli/umn/dli_01_0463.html
@@ -1,37 +1,36 @@
 
                                                                                        Adding Tags to a Flink Job
                                                                                        
-
                                                                                        A tag is a key-value pair customized by users and used to identify cloud resources. It helps users to classify and search for cloud resources. A tag consists of a tag key and a tag value.
                                                                                        
+
                                                                                        A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value.
                                                                                        
 
                                                                                        DLI allows you to add tags to Flink jobs. You can add tags to Flink jobs to identify information such as the project name, service type, and background. If you use tags in other cloud services, you are advised to create the same tag key-value pairs for cloud resources used by the same business to keep consistency.
                                                                                        
-
                                                                                        DLI supports the following two types of tags:
                                                                                        
-
                                                                                        • Resource tags: indicate non-global tags created on DLI.
                                                                                        
-
                                                                                        • Predefined tags: global tags created on Tag Management Service (TMS).
                                                                                          
+
                                                                                          DLI supports the following two types of tags:
                                                                                          • Resource tags: indicate non-global tags created on DLI.
                                                                                          • Predefined tags: global tags created on Tag Management Service (TMS).
                                                                                            For details about predefined tags, see Tag Management Service User Guide.
                                                                                            
 
                                                                                          
+
                                                                                          
 
                                                                                          This section includes the following content:
                                                                                          
 
 
                                                                                          Managing a Job Tag
                                                                                          DLI allows you to add, modify, or delete tags for jobs.
                                                                                          
-
                                                                                          1. In the left navigation pane of the DLI management console, choose Job Management > Flink Jobs. The Flink Jobs page is displayed.
                                                                                          2. Click the name of the job to be viewed. The Job Details page is displayed.
                                                                                          3. Click Tags to display the tag information about the current job.
                                                                                          4. Click Add/Edit Tag to open to the Add/Edit Tag dialog box.
                                                                                          5. Configure the tag parameters in the Add/Edit Tag dialog box.
                                                                                            
-
                                                                                        Table 4 Parameter descriptions
                                                                                        Parameter
                                                                                        
                                                                                         		
 
                                                                                        Description
                                                                                        
                                                                                         		
 
 
                                                                                        Table 1 Tag parameters
                                                                                        Parameter
                                                                                        
+
                                                                                        1. In the left navigation pane of the DLI management console, choose Job Management > Flink Jobs. The Flink Jobs page is displayed.
                                                                                        2. Click the name of the job to be viewed. The Job Details page is displayed.
                                                                                        3. Click Tags to display the tag information about the current job.
                                                                                        4. On the page that appears, click Add/Edit Tag in the upper left corner.
                                                                                        5. Configure the tag parameters in the Add/Edit Tag dialog box.
                                                                                          
+
                                                                                          
-
-
-
-
-
@@ -41,7 +40,7 @@
 
                                                                                           
                                                                                          • A maximum of 20 tags can be added.
                                                                                          • Only one tag value can be added to a tag key.
                                                                                          • The key name in each resource must be unique.
                                                                                          
 
                                                                                          
-
                                                                                        6. Click OK.
                                                                                        7. (Optional) In the tag list, locate the row where the tag you want to delete resides, click Delete in the Operation column to delete the tag.
                                                                                          8. 
+
                                                                                        8. Click OK.
                                                                                        9. (Optional) To delete a tag, locate the tag in the tag list and click Delete in its Operation column.
                                                                                          10. Searching for a Job by Tag
                                                                                          If tags have been added to a job, you can search for the job by setting tag filtering conditions to quickly find it.
                                                                                          
 
                                                                                          1. In the left navigation pane of the DLI management console, choose Job Management > Flink Jobs. The Flink Jobs page is displayed.
                                                                                          2. In the upper right corner of the page, click the search box and select Tags.
                                                                                          3. Choose a tag key and value as prompted. If no tag key or value is available, create a tag for the job. For details, see Managing a Job Tag.
                                                                                          4. Choose other tags to generate a tag combination for job search. 
                                                                                          5. Click search icon. The target job will be displayed in the job list.
                                                                                          
@@ -49,7 +48,7 @@
 
                                                                                          
 
diff --git a/docs/dli/umn/dli_01_0464.html b/docs/dli/umn/dli_01_0464.html
index 2c950b7bf..c420cab0d 100644
--- a/docs/dli/umn/dli_01_0464.html
+++ b/docs/dli/umn/dli_01_0464.html
@@ -15,7 +15,7 @@
 
-
-
-
@@ -69,7 +69,7 @@
 
-
-
@@ -128,10 +128,10 @@
 
@@ -163,7 +163,7 @@
 
-
                                                                                          Table 1 Tag parameters
                                                                                          Parameter
                                                                                          
 
                                                                                          Description
                                                                                          
+
                                                                                          Description
                                                                                          
                                                                                           		
 
                                                                                          
 
                                                                                          Tag key
                                                                                          
+
                                                                                          Tag key
                                                                                          
 
                                                                                          You can perform the following operations:
                                                                                          
+
                                                                                          You can perform the following operations:
                                                                                          
 
                                                                                          • Click the text box and select a predefined tag key from the drop-down list.
                                                                                            To add a predefined tag, you need to create one on TMS and then select it from the Tag key drop-down list. You can click View predefined tags to go to the Predefined Tags page of the TMS console. Then, click Create Tag in the upper corner of the page to create a predefined tag.
                                                                                            
 
                                                                                            
 
                                                                                          
-
                                                                                          • Enter a tag key in the text box.
                                                                                             NOTE: 
                                                                                            A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                            
+
                                                                                            • Enter a tag key in the text box.
                                                                                               NOTE: 
                                                                                              A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                              
 
                                                                                              
 
                                                                                            
 
                                                                                          		
 
                                                                                          Tag value
                                                                                          
+
                                                                                          Tag value
                                                                                          
 
                                                                                          You can perform the following operations:
                                                                                          
-
                                                                                          • Click the text box and select a predefined tag value from the drop-down list.
                                                                                          • Enter a tag value in the text box.
                                                                                             NOTE: 
                                                                                            A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.
                                                                                            
+
                                                                                          You can perform the following operations:
                                                                                          
+
                                                                                          • Click the text box and select a predefined tag value from the drop-down list.
                                                                                          • Enter a tag value in the text box.
                                                                                             NOTE: 
                                                                                            A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.
                                                                                            
 
                                                                                            
 
                                                                                          
                                                                                           		
 
 
 
 
 
                                                                                          Name
                                                                                          
 
                                                                                          Template name. Enter 1 to 64 characters. Only letters, numbers, hyphens (-), and underscores (_) are allowed.
                                                                                          
+
                                                                                          Template name. The value can contain up to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
                                                                                          
                                                                                           		
 
                                                                                          
 
                                                                                          Description
                                                                                          
@@ -42,7 +42,7 @@
 
 
                                                                                          Name
                                                                                          
 
                                                                                          Template name. Enter 1 to 64 characters. Only letters, numbers, hyphens (-), and underscores (_) are allowed.
                                                                                          
+
                                                                                          Template name. The value can contain up to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
                                                                                          
                                                                                           		
 
                                                                                          
 
                                                                                          Description
                                                                                          
@@ -52,7 +52,7 @@
 
                                                                                          
 
                                                                                          Operation
                                                                                          
 
                                                                                          Create Job: Create a job directly by using the template. After a job is created, the system switches to the Edit page under Job Management.
                                                                                          
+
                                                                                          Create Job: Create a job directly by using the template. After a job is created, the system switches to the Edit page under Job Management.
                                                                                          
                                                                                           		
 
                                                                                          
                                                                                           
 
                                                                                          Name
                                                                                          
 
                                                                                          Template name. Enter 1 to 64 characters. Only letters, numbers, hyphens (-), and underscores (_) are allowed.
                                                                                          
+
                                                                                          Template name. The value can contain up to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
                                                                                          
                                                                                           		
 
                                                                                          
 
                                                                                          Description
                                                                                          
@@ -113,7 +113,7 @@
 
                                                                                          
 
                                                                                          Name
                                                                                          
 
                                                                                          Template name. Enter 1 to 64 characters. Only letters, numbers, hyphens (-), and underscores (_) are allowed.
                                                                                          
+
                                                                                          Template name. The value can contain up to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
                                                                                          
 
                                                                                           NOTE: 
                                                                                          The template name must be unique.
                                                                                          
 
                                                                                          
 
                                                                                          Tags used to identify cloud resources. A tag includes the tag key and tag value. If you want to use the same tag to identify multiple cloud resources, that is, to select the same tag from the drop-down list box for all services, you are advised to create predefined tags on the Tag Management Service (TMS).
                                                                                          
 
                                                                                           NOTE: 
                                                                                          • A maximum of 20 tags can be added.
                                                                                          • Only one tag value can be added to a tag key.
                                                                                          • The key name in each resource must be unique.
                                                                                          
 
                                                                                          
-
                                                                                          • Tag key: Enter a tag key name in the text box.
                                                                                             NOTE: 
                                                                                            A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                            
+
                                                                                            • Tag key: Enter a tag key name in the text box.
                                                                                               NOTE: 
                                                                                              A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                              
 
                                                                                              
 
                                                                                            
-
                                                                                            • Tag value: Enter a tag value in the text box.
                                                                                               NOTE: 
                                                                                              A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.
                                                                                              
+
                                                                                              • Tag value: Enter a tag value in the text box.
                                                                                                 NOTE: 
                                                                                                A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.
                                                                                                
 
                                                                                                
 
                                                                                              
 
                                                                                          
 
                                                                                          SQL statement editing area
                                                                                          
 
                                                                                          In the area, you can enter detailed SQL statements to implement business logic. For how to compile SQL statements, see Data Lake Insight SQL Syntax Reference.
                                                                                          
+
                                                                                          In the area, you can enter detailed SQL statements to implement business logic. For how to compile SQL statements, see Data Lake Insight SQL Syntax Reference.
                                                                                          
                                                                                           		
 
                                                                                          
 
                                                                                          Save
                                                                                          
@@ -190,7 +190,7 @@
 
                                                                                          
 
                                                                                          
 
-
                                                                                        10. In the SQL statement editing area, enter SQL statements to implement service logic. For how to compile SQL statements, see Data Lake Insight SQL Syntax Reference.
                                                                                        11. After the SQL statement is edited, click Save in the upper right corner to complete the template creation.
                                                                                        12. (Optional) If you do not need to modify the template, click Create Job in the upper right corner to create a job based on the current template. For how to create a job, see Creating a Flink Jar Job.
                                                                                        
+
                                                                                      3. In the SQL statement editing area, enter SQL statements to implement service logic. For how to compile SQL statements, see Data Lake Insight SQL Syntax Reference.
                                                                                      4. After the SQL statement is edited, click Save in the upper right corner to complete the template creation.
                                                                                      5. (Optional) If you do not need to modify the template, click Create Job in the upper right corner to create a job based on the current template. For how to create a job, see Creating a Flink Jar Job.
                                                                                        6. 
 
                                                                                      6. Creating a template based on an existing job template
                                                                                        1. In the left navigation pane of the DLI management console, choose Job Templates > Flink Templates. Click the Custom Templates tab.
                                                                                        2. In the row where the desired template is located in the custom template list, click Edit under Operation to enter the Edit page.
                                                                                        3. After the modification is complete, set Saving Mode to Save as New.
                                                                                        4. Click Save in the upper right corner to save the template as a new one.
                                                                                        
 
                                                                                        7. 
 
                                                                                        • Creating a template using a created job
                                                                                          1. In the left navigation pane of the DLI management console, choose Job Management > Flink Jobs. The Flink Jobs page is displayed.
                                                                                          2. Click Create Job in the upper right corner. The Create Job page is displayed.
                                                                                          3. Specify parameters as required.
                                                                                          4. Click OK to enter the editing page.
                                                                                          5. After the SQL statement is compiled, click Set as Template.
                                                                                          6. In the Set as Template dialog box that is displayed, specify Name and Description and click OK.
                                                                                          
@@ -210,7 +210,7 @@
 
 
 
diff --git a/docs/dli/umn/dli_01_0465.html b/docs/dli/umn/dli_01_0465.html
index 8d36c8297..5c891f45c 100644
--- a/docs/dli/umn/dli_01_0465.html
+++ b/docs/dli/umn/dli_01_0465.html
@@ -1,6 +1,6 @@
 
 
-
                                                                                          Submitting a Spark Job Using DLI
                                                                                          
+
                                                                                          Submitting a Spark Job on the DLI Management Console
                                                                                          
 
                                                                                          
 
                                                                                          
 
                                                                                            
diff --git a/docs/dli/umn/dli_01_0475.html b/docs/dli/umn/dli_01_0475.html
index 3f527ff73..0942d9ebc 100644
--- a/docs/dli/umn/dli_01_0475.html
+++ b/docs/dli/umn/dli_01_0475.html
@@ -1,82 +1,22 @@
 
 
-
                                                                                            DLI Request Conditions
                                                                                            
-
                                                                                            Request conditions are useful in determining when a custom policy takes effect. A request condition consists of a condition key and operator. Condition keys are either global or service-level and are used in the Condition element of a policy statement. Global condition keys (starting with g:) are available for operations of all services, while service-level condition keys (starting with a service name such as dli) are available only for operations of a specific service. An operator is used together with a condition key to form a complete condition statement.
                                                                                            
-
                                                                                            IAM provides a set of DLI predefined condition keys. The following table lists the predefined condition keys of DLI.
                                                                                            
-
-
                                                                                            
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                                            Table 1 DLI request conditions
                                                                                            Condition Key
                                                                                            
-
                                                                                            Type
                                                                                            
-
                                                                                            Operator
                                                                                            
-
                                                                                            Description
                                                                                            
-
                                                                                            g:CurrentTime
                                                                                            
-
                                                                                            Global
                                                                                            
-
                                                                                            Date and time
                                                                                            
-
                                                                                            Time when an authentication request is received
                                                                                            
-
                                                                                             NOTE: 
                                                                                            The time is expressed in the format defined by ISO 8601, for example, 2012-11-11T23:59:59Z.
                                                                                            
-
                                                                                            
-
                                                                                            g:MFAPresent
                                                                                            
-
                                                                                            Global
                                                                                            
-
                                                                                            Boolean
                                                                                            
-
                                                                                            Whether multi-factor authentication is used during user login
                                                                                            
-
                                                                                            g:UserId
                                                                                            
-
                                                                                            Global
                                                                                            
-
                                                                                            String
                                                                                            
-
                                                                                            ID of the current login user
                                                                                            
-
                                                                                            g:UserName
                                                                                            
-
                                                                                            Global
                                                                                            
-
                                                                                            String
                                                                                            
-
                                                                                            Current login user
                                                                                            
-
                                                                                            g:ProjectName
                                                                                            
-
                                                                                            Global
                                                                                            
-
                                                                                            String
                                                                                            
-
                                                                                            Project that you have logged in to
                                                                                            
-
                                                                                            g:DomainName
                                                                                            
-
                                                                                            Global
                                                                                            
-
                                                                                            String
                                                                                            
-
                                                                                            Domain that you have logged in to
                                                                                            
-
                                                                                            
-
                                                                                            
+
                                                                                            IAM Permission Management
                                                                                            
+
                                                                                            
 
                                                                                            
 
 
diff --git a/docs/dli/umn/dli_01_0479.html b/docs/dli/umn/dli_01_0479.html
index bb4870e92..051aadba1 100644
--- a/docs/dli/umn/dli_01_0479.html
+++ b/docs/dli/umn/dli_01_0479.html
@@ -49,7 +49,7 @@
 
                                                                                            
 
 
diff --git a/docs/dli/umn/dli_01_0480.html b/docs/dli/umn/dli_01_0480.html
index 19d4f9021..06a96e0e6 100644
--- a/docs/dli/umn/dli_01_0480.html
+++ b/docs/dli/umn/dli_01_0480.html
@@ -8,7 +8,7 @@
 
                                                                                            
 
                                                                                          
 
                                                                                          
-
                                                                                          Granting Permissions on Datasource Connections
                                                                                          1. Log in to the DLI management console.
                                                                                          2. Choose Datasource Connections. On the page displayed, click Datasource Authentication.
                                                                                          3. Locate the row containing the datasource authentication to be authorized and click Manage Permission in the Operation column. The User Permissions page is displayed.
                                                                                          4. Click Grant Permission in the upper right corner of the page. On the Grant Permission dialog box displayed, grant permissions on this datasource authentication to other users.
+
                                                                                            Granting Permissions on Datasource Connections
                                                                                            1. Log in to the DLI management console.
                                                                                            2. Choose Datasource Connections. On the page displayed, click Datasource Authentication.
                                                                                            3. Locate the row containing the datasource authentication to be authorized and click Manage Permission in the Operation column. The User Permissions page is displayed.
                                                                                            4. Click Grant Permission in the upper right corner of the page. On the Grant Permission dialog box displayed, grant permissions on this datasource authentication to other users.
 
                                                                                              Table 1 Permission granting parameters
                                                                                              Parameter
                                                                                              
                                                                                               		
 
                                                                                              Description
                                                                                              
@@ -32,7 +32,7 @@
 
 
 
-
                                                                                              Modifying the Permissions of Current User
                                                                                              1. Log in to the DLI management console.
                                                                                              2. Choose Datasource Connections. On the page displayed, click Datasource Authentication.
                                                                                              3. Locate the row containing the datasource authentication to be authorized and click Manage Permission in the Operation column. The User Permissions page is displayed.
                                                                                              4. Click Set Permission in the Operation column to modify the permissions of the current user. Table 1 lists the detailed permission descriptions.
                                                                                                 
                                                                                                • If all options under Set Permission are gray, you are not allowed to change permissions on this datasource connection. You can apply to the administrator, group owner, or other users who have the permission to grant permissions for the permissions to grant and revoke the datasource authentication permissions.
                                                                                                • To revoke all permissions of the current user, click Revoke Permission in the Operation column. The IAM user will no longer have any permission on the datasource authentication.
                                                                                                
+
                                                                                                Modifying the Permissions of Current User
                                                                                                1. Log in to the DLI management console.
                                                                                                2. Choose Datasource Connections. On the page displayed, click Datasource Authentication.
                                                                                                3. Locate the row containing the datasource authentication to be authorized and click Manage Permission in the Operation column. The User Permissions page is displayed.
                                                                                                4. Click Set Permission in the Operation column to modify the permissions of the current user. Table 1 lists the detailed permission descriptions.
                                                                                                   
                                                                                                  • If all options under Set Permission are gray, you are not allowed to change permissions on this datasource connection. You can apply to the administrator, group owner, or other users who have the permission to grant permissions for the permissions to grant and revoke the datasource authentication permissions.
                                                                                                  • To revoke all permissions of the current user, click Revoke Permission in the Operation column. The IAM user will no longer have any permission on the datasource authentication.
                                                                                                  
 
                                                                                                  
 
                                                                                                
 
                                                                                                
diff --git a/docs/dli/umn/dli_01_0487.html b/docs/dli/umn/dli_01_0487.html
index 41c883daa..813409a50 100644
--- a/docs/dli/umn/dli_01_0487.html
+++ b/docs/dli/umn/dli_01_0487.html
@@ -1,11 +1,11 @@
 
 
-
                                                                                                Auto Scaling of Standard Queues
                                                                                                
+
                                                                                                Enabling Elastic Scaling for a Queue in a Non-Elastic Resource Pool
                                                                                                
 
                                                                                                Prerequisites
                                                                                                Newly created queues need to run jobs before they can be scaled in or out.
                                                                                                
-
                                                                                                 
                                                                                                The operations described in this section only apply to standard queues.
                                                                                                
+
                                                                                                 
                                                                                                The operations described in this section only apply to queues in non-elastic resource pools.
                                                                                                
 
                                                                                                
 
                                                                                                
-
                                                                                                Notes and Constraints
                                                                                                • Queues with 16 CUs do not support scale-out or scale-in.
                                                                                                • Queues with 64 CUs do not support scale-in.
                                                                                                • If Status of queue xxx is assigning, which is not available is displayed on the Elastic Scaling page, the queue can be scaled only after the queue resources are allocated.
                                                                                                • If there are not enough physical resources, a queue may not be able to scale out to the desired target size.
                                                                                                • The system does not guarantee that a queue will be scaled in to the desired target size. Typically, the system checks the resource usage before scaling in the queue to determine if there is enough space for scaling in. If the existing resources cannot be scaled in according to the minimum scaling step, the queue may not be scaled in successfully or only partially.
                                                                                                  The scaling step may vary depending on the resource specifications, usually 16 CUs, 32 CUs, 48 CUs, 64 CUs, etc.
                                                                                                  
+
                                                                                                  Notes and Constraints
                                                                                                  • Queues with 16 CUs do not support scale-out or scale-in.
                                                                                                  • Queues with 64 CUs do not support scale-in.
                                                                                                  • If Status of queue xxx is assigning, which is not available is displayed on the Elastic Scaling page, the queue can be scaled only after the queue resources are allocated.
                                                                                                  • If there are not enough physical resources, a queue may not be able to scale out to the desired target size.
                                                                                                  • The system does not guarantee that a queue will be scaled in to the desired target size. Typically, the system checks the resource usage before scaling in the queue to determine if there is enough space for scaling in. If the existing resources cannot be scaled in according to the minimum scaling step, the queue may not be scaled in successfully or only partially.
                                                                                                    The scaling step may vary depending on the resource specifications, usually 16 CUs, 32 CUs, 48 CUs, 64 CUs, and more.
                                                                                                    
 
                                                                                                    For example, if the queue size is 48 CUs and job execution uses 18 CUs, the remaining 30 CUs do not meet the requirement for scaling in by the minimum step of 32 CUs. If a scaling in task is executed, it will fail.
                                                                                                    
 
                                                                                                  
 
                                                                                                  
diff --git a/docs/dli/umn/dli_01_0488.html b/docs/dli/umn/dli_01_0488.html
index 2baf2137b..0b2268ad4 100644
--- a/docs/dli/umn/dli_01_0488.html
+++ b/docs/dli/umn/dli_01_0488.html
@@ -1,9 +1,9 @@
 
 
-
                                                                                                  Setting a Scheduled Auto Scaling Task for a Standard Queue
                                                                                                  
+
                                                                                                  Creating a Scheduled Elastic Scaling Task for a Queue in a Non-Elastic Resource Pool
                                                                                                  
 
                                                                                                  Scenario
                                                                                                  When services are busy, you might need to use more compute resources to process services in a period. After this period, you do not require the same amount of resources. If the purchased queue specifications are small, resources may be insufficient during peak hours. If the queue specifications are large, resources may be wasted.
                                                                                                  
 
                                                                                                  DLI provides scheduled tasks for elastic scale-in and -out in the preceding scenario. You can set different queue sizes (CUs) at different time or in different periods based on your service period or usage and the existing queue specifications to meet your service requirements and reduce costs.
                                                                                                  
-
                                                                                                   
                                                                                                  The operations described in this section only apply to standard queues.
                                                                                                  
+
                                                                                                   
                                                                                                  The operations described in this section only apply to queues in non-elastic resource pools.
                                                                                                  
 
                                                                                                  
 
                                                                                                  
 
                                                                                                  Precautions
                                                                                                  • Newly created queues need to run jobs before they can be scaled in or out.
                                                                                                  • Scheduled scaling tasks are available only for a queue with more than 64 CUs. That is, the minimum specifications of a queue are 64 CUs.
                                                                                                  • A maximum of 12 scheduled tasks can be created for each queue.
                                                                                                  • When each scheduled task starts, the actual start time of the specification change has a deviation of 5 minutes. It is recommended that the task start time be at least 20 minutes earlier than the time when the queue is actually used.
                                                                                                  • The interval between two scheduled tasks must be at least 2 hours.
                                                                                                  • Changing the specifications of a queue is time-consuming. The time required for changing the specifications depends on the difference between the target specifications and the current specifications. You can view the specifications of the current queue on the Queue Management page.
                                                                                                  • If a job is running in the current queue, the queue may fail to be scaled in to the target CU amount value. Instead, it will be scaled in to a value between the current queue specifications and the target specifications. The system will try to scale in again 1 hour later until the next scheduled task starts.
                                                                                                  • If a scheduled task does not scale out or scale in to the target CU amount value, the system triggers the scaling plan again 15 minutes later until the next scheduled task starts.
                                                                                                  
@@ -11,7 +11,7 @@
 
                                                                                                  Creating Periodic Task
                                                                                                  • If only scale-out or scale-in is required, you need to create only one task for changing specifications. Set the Task Name, Final CU Count, and Executed parameters. For details, see Table 1.
                                                                                                  • To set both scale-out and scale-in parameters, you need to create two periodic tasks, and set the Task Name, Final CU Count, and Executed parameters. For details, see Table 1.
                                                                                                  
 
                                                                                                  The procedure is as follows:
                                                                                                  
 
                                                                                                  1. In the navigation pane on the left of the DLI management console, choose Resources > Queue Management.
                                                                                                  2. Locate the queue for which you want to schedule a periodic task for elastic scaling, and choose More > Schedule CU Changes in the Operation column.
                                                                                                  3. On the displayed page, click Create Periodic Task in the upper right corner.
                                                                                                  4. On the Create Periodic Task page, set the required parameters. Click OK.
-
                                                                                                    
-
+
+
+
-
+
+
+
-
-
-
                                                                                                    Table 1 Parameters
                                                                                                    Parameter
                                                                                                    
+
                                                                                                    
@@ -20,7 +20,7 @@
 
diff --git a/docs/dli/umn/dli_01_0489.html b/docs/dli/umn/dli_01_0489.html
index c59b1c359..3443d0865 100644
--- a/docs/dli/umn/dli_01_0489.html
+++ b/docs/dli/umn/dli_01_0489.html
@@ -1,14 +1,12 @@
 
 
-
                                                                                                    Testing Address Connectivity
                                                                                                    
+
                                                                                                    Testing the Network Connectivity Between a Queue and a Data Source
                                                                                                    DLI's address connectivity testing feature can be used to verify network connectivity between DLI queues and destination addresses.
                                                                                                    
 
                                                                                                    This feature is typically utilized for reading and writing external data sources. Once a datasource connection is configured, the communication capability between the DLI queue and the bound peer address is verified.
                                                                                                    
-
                                                                                                    Testing the Address Connectivity Between a Queue and the Data Source
                                                                                                    1. Log in to the DLI management console. In the navigation pane on the left, choose Resources > Queue Management.
                                                                                                    2. On the Queue Management page, locate the row containing the target queue, click More in the Operation column, and select Test Address Connectivity.
                                                                                                    3. On the Test Address Connectivity page, enter the address to be tested. The domain name and IP address are supported, and the port number can be specified.
                                                                                                      You can input the data source address in the following formats: IPv4 address; IPv4 address + Port number; Domain name; Domain name + Port number.
                                                                                                      
-
                                                                                                      · IPv4 address: 192.168.x.x
                                                                                                      
-
                                                                                                      · IPv4 + Port number: 192.168.x.x:8080
                                                                                                      
-
                                                                                                      · Domain name: domain-xxxxxx.com
                                                                                                      
-
                                                                                                      · Domain name + Port number: domain-xxxxxx.com:8080
                                                                                                      
-
                                                                                                    4. Click Test.
                                                                                                      • If the test address is reachable, a message is displayed on the page, indicating that the address is reachable.
                                                                                                      • If the test address is unreachable, the system displays a message indicating that the address is unreachable. Check the network configurations and retry. Network configurations include the VPC peering and the datasource connection. Check whether they have been activated.
                                                                                                      
+
                                                                                                      Testing the Address Connectivity Between a Queue and the Data Source
                                                                                                      1. Log in to the DLI management console. In the navigation pane on the left, choose Resources > Queue Management.
                                                                                                      2. On the Queue Management page, locate the row containing the target queue, click More in the Operation column, and select Test Address Connectivity.
                                                                                                      3. On the Test Address Connectivity page, enter the address to be tested. The domain name and IP address are supported, and the port number can be specified.
                                                                                                        You can input the data source address in the following formats: IPv4 address; IPv4 address + Port number; Domain name; Domain name + Port number.
                                                                                                        
+
                                                                                                        • IPv4 address: 192.168.x.x
                                                                                                        • IPv4 + Port number: 192.168.x.x:8080
                                                                                                        • Domain name: domain-xxxxxx.com
                                                                                                        • Domain name + Port number: domain-xxxxxx.com:8080
                                                                                                        
+
                                                                                                        
+
                                                                                                      4. Click Test.
                                                                                                        • If the test address is reachable, you will receive a message.
                                                                                                        • If the test address is unreachable, you will also receive a message. Check the network configurations and retry. Network configurations include the VPC peering and the datasource connection. Check whether they have been activated.
                                                                                                        
 
                                                                                                      
 
                                                                                                      
 
                                                                                                      Related Operations
                                                                                                      Why Is a Datasource Connection Successfully Created But the Network Connectivity Test Fails?
                                                                                                      
diff --git a/docs/dli/umn/dli_01_0494.html b/docs/dli/umn/dli_01_0494.html
index 4e262bc62..64ece7483 100644
--- a/docs/dli/umn/dli_01_0494.html
+++ b/docs/dli/umn/dli_01_0494.html
@@ -1,6 +1,6 @@
 
 
-
                                                                                                      Using a Custom Image to Enhance the Job Running Environment
                                                                                                      
+
                                                                                                      Enhancing the Job Runtime Environment Using a Custom Image
                                                                                                      
 
                                                                                                      Scenario
                                                                                                      To enhance the functions and performance of Spark and Flink jobs, you can create custom images by downloading the base images provided by DLI and adding dependencies (files, JAR files, or software) and private capabilities required for job execution. This changes the container runtime environment for the jobs.
                                                                                                      
 
                                                                                                      For example, you can add a Python package or C library related to machine learning to a custom image to help you extend functions.
                                                                                                      
 
                                                                                                       
                                                                                                      To use the custom image function, you need to have basic knowledge of Docker.
                                                                                                      
@@ -8,7 +8,7 @@
 
                                                                                                      
 
                                                                                                      Notes and Constraints
                                                                                                      • The base images provided by DLI must be used to create custom images.
                                                                                                      • You cannot modify the DLI components and directories in the base images.
                                                                                                      • Only Spark Jar and Flink Jar jobs are supported.
                                                                                                      
 
                                                                                                      
-
                                                                                                      Use Process
                                                                                                      Figure 1 Process of using a custom image
                                                                                                      
+
                                                                                                      Use Process
                                                                                                      Figure 1 Process of using a custom image
                                                                                                      
 
                                                                                                      1. Obtain DLI base images.
                                                                                                      2. Use Dockerfile to pack dependencies (files, JAR files, or software) required for job execution into the base image to create a custom image.
                                                                                                      3. Publish the custom image to SoftWare Repository for Container (SWR).
                                                                                                      4. On the DLI job editing page, select the created image and run the job.
                                                                                                      5. Check the job execution status.
                                                                                                      
 
                                                                                                      
 
                                                                                                      Obtaining DLI Base Images
                                                                                                      Contact the administrator to obtain DLI base images.
                                                                                                      
@@ -18,14 +18,12 @@
 
                                                                                                      Creating a Custom Image
                                                                                                      The following describes how to package TensorFlow into an image to generate a custom image with TensorFlow installed. Then, you can use the image to run jobs in DLI.
                                                                                                      
 
                                                                                                      1. Prepare the container environment.
                                                                                                      2. Log in to the prepared container environment as user root and run a command to obtain the base image.
                                                                                                        In this example, the Spark base image is used and downloaded to the container image environment in 1 by running the following command:
                                                                                                        
 
                                                                                                        docker pull Address for downloading the base image
                                                                                                        
-
                                                                                                        For details about the address, see Using a Custom Image to Enhance the Job Running Environment.
                                                                                                        
-
                                                                                                        For example, to download the Spark base image, run the following command:
                                                                                                        docker pull swr.xxx/dli-public/spark_general-x86_64:3.3.1-2.3.7.1720240419835647952528832.202404250955
                                                                                                        
-
                                                                                                        
+
                                                                                                        For details about the address, see Obtaining DLI Base Images.
                                                                                                        
 
                                                                                                      3. Access SWR.
                                                                                                        1. Log in to the SWR management console.
                                                                                                        2. In the navigation pane on the left, choose Dashboard and click Generate Login Command in the upper right corner. On the displayed page, click  to copy the login command.
                                                                                                        3. Run the login command on the VM where the container engine is installed.
                                                                                                        
 
                                                                                                      4. Create an organization. If an organization has been created, skip this step.
                                                                                                        1. Log in to the SWR management console.
                                                                                                        2. In the navigation pane on the left, choose Organization Management. On the displayed page, click Create Organization in the upper right corner.
                                                                                                        3. Enter the organization name and click OK.
                                                                                                        
 
                                                                                                      5. Write a Dockerfile.
                                                                                                        vi Dockerfile
                                                                                                        
 
                                                                                                        Pack TensorFlow into the image as follows:
                                                                                                        
-
                                                                                                        ARG BASE_IMG=swr.xxx/dli-public/spark_general-x86_64:3.3.1-2.3.7.1720240419835647952528832.202404250955//Replace xxx with the URL of the base image.
+
                                                                                                        ARG BASE_IMG=swr.xxx/dli-public/spark_general-x86_64:3.3.1-2.3.8.1120250109929356803819072.202501141605//Replace xxx with the URL of the base image.
 
 FROM ${BASE_IMG} as builder
 USER omm //Run this command as user omm.
@@ -39,14 +37,14 @@ USER omm
                                                                                                        
 
                                                                                                      6. Use Dockerfile to generate a custom image.
                                                                                                        Format of the image packaging command:
                                                                                                        docker build -t [Custom organization name]/[Custom image name]: [Image version] --build-arg BASE_IMG= [DLI base image path] -f Dockerfile .
                                                                                                        
 
                                                                                                        
 
                                                                                                        The DLI base image path is the image path in Obtaining DLI Base Images.
                                                                                                        
-
                                                                                                        The following is an example:
                                                                                                        docker build -t mydli/spark:2.4 --build-arg BASE_IMG=swr.xxx/dli-public/spark_general-x86_64:3.3.1-2.3.7.1720240419835647952528832.202404250955 -f Dockerfile .
                                                                                                        
+
                                                                                                        Example:
                                                                                                        docker build -t mydli/spark:2.4 --build-arg BASE_IMG=swr.xxx/dli-public/spark_general-x86_64:3.3.1-2.3.8.1120250109929356803819072.202501141605 -f Dockerfile .
                                                                                                        
 
                                                                                                        
 
                                                                                                      7. Add a tag to the custom image.
                                                                                                        docker tag [Organization name]/[Image name]:[Image version][Image repository address]/[Organization name]/[Image name:version] in 6
                                                                                                        
-
                                                                                                        The following is an example:
                                                                                                        docker tag mydli/spark:2.4 swr.xxx/testdli0617/spark:2.4.5.tensorflow
                                                                                                        
+
                                                                                                        Example:
                                                                                                        docker tag mydli/spark:2.4 swr.xxx/testdli0617/spark:2.4.5.tensorflow
                                                                                                        
 
                                                                                                        
 
                                                                                                      8. Upload the custom image.
                                                                                                        docker push [Image repository address]/[Organization name]/[Image name:Version]
                                                                                                        
 
                                                                                                        Set [Image repository address]/[Organization name]/[Image name:Version] the same as those in 7.
                                                                                                        
-
                                                                                                        The following is an example:
                                                                                                        docker push swr.xxx/testdli0617/spark:2.4.5.tensorflow
                                                                                                        
+
                                                                                                        Example:
                                                                                                        docker push swr.xxx/testdli0617/spark:2.4.5.tensorflow
                                                                                                        
 
                                                                                                        
 
                                                                                                      9. When submitting a Spark or Flink JAR job in DLI, select a custom image.
                                                                                                        • Open the Spark job or Flink job editing page on the management console, select the uploaded and shared image from the custom image list, and run the job.
                                                                                                          If you select a non- shared image, the system displays a message indicating that the image is not authorized. You can use the image only after it is authorized. 
                                                                                                          
 
                                                                                                          
@@ -60,3 +58,10 @@ USER omm
 
                                                                                                      
 
                                                                                                      
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_01_0498.html b/docs/dli/umn/dli_01_0498.html
index 2edbd2e77..78cd5eca5 100644
--- a/docs/dli/umn/dli_01_0498.html
+++ b/docs/dli/umn/dli_01_0498.html
@@ -2,8 +2,8 @@
 
 
                                                                                                      Creating a Flink OpenSource SQL Job
                                                                                                      
 
                                                                                                      This section describes how to create a Flink OpenSource SQL job.
                                                                                                      
-
                                                                                                      DLI Flink OpenSource SQL jobs are fully compatible with the syntax of Flink provided by the community. In addition, Redis and GaussDB(DWS) data source types are added based on the community connector. For the syntax and constraints of Flink SQL DDL, DML, and functions, see Table API & SQL.
                                                                                                      
-
                                                                                                      Prerequisites
                                                                                                    
-
-
@@ -53,7 +52,7 @@
 
                                                                                                    Table 1 Parameter descriptions
                                                                                                    Parameter
                                                                                                    
                                                                                                     		
 
                                                                                                    Description
                                                                                                    
 
                                                                                                    Task Name
                                                                                                    
                                                                                                     		
 
                                                                                                    Enter the name of the periodic task.
                                                                                                    
-
                                                                                                    • Only numbers, letters, and underscores (_) are allowed. The value cannot contain only numbers or start with an underscore (_) or be left unspecified.
                                                                                                    • The value can contain a maximum of 128 characters.
                                                                                                    
+
                                                                                                    • Only digits, letters, and underscores (_) are allowed. The value cannot contain only digits or start with an underscore (_) or be left unspecified.
                                                                                                    • The value can contain a maximum of 128 characters.
                                                                                                    
                                                                                                     		
 
                                                                                                    
 
                                                                                                    Enable Task
                                                                                                    
@@ -41,7 +41,7 @@
 
                                                                                                    Final CUs
                                                                                                    
                                                                                                     		
 
                                                                                                    Specifications after the queue is scaled in or out.
                                                                                                    
-
                                                                                                     NOTE: 
                                                                                                    • By default, the maximum specifications of a queue are 512 CUs.
                                                                                                    • The minimum queue specifications for scheduled scaling are 64 CUs. That is, only when Actual CUs are more than 64 CUs, the scheduled scaling can be performed.
                                                                                                    • The value of Actual CUs must be a multiple of 16.
                                                                                                    
+
                                                                                                     NOTE: 
                                                                                                    • By default, the maximum specifications of a queue are 512 CUs.
                                                                                                    • The minimum queue specifications for scheduled scaling are 64 CUs. That is, only when Actual CUs are more than 64 CUs, the scheduled scaling can be performed.
                                                                                                    • The value of Actual CUs must be a multiple of 16.
                                                                                                    
 
                                                                                                    
 
                                                                                                    		
 
                                                                                                    
 
                                                                                                    Name
                                                                                                    
 
                                                                                                    Job name. Enter 1 to 57 characters. Only letters, numbers, hyphens (-), and underscores (_) are allowed.
                                                                                                    
-
                                                                                                     NOTE: 
                                                                                                    The job name must be globally unique.
                                                                                                    
-
                                                                                                    
+
                                                                                                    Job name. The value can contain up to 57 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
                                                                                                    
+
                                                                                                    The job name must be globally unique.
                                                                                                    
                                                                                                     		
 
                                                                                                    
 
                                                                                                    Description
                                                                                                    
 
                                                                                                    Description of a job. It can contain a maximum of 512 characters.
                                                                                                    
+
                                                                                                    Job description. It can contain up to 512 characters.
                                                                                                    
                                                                                                     		
 
                                                                                                    
 
                                                                                                    Template Name
                                                                                                    
@@ -42,10 +41,10 @@
 
                                                                                                    Tags used to identify cloud resources. A tag includes the tag key and tag value. If you want to use the same tag to identify multiple cloud resources, that is, to select the same tag from the drop-down list box for all services, you are advised to create predefined tags on the Tag Management Service (TMS).
                                                                                                    
 
                                                                                                     NOTE: 
                                                                                                    • A maximum of 20 tags can be added.
                                                                                                    • Only one tag value can be added to a tag key.
                                                                                                    • The key name in each resource must be unique.
                                                                                                    
 
                                                                                                    
-
                                                                                                    • Tag key: Enter a tag key name in the text box.
                                                                                                       NOTE: 
                                                                                                      A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                                      
+
                                                                                                      • Tag key: Enter a tag key name in the text box.
                                                                                                         NOTE: 
                                                                                                        A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                                        
 
                                                                                                        
 
                                                                                                      
-
                                                                                                      • Tag value: Enter a tag value in the text box.
                                                                                                         NOTE: 
                                                                                                        A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.
                                                                                                        
+
                                                                                                        • Tag value: Enter a tag value in the text box.
                                                                                                           NOTE: 
                                                                                                          A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.
                                                                                                          
 
                                                                                                          
 
                                                                                                        
 
                                                                                                    
 
                                                                                                    
 
                                                                                                    
-
                                                                                                  5. Click OK to enter the editing page.
                                                                                                  6. Edit an OpenSource SQL job.
                                                                                                    Enter detailed SQL statements in the statement editing area. For details about SQL statements, see the Data Lake Insight Flink OpenSource SQL Syntax Reference.
                                                                                                    
+
                                                                                                  7. Click OK to enter the editing page.
                                                                                                  8. Edit an OpenSource SQL job.
                                                                                                    Enter detailed SQL statements in the statement editing area. For details about SQL statements, see Data Lake Insight Flink OpenSource SQL Syntax Reference.
                                                                                                    
 
                                                                                                  9. Click Check Semantics.
                                                                                                    • You can Start a job only after the semantic verification is successful.
                                                                                                    • If verification is successful, the message "The SQL semantic verification is complete. No error." will be displayed.
                                                                                                    • If verification fails, a red "X" mark will be displayed in front of each SQL statement that produced an error. You can move the cursor to the "X" mark to view error details and change the SQL statement as prompted.
                                                                                                    
 
                                                                                                     
                                                                                                    Flink 1.15 does not support syntax verification.
                                                                                                    
 
                                                                                                    
@@ -66,7 +65,18 @@
 
                                                                                                    10. 
 
                                                                                                    Queue
                                                                                                    
 
                                                                                                    Select a queue to run the job.
                                                                                                    
+
                                                                                                    Resource queue used to execute Flink jobs.
                                                                                                    
+
                                                                                                    A queue determines the compute resources accessible to a job during its operation within an elastic resource pool. Every queue is allocated with specific resources, known as CUs, whose configuration significantly impacts the job's performance and execution efficiency.
                                                                                                    
+
                                                                                                    Before submitting a job, assess its resource needs and select an appropriate queue.
                                                                                                    
+
                                                                                                    Flink OpenSource SQL jobs support selecting For general purpose queues.
                                                                                                    
+
                                                                                                    Flink Version
                                                                                                    
+
                                                                                                    Flink version used for job running. Flink versions have varying feature support.
                                                                                                    
+
                                                                                                     NOTE: 
                                                                                                    You are advised not to use Flink of different versions for a long time.
                                                                                                    
+
                                                                                                    • Doing so can lead to code incompatibility, which can negatively impact job execution efficiency.
                                                                                                    • Doing so may result in job execution failures due to conflicts in dependencies. Jobs rely on specific versions of libraries or components.
                                                                                                    
+
                                                                                                    
                                                                                                     		
 
                                                                                                    
 
                                                                                                    UDF Jar
                                                                                                    
@@ -79,35 +89,47 @@
 
                                                                                                    
 
                                                                                                    Agency
                                                                                                    
 
                                                                                                    If you choose Flink 1.15 to execute your job, you can create a custom agency to allow DLI to access other services.
                                                                                                    
+
                                                                                                    If you choose Flink 1.15 or later to execute your job, you can create a custom agency to allow DLI to access other services.
                                                                                                    
+
                                                                                                    For how to create a custom agency, see Creating a Custom DLI Agency.
                                                                                                    
+
                                                                                                    Resource Configuration Version
                                                                                                    
+
                                                                                                    DLI offers various resource configuration templates based on different Flink engine versions.
                                                                                                    
+
                                                                                                    Compared with the v1 template, the v2 template does not support the setting of the number of CUs. The v2 template supports the setting of Job Manager Memory and Task Manager Memory.
                                                                                                    
+
                                                                                                    v1: applicable to Flink 1.12, 1.13, and 1.15.
                                                                                                    
+
                                                                                                    v2: applicable to Flink 1.13, 1.15, and 1.17.
                                                                                                    
+
                                                                                                    You are advised to use the parameter settings of v2.
                                                                                                    
+
                                                                                                    For details about the parameters of v1, see Table 3.
                                                                                                    
+
                                                                                                    For details about the parameters of v2, see Table 4.
                                                                                                    
                                                                                                     		
 
                                                                                                    
 
                                                                                                    CUs
                                                                                                    
 
                                                                                                    Sum of the number of compute units and job manager CUs of DLI. One CU equals 1 vCPU and 4 GB.
                                                                                                    
+
                                                                                                    Sum of the number of compute units and JobManager CUs of DLI. One CU equals 1 vCPU and 4 GB of memory.
                                                                                                    
 
                                                                                                    The value is the number of CUs required for job running and cannot exceed the number of CUs in the bound queue.
                                                                                                    
-
                                                                                                     NOTE: 
                                                                                                    When Task Manager Config is selected, elastic resource pool queue management is optimized by automatically adjusting CUs to match Actual CUs after setting Slot(s) per TM.
                                                                                                    
-
                                                                                                    CUs = Actual number of CUs = max[Job Manager CPUs + Task Manager CPU, (Job Manager Memory + Task Manager Memory/4)]
                                                                                                    
-
                                                                                                    • Job Manager CPUs + Task Manager CPUs = Actual TMs x CU(s) per TM + Job Manager CUs.
                                                                                                    • Job Manager Memory + Task Manager Memory = Actual TMs x Memory per TM + Job Manager Memory
                                                                                                    • If Slot(s) per TM is set, then: Actual TMs = Parallelism/Slot(s) per TM.
                                                                                                    • If Slot(s) per TM is not set, then: Actual TMs = (CUs – Job Manager CUs)/CU(s) per TM.
                                                                                                    • If Memory per TM and Job Manager Memory in the optimization parameters are not set, then: Memory per TM = CU(s) per TM x 4. Job Manager Memory = Job Manager CUs x 4.
                                                                                                    • The parallelism degree of Spark resources is jointly determined by the number of Executors and the number of Executor CPU cores.
                                                                                                    
+
                                                                                                     NOTE: 
                                                                                                    When Task Manager Config is selected, elastic resource pool queue management is optimized by automatically adjusting CUs to match Actual CUs after setting Slot(s) per TM.
                                                                                                    
+
                                                                                                    CUs = Actual number of CUs = max[Job Manager CPU + Task Manager CPU, (Job Manager Memory + Task Manager Memory/4)]
                                                                                                    
+
                                                                                                    • Job Manager CPU + Task Manager CPU = Actual TMs x CU(s) per TM + Job Manager CUs.
                                                                                                    • Job Manager Memory + Task Manager Memory = Actual TMs x Memory per TM + Job Manager Memory
                                                                                                    • If Slot(s) per TM is set, then: Actual TMs = Parallelism/Slot(s) per TM.
                                                                                                    • If Slot(s) per TM is not set, then: Actual TMs = (CUs – Job Manager CUs)/CU(s) per TM.
                                                                                                    • If Memory per TM and Job Manager Memory in the optimization parameters are not set, then: Memory per TM = CU(s) per TM x 4. Job Manager Memory = Job Manager CUs x 4.
                                                                                                    • The parallelism degree of Spark resources is jointly determined by the number of Executors and the number of Executor CPU cores.
                                                                                                    
 
                                                                                                    
 
                                                                                                    		
 
                                                                                                    
 
                                                                                                    Job Manager CUs
                                                                                                    
 
                                                                                                    Number of CUs of the management unit.
                                                                                                    
+
                                                                                                    Number of JobManager CUs.
                                                                                                    
                                                                                                     		
 
                                                                                                    
 
                                                                                                    Parallelism
                                                                                                    
                                                                                                     		
 
                                                                                                    Number of tasks concurrently executed by each operator in a job.
                                                                                                    
-
                                                                                                     NOTE: 
                                                                                                    This value cannot be greater than four times the compute units (number of CUs minus the number of job manager CUs).
                                                                                                    
+
                                                                                                     NOTE: 
                                                                                                    This value cannot be greater than four times the compute units (CUs – Job Manager CUs).
                                                                                                    
 
                                                                                                    
 
                                                                                                    		
 
                                                                                                    
 
                                                                                                    Task Manager Config
                                                                                                    
 
                                                                                                    Whether Task Manager resource parameters are set
                                                                                                    
-
                                                                                                    • If selected, you need to set the following parameters:
                                                                                                      • CU(s) per TM: Number of resources occupied by each Task Manager.
                                                                                                      • Slot(s) per TM: Number of slots contained in each Task Manager.
                                                                                                      
+
                                                                                                    Whether TaskManager resource parameters are set
                                                                                                    
+
                                                                                                    • If selected, you need to set the following parameters:
                                                                                                      • CU(s) per TM: Number of resources occupied by each TaskManager.
                                                                                                      • Slot(s) per TM: Number of slots contained in each TaskManager.
                                                                                                      
 
                                                                                                    
 
                                                                                                    • If not selected, the system automatically uses the default values.
                                                                                                      • CU(s) per TM: The default value is 1.
                                                                                                      • Slot(s) per TM: The default value is (Parallelism x CU(s) per TM)/(CUs – Job Manager CUs).
                                                                                                      
 
                                                                                                    
@@ -121,7 +143,7 @@
 
                                                                                                    Save Job Log
                                                                                                    
                                                                                                     		
 
                                                                                                    Whether job running logs are saved to OBS. The logs are saved in the following path: Bucket name/jobs/logs/Directory starting with the job ID.
                                                                                                    
-
                                                                                                     CAUTION: 
                                                                                                    You are advised to configure this parameter. Otherwise, no run log is generated after the job is executed. If the job fails, the run log cannot be obtained for fault locating.
                                                                                                    
+
                                                                                                     CAUTION: 
                                                                                                    You are advised to select this parameter. Otherwise, no run logs will be generated after the job is executed. If the job runs abnormally later, you will be unable to obtain the run logs for troubleshooting.
                                                                                                    
 
                                                                                                    
 
                                                                                                    If this option is selected, you need to set the following parameters:
                                                                                                    
 
                                                                                                    OBS Bucket: Select an OBS bucket to store job logs. If the OBS bucket you selected is unauthorized, click Authorize.
                                                                                                     NOTE: 
                                                                                                    If Enable Checkpointing and Save Job Log are both selected, you only need to authorize OBS once.
                                                                                                    
@@ -173,8 +195,267 @@
 
                                                                                                    
 
                                                                                                    
 
                                                                                                    
+
+
                                                                                                    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                    Table 3 Resource specification parameters of v1
                                                                                                    Parameter
                                                                                                    
+
                                                                                                    Description
                                                                                                    
+
                                                                                                    CUs
                                                                                                    
+
                                                                                                    Sum of the number of compute units and JobManager CUs of DLI. One CU equals 1 vCPU and 4 GB of memory.
                                                                                                    
+
                                                                                                    The value is the number of CUs required for job running and cannot exceed the number of CUs in the bound queue.
                                                                                                    
+
                                                                                                     NOTE: 
                                                                                                    When Task Manager Config is selected, elastic resource pool queue management is optimized by automatically adjusting CUs to match Actual CUs after setting Slot(s) per TM.
                                                                                                    
+
                                                                                                    CUs = Actual number of CUs = max[Job Manager CPU + Task Manager CPU, (Job Manager Memory + Task Manager Memory/4)]
                                                                                                    
+
                                                                                                    • Job Manager CPU + Task Manager CPU = Actual TMs x CU(s) per TM + Job Manager CUs.
                                                                                                    • Job Manager Memory + Task Manager Memory = Actual TMs x Memory per TM + Job Manager Memory
                                                                                                    • If Slot(s) per TM is set, then: Actual TMs = Parallelism/Slot(s) per TM.
                                                                                                    • If Slot(s) per TM is not set, then: Actual TMs = (CUs – Job Manager CUs)/CU(s) per TM.
                                                                                                    • If Memory per TM and Job Manager Memory in the optimization parameters are not set, then: Memory per TM = CU(s) per TM x 4. Job Manager Memory = Job Manager CUs x 4.
                                                                                                    • The parallelism degree of Spark resources is jointly determined by the number of Executors and the number of Executor CPU cores.
                                                                                                    
+
                                                                                                    
+
                                                                                                    Job Manager CUs
                                                                                                    
+
                                                                                                    Number of JobManager CUs.
                                                                                                    
+
                                                                                                    Parallelism
                                                                                                    
+
                                                                                                    Number of tasks concurrently executed by each operator in a job.
                                                                                                    
+
                                                                                                     NOTE: 
                                                                                                    This value cannot be greater than four times the compute units (CUs – Job Manager CUs).
                                                                                                    
+
                                                                                                    
+
                                                                                                    Task Manager Config
                                                                                                    
+
                                                                                                    Whether TaskManager resource parameters are set
                                                                                                    
+
                                                                                                    • If selected, you need to set the following parameters:
                                                                                                      • CU(s) per TM: Number of resources occupied by each TaskManager.
                                                                                                      • Slot(s) per TM: Number of slots contained in each TaskManager.
                                                                                                      
+
                                                                                                    
+
                                                                                                    • If not selected, the system automatically uses the default values.
                                                                                                      • CU(s) per TM: The default value is 1.
                                                                                                      • Slot(s) per TM: The default value is (Parallelism x CU(s) per TM)/(CUs – Job Manager CUs).
                                                                                                      
+
                                                                                                    
+
                                                                                                    OBS Bucket
                                                                                                    
+
                                                                                                    OBS bucket to store job logs and checkpoint information. If the OBS bucket you selected is unauthorized, click Authorize.
                                                                                                    
+
                                                                                                    Save Job Log
                                                                                                    
+
                                                                                                    Whether job running logs are saved to OBS. The logs are saved in the following path: Bucket name/jobs/logs/Directory starting with the job ID.
                                                                                                    
+
                                                                                                     CAUTION: 
                                                                                                    You are advised to select this parameter. Otherwise, no run logs will be generated after the job is executed. If the job runs abnormally later, you will be unable to obtain the run logs for troubleshooting.
                                                                                                    
+
                                                                                                    
+
                                                                                                    If this option is selected, you need to set the following parameters:
                                                                                                    
+
                                                                                                    OBS Bucket: Select an OBS bucket to store job logs. If the OBS bucket you selected is unauthorized, click Authorize.
                                                                                                     NOTE: 
                                                                                                    If Enable Checkpointing and Save Job Log are both selected, you only need to authorize OBS once.
                                                                                                    
+
                                                                                                    
+
                                                                                                    
+
                                                                                                    Alarm on Job Exception
                                                                                                    
+
                                                                                                    Whether to notify users of any job exceptions, such as running exceptions or arrears, via SMS or email.
                                                                                                    
+
                                                                                                    If this option is selected, you need to set the following parameters:
                                                                                                    
+
                                                                                                    SMN Topic
                                                                                                    
+
                                                                                                    Select a custom SMN topic. For how to create a custom SMN topic, see "Creating a Topic" in the Simple Message Notification User Guide.
                                                                                                    
+
                                                                                                    Enable Checkpointing
                                                                                                    
+
                                                                                                    Whether to enable job snapshots. If this function is enabled, jobs can be restored based on the checkpoints.
                                                                                                    
+
                                                                                                    If this option is selected, you need to set the following parameters:
                                                                                                    • Checkpoint Interval: interval for creating checkpoints, in seconds. The value ranges from 1 to 999999, and the default value is 30.
                                                                                                    • Checkpoint Mode can be set to either of the following values:
                                                                                                      • At least once: Events are processed at least once.
                                                                                                      • Exactly once: Events are processed only once.
                                                                                                      
+
                                                                                                    
+
                                                                                                    • OBS Bucket: Select an OBS bucket to store your checkpoints. If the OBS bucket you selected is unauthorized, click Authorize.
                                                                                                      The checkpoint path is Bucket name/jobs/checkpoint/Directory starting with the job ID.
                                                                                                       NOTE: 
                                                                                                      If Enable Checkpointing and Save Job Log are both selected, you only need to authorize OBS once.
                                                                                                      
+
                                                                                                      
+
                                                                                                      
+
                                                                                                    
+
                                                                                                    
+
                                                                                                    Auto Restart upon Exception
                                                                                                    
+
                                                                                                    Whether automatic restart is enabled. If enabled, jobs will be automatically restarted and restored when exceptions occur.
                                                                                                    
+
                                                                                                    If this option is selected, you need to set the following parameters:
                                                                                                    
+
                                                                                                    • Max. Retry Attempts: maximum number of retries upon an exception. The unit is times/hour.
                                                                                                      • Unlimited: The number of retries is unlimited.
                                                                                                      • Limited: The number of retries is user-defined.
                                                                                                      
+
                                                                                                    • Restore Job from Checkpoint: This parameter is available only when Enable Checkpointing is selected.
                                                                                                    
+
                                                                                                    Idle State Retention Time
                                                                                                    
+
                                                                                                    Clears intermediate states of operators such as GroupBy, RegularJoin, Rank, and Depulicate that have not been updated after the maximum retention time. The default value is 1 hour.
                                                                                                    
+
                                                                                                    Dirty Data Policy
                                                                                                    
+
                                                                                                    Policy for processing dirty data. The following policies are supported: Ignore, Trigger a job exception, and Save.
                                                                                                    
+
                                                                                                    If you set this field to Save, the Dirty Data Dump Address must be set. Click the address box to select the OBS path for storing dirty data.
                                                                                                    
+
                                                                                                    This parameter is available only when a DIS data source is used.
                                                                                                    
+
                                                                                                    
+
                                                                                                    
+
+
                                                                                                    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                    Table 4 Resource specification parameters of v2
                                                                                                    Parameter
                                                                                                    
+
                                                                                                    Description
                                                                                                    
+
                                                                                                    Parallelism
                                                                                                    
+
                                                                                                    Number of tasks concurrently executed by each operator in a job.
                                                                                                    
+
                                                                                                     NOTE: 
                                                                                                    • The minimum parallelism must not be less than 1. The default value is 1.
                                                                                                    • This value cannot be greater than four times the compute units (number of CUs minus the number of JobManager CUs).
                                                                                                    
+
                                                                                                    
+
                                                                                                    Job Manager CPU
                                                                                                    
+
                                                                                                    Number of vCPUs available for JobManager.
                                                                                                    
+
                                                                                                    The default value is 1. The minimum value cannot be less than 0.5.
                                                                                                    
+
                                                                                                    Job Manager Memory
                                                                                                    
+
                                                                                                    Memory available for JobManager.
                                                                                                    
+
                                                                                                    The default value is 4 GB. The minimum size cannot be less than 2 GB (2,048 MB). The default unit is GB, which can be set to GB or MB.
                                                                                                    
+
                                                                                                    Task Manager CPU
                                                                                                    
+
                                                                                                    Number of vCPUs available for TaskManager.
                                                                                                    
+
                                                                                                    The default value is 1. The minimum value cannot be less than 0.5.
                                                                                                    
+
                                                                                                    Task Manager Memory
                                                                                                    
+
                                                                                                    Memory available for TaskManager.
                                                                                                    
+
                                                                                                    The default value is 4 GB. The minimum size cannot be less than 2 GB (2,048 MB). The default unit is GB, which can be set to GB or MB.
                                                                                                    
+
                                                                                                    Slot(s) per TM
                                                                                                    
+
                                                                                                    Number of parallel tasks that a single TaskManager can support. Each task slot can execute one task in parallel. Increasing task slots enhances the parallel processing capacity of TaskManagers but also increases resource consumption.
                                                                                                    
+
                                                                                                    The number of task slots is linked to the CPU count of TaskManagers since each CPU can offer one task slot.
                                                                                                    
+
                                                                                                    By default, a single TM slot is set to 1. The minimum parallelism must not be less than 1.
                                                                                                    
+
                                                                                                    OBS Bucket
                                                                                                    
+
                                                                                                    OBS bucket to store job logs and checkpoint information. If the OBS bucket you selected is unauthorized, click Authorize.
                                                                                                    
+
                                                                                                    Save Job Log
                                                                                                    
+
                                                                                                    Whether job running logs are saved to OBS. The logs are saved in the following path: Bucket name/jobs/logs/Directory starting with the job ID.
                                                                                                    
+
                                                                                                     CAUTION: 
                                                                                                    You are advised to select this parameter. Otherwise, no run logs will be generated after the job is executed. If the job runs abnormally later, you will be unable to obtain the run logs for troubleshooting.
                                                                                                    
+
                                                                                                    
+
                                                                                                    If this option is selected, you need to set the following parameters:
                                                                                                    
+
                                                                                                    OBS Bucket: Select an OBS bucket to store job logs. If the OBS bucket you selected is unauthorized, click Authorize.
                                                                                                     NOTE: 
                                                                                                    If Enable Checkpointing and Save Job Log are both selected, you only need to authorize OBS once.
                                                                                                    
+
                                                                                                    
+
                                                                                                    
+
                                                                                                    Alarm on Job Exception
                                                                                                    
+
                                                                                                    Whether to notify users of any job exceptions, such as running exceptions or arrears, via SMS or email.
                                                                                                    
+
                                                                                                    If this option is selected, you need to set the following parameters:
                                                                                                    
+
                                                                                                    SMN Topic
                                                                                                    
+
                                                                                                    Select a custom SMN topic. For how to create a custom SMN topic, see "Creating a Topic" in the Simple Message Notification User Guide.
                                                                                                    
+
                                                                                                    Enable Checkpointing
                                                                                                    
+
                                                                                                    Whether to enable job snapshots. If this function is enabled, jobs can be restored based on the checkpoints.
                                                                                                    
+
                                                                                                    If this option is selected, you need to set the following parameters:
                                                                                                    • Checkpoint Interval: interval for creating checkpoints, in seconds. The value ranges from 1 to 999999, and the default value is 30.
                                                                                                    • Checkpoint Mode can be set to either of the following values:
                                                                                                      • At least once: Events are processed at least once.
                                                                                                      • Exactly once: Events are processed only once.
                                                                                                      
+
                                                                                                    
+
                                                                                                    • OBS Bucket: Select an OBS bucket to store your checkpoints. If the OBS bucket you selected is unauthorized, click Authorize.
                                                                                                      The checkpoint path is Bucket name/jobs/checkpoint/Directory starting with the job ID.
                                                                                                       NOTE: 
                                                                                                      If Enable Checkpointing and Save Job Log are both selected, you only need to authorize OBS once.
                                                                                                      
+
                                                                                                      
+
                                                                                                      
+
                                                                                                    
+
                                                                                                    
+
                                                                                                    Auto Restart upon Exception
                                                                                                    
+
                                                                                                    Whether automatic restart is enabled. If enabled, jobs will be automatically restarted and restored when exceptions occur.
                                                                                                    
+
                                                                                                    If this option is selected, you need to set the following parameters:
                                                                                                    
+
                                                                                                    • Max. Retry Attempts: maximum number of retries upon an exception. The unit is times/hour.
                                                                                                      • Unlimited: The number of retries is unlimited.
                                                                                                      • Limited: The number of retries is user-defined.
                                                                                                      
+
                                                                                                    • Restore Job from Checkpoint: This parameter is available only when Enable Checkpointing is selected.
                                                                                                    
+
                                                                                                    Idle State Retention Time
                                                                                                    
+
                                                                                                    Clears intermediate states of operators such as GroupBy, RegularJoin, Rank, and Depulicate that have not been updated after the maximum retention time. The default value is 1 hour.
                                                                                                    
+
                                                                                                    Dirty Data Policy
                                                                                                    
+
                                                                                                    Policy for processing dirty data. The following policies are supported: Ignore, Trigger a job exception, and Save.
                                                                                                    
+
                                                                                                    If you set this field to Save, the Dirty Data Dump Address must be set. Click the address box to select the OBS path for storing dirty data.
                                                                                                    
+
                                                                                                    This parameter is available only when a DIS data source is used.
                                                                                                    
+
                                                                                                    
+
                                                                                                    
 
                                                                                                  10. (Optional) Set the runtime configuration as required. 
                                                                                                    
-
                                                                                                  11. Click Save.
                                                                                                  12. Click Start. On the displayed Start Flink Jobs page, confirm the job specifications, and click Start Now to start the job.
                                                                                                    After the job is started, the system automatically switches to the Flink Jobs page, and the created job is displayed in the job list. You can view the job status in the Status column. Once a job is successfully submitted, its status changes from Submitting to Running. After the execution is complete, the status changes to Completed.
                                                                                                    
+
                                                                                                    You can set compute resource specification parameters on the Runtime Configuration tab of Flink jobs, and the parameter values have a higher priority than the specified values.
                                                                                                    
+
                                                                                                    Table 5 describes the parameter mapping.
                                                                                                    
+
                                                                                                     
                                                                                                    In Flink 1.12, you are advised to set compute resource specification parameters based on the configuration method on the console. Using custom parameter settings may result in discrepancies in actual CU statistics.
                                                                                                    
+
                                                                                                    
+
+
                                                                                                    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                    Table 5 Mapping between compute resource specification parameters on the console and those on the Runtime Configuration tab
                                                                                                    Runtime Configuration
                                                                                                    
+
                                                                                                    Compute Resource Specification Parameter of v1
                                                                                                    
+
                                                                                                    Compute Resource Specification Parameter of v2
                                                                                                    
+
                                                                                                    Description
                                                                                                    
+
                                                                                                    kubernetes.jobmanager.cpu
                                                                                                    
+
                                                                                                    Job Manager CUs
                                                                                                    
+
                                                                                                    Job Manager CPU
                                                                                                    
+
                                                                                                    Number of vCPUs available for JobManager.
                                                                                                    
+
                                                                                                    The default value is 1. The minimum value cannot be less than 0.5.
                                                                                                    
+
                                                                                                    kubernetes.taskmanager.cpu
                                                                                                    
+
                                                                                                    CU(s) per TM
                                                                                                    
+
                                                                                                    Task Manager CPU
                                                                                                    
+
                                                                                                    Number of vCPUs available for TaskManager.
                                                                                                    
+
                                                                                                    The default value is 1. The minimum value cannot be less than 0.5.
                                                                                                    
+
                                                                                                    jobmanager.memory.process.size
                                                                                                    
+
                                                                                                    -
                                                                                                    
+
                                                                                                    Job Manager Memory
                                                                                                    
+
                                                                                                    Memory available for JobManager.
                                                                                                    
+
                                                                                                    The default value is 4 GB. The minimum size cannot be less than 2 GB (2,048 MB). The default unit is GB, which can be set to GB or MB.
                                                                                                    
+
                                                                                                    taskmanager.memory.process.size
                                                                                                    
+
                                                                                                    -
                                                                                                    
+
                                                                                                    Task Manager Memory
                                                                                                    
+
                                                                                                    Memory available for TaskManager.
                                                                                                    
+
                                                                                                    The default value is 4 GB. The minimum size cannot be less than 2 GB (2,048 MB). The default unit is GB, which can be set to GB or MB.
                                                                                                    
+
                                                                                                    
+
                                                                                                    
+
                                                                                                  13. Click Save.
                                                                                                  14. Click Start. On the displayed Start Flink Job page, confirm the job specifications, and click Start Now to start the job.
                                                                                                    After the job is started, the system automatically switches to the Flink Jobs page, and the created job is displayed in the job list. You can view the job status in the Status column. Once a job is successfully submitted, its status changes from Submitting to Running. After the execution is complete, the status changes to Completed.
                                                                                                    
 
                                                                                                    If the job status is Submission failed or Running exception, the job fails to submit or run. In this case, you can hover over the status icon in the Status column of the job list to view the error details. You can click  to copy these details. Rectify the fault based on the error information and resubmit the job.
                                                                                                    
 
                                                                                                     
                                                                                                    Other buttons are as follows:
                                                                                                    
 
                                                                                                    • Save As: Save the created job as a new job.
                                                                                                    • Static Stream Graph: Provide the static concurrency estimation function and stream graph display function. 
                                                                                                    • Simplified Stream Graph: Display the data processing flow from the source to the sink. 
                                                                                                    • Format: Format the SQL statements in the editing box.
                                                                                                    • Set as Template: Set the created SQL statements as a job template.
                                                                                                    • Theme Settings: Set the theme related parameters, including Font Size, Wrap, and Page Style.
                                                                                                    
@@ -196,7 +477,7 @@
 
                                                                                                    
 
 
diff --git a/docs/dli/umn/dli_01_0504.html b/docs/dli/umn/dli_01_0504.html
index 2224a7e56..841279e30 100644
--- a/docs/dli/umn/dli_01_0504.html
+++ b/docs/dli/umn/dli_01_0504.html
@@ -3,83 +3,13 @@
 
                                                                                                    Overview of DLI Elastic Resource Pools and Queues
                                                                                                    
 
                                                                                                    DLI compute resources are the foundation to run jobs. This section describes the modes of DLI compute resources and queue types.
                                                                                                    
 
                                                                                                    What Are Elastic Resource Pools and Queues?
                                                                                                    Before we dive into the compute resource modes of DLI, let us first understand the basic concepts of elastic resource pools and queues.
                                                                                                    
-
                                                                                                    • An elastic resource pool is a pooled management mode for DLI compute resources, which can be seen as a collection of DLI compute resources. DLI supports the creation of multiple queues within an elastic resource pool, and these queues can share the resources in the elastic resource pool.
                                                                                                    • Queues are the basic units of compute resources that are actually used and allocated in DLI. You can create different queues for different jobs or data processing tasks, and allocate and adjust resources for these queues as needed. To learn more about the queue types in DLI, refer to DLI Queue Types.
                                                                                                    
-
                                                                                                    
-
                                                                                                     
                                                                                                    DLI elastic resource pools are physically isolated, while queues within the same elastic resource pool are logically isolated.
                                                                                                    
-
                                                                                                    You are advised to create separate elastic resource pools for testing and production scenarios to ensure the independence and security of resource management through physical isolation.
                                                                                                    
-
                                                                                                    
-
                                                                                                    DLI Compute Resource Modes
                                                                                                    DLI offers three compute resource management modes, each with unique advantages and use cases.
                                                                                                    
-
                                                                                                    Figure 1 DLI compute resource modes
                                                                                                    
-
                                                                                                    • Elastic resource pool mode: a pooled management mode for compute resources that provides dynamic scaling capabilities. Queues within the same elastic resource pool share compute resources. By setting up a reasonable compute resource allocation policy for queues, you can improve compute resource utilization and meet resource demands during peak hours.
                                                                                                      • Use cases: suitable for scenarios with significant fluctuations in business volume, such as periodic data batch processing tasks or real-time data processing needs.
                                                                                                      • Supported queue types: for SQL (Spark), for SQL (HetuEngine), and for general purpose. To learn more about the queue types in DLI, refer to DLI Queue Types.
                                                                                                         
                                                                                                        General-purpose queues and SQL queues in elastic resource pool mode do not support cross-AZ deployment.
                                                                                                        
-
                                                                                                        
-
                                                                                                      • Usage: first create an elastic resource pool, then create queues within the pool and allocate compute resources. Queues are associated with specific jobs and data processing tasks.
                                                                                                        For how to buy an elastic resource pool and create queues within it, see Creating an Elastic Resource Pool and Creating Queues Within It.
                                                                                                        
+
                                                                                                        • Elastic resource pool
                                                                                                          An elastic resource pool is a pooled management mode for DLI compute resources, which can be seen as a collection of DLI compute resources. DLI supports the creation of multiple queues within an elastic resource pool, and these queues can share the resources in the elastic resource pool.
                                                                                                          
+
                                                                                                          For details about the product specifications of elastic resource pools, see Elastic Resource Pool Specifications.
                                                                                                          
+
                                                                                                          For more about the advantages of elastic resource pools, see Advantages of Elastic Resource Pools.
                                                                                                          
+
                                                                                                          • The physical resource layer of an elastic resource pool consists of compute nodes distributed in different AZs, supporting cross-AZ HA.
                                                                                                          • Multiple queues within the same resource pool share physical resources but maintain logical isolation to enforce resource allocation policies such as priorities and quotas.
                                                                                                          • Elastic resource pools can adjust resources in real time based on queue loads, achieving on-demand auto scaling in minutes.
                                                                                                          • An elastic resource pool can simultaneously support SQL, Spark, and Flink jobs. The specific job types supported depend on the queue types created within the elastic resource pool.
                                                                                                            Refer to DLI Compute Resource Modes and Supported Queue Types.
                                                                                                            
 
                                                                                                          
-
                                                                                                        • Global sharing mode:
                                                                                                          Global sharing mode is a compute resource allocation mode that allocates resources based on the actual amount of data scanned in SQL queries. It does not support specifying or reserving compute resources.
                                                                                                          
-
                                                                                                          The default queue, which is preset by DLI, is the compute resource for global sharing mode, and the resource size is allocated on demand. Users who are unsure of the data size or occasionally need to process data can use the default queue to run jobs.
                                                                                                          
-
                                                                                                          • Use cases: suitable for testing jobs or scenarios with low resource consumption.
                                                                                                          • Supported queue types: Only the preset default queue in DLI is the compute resource for global sharing mode.
                                                                                                            The default queue is typically used by users who are new to DLI but it may lead to resource contention and prevent you from getting the resources you need for your jobs, as its resources are shared among all users. You are advised to use self-built queues to run production jobs.
                                                                                                            
-
                                                                                                          • Usage: The default queue is only applicable to submitting SQL jobs. When submitting SQL jobs on the DLI management console, select the default queue.
                                                                                                          
-
                                                                                                        • Non-elastic resource pool mode (discarded and not recommended):
                                                                                                          The previous-gen of DLI's compute resource management mode is no longer recommended due to its lack of flexibility.
                                                                                                          
-
                                                                                                          Non-elastic resource pool mode provides fixed-specification compute resources that are purchased and exclusively used, and cannot be dynamically adjusted according to demand, which may result in resource waste or insufficient resources during peak hours.
                                                                                                          
-
                                                                                                        
-
-
                                                                                                        
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                                                        Table 1 DLI compute resource modes and supported queue types
                                                                                                        DLI Compute Resource Mode
                                                                                                        
-
                                                                                                        Supported Queue Type
                                                                                                        
-
                                                                                                        Resource Characteristic
                                                                                                        
-
                                                                                                        Use Case
                                                                                                        
-
                                                                                                        Elastic resource pool mode
                                                                                                        
-
                                                                                                        For SQL (Spark)
                                                                                                        
-
                                                                                                        For SQL (HetuEngine)
                                                                                                        
-
                                                                                                        For general purpose
                                                                                                        
-
                                                                                                        Resources are shared among multiple queues for a single user.
                                                                                                        
-
                                                                                                        Resources are dynamically allocated and can be flexibly adjusted.
                                                                                                        
-
                                                                                                        Suitable for scenarios with significant fluctuations in business demand, where resources need to be flexibly adjusted to meet peak and off-peak demands.
                                                                                                        
-
                                                                                                        Global sharing mode
                                                                                                        
-
                                                                                                        default queue
                                                                                                        
-
                                                                                                        Resources are shared among multiple queues for multiple users.
                                                                                                        
-
                                                                                                        You are billed on a pay-per-use basis. Resources cannot be reserved.
                                                                                                        
-
                                                                                                        Suitable for temporary or testing projects where data size is uncertain or data processing is only required occasionally.
                                                                                                        
-
                                                                                                        Non-elastic resource pool mode
                                                                                                        
-
                                                                                                        (discarded, not recommended)
                                                                                                        
-
                                                                                                        For SQL
                                                                                                        
-
                                                                                                        For general purpose
                                                                                                        
-
                                                                                                        Resources are exclusively used by a single user and a single queue.
                                                                                                        
-
                                                                                                        Resources cannot be dynamically adjusted and may remain idle.
                                                                                                        
-
                                                                                                        Discarded and not recommended.
                                                                                                        
-
                                                                                                        
-
                                                                                                        
-
                                                                                                    
-
                                                                                                    To help you understand the use cases for different DLI compute resource modes, we can compare purchasing DLI compute resources to using car services:
                                                                                                    
-
                                                                                                    • The elastic resource pool mode can be compared to "renting a car" where you can dynamically adjust the scale of resources based on actual needs.
                                                                                                      This mode is suitable for scenarios with significant fluctuations in business demand, allowing for flexible adjustment of resources based on peak and off-peak demands to optimize costs.
                                                                                                      
-
                                                                                                    • The global sharing mode can be compared to "taking a taxi" where you only pay for the actual amount of data used.
                                                                                                      This mode is suitable for scenarios where data size is uncertain or data processing is only required occasionally, allowing for on-demand use of resources without the need to pre-purchase or reserve resources.
                                                                                                      
-
                                                                                                    
-
                                                                                                    Elastic Resource Pool Scaling
                                                                                                    Creating or deleting queues within an elastic resource pool triggers elastic resource scaling.
                                                                                                    
-
                                                                                                    Scaling in an elastic resource pool may affect nodes containing shuffle data, leading to the recomputation of Spark tasks. This causes automatic retries for Spark and SQL jobs, and if the retries exceed the limit, the job execution fails, requiring you to rerun the job.
                                                                                                    
-
                                                                                                     
                                                                                                    • Spark 2.3 jobs need to be upgraded to a later Spark version to support dynamic scale-in of the jobs while they are running.
                                                                                                    • Spark Streaming and Flink jobs cannot be scaled in while they are running. To perform a scale-in, suspend the jobs or migrate them to another elastic resource pool.
                                                                                                    
-
                                                                                                    
-
                                                                                                    
-
                                                                                                    DLI Queue Types
                                                                                                    DLI is divided into three queue types: default queue, for SQL, and for general purpose. You can choose the most suitable queue type based on your business scenario and job characteristics.
                                                                                                    
+
                                                                                                  15. Queue
                                                                                                    Queues are the basic units of compute resources that are actually used and allocated in DLI. You can create different queues for different jobs or data processing tasks, and allocate and adjust resources for these queues as needed.
                                                                                                    
+
                                                                                                    DLI is divided into three queue types: default queue, for SQL, and for general purpose. You can choose the most suitable queue type based on your business scenario and job characteristics.
                                                                                                    
 
                                                                                                    • default queue:
                                                                                                      The default queue is a preset queue that is shared among all users. 
                                                                                                      
 
                                                                                                      The default queue does not support specifying the size of resources and resources are allocated on-demand during job execution, with billing based on the actual amount of data scanned.
                                                                                                      
 
                                                                                                      As resources of the default queue are shared among all users, there may be resource contention during use, and it cannot be guaranteed that resources will be available for every job execution.
                                                                                                      
@@ -90,14 +20,175 @@
 
                                                                                                      • For general purpose:
                                                                                                        For general purpose queues are used to execute Spark jobs, Flink OpenSource SQL jobs, and Flink Jar jobs.
                                                                                                        
 
                                                                                                        It is suitable for complex data processing, real-time data stream processing, or batch data processing scenarios.
                                                                                                        
 
                                                                                                      
+
                                                                                                    
+
                                                                                                  
+
                                                                                                   
                                                                                                  DLI elastic resource pools are physically isolated, while queues within the same elastic resource pool are logically isolated.
                                                                                                  
+
                                                                                                  You are advised to create separate elastic resource pools for testing and production scenarios to ensure the independence and security of resource management through physical isolation.
                                                                                                  
+
                                                                                                  
+
                                                                                                  DLI Compute Resource Modes
                                                                                                  DLI offers three compute resource management modes, each with unique advantages and use cases.
                                                                                                  
+
                                                                                                  Figure 1 DLI compute resource modes
                                                                                                  
+
                                                                                                  • Elastic resource pool mode:
                                                                                                    A pooled management mode for compute resources that provides dynamic scaling capabilities. Queues within the same elastic resource pool share compute resources. By setting up a reasonable compute resource allocation policy for queues, you can improve compute resource utilization and meet resource demands during peak hours.
                                                                                                    • Use cases: suitable for scenarios with significant fluctuations in business volume, such as periodic data batch processing tasks or real-time data processing needs.
                                                                                                    • Supported queue types: for SQL (Spark), for SQL (HetuEngine), and for general purpose. For details about DLI queue types, see Queue Types.
                                                                                                       
                                                                                                      General-purpose queues and SQL queues in elastic resource pool mode do not support cross-AZ deployment.
                                                                                                      
+
                                                                                                      
+
                                                                                                    • Usage: first create an elastic resource pool, then create queues within the pool and allocate compute resources. Queues are associated with specific jobs and data processing tasks.
                                                                                                      For how to buy an elastic resource pool and create queues within it, see Creating an Elastic Resource Pool and Creating Queues Within It.
                                                                                                      
+
                                                                                                    
+
                                                                                                    
+
                                                                                                  • Global sharing mode:
                                                                                                    Global sharing mode is a compute resource allocation mode that allocates resources based on the actual amount of data scanned in SQL queries. It does not support specifying or reserving compute resources.
                                                                                                    
+
                                                                                                    The default queue, which is preset by DLI, is the compute resource for global sharing mode, and the resource size is allocated on demand. Users who are unsure of the data size or occasionally need to process data can use the default queue to run jobs.
                                                                                                    
+
                                                                                                    • Use cases: suitable for testing jobs or scenarios with low resource consumption.
                                                                                                    • Supported queue types: Only the preset default queue in DLI is the compute resource for global sharing mode.
                                                                                                      The default queue is typically used by users who are new to DLI but it may lead to resource contention and prevent you from getting the resources you need for your jobs, as its resources are shared among all users. You are advised to use self-built queues to run production jobs.
                                                                                                      
+
                                                                                                    • Usage: The default queue is only applicable to submitting SQL jobs. When submitting SQL jobs on the DLI management console, select the default queue.
                                                                                                    
+
                                                                                                  • Non-elastic resource pool mode (deprecated and not recommended):
                                                                                                    The previous-gen of DLI's compute resource management mode is no longer recommended due to its lack of flexibility.
                                                                                                    
+
                                                                                                    Non-elastic resource pool mode provides fixed-specification compute resources that are purchased and exclusively used, and cannot be dynamically adjusted according to demand, which may result in resource waste or insufficient resources during peak hours.
                                                                                                    
+
                                                                                                  
+
                                                                                                  To help you understand the use cases for different DLI compute resource modes, we can compare purchasing DLI compute resources to using car services:
                                                                                                  
+
                                                                                                  • The elastic resource pool mode can be compared to "renting a car" where you can dynamically adjust the scale of resources based on actual needs.
                                                                                                    This mode is suitable for scenarios with significant fluctuations in business demand, allowing for flexible adjustment of resources based on peak and off-peak demands to optimize costs.
                                                                                                    
+
                                                                                                  • The global sharing mode can be compared to "taking a taxi" where you only pay for the actual amount of data used.
                                                                                                    This mode is suitable for scenarios where data size is uncertain or data processing is only required occasionally, allowing for on-demand use of resources without the need to pre-purchase or reserve resources.
                                                                                                    
+
                                                                                                  
+
                                                                                                  
+
                                                                                                  DLI Compute Resource Modes and Supported Queue Types
                                                                                                  Table 1 describes the queue types supported by different compute resources in DLI.
                                                                                                  
+
+
                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                  Table 1 DLI compute resource modes and supported queue types
                                                                                                  DLI Compute Resource Mode
                                                                                                  
+
                                                                                                  Supported Queue Type
                                                                                                  
+
                                                                                                  Resource Characteristic
                                                                                                  
+
                                                                                                  Use Case
                                                                                                  
+
                                                                                                  Elastic resource pool mode
                                                                                                  
+
                                                                                                  For SQL (Spark)
                                                                                                  
+
                                                                                                  For SQL (HetuEngine)
                                                                                                  
+
                                                                                                  For general purpose
                                                                                                  
+
                                                                                                  Resources are shared among multiple queues for a single user.
                                                                                                  
+
                                                                                                  Resources are dynamically allocated and can be flexibly adjusted.
                                                                                                  
+
                                                                                                  Suitable for scenarios with significant fluctuations in business demand, where resources need to be flexibly adjusted to meet peak and off-peak demands.
                                                                                                  
+
                                                                                                  Global sharing mode
                                                                                                  
+
                                                                                                  default queue
                                                                                                  
+
                                                                                                  Resources are shared among multiple queues for multiple users.
                                                                                                  
+
                                                                                                  You are billed on a pay-per-use basis. Resources cannot be reserved.
                                                                                                  
+
                                                                                                  Suitable for temporary or testing projects where data size is uncertain or data processing is only required occasionally.
                                                                                                  
+
                                                                                                  Non-elastic resource pool mode
                                                                                                  
+
                                                                                                  (deprecated, not recommended)
                                                                                                  
+
                                                                                                  For SQL
                                                                                                  
+
                                                                                                  For general purpose
                                                                                                  
+
                                                                                                  Resources are exclusively used by a single user and a single queue.
                                                                                                  
+
                                                                                                  Resources cannot be dynamically adjusted and may remain idle.
                                                                                                  
+
                                                                                                  Deprecated, not recommended
                                                                                                  
+
                                                                                                  
+
                                                                                                  
+
                                                                                                  
+
                                                                                                  Elastic Resource Pool Specifications
                                                                                                  An elastic resource pool provides compute resources (CPU and memory) for running DLI jobs. The unit is CU. One CU contains 1 vCPU and 4 GB memory.
                                                                                                  
+
                                                                                                  You can create multiple queues in an elastic resource pool. Compute resources can be shared among queues. By appropriately setting up compute resource allocation policies for queues, you can enhance compute resource utilization.
                                                                                                  
+
                                                                                                   
                                                                                                  DLI elastic resource pools are physically isolated, while queues within the same elastic resource pool are logically isolated.
                                                                                                  
+
                                                                                                  You are advised to create separate elastic resource pools for testing and production scenarios to ensure the independence and security of resource management through physical isolation.
                                                                                                  
+
                                                                                                  
+
                                                                                                  Table 2 lists the specifications of the elastic resource pools provided by DLI.
                                                                                                  
+
+
                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                  Table 2 Elastic resource pool specifications
                                                                                                  Edition
                                                                                                  
+
                                                                                                  Specifications
                                                                                                  
+
                                                                                                  Notes and Constraints
                                                                                                  
+
                                                                                                  Use Case
                                                                                                  
+
                                                                                                  Basic
                                                                                                  
+
                                                                                                  16–64 CUs
                                                                                                  
+
                                                                                                  • High reliability and availability are not supported.
                                                                                                  • Queue properties cannot be set.
                                                                                                  • Job priorities are not supported.
                                                                                                  • Notebook instances cannot be interconnected with.
                                                                                                  
+
                                                                                                  This edition is suitable for testing scenarios with low resource consumption and low requirements for resource reliability and availability.
                                                                                                  
+
                                                                                                  Standard
                                                                                                  
+
                                                                                                  64 CUs or higher
                                                                                                  
+
                                                                                                  For notes and constraints on using an elastic resource pool, see Notes and Constraints on Using an Elastic Resource Pool.
                                                                                                  
+
                                                                                                  This edition offers powerful computing capabilities, high availability, and flexible resource management. It is suitable for large-scale computing tasks and business scenarios with long-term resource planning needs.
                                                                                                  
+
                                                                                                  
+
                                                                                                  
+
                                                                                                  
+
                                                                                                  Advantages of Elastic Resource Pools
                                                                                                  Elastic resource pools have the following advantages:
                                                                                                  
+
                                                                                                  • Unified resource management
                                                                                                    You can manage multiple internal clusters and schedule jobs in a unified manner. The scale of compute resources can reach million vCPUs.
                                                                                                    
+
                                                                                                  • Tenant resource isolation
                                                                                                    Resources of different queues are isolated to reduce the impact on each other.
                                                                                                    
+
                                                                                                  • Time-based on-demand elasticity
                                                                                                    • Minute-level scaling to cope with traffic peaks and resource requirements.
                                                                                                    • You can queue priorities and CU quotas at different times to improve resource utilization.
                                                                                                    
+
                                                                                                  • Job-level resource isolation (not implemented currently and will be supported in later versions)
                                                                                                    You can run SQL jobs on independent Spark instances, reducing mutual impacts between jobs.
                                                                                                    
+
                                                                                                  • Automatic scaling (not implemented currently and will be supported in later versions)
                                                                                                    Queue quotas are automatically updated in real time based on queue loads and priorities.
                                                                                                    
+
                                                                                                  
+
                                                                                                  The advantages of using elastic resource pools include:
                                                                                                  
+
+
                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                  Table 3 Advantages of elastic resource pools
                                                                                                  Dimension
                                                                                                  
+
                                                                                                  No Elastic Resource Pool
                                                                                                  
+
                                                                                                  Elastic Resource Pool
                                                                                                  
+
                                                                                                  Expansion duration
                                                                                                  
+
                                                                                                  You will need to spend several minutes manually scaling out.
                                                                                                  
+
                                                                                                  No manual intervention is required, as dynamic scale out can be done in seconds.
                                                                                                  
+
                                                                                                  Resource utilization
                                                                                                  
+
                                                                                                  
+
                                                                                                  Resources cannot be shared among queues.
                                                                                                  
+
                                                                                                  For example, if queue 1 has 10 unused CUs and queue 2 requires more resources due to heavy load, queue 2 cannot utilize the resources of queue 1. It has to be scaled up.
                                                                                                  
+
                                                                                                  Multiple queues added to the same elastic resource pool can share CU resources, enhancing resource utilization.
                                                                                                  
+
                                                                                                  When creating a datasource connection, you need to assign non-overlapping network segments to each queue, consuming a significant amount of VPC network segments.
                                                                                                  
+
                                                                                                  You can centrally assign network segments to multiple queues in an elastic resource pool, thereby simplifying datasource configuration.
                                                                                                  
+
                                                                                                  Resource allocation
                                                                                                  
+
                                                                                                  You cannot set priorities when scaling out multiple queues concurrently. If there are insufficient resources, some queues will fail to be scaled out.
                                                                                                  
+
                                                                                                  You can set the priority for each queue in an elastic resource pool based on the peak and off-peak hours of the current service to ensure reasonable resource allocation.
                                                                                                  
+
                                                                                                  
+
                                                                                                  
 
                                                                                                  
 
                                                                                                  Use Cases of Elastic Resource Pools
                                                                                                  Queues in an elastic resource pool are recommended, as they offer the flexibility to use resources with high utilization as needed. This part describes common use cases of elastic resource pools.
                                                                                                  
 
                                                                                                  Resources too fixed to meet a range of requirements.
                                                                                                  
 
                                                                                                  The quantities of compute resources required for jobs change in different time of a day. If the resources cannot be scaled based on service requirements, they may be wasted or insufficient. Figure 2 shows the resource usage during a day.
                                                                                                  
-
                                                                                                  • After ETL jobs are complete, no other jobs are running during 04:00 to 07:00 in the early morning. The resources could be released at that time.
                                                                                                  • From 09:00 to 12:00 a.m. and 02:00 to 04:00 p.m., a large number of ETL report and job queries are queuing for compute resources.
                                                                                                    Figure 2 Fixed resources
                                                                                                    
+
                                                                                                    • During the data period from approximately 04:00 to 07:00 in the morning, there are no other jobs running after ETL jobs complete. Since the resources remain constantly occupied, it leads to significant resource wastage.
                                                                                                    • Between 09:00 a.m. to 12:00 p.m. and 14:00 p.m. to 16:00 p.m., the volume of ETL report and job query requests is high. Due to insufficient allocated resources, jobs end up queuing continuously.
                                                                                                      Figure 2 Fixed resources
                                                                                                      
 
                                                                                                    
 
                                                                                                    Resources are isolated and cannot be shared.
                                                                                                    
-
                                                                                                    A company has two departments, and each run their jobs on a DLI queue. Department A is idle from 08:00 to 12:00 a.m. and has remaining resources, while department B has a large number of service requests during this period and needs more resources to meet the requirements. Since the resources are isolated and cannot be shared between department A and B, the idle resources are wasted.
                                                                                                    Figure 3 Resource waste due to resource isolation
                                                                                                    
+
                                                                                                    A company has two departments with different jobs running on two queues of DLI. Department A experiences low activity from 8:00 a.m. to 12:00 p.m., leaving some resources unused, while department B faces high demand during this time, exceeding its current resource specifications. When scaling up is necessary, it cannot utilize the idle queue resources of department A, leading to resource wastage.
                                                                                                    Figure 3 Resource waste due to resource isolation
                                                                                                    
 
                                                                                                    
 
                                                                                                    Elastic resource pools can be accessed by different queues and automatically scaled to improve resource utilization and handle resource peaks.
                                                                                                    
 
                                                                                                    You can use elastic resource pools to centrally manage and allocate resources. Multiple queues can be bound to an elastic resource pool to share the pooled resources.
                                                                                                    
@@ -105,7 +196,14 @@
 
                                                                                                    
 
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_01_0505.html b/docs/dli/umn/dli_01_0505.html
index 1b58f9597..e487cb8c5 100644
--- a/docs/dli/umn/dli_01_0505.html
+++ b/docs/dli/umn/dli_01_0505.html
@@ -27,7 +27,7 @@
 
                                                                                              Elastic resource pool scaling
                                                                                              
                                                                                               		
 
                                                                                              • Changes to elastic resource pool CUs can occur when setting the CU, adding or deleting queues in an elastic resource pool, or modifying the scaling policies of queues in an elastic resource pool, or when the system automatically triggers elastic resource pool scaling. However, in some cases, the system cannot guarantee that the scaling will reach the target CUs as planned.
                                                                                                • If there are not enough physical resources, an elastic resource pool may not be able to scale out to the desired target size.
                                                                                                • The system does not guarantee that an elastic resource pool will be scaled in to the desired target size.
                                                                                                  The system checks the resource usage before scaling in the elastic resource pool to determine if there is enough space for scaling in. If the existing resources cannot be scaled in according to the minimum scaling step, the pool may not be scaled in successfully or only partially.
                                                                                                  
-
                                                                                                  The scaling step may vary depending on the resource specifications, usually 16 CUs, 32 CUs, 48 CUs, 64 CUs, etc.
                                                                                                  
+
                                                                                                  The scaling step may vary depending on the resource specifications, usually 16 CUs, 32 CUs, 48 CUs, 64 CUs, and more.
                                                                                                  
 
                                                                                                  For example, if the elastic resource pool has a capacity of 192 CUs and the queues in the pool are using 68 CUs due to running jobs, the plan is to scale in to 64 CUs.
                                                                                                  
 
                                                                                                  When executing a scaling in task, the system determines that there are 124 CUs remaining and scales in by the minimum step of 64 CUs. However, the remaining 60 CUs cannot be scaled in any further. Therefore, after the elastic resource pool executes the scaling in task, its capacity is reduced to 128 CUs.
                                                                                                  
 
                                                                                                
@@ -39,7 +39,7 @@
 
 
 
                                                                                                Creating an Elastic Resource Pool
                                                                                                1. In the navigation pane on the left, choose Resources > Resource Pool.
                                                                                                2. On the displayed page, click Buy Resource Pool in the upper right corner.
                                                                                                3. On the displayed page, set the following parameters:
                                                                                                  
-
                                                                                                  Table 2 Parameters
                                                                                                  Parameter
                                                                                                  
+
                                                                                                  
@@ -47,7 +47,7 @@
 
-
-
@@ -73,11 +73,11 @@
 
@@ -107,10 +107,10 @@
 
@@ -142,7 +142,8 @@
 
@@ -199,7 +200,7 @@
 
@@ -207,6 +208,14 @@
 
+
+
+
@@ -219,7 +228,7 @@
 
 
diff --git a/docs/dli/umn/dli_01_0506.html b/docs/dli/umn/dli_01_0506.html
index ee547c2a7..51c23b372 100644
--- a/docs/dli/umn/dli_01_0506.html
+++ b/docs/dli/umn/dli_01_0506.html
@@ -12,28 +12,28 @@
 
@@ -84,8 +84,8 @@
 
-
@@ -162,7 +162,7 @@
 
                                                                                                  Table 2 Parameter descriptions
                                                                                                  Parameter
                                                                                                  
                                                                                                   		
 
                                                                                                  Description
                                                                                                  
 
                                                                                                  
 
                                                                                                  Region
                                                                                                  
 
                                                                                                  Select a region. Select a region near you to ensure the lowest latency possible.
                                                                                                  
+
                                                                                                  Select a region where you want to buy the elastic resource pool. A region refers to the location of the physical data center of an elastic resource pool. Select a region near you to ensure the lowest latency possible.
                                                                                                  
                                                                                                   		
 
                                                                                                  
 
                                                                                                  Project
                                                                                                  
@@ -58,14 +58,14 @@
 
                                                                                                  Name
                                                                                                  
                                                                                                   		
 
                                                                                                  Name of the elastic resource pool.
                                                                                                  
-
                                                                                                  • Only numbers, letters, and underscores (_) are allowed. The value cannot contain only numbers or start with an underscore (_) or number.
                                                                                                  • The value can contain a maximum of 128 characters.
                                                                                                  
+
                                                                                                  • Only digits, letters, and underscores (_) are allowed. The value cannot contain only digits or start with an underscore (_) or digit.
                                                                                                  • The value can contain a maximum of 128 characters.
                                                                                                  
 
                                                                                                   NOTE: 
                                                                                                  The elastic resource pool name is case-insensitive. Uppercase letters will be automatically converted to lowercase letters.
                                                                                                  
 
                                                                                                  
                                                                                                   		
 
                                                                                                  
 
                                                                                                  Type
                                                                                                  
 
                                                                                                  • Basic edition: offers 16 CUs to 64 CUs
                                                                                                    • This edition is suitable for testing scenarios with low resource consumption and low requirements for resource reliability and availability.
                                                                                                    • High reliability and availability are not supported.
                                                                                                    • Queue properties and job priorities cannot be set.
                                                                                                    • Notebook instances cannot be interconnected with.
                                                                                                    
+
                                                                                                  • Basic edition: offers 16 CUs to 64 CUs
                                                                                                    • This edition is suitable for testing scenarios with low resource consumption and low requirements for resource reliability and availability.
                                                                                                    • High reliability and availability are not supported.
                                                                                                    • Job priorities cannot be set.
                                                                                                    
 
                                                                                                  • Standard edition: offers at least 64 CUs
                                                                                                    This edition offers powerful computing capabilities, high availability, and flexible resource management. It is suitable for large-scale computing tasks and business scenarios with long-term resource planning needs.
                                                                                                    
 
                                                                                                  
 
                                                                                                  CU Range
                                                                                                  
                                                                                                   		
 
                                                                                                  The maximum and minimum CUs allowed for the elastic resource pool.
                                                                                                  
-
                                                                                                  CU settings are used to control the maximum and minimum CU ranges for elastic resource pools to avoid unlimited resource scaling.
                                                                                                  
+
                                                                                                  CU settings are used to control the maximum and minimum CU ranges for elastic resource pool scaling to prevent unlimited resource expansion risks.
                                                                                                  
 
                                                                                                  In CU Range, set the minimum CUs on the left and the maximum CUs on the right.
                                                                                                  
 
                                                                                                  • The total minimum CUs of all queues in an elastic resource pool must be no more than the minimum CUs of the pool.
                                                                                                  • The maximum CUs of any queue in an elastic resource pool must be no more than the maximum CUs of the pool.
                                                                                                  
 
                                                                                                  An elastic resource pool should at least ensure that all queues in it can run with the minimum CUs and should try to ensure that all queues in it can run with the maximum CUs.
                                                                                                  
-
                                                                                                  The specifications (yearly/monthly CUs) of an elastic resource pool are equal to the minimum CUs allocated during creation. This means that when the elastic resource pool is first created, the actual CUs will be equal to the specifications, which is also the minimum CUs.
                                                                                                  
+
                                                                                                  The specifications of an elastic resource pool are equal to the minimum CUs allocated during creation. This means that when the elastic resource pool is first created, the actual CUs will be equal to the specifications, which is also the minimum CUs.
                                                                                                  
                                                                                                   		
 
                                                                                                  
 
                                                                                                  Description
                                                                                                  
@@ -88,7 +88,7 @@
 
                                                                                                  CIDR Block
                                                                                                  
                                                                                                   		
 
                                                                                                  CIDR block the elastic resource pool belongs to. If you use an enhanced datasource connection, this CIDR block cannot overlap that of the data source. Once set, this CIDR block cannot be changed.
                                                                                                  
-
                                                                                                  Recommended CIDR block:
                                                                                                  
+
                                                                                                  Recommended CIDR blocks:
                                                                                                  
 
                                                                                                  10.0.0.0–10.255.0.0/16–19
                                                                                                  
 
                                                                                                  172.16.0.0–172.31.0.0/16–19
                                                                                                  
 
                                                                                                  192.168.0.0–192.168.0.0/16–19
                                                                                                  
@@ -98,7 +98,7 @@
                                                                                                   		
 
                                                                                                  If the created elastic resource pool belongs to an enterprise project, select the enterprise project.
                                                                                                  
 
                                                                                                  Enterprise projects let you manage cloud resources and users by project.
                                                                                                  
-
                                                                                                   NOTE: 
                                                                                                  This parameter is displayed only for users who have enabled the Enterprise Management Service.
                                                                                                  
+
                                                                                                   NOTE: 
                                                                                                  This parameter is available only for users who have subscribed to the Enterprise Management Service.
                                                                                                  
 
                                                                                                  
 
                                                                                                  		
 
                                                                                                  Tags used to identify cloud resources. A tag includes the tag key and tag value. If you want to use the same tag to identify multiple cloud resources, that is, to select the same tag from the drop-down list box for all services, you are advised to create predefined tags on the Tag Management Service (TMS).
                                                                                                  
 
                                                                                                   NOTE: 
                                                                                                  • A maximum of 20 tags can be added.
                                                                                                  • Only one tag value can be added to a tag key.
                                                                                                  • The key name in each resource must be unique.
                                                                                                  
 
                                                                                                  
-
                                                                                                  • Tag key: Enter a tag key name in the text box.
                                                                                                     NOTE: 
                                                                                                    A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                                    
+
                                                                                                    • Tag key: Enter a tag key name in the text box.
                                                                                                       NOTE: 
                                                                                                      A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                                      
 
                                                                                                      
 
                                                                                                    
-
                                                                                                    • Tag value: Enter a tag value in the text box.
                                                                                                       NOTE: 
                                                                                                      A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.
                                                                                                      
+
                                                                                                      • Tag value: Enter a tag value in the text box.
                                                                                                         NOTE: 
                                                                                                        A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.
                                                                                                        
 
                                                                                                        
 
                                                                                                      
 
                                                                                                  Engine
                                                                                                  
                                                                                                   		
 
                                                                                                  If Type is For SQL, the queue engine can be Spark or HetuEngine.
                                                                                                  
-
                                                                                                  For a HetuEngine SQL queue, there must be at least 96 CUs.
                                                                                                  
+
                                                                                                  If HetuEngine is selected, the minimum number of CUs of the SQL queue cannot be fewer than 96 CUs.
                                                                                                  
+
                                                                                                  To use HetuEngine to submit SQL jobs, you need to configure a DLI job bucket. For details, see Configuring a DLI Job Bucket.
                                                                                                  
                                                                                                   		
 
                                                                                                  
 
                                                                                                  Enterprise Project
                                                                                                  
@@ -164,10 +165,10 @@
 
                                                                                                  
 
                                                                                                   NOTE: 
                                                                                                  • A maximum of 20 tags can be added.
                                                                                                  • Only one tag value can be added to a tag key.
                                                                                                  • The key name in each resource must be unique.
                                                                                                  
 
                                                                                                  
-
                                                                                                  • Tag key: Enter a tag key name in the text box.
                                                                                                     NOTE: 
                                                                                                    A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                                    
+
                                                                                                    • Tag key: Enter a tag key name in the text box.
                                                                                                       NOTE: 
                                                                                                      A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                                      
 
                                                                                                      
 
                                                                                                    
-
                                                                                                    • Tag value: Enter a tag value in the text box.
                                                                                                       NOTE: 
                                                                                                      A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.
                                                                                                      
+
                                                                                                      • Tag value: Enter a tag value in the text box.
                                                                                                         NOTE: 
                                                                                                        A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.
                                                                                                        
 
                                                                                                        
 
                                                                                                      
 
                                                                                                  Min CU
                                                                                                  
                                                                                                   		
 
                                                                                                  Minimum number of CUs allowed by the scaling policy.
                                                                                                  
-
                                                                                                  • In any time segment of a day, the total minimum CUs of all queues in an elastic resource pool cannot be more than the minimum CUs of the pool.
                                                                                                  • If the minimum CUs of the queue is less than 16 CUs, both Max. Spark Driver Instances and Max. Prestart Spark Driver Instances set in the queue properties do not apply. Refer to Setting Queue Properties.
                                                                                                  
+
                                                                                                  • In any time segment of a day, the total minimum CUs of all queues in an elastic resource pool cannot be more than the minimum CUs of the pool.
                                                                                                  • If the minimum CUs of the queue are fewer than 16 CUs, both Max. Spark Driver Instances and Max. Prestart Spark Driver Instances set in the queue properties do not apply. Refer to Setting Queue Properties.
                                                                                                  
 
                                                                                                  For a HetuEngine SQL queue, there must be at least 96 CUs.
                                                                                                  
                                                                                                   		
 
                                                                                                  
 
                                                                                                  Maximum number of CUs allowed by the scaling policy.
                                                                                                  
 
                                                                                                  In any time segment of a day, the maximum CUs of any queue in an elastic resource pool cannot be more than the maximum CUs of the pool.
                                                                                                  
+
                                                                                                  • The maximum CUs of a queue in the elastic resource pool of the basic edition must be a multiple of 4.
                                                                                                  • The maximum CUs of a queue in the elastic resource pool of the standard edition must be a multiple of 16.
                                                                                                  
+
                                                                                                  Use Resource Pool's Max CU
                                                                                                  
+
                                                                                                  When selected, the maximum CUs of queues equal the maximum CUs of the resource pool within the period specified by the current scaling policy.
                                                                                                  
+
                                                                                                  Increasing the maximum CUs of the elastic resource pool automatically adjusts the queue's maximum CUs to match without manual intervention.
                                                                                                  
+
                                                                                                  The setting takes effect only within the period specified by the current scaling policy. You need to manually configure CU limits for other periods.
                                                                                                  
                                                                                                   		
 
                                                                                                  
                                                                                                   
 
 
 
                                                                                                  An elastic resource pool has a maximum number of 256 CUs for queue A and queue B. The scaling policies are as follows:
                                                                                                  
-
                                                                                                  • Queue A: priority 5; period: 00:00–09:00; minimum CU: 32; maximum CU: 64
                                                                                                  • Queue B: priority 10; time period: 00:00–09:00; minimum CU: 64; maximum CU: 128
                                                                                                  
+
                                                                                                  • Queue A: priority 5; period: 00:00–09:00; minimum CUs: 32; maximum CUs: 64
                                                                                                  • Queue B: priority 10; time period: 00:00–09:00; minimum CUs: 64; maximum CUs: 128
                                                                                                  
                                                                                                   		
 
                                                                                                  From 00:00 a.m. to 09:00 a.m.:
                                                                                                  
 
                                                                                                  1. The minimum CUs are allocated to the two queues. Queue A has 32 CUs, and queue B has 64 CUs. There are 160 CUs remaining.
                                                                                                  2. The remaining CUs are allocated based on priority. Since queue B has a higher priority than queue A, 64 CUs will be allocated to queue B first, followed by the allocation of 32 CUs to queue A.
                                                                                                  
                                                                                                   		
 
                                                                                                  
 
                                                                                                  An elastic resource pool has a maximum number of 96 CUs for queue A and queue B. The scaling policies are as follows:
                                                                                                  
-
                                                                                                  • Queue A: priority 5; period: 00:00–09:00; minimum CU: 32; maximum CU: 64
                                                                                                  • Queue B: priority 10; time period: 00:00–09:00; minimum CU: 64; maximum CU: 128
                                                                                                  
+
                                                                                                  • Queue A: priority 5; period: 00:00–09:00; minimum CUs: 32; maximum CUs: 64
                                                                                                  • Queue B: priority 10; time period: 00:00–09:00; minimum CUs: 64; maximum CUs: 128
                                                                                                  
                                                                                                   		
 
                                                                                                  From 00:00 a.m. to 09:00 a.m.:
                                                                                                  
 
                                                                                                  1. The minimum CUs are allocated to the two queues. Queue A has 32 CUs, and queue B has 64 CUs. There are no remaining CUs.
                                                                                                  2. The allocation is complete.
                                                                                                  
                                                                                                   		
 
                                                                                                  
 
                                                                                                  An elastic resource pool has a maximum number of 128 CUs for queue A and queue B. The scaling policies are as follows:
                                                                                                  
-
                                                                                                  • Queue A: priority 5; period: 00:00–09:00; minimum CU: 32; maximum CU: 64
                                                                                                  • Queue B: priority 10; time period: 00:00–09:00; minimum CU: 64; maximum CU: 128
                                                                                                  
+
                                                                                                  • Queue A: priority 5; period: 00:00–09:00; minimum CUs: 32; maximum CUs: 64
                                                                                                  • Queue B: priority 10; time period: 00:00–09:00; minimum CUs: 64; maximum CUs: 128
                                                                                                  
                                                                                                   		
 
                                                                                                  From 00:00 a.m. to 09:00 a.m.:
                                                                                                  
 
                                                                                                  1. The minimum CUs are allocated to the two queues. Queue A has 32 CUs, and queue B has 64 CUs. There are 32 CUs remaining.
                                                                                                  2. The remaining 32 CUs are preferentially allocated to queue B.
                                                                                                  
                                                                                                   		
 
                                                                                                  
 
                                                                                                  An elastic resource pool has a maximum number of 128 CUs for queue A and queue B. The scaling policies are as follows:
                                                                                                  
-
                                                                                                  • Queue A: priority 5; period: 00:00–09:00; minimum CU: 32; maximum CU: 64
                                                                                                  • Queue B: priority 5; time period: 00:00–09:00; minimum CU: 64; maximum CU: 128
                                                                                                  
+
                                                                                                  • Queue A: priority 5; period: 00:00–09:00; minimum CUs: 32; maximum CUs: 64
                                                                                                  • Queue B: priority 5; time period: 00:00–09:00; minimum CUs: 64; maximum CUs: 128
                                                                                                  
                                                                                                   		
 
                                                                                                  From 00:00 a.m. to 09:00 a.m.:
                                                                                                  
 
                                                                                                  1. The minimum CUs are allocated to the two queues. Queue A has 32 CUs, and queue B has 64 CUs. There are 32 CUs remaining.
                                                                                                  2. The two queues have the same priority, the remaining 32 CUs are randomly allocated to the two queues.
                                                                                                  
@@ -56,7 +56,7 @@
 
                                                                                                  
 
 
                                                                                                  Queues A and B are added to the elastic resource pool. The scaling policies are as follows:
                                                                                                  
-
                                                                                                  • Queue A: period: 00:00–09:00; minimum CU: 32; maximum CU: 64
                                                                                                  • Queue B: period: 00:00–09:00; minimum CU: 64; maximum CU: 128
                                                                                                  
+
                                                                                                  • Queue A: period: 00:00–09:00; minimum CUs: 32; maximum CUs: 64
                                                                                                  • Queue B: period: 00:00–09:00; minimum CUs: 64; maximum CUs: 128
                                                                                                  
                                                                                                   		
 
                                                                                                  192 CUs
                                                                                                  
                                                                                                   		
 
                                                                                                  64 CUs to 96 CUs
                                                                                                  
 
                                                                                                  The elastic resource pool preferentially meets the minimum CUs of the two queues. That is, 32 CUs are allocated to queue A, 64 CUs are allocated to queue B, and the remaining 32 CUs are available.
                                                                                                  
-
                                                                                                  The remaining CUs are allocated based on the queue load and priority. The actual CUs of the queue change within the range listed.
                                                                                                  
+
                                                                                                  The elastic resource pool prioritizes meeting the minimum CUs of both queues, allocating 32 CUs to queue A and 64 CUs to queue B first, with an additional 32 CUs available for allocation.
                                                                                                  
+
                                                                                                  The remaining portion is distributed according to the queue's load and priority. The actual CUs of the queues fluctuate within the specified range.
                                                                                                  
                                                                                                   		
 
                                                                                                  
 
                                                                                                  
 
                                                                                                  
 
                                                                                                4. Locate the target queue and click Edit in the Operation column.
                                                                                                5. In the displayed Queue Management pane, perform the following operations as needed:
                                                                                                  • Add: Click Create to add a scaling policy. Set Priority, Period, Min CU, and Max CU, and click OK.
                                                                                                  • Modify: Modify parameters of an existing scaling policy and click OK.
                                                                                                  • Delete: Locate the row that contains the scaling policy you want, click Delete and click OK.
                                                                                                     
                                                                                                    The Priority and Period parameters must meet the following requirements:
                                                                                                    
-
                                                                                                    • Priority: The default value is 1. The value ranges from 1 to 100. A larger value indicates a higher priority.
                                                                                                    • Period:
                                                                                                      • You can only set the period to hours in [start time,end time) format.
                                                                                                      • For example, if the Period to 01 and 17, the scaling policy takes effect at 01:00 a.m. till 05:00 p.m.
                                                                                                      • The periods of scaling policies with different priorities cannot overlap.
                                                                                                      
+
                                                                                                      • Priority: The default value is 1. The value ranges from 1 to 100. A larger value indicates a higher priority.
                                                                                                      • Period:
                                                                                                        • You can only set the period to hours in [start time,end time) format.
                                                                                                        • For example, if you set Period to 01 and 17, the scaling policy takes effect at 01:00 a.m. till 05:00 p.m.
                                                                                                        • The periods of scaling policies with different priorities cannot overlap.
                                                                                                        
 
                                                                                                      • Max CUs and Min CUs:
                                                                                                        • In any time segment of a day, the total minimum CUs of all queues in an elastic resource pool cannot be more than the minimum CUs of the pool.
                                                                                                        • In any time segment of a day, the maximum CUs of any queue in an elastic resource pool cannot be more than the maximum CUs of the pool.
                                                                                                        
 
                                                                                                      
 
                                                                                                    
diff --git a/docs/dli/umn/dli_01_0507.html b/docs/dli/umn/dli_01_0507.html
index d761e5ef7..5d945b92f 100644
--- a/docs/dli/umn/dli_01_0507.html
+++ b/docs/dli/umn/dli_01_0507.html
@@ -1,11 +1,15 @@
 
 
 
                                                                                                    Setting CUs
                                                                                                    
-
                                                                                                    CU settings are used to control the maximum and minimum CU ranges for elastic resource pools to avoid unlimited resource scaling.
                                                                                                    
-
                                                                                                    For example, an elastic resource pool has a maximum of 256 and two queues, and each queue must have at least 64 CUs. If you want to add another queue that needs at lest 256 CUs to the elastic resource pool, the operation is not allowed due to the maximum CUs of the elastic resource pool.
                                                                                                    
-
                                                                                                    Precautions
                                                                                                    • In any time segment of a day, the total minimum CUs of all queues in an elastic resource pool cannot be more than the minimum CUs of the pool.
                                                                                                    • In any time segment of a day, the maximum CUs of any queue in an elastic resource pool cannot be more than the maximum CUs of the pool.
                                                                                                    • When you change the minimum CUs of a created elastic resource pool, ensure that the value is no more than the current CU value. Otherwise, the modification fails.
                                                                                                    
+
                                                                                                    CU settings are used to control the maximum and minimum CU ranges for elastic resource pool scaling to prevent unlimited resource expansion risks.
                                                                                                    
+
                                                                                                    For example, if the current maximum CUs of an elastic resource pool is 256 CUs, and two queues have been added with their scaling policies set to a minimum of 64 CUs each, attempting to add another queue requiring a minimum of 256 CUs would fail due to the constraints imposed by the maximum CU setting.
                                                                                                    
+
                                                                                                    Notes and Constraints
                                                                                                    The minimum value of the CU range of the elastic resource pool cannot exceed the current actual CUs.
                                                                                                    
+
                                                                                                    For example, if you want to raise the minimum value of the CU range (for example, from 64 CUs to 80 CUs), you must first ensure that the actual CUs are at least 80.
                                                                                                    
+
                                                                                                    For methods on adjusting the actual CUs, refer to Scaling Out or In an Elastic Resource Pool.
                                                                                                    
 
                                                                                                    
-
                                                                                                    Setting CUs
                                                                                                    1. In the navigation pane on the left, choose Resources > Resource Pool.
                                                                                                    2. Locate the row that contains the desired elastic resource pool, click More in the Operation column, and select Set CUs.
                                                                                                    3. In the Set CUs dialog box, set the minimum CUs on the left and the maximum CUs on the right. Click OK.
                                                                                                    
+
                                                                                                    Precautions
                                                                                                    • In any time segment of a day, the total minimum CUs of all queues in an elastic resource pool cannot be more than the minimum CUs of the pool.
                                                                                                    • In any time segment of a day, the maximum CUs of any queue in an elastic resource pool cannot be more than the maximum CUs of the pool.
                                                                                                    • When adjusting the minimum CUs of a created elastic resource pool, the minimum CUs must be less than or equal to the actual CUs of the pool. Otherwise, the modification will fail.
                                                                                                    • The adjustment of the CU range of a queue, the change of the elastic resource pool specifications, and the CU setting of an elastic resource pool take effect on the next hour.
                                                                                                    • You can add queues to adjust the actual CUs of an elastic resource pool. The adjustment takes effect immediately.
                                                                                                    
+
                                                                                                    
+
                                                                                                    Procedure
                                                                                                    1. In the navigation pane on the left, choose Resources > Resource Pool.
                                                                                                    2. Locate the row that contains the desired elastic resource pool, click More in the Operation column, and select Set CUs.
                                                                                                    3. In the Set CUs dialog box, set the minimum CUs on the left and the maximum CUs on the right. Click OK.
                                                                                                    
 
                                                                                                    
 
                                                                                                    FAQ
                                                                                                    
 
diff --git a/docs/dli/umn/dli_01_0512.html b/docs/dli/umn/dli_01_0512.html
index a2578c7ec..13d97f4a4 100644
--- a/docs/dli/umn/dli_01_0512.html
+++ b/docs/dli/umn/dli_01_0512.html
@@ -1,12 +1,12 @@
 
 
-
                                                                                                    Using DLI to Submit a Flink Jar Job
                                                                                                    
+
                                                                                                    Submitting a Flink Jar Job Using DLI
                                                                                                    
 
                                                                                                    Scenario
                                                                                                    Flink Jar jobs are suitable for data analysis scenarios that require custom stream processing logic, complex state management, or integration with specific libraries. You need to write and build a Jar job package. Before submitting a Flink Jar job, upload the Jar job package to OBS and submit it together with the data and job parameters to run the job.
                                                                                                    
 
                                                                                                    This example introduces the basic process of submitting a Flink Jar job package through the DLI console. Due to different service requirements, the specific writing of the Jar package may vary. It is recommended that you refer to the sample code provided by DLI and edit and customize it according to your actual business scenario. 
                                                                                                    
 
                                                                                                    
 
                                                                                                    Procedure
                                                                                                    Table 1 describes the procedure for submitting a Flink Jar job using DLI.
                                                                                                    
 
-
                                                                                                    Table 1 Procedure for submitting a Flink Jar job using DLI
                                                                                                    Procedure
                                                                                                    
+
                                                                                                    
@@ -17,12 +17,22 @@
 
-
-
+
+
+
+
+
+
@@ -38,12 +48,12 @@
 
                                                                                                  • Click Create Now.
                                                                                                  • In the bucket list, click the name of the dli-test-obs01 bucket you just created to access its Objects tab.
                                                                                                  • Click Upload Object. In the displayed dialog box, drag or add files or folders, for example, flink-examples.jar, to the upload area. Then, click Upload.
                                                                                                    In this example, the path after upload is obs://dli-test-obs01/flink-examples.jar.
                                                                                                    
-
                                                                                                    For more operations on the OBS console, see the Object Storage Service User Guide.
                                                                                                    
+
                                                                                                    For more operations on the OBS console, see Object Storage Service User Guide.
                                                                                                    
 
                                                                                                    • 
-
                                                                                                    Step 2: Buy an Elastic Resource Pool and Add Queues to the Pool
                                                                                                    To execute SQL jobs in datasource scenarios, you must use your own SQL queue as the existing default queue cannot be used. In this example, create an elastic resource pool named dli_resource_pool and a queue named dli_queue_01.
                                                                                                    
-
                                                                                                    1. Log in to the DLI management console.
                                                                                                    2. In the navigation pane on the left, choose Resources > Resource Pool.
                                                                                                    3. On the displayed page, click Buy Resource Pool in the upper right corner.
                                                                                                    4. On the displayed page, set the parameters.
                                                                                                      Table 2 describes the parameters.
-
                                                                                                    Table 1 Procedure for submitting a Flink Jar job using DLI
                                                                                                    Step
                                                                                                    
                                                                                                     		
 
                                                                                                    Description
                                                                                                    
 
                                                                                                    Prepare a Flink Jar job package and upload it to OBS.
                                                                                                    
                                                                                                     		
 
                                                                                                    Step 2: Buy an Elastic Resource Pool and Add Queues to the Pool
                                                                                                    
+
                                                                                                    Step 2: Buy an Elastic Resource Pool and Create Queues Within It
                                                                                                    
                                                                                                     		
 
                                                                                                    Create compute resources required for submitting the Flink Jar job.
                                                                                                    
                                                                                                     		
 
                                                                                                    Step 3: Create a Flink Jar Job and Configure Job Information
                                                                                                    
+
                                                                                                    Step 3: Use DEW to Manage Access Credentials
                                                                                                    
+
                                                                                                    In cross-source analysis scenarios, use DEW to manage access credentials of data sources.
                                                                                                    
+
                                                                                                    Step 4: Create a Custom Agency to Allow DLI to Access DEW and Read Credentials
                                                                                                    
+
                                                                                                    Create an agency to allow DLI to access DEW.
                                                                                                    
+
                                                                                                    Step 5: Create a Flink Jar Job and Configure Job Information
                                                                                                    
                                                                                                     		
 
                                                                                                    Create a Flink Jar job to analyze data.
                                                                                                    
                                                                                                     		
 
 
 
                                                                                                    Table 2 Parameters
                                                                                                    Parameter
                                                                                                    
+
                                                                                                    Step 2: Buy an Elastic Resource Pool and Create Queues Within It
                                                                                                    To execute SQL jobs in datasource scenarios, you must use your own SQL queue as the existing default queue cannot be used. In this example, create an elastic resource pool named dli_resource_pool and a queue named dli_queue_01.
                                                                                                    
+
                                                                                                    1. Log in to the DLI management console.
                                                                                                    2. In the navigation pane on the left, choose Resources > Resource Pool.
                                                                                                    3. On the displayed page, click Buy Resource Pool in the upper right corner.
                                                                                                    4. On the displayed page, set the parameters.
                                                                                                      Table 2 describes the parameters.
+
                                                                                                      
@@ -72,7 +82,7 @@
 
-
@@ -88,7 +98,7 @@
 
-
@@ -104,41 +114,41 @@
 
                                                                                                      Table 2 Parameter descriptions
                                                                                                      Parameter
                                                                                                      
                                                                                                       		
 
                                                                                                      Description
                                                                                                      
 
                                                                                                      dli_resource_pool
                                                                                                      
                                                                                                       		
 
                                                                                                      Specifications
                                                                                                      
+
                                                                                                      Type
                                                                                                      
                                                                                                       		
 
                                                                                                      Specifications of the elastic resource pool
                                                                                                      
 
                                                                                                      
 
                                                                                                      CIDR Block
                                                                                                      
 
                                                                                                      CIDR block the elastic resource pool belongs to. If you use an enhanced datasource connection, this CIDR block cannot overlap that of the data source. Once set, this CIDR block cannot be changed.
                                                                                                      
+
                                                                                                      CIDR block the elastic resource pool belongs to. If you use an enhanced datasource connection, this CIDR block cannot overlap that of the data source. Once set, this CIDR block cannot be changed.
                                                                                                      
                                                                                                       		
 
                                                                                                      172.16.0.0/19
                                                                                                      
 
                                                                                                      
 
                                                                                                      
 
                                                                                                      
-
                                                                                                    5. Click Buy.
                                                                                                    6. Click Submit.
                                                                                                    7. In the elastic resource pool list, locate the pool you just created and click Add Queue in the Operation column.
                                                                                                    8. Set the basic parameters listed below.
+
                                                                                                    9. Click Buy.
                                                                                                    10. Click Submit.
                                                                                                    11. In the elastic resource pool list, locate the pool you just created and click Add Queue in the Operation column.
                                                                                                    12. Set the basic parameters listed below.
 
                                                                                                      
-
-
-
-
-
-
-
-
                                                                                                      Table 3 Basic parameters for adding a queue
                                                                                                      Parameter
                                                                                                      
 
                                                                                                      Description
                                                                                                      
+
                                                                                                      Description
                                                                                                      
 
                                                                                                      Example Value
                                                                                                      
+
                                                                                                      Example Value
                                                                                                      
                                                                                                       		
 
                                                                                                      
                                                                                                       
 
                                                                                                      Name
                                                                                                      
 
                                                                                                      Name of the queue to add
                                                                                                      
+
                                                                                                      Name of the queue to add
                                                                                                      
 
                                                                                                      dli_queue_01
                                                                                                      
+
                                                                                                      dli_queue_01
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Type
                                                                                                      
 
                                                                                                      Type of the queue
                                                                                                      
-
                                                                                                      • To execute SQL jobs, select For SQL.
                                                                                                      • To execute Flink or Spark jobs, select For general purpose.
                                                                                                      
+
                                                                                                      Type of the queue
                                                                                                      
+
                                                                                                      • To execute SQL jobs, select For SQL.
                                                                                                      • To execute Flink or Spark jobs, select For general purpose.
                                                                                                      
 
                                                                                                      _
                                                                                                      
+
                                                                                                      For general purpose
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Enterprise Project
                                                                                                      
 
                                                                                                      Select an enterprise project.
                                                                                                      
+
                                                                                                      Select an enterprise project for the elastic resource pool.
                                                                                                      
 
                                                                                                      default
                                                                                                      
+
                                                                                                      default
                                                                                                      
                                                                                                       		
 
                                                                                                      
                                                                                                       
 
                                                                                                      
 
                                                                                                      
-
                                                                                                    13. Click Next and configure scaling policies for the queue.
                                                                                                      Click Create to add a scaling policy with varying priority, period, minimum CUs, and maximum CUs.
                                                                                                      
+
                                                                                                    14. Click Next and configure scaling policies for the queue.
                                                                                                      Click Create to add a scaling policy with varying priority, period, minimum CUs, and maximum CUs.
                                                                                                      
 
                                                                                                      
 
 
                                                                                                      
-
-
-
-
@@ -181,39 +191,71 @@
 
                                                                                                      Table 4 Scaling policy parameters
                                                                                                      Parameter
                                                                                                      
@@ -151,17 +161,17 @@
 
                                                                                                      
 
                                                                                                      Priority
                                                                                                      
 
                                                                                                      Priority of the scaling policy in the current elastic resource pool. A larger value indicates a higher priority. In this example, only one scaling policy is configured, so its priority is set to 1 by default.
                                                                                                      
+
                                                                                                      Priority of the scaling policy in the current elastic resource pool. A larger value indicates a higher priority. In this example, only one scaling policy is configured, so its priority is set to 1 by default.
                                                                                                      
                                                                                                       		
 
                                                                                                      1
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Period
                                                                                                      
 
                                                                                                      The first scaling policy is the default policy, and its Period parameter configuration cannot be deleted or modified.
                                                                                                      
+
                                                                                                      The first scaling policy is the default policy, and its Period parameter configuration cannot be deleted or modified.
                                                                                                      
 
                                                                                                      The period for the scaling policy is from 00 to 24.
                                                                                                      
 
                                                                                                      00–24
                                                                                                      
+
                                                                                                      00-24
                                                                                                      
                                                                                                       		
 
                                                                                                      
 
                                                                                                      Min CU
                                                                                                      
@@ -173,7 +183,7 @@
 
                                                                                                      
 
                                                                                                      Max CU
                                                                                                      
 
                                                                                                      Maximum number of CUs allowed by the scaling policy
                                                                                                      
+
                                                                                                      Maximum number of CUs allowed by the scaling policy.
                                                                                                      
                                                                                                       		
 
                                                                                                      64
                                                                                                      
 
                                                                                                      
 
                                                                                                      
 
                                                                                                      
-
                                                                                                    15. Click OK.
                                                                                                    
+
                                                                                                  • Click OK.
                                                                                                    • 
 
                                                                                                    
-
                                                                                                    Step 3: Create a Flink Jar Job and Configure Job Information
                                                                                                    1. Create a Flink Jar job.
                                                                                                      1. In the navigation pane on the left of the DLI management console, choose Job Management > Flink Jobs.
                                                                                                      2. On the displayed page, click Create Job in the upper right corner.
                                                                                                        In this example, set Type to Flink Jar and Name to Flink_Jar_for_test.
                                                                                                        
+
                                                                                                        Step 3: Use DEW to Manage Access Credentials
                                                                                                        In cross-source analysis scenarios, you need to set attributes such as the username and password in the connector. However, information such as usernames and passwords is highly sensitive and needs to be encrypted to ensure user data privacy.
                                                                                                        
+
                                                                                                        DEW is a secure, reliable, and easy-to-use solution for encrypting and decrypting private data while ensuring its security.
                                                                                                        
+
                                                                                                        This example introduces how to create a shared secret in DEW. 
                                                                                                        
+
                                                                                                        1. Log in to the DEW management console.
                                                                                                        2. In the navigation pane on the left, choose Cloud Secret Management Service > Secrets.
                                                                                                        3. Click Create Secret. On the displayed page, configure basic secret information.
                                                                                                          • In this example, the key in the first line is the user's access key ID (AK).
                                                                                                          • In this example, the key in the second line is the user's secret access key (SK).
                                                                                                          
+
                                                                                                        4. Set access credential parameters on the DLI Flink Jar job editing page.
                                                                                                          flink.hadoop.fs.obs.bucket.USER_BUCKET_NAME.dew.access.key=USER_AK_CSMS_KEY_obstest1
+flink.hadoop.fs.obs.bucket.USER_BUCKET_NAME.dew.secret.key=USER_SK_CSMS_KEY_obstest1
+flink.hadoop.fs.obs.security.provider=com.dli.provider.UserObsBasicCredentialProvider
+flink.hadoop.fs.dew.csms.secretName=obsAksK
+flink.hadoop.fs.dew.endpoint=kmsendpoint
+flink.hadoop.fs.dew.csms.version=v6
+flink.hadoop.fs.dew.csms.cache.time.second=3600
+flink.dli.job.agency.name=agencyname
                                                                                                          
+
                                                                                                        
+
                                                                                                        
+
                                                                                                        Step 4: Create a Custom Agency to Allow DLI to Access DEW and Read Credentials
                                                                                                        1. Log in to the management console.
                                                                                                        2. In the upper right corner of the page, hover over the username and select Identity and Access Management.
                                                                                                        3. In the navigation pane of the IAM console, choose Agencies.
                                                                                                        4. On the displayed page, click Create Agency.
                                                                                                        5. On the Create Agency page, set the following parameters:
                                                                                                          • Agency Name: Enter an agency name, for example, dli_dew_agency_access.
                                                                                                          • Agency Type: Select Cloud service.
                                                                                                          • Cloud Service: This parameter is available only when you select Cloud service for Agency Type. Select Data Lake Insight (DLI) from the drop-down list.
                                                                                                          • Validity Period: Select Unlimited.
                                                                                                          • Description: You can enter Agency with OBS OperateAccess permissions. This parameter is optional.
                                                                                                          
+
                                                                                                        6. Click Next.
                                                                                                        7. Click the agency name. On the displayed page, click the Permissions tab. Click Authorize. On the displayed page, click Create Policy.
                                                                                                        8. Configure policy information.
                                                                                                          1. Enter a policy name, for example, dli-dew-agency.
                                                                                                          2. Select JSON.
                                                                                                          3. In the Policy Content area, paste a custom policy.
                                                                                                            {
+    "Version": "1.1",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "csms:secretVersion:get",
+                "csms:secretVersion:list",
+                "kms:dek:decrypt"
+            ]
+        }
+    ]
+}
                                                                                                            
+
                                                                                                          4. Enter a policy description as required.
                                                                                                          
+
                                                                                                        9. Click Next.
                                                                                                        10. On the Select Policy/Role page, select Custom policy from the first drop-down list and select the custom policy created in 8.
                                                                                                        11. Click Next. On the Select Scope page, set the authorization scope. In this example, select All resources.
                                                                                                        12. Click OK.
                                                                                                          It takes 15 to 30 minutes for the authorization to be in effect.
                                                                                                          
+
                                                                                                        
+
                                                                                                        
+
                                                                                                        Step 5: Create a Flink Jar Job and Configure Job Information
                                                                                                        1. Create a Flink Jar job.
                                                                                                          1. In the navigation pane on the left of the DLI management console, choose Job Management > Flink Jobs.
                                                                                                          2. On the displayed page, click Create Job in the upper right corner.
                                                                                                            In this example, set Type to Flink Jar and Name to Flink_Jar_for_test.
                                                                                                            
 
                                                                                                          3. Click OK.
                                                                                                          
 
                                                                                                        2. Configure basic job information.
                                                                                                          Configure basic job information based on Table 5.
                                                                                                          
 
-
                                                                                                          Table 5 Parameters
                                                                                                          Parameter
                                                                                                          
+
                                                                                                          
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
@@ -234,70 +284,70 @@
 
                                                                                                        3. Configure advanced settings for the Flink Jar job.
                                                                                                          Configure the Flink Jar job based on Table 6.
                                                                                                          
 
-
                                                                                                          4. Table 5 Parameter descriptions
                                                                                                          Parameter
                                                                                                          
 
                                                                                                          Mandatory
                                                                                                          
+
                                                                                                          Mandatory
                                                                                                          
 
                                                                                                          Description
                                                                                                          
+
                                                                                                          Description
                                                                                                          
                                                                                                           		
 
                                                                                                          
 
                                                                                                          Queue
                                                                                                          
+
                                                                                                          Queue
                                                                                                          
 
                                                                                                          Yes
                                                                                                          
+
                                                                                                          Yes
                                                                                                          
 
                                                                                                          Select a queue where you want to run your job.
                                                                                                          
+
                                                                                                          Select a queue where you want to run your job.
                                                                                                          
                                                                                                           		
 
                                                                                                          Application
                                                                                                          
+
                                                                                                          Application
                                                                                                          
 
                                                                                                          Yes
                                                                                                          
+
                                                                                                          Yes
                                                                                                          
 
                                                                                                          Select the custom package in Step 1: Develop a JAR File and Upload It to OBS.
                                                                                                          
+
                                                                                                          Select the custom package in Step 1: Develop a JAR File and Upload It to OBS.
                                                                                                          
                                                                                                           		
 
                                                                                                          Main Class
                                                                                                          
+
                                                                                                          Main Class
                                                                                                          
 
                                                                                                          Yes
                                                                                                          
+
                                                                                                          Yes
                                                                                                          
 
                                                                                                          Class name of the JAR file to load
                                                                                                          
+
                                                                                                          Class name of the JAR file to load
                                                                                                          
 
                                                                                                          This parameter specifies the entry for the Flink job, that is, the class that contains the main method. This is the class that is executed first when a Flink job is started.
                                                                                                          
 
                                                                                                          If the application program is of type .jar, the main class name must be provided.
                                                                                                          
 
                                                                                                          The main class name is case-sensitive and must be correct.
                                                                                                          
@@ -222,11 +264,19 @@
 
                                                                                                           		
 
                                                                                                          Flink Version
                                                                                                          
+
                                                                                                          Flink Version
                                                                                                          
 
                                                                                                          Yes
                                                                                                          
+
                                                                                                          Yes
                                                                                                          
 
                                                                                                          Flink version used for job running
                                                                                                          
+
                                                                                                          Flink version used for job running
                                                                                                          
+
                                                                                                          If you choose to use Flink 1.15, make sure to configure the agency information for the cloud service that DLI is allowed to access in the job.
                                                                                                          
+
                                                                                                          Agency
                                                                                                          
+
                                                                                                          No
                                                                                                          
+
                                                                                                          If you choose to use Flink 1.15, configure the agency name yourself to ensure smooth job running.
                                                                                                          
                                                                                                           		
 
                                                                                                          
                                                                                                           
 
                                                                                                          Table 6 Advanced settings for the Flink Jar job
                                                                                                          Parameter
                                                                                                          
+
                                                                                                          
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                                                          Table 6 Advanced settings for the Flink Jar job
                                                                                                          Parameter
                                                                                                          
 
                                                                                                          Mandatory
                                                                                                          
+
                                                                                                          Mandatory
                                                                                                          
 
                                                                                                          Description
                                                                                                          
+
                                                                                                          Description
                                                                                                          
                                                                                                           		
 
                                                                                                          
 
                                                                                                          CUs
                                                                                                          
+
                                                                                                          CUs
                                                                                                          
 
                                                                                                          Yes
                                                                                                          
+
                                                                                                          Yes
                                                                                                          
 
                                                                                                          One CU consists of one vCPU and 4 GB of memory. The number of CUs ranges from 2 to 400.
                                                                                                          
+
                                                                                                          One CU consists of one vCPU and 4 GB of memory. The number of CUs ranges from 2 to 400.
                                                                                                          
                                                                                                           		
 
                                                                                                          Job Manager CUs
                                                                                                          
+
                                                                                                          Job Manager CUs
                                                                                                          
 
                                                                                                          Yes
                                                                                                          
+
                                                                                                          Yes
                                                                                                          
 
                                                                                                          Number of CUs allowed for the job manager. The value ranges from 1 to 4. The default value is 1.
                                                                                                          
+
                                                                                                          Number of CUs allowed for JobManager. The value ranges from 1 to 4. The default value is 1.
                                                                                                          
                                                                                                           		
 
                                                                                                          Parallelism
                                                                                                          
+
                                                                                                          Parallelism
                                                                                                          
 
                                                                                                          Yes
                                                                                                          
+
                                                                                                          Yes
                                                                                                          
 
                                                                                                          Maximum number of parallel operators in a job
                                                                                                          
+
                                                                                                          Maximum number of parallel operators in a job
                                                                                                          
 
                                                                                                           NOTE: 
                                                                                                          • The value cannot exceed four times the number of compute units (CUs – Job Manager CUs).
                                                                                                          • You are advised to set this parameter to a value greater than that configured in the code. Otherwise, job submission may fail.
                                                                                                          
 
                                                                                                          
                                                                                                           		
 
                                                                                                          Task Manager Config
                                                                                                          
+
                                                                                                          Task Manager Config
                                                                                                          
 
                                                                                                          No
                                                                                                          
+
                                                                                                          No
                                                                                                          
 
                                                                                                          Whether Task Manager resource parameters are set
                                                                                                          
+
                                                                                                          Whether TaskManager resource parameters are set
                                                                                                          
 
                                                                                                          If this option is selected, you need to set the following parameters:
                                                                                                          
-
                                                                                                          • CU(s) per TM: Number of resources occupied by each Task Manager.
                                                                                                          • Slot(s) per TM: Number of slots contained in each Task Manager.
                                                                                                          
+
                                                                                                          • CU(s) per TM: Number of resources occupied by each TaskManager.
                                                                                                          • Slot(s) per TM: Number of slots contained in each TaskManager.
                                                                                                          
                                                                                                           		
 
                                                                                                          Save Job Log
                                                                                                          
+
                                                                                                          Save Job Log
                                                                                                          
 
                                                                                                          No
                                                                                                          
+
                                                                                                          No
                                                                                                          
 
                                                                                                          Whether job running logs are saved to OBS
                                                                                                          
+
                                                                                                          Whether job running logs are saved to OBS
                                                                                                          
 
                                                                                                          If this option is selected, you need to set the following parameters:
                                                                                                          
 
                                                                                                          OBS Bucket: Select an OBS bucket to store job logs. If the OBS bucket you selected is unauthorized, click Authorize.
                                                                                                          
                                                                                                           		
 
                                                                                                          Alarm on Job Exception
                                                                                                          
+
                                                                                                          Alarm on Job Exception
                                                                                                          
 
                                                                                                          No
                                                                                                          
+
                                                                                                          No
                                                                                                          
 
                                                                                                          Whether to notify users of any job exceptions, such as running exceptions or arrears, via SMS or email.
                                                                                                          
+
                                                                                                          Whether to notify users of any job exceptions, such as running exceptions or arrears, via SMS or email.
                                                                                                          
 
                                                                                                          If this option is selected, you need to set the following parameters:
                                                                                                          
 
                                                                                                          SMN Topic
                                                                                                          
 
                                                                                                          Select a custom SMN topic. For how to create a custom SMN topic, see "Creating a Topic" in the Simple Message Notification User Guide.
                                                                                                          
                                                                                                           		
 
                                                                                                          Auto Restart on Exception
                                                                                                          
+
                                                                                                          Auto Restart on Exception
                                                                                                          
 
                                                                                                          No
                                                                                                          
+
                                                                                                          No
                                                                                                          
 
                                                                                                          Whether automatic restart is enabled. If enabled, jobs will be automatically restarted and restored when exceptions occur.
                                                                                                          
+
                                                                                                          Whether automatic restart is enabled. If enabled, jobs will be automatically restarted and restored when exceptions occur.
                                                                                                          
 
                                                                                                          If this option is selected, you need to set the following parameters:
                                                                                                          
 
                                                                                                          • Max. Retry Attempts: maximum number of retries upon an exception. The unit is times/hour.
                                                                                                            • Unlimited: The number of retries is unlimited.
                                                                                                            • Limited: The number of retries is user-defined.
                                                                                                            
 
                                                                                                          • Restore Job from Checkpoint: Restore the job from the latest checkpoint.
                                                                                                            If you select this parameter, you also need to set Checkpoint Path.
                                                                                                            
@@ -308,7 +358,7 @@
 
                                                                                                          
 
                                                                                                          
 
                                                                                                          
-
                                                                                                        4. Click Save in the upper right of the page.
                                                                                                        5. Click Start in the upper right corner.
                                                                                                        6. On the displayed Start Flink Job page, confirm the job specification and click Start Now to start the job.
                                                                                                          Once the job is started, the system automatically switches to the Flink Jobs page. Locate the job you created and check its status in the Status column.
                                                                                                          
+
                                                                                                        7. Click Save in the upper right of the page.
                                                                                                        8. Click Start in the upper right corner.
                                                                                                        9. On the displayed Start Flink Job page, confirm the job specifications and click Start Now to start the job.
                                                                                                          Once the job is started, the system automatically switches to the Flink Jobs page. Locate the job you created and check its status in the Status column.
                                                                                                          
 
                                                                                                          Once a job is successfully submitted, its status changes from Submitting to Running. After the execution is complete, the status changes to Completed.
                                                                                                          
 
                                                                                                          If the job status is Submission failed or Running exception, the job fails to submit or run. In this case, you can hover over the status icon in the Status column of the job list to view the error details. You can click  to copy these details. Rectify the fault based on the error information and resubmit the job.
                                                                                                          
 
                                                                                                          10. 
diff --git a/docs/dli/umn/dli_01_0514.html b/docs/dli/umn/dli_01_0514.html
deleted file mode 100644
index fd4a93f6d..000000000
--- a/docs/dli/umn/dli_01_0514.html
+++ /dev/null
@@ -1,70 +0,0 @@
-
-
-
                                                                                                          Binding or Unbinding an Enhanced Datasource Connection to a Queue
                                                                                                          
-
                                                                                                          Bind an elastic resource pool to a queue to connect the queue to a target data source. When an enhanced datasource connection is no longer needed, unbind the queue that was bound to it to free up resources.
                                                                                                          
-
                                                                                                          This section describes how to bind and unbind an enhanced datasource connection to a queue.
                                                                                                          
-
                                                                                                           
                                                                                                          The operations described in this section only apply to standard queues.
                                                                                                          
-
                                                                                                          
-
                                                                                                          Notes and Constraints
                                                                                                          • The CIDR block of the DLI queue that is bound with a datasource connection cannot overlap with that of the data source.
                                                                                                          • The default queue cannot be bound with a connection.
                                                                                                          
-
                                                                                                          
-
                                                                                                          Binding a Queue
                                                                                                          Before using an enhanced datasource connection, you must bind a queue and ensure that the VPC peering connection is in the Active state.
                                                                                                          
-
                                                                                                          • Method 1
                                                                                                            In the Enhanced tab, select a connection and click Bind Queue in the Operation column. In the dialog box that is displayed, select the queues to be bound and click OK.
                                                                                                            
-
                                                                                                          
-
                                                                                                          • Method 2
                                                                                                            Click the name of the selected connection. The Details page is displayed. Click Create in the upper left corner. In the dialog box that is displayed, select the queues to be bound and click OK.
                                                                                                            
-
                                                                                                          
-
                                                                                                          
-
                                                                                                          Viewing Details about a Bound Queue
                                                                                                          On the Enhanced tab page, select a connection and click the connection name to view the information about the bound queue.
-
                                                                                                          
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                                                          Table 1 Parameters in the details list of datasource connection queues
                                                                                                          Parameter
                                                                                                          
-
                                                                                                          Description
                                                                                                          
-
                                                                                                          VPC Peering ID
                                                                                                          
-
                                                                                                          ID of the VPC peering connection created in the cluster to which the queue belongs.
                                                                                                          
-
                                                                                                           NOTE: 
                                                                                                          A VPC peering connection is created for each queue bound to an enhanced datasource connection. The VPC peering connection is used for cross-VPC communication. Ensure that the security group used by the data source allows access from the DLI queue CIDR block, and do not delete the VPC peering connection during the datasource connection.
                                                                                                          
-
                                                                                                          
-
                                                                                                          Name
                                                                                                          
-
                                                                                                          Name of a bound queue.
                                                                                                          
-
                                                                                                          Connection Status
                                                                                                          
-
                                                                                                          Datasource connection status. The following three statuses are available:
                                                                                                          
-
                                                                                                          • Creating
                                                                                                          • Active
                                                                                                          • Failed
                                                                                                          
-
                                                                                                           NOTE: 
                                                                                                          If the connection status is Failed, click  on the left to view the detailed error information.
                                                                                                          
-
                                                                                                          
-
                                                                                                          Updated
                                                                                                          
-
                                                                                                          Time when a connection is updated. The connections in the connection list can be displayed according to the update time in ascending or descending order.
                                                                                                          
-
                                                                                                          Operation
                                                                                                          
-
                                                                                                          Unbind Queue: This operation is used to unbind a datasource connection from a queue.
                                                                                                          
-
                                                                                                          
-
                                                                                                          
-
                                                                                                          
-
                                                                                                          
-
                                                                                                          Unbinding a Queue
                                                                                                          If you do not need to use an enhanced datasource connection, you can unbind the queue from it to release resources.
                                                                                                          
-
                                                                                                          • Method 1
                                                                                                            On the Enhanced tab page, select a connection and click More > Unbind Queue in the Operation column. In the dialog box that is displayed, select the queues to be unbound and click OK.
                                                                                                            
-
                                                                                                          
-
                                                                                                          • Method 2
                                                                                                            Click the name of the target connection. The Details page is displayed. Select the queue to be unbound and click Unbind Queue in the Operation column. In the displayed dialog box, confirm the queue to be unbound and click Yes.
                                                                                                            
-
                                                                                                          
-
                                                                                                          
-
                                                                                                          
-
-
diff --git a/docs/dli/umn/dli_01_0515.html b/docs/dli/umn/dli_01_0515.html
index 8e7050394..f8be039f9 100644
--- a/docs/dli/umn/dli_01_0515.html
+++ b/docs/dli/umn/dli_01_0515.html
@@ -1,7 +1,7 @@
 
 
 
                                                                                                          Example Use Case: Creating an Elastic Resource Pool and Running Jobs
                                                                                                          
-
                                                                                                          This section walks you through the procedure of adding a queue to an elastic resource pool and binding an enhanced datasource connection to the elastic resource pool.
                                                                                                          Figure 1 Process of creating an elastic resource pool
                                                                                                          
+
                                                                                                          This section walks you through the procedure of adding a queue to an elastic resource pool and binding an enhanced datasource connection to the elastic resource pool.
                                                                                                          Figure 1 Process of creating an elastic resource pool
                                                                                                          
 
                                                                                                          
 
 
                                                                                                          
-
-
@@ -48,15 +48,15 @@
 
-
-
@@ -75,28 +75,28 @@
 
                                                                                                          Table 1 Procedure
                                                                                                          Step
                                                                                                          
@@ -63,7 +63,7 @@
 	`id` int(11) unsigned,
 	`name` VARCHAR(32)
 )	ENGINE = InnoDB	DEFAULT CHARACTER SET = utf8mb4;
-
                                                                                                        10. On the RDS console, choose Instances form the navigation pane. Click the name of a created RDS DB instance to view its basic information.
                                                                                                        11. In the Connection Information pane, obtain the floating IP address, database port, VPC, and subnet.
                                                                                                        12. Click the security group name. In the Inbound Rules tab, add a rule to allow access from the CIDR block of the elastic resource pool. For example, if the CIDR block of the elastic resource pool is 172.16.0.0/18 and the database port is 3306, set the rule Priority to 1, Action to Allow, Protocol to TCP and Port to 3306, Type to IPv4, and Source to 172.16.0.0/18.
                                                                                                          Click OK. The security group rule is added.
                                                                                                          
+
                                                                                                        13. On the RDS console, choose Instances form the navigation pane. Click the name of a created RDS DB instance to view its basic information.
                                                                                                        14. In the Connection Information pane, obtain the floating IP address, database port, VPC, and subnet.
                                                                                                        15. Click the security group name. In the Inbound Rules tab, add a rule to allow access from the CIDR block of the elastic resource pool. For example, if the CIDR block of the elastic resource pool is 172.16.0.0/18 and the database port is 3306, set the rule Priority to 1, Action to Allow, Protocol to TCP and Port to 3306, Type to IPv4, and Source to 172.16.0.0/18.
                                                                                                          Click OK. The security group rule is added.
                                                                                                          
 
                                                                                                        16. Log in to the DLI management console. In the navigation pane on the left, choose Datasource Connections. On the displayed page, click Create in the Enhanced tab.
                                                                                                        17. In the displayed dialog box, set the following parameters:
                                                                                                          • Connection Name: Name of the enhanced datasource connection
                                                                                                          • Resource Pool: Select the elastic resource pool created in Step 1: Create an Elastic Resource Pool.
                                                                                                             
                                                                                                            If you cannot decide the elastic resource pool in this step, you can skip this parameter, go to the Enhanced tab, and click More > Bind Resource Pool in the Operation column of the row that contains this datasource connection after it is created.
                                                                                                            
 
                                                                                                            
 
                                                                                                          • VPC: Select the VPC of the RDS DB instance obtained in 5.
                                                                                                          • Subnet: Select the subnet of the RDS DB instance obtained in 5. 
                                                                                                          • Set other parameters as you need.
                                                                                                          
@@ -89,7 +89,14 @@ SELECT
 
 
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_01_0516.html b/docs/dli/umn/dli_01_0516.html
index 0579404fe..a58da56f8 100644
--- a/docs/dli/umn/dli_01_0516.html
+++ b/docs/dli/umn/dli_01_0516.html
@@ -29,15 +29,15 @@
 
 
                                                                                                          18. 20
                                                                                                          
 
                                                                                                          Minimum CU: 64
                                                                                                          
-
                                                                                                          Maximum CU: 128
                                                                                                          
+
                                                                                                          Minimum CUs: 64
                                                                                                          
+
                                                                                                          Maximum CUs: 128
                                                                                                          
                                                                                                           		
 
                                                                                                          The time segments beyond [00:00, 09:00)
                                                                                                          
                                                                                                           		
 
                                                                                                          5
                                                                                                          
 
                                                                                                          Minimum CU: 16
                                                                                                          
-
                                                                                                          Maximum CU: 32
                                                                                                          
+
                                                                                                          Minimum CUs: 16
                                                                                                          
+
                                                                                                          Maximum CUs: 32
                                                                                                          
                                                                                                           		
 
                                                                                                          Jobs of department A
                                                                                                          
                                                                                                           		
 
                                                                                                          20
                                                                                                          
 
                                                                                                          Minimum CU: 64
                                                                                                          
-
                                                                                                          Maximum CU: 128
                                                                                                          
+
                                                                                                          Minimum CUs: 64
                                                                                                          
+
                                                                                                          Maximum CUs: 128
                                                                                                          
                                                                                                           		
 
                                                                                                          The time segments beyond [10:00, 23:00)
                                                                                                          
                                                                                                           		
 
                                                                                                          5
                                                                                                          
 
                                                                                                          Minimum CU: 32
                                                                                                          
-
                                                                                                          Maximum CU: 64
                                                                                                          
+
                                                                                                          Minimum CUs: 32
                                                                                                          
+
                                                                                                          Maximum CUs: 64
                                                                                                          
                                                                                                           		
 
                                                                                                          Jobs of department B
                                                                                                          
 
                                                                                                          
                                                                                                           
 
                                                                                                          An elastic resource pool has a maximum number of 256 CUs for queue A and queue B. The scaling policies are as follows:
                                                                                                          
-
                                                                                                          • Queue A: priority 5; period: 00:00–09:00; minimum CU: 32; maximum CU: 128
                                                                                                          • Queue B: priority 10; time period: 00:00–09:00; minimum CU: 64; maximum CU: 128
                                                                                                          
+
                                                                                                          • Queue A: priority 5; period: 00:00–09:00; minimum CUs: 32; maximum CUs: 128
                                                                                                          • Queue B: priority 10; time period: 00:00–09:00; minimum CUs: 64; maximum CUs: 128
                                                                                                          
                                                                                                           		
 
                                                                                                          From 00:00 a.m. to 09:00 a.m.:
                                                                                                          
 
                                                                                                          1. The minimum CUs are allocated to the two queues. Queue A has 32 CUs, and queue B has 64 CUs. There are 160 CUs remaining.
                                                                                                          2. The remaining CUs are allocated based on the priorities. Queue B is prior to queue A. Therefore, queue B gets 64 CUs, and queue A has 96 CUs.
                                                                                                          
                                                                                                           		
 
                                                                                                          
 
                                                                                                          An elastic resource pool has a maximum number of 96 CUs for queue A and queue B. The scaling policies are as follows:
                                                                                                          
-
                                                                                                          • Queue A: priority 5; period: 00:00–09:00; minimum CU: 32; maximum CU: 64
                                                                                                          • Queue B: priority 10; time period: 00:00–09:00; minimum CU: 64; maximum CU: 128
                                                                                                          
+
                                                                                                          • Queue A: priority 5; period: 00:00–09:00; minimum CUs: 32; maximum CUs: 64
                                                                                                          • Queue B: priority 10; time period: 00:00–09:00; minimum CUs: 64; maximum CUs: 128
                                                                                                          
                                                                                                           		
 
                                                                                                          From 00:00 a.m. to 09:00 a.m.:
                                                                                                          
 
                                                                                                          1. The minimum CUs are allocated to the two queues. Queue A has 32 CUs, and queue B has 64 CUs. There are no remaining CUs.
                                                                                                          2. The allocation is complete.
                                                                                                          
                                                                                                           		
 
                                                                                                          
 
                                                                                                          An elastic resource pool has a maximum number of 128 CUs for queue A and queue B. The scaling policies are as follows:
                                                                                                          
-
                                                                                                          • Queue A: priority 5; period: 00:00–09:00; minimum CU: 32; maximum CU: 64
                                                                                                          • Queue B: priority 10; time period: 00:00–09:00; minimum CU: 64; maximum CU: 128
                                                                                                          
+
                                                                                                          • Queue A: priority 5; period: 00:00–09:00; minimum CUs: 32; maximum CUs: 64
                                                                                                          • Queue B: priority 10; time period: 00:00–09:00; minimum CUs: 64; maximum CUs: 128
                                                                                                          
                                                                                                           		
 
                                                                                                          From 00:00 a.m. to 09:00 a.m.:
                                                                                                          
 
                                                                                                          1. The minimum CUs are allocated to the two queues. Queue A has 32 CUs, and queue B has 64 CUs. There are 32 CUs remaining.
                                                                                                          2. The remaining 32 CUs are all preferentially allocated to queue B.
                                                                                                          
                                                                                                           		
 
                                                                                                          
 
                                                                                                          An elastic resource pool has a maximum number of 128 CUs for queue A and queue B. The scaling policies are as follows:
                                                                                                          
-
                                                                                                          • Queue A: priority 5; period: 00:00–09:00; minimum CU: 32; maximum CU: 64
                                                                                                          • Queue B: priority 5; time period: 00:00–09:00; minimum CU: 64; maximum CU: 128
                                                                                                          
+
                                                                                                          • Queue A: priority 5; period: 00:00–09:00; minimum CUs: 32; maximum CUs: 64
                                                                                                          • Queue B: priority 5; time period: 00:00–09:00; minimum CUs: 64; maximum CUs: 128
                                                                                                          
                                                                                                           		
 
                                                                                                          From 00:00 a.m. to 09:00 a.m.:
                                                                                                          
 
                                                                                                          1. The minimum CUs are allocated to the two queues. Queue A has 32 CUs, and queue B has 64 CUs. There are 32 CUs remaining.
                                                                                                          2. The two queues have the same priority, the remaining 32 CUs are randomly allocated to the two queues.
                                                                                                          
@@ -117,7 +117,7 @@
 
 
 
diff --git a/docs/dli/umn/dli_01_0524.html b/docs/dli/umn/dli_01_0524.html
deleted file mode 100644
index 2675ec686..000000000
--- a/docs/dli/umn/dli_01_0524.html
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
                                                                                                          Modifying Specifications
                                                                                                          
-
                                                                                                          Scenario
                                                                                                          If the current specifications of your elastic resource pool do not meet your service needs, you can modify them using the change yearly/monthly CUs function.
                                                                                                          
-
                                                                                                          
-
                                                                                                          Scaling Out
                                                                                                          1. In the navigation pane on the left of the console, choose Resources > Resource Pool.
                                                                                                          2. Locate the elastic resource pool you want to scale out, click More in the Operation column, and select Modify Yearly/Monthly CU.
                                                                                                          3. On the Modify Yearly/Monthly CU page, set Operation to Scale-out and specify the number of CUs you want to add.
                                                                                                          4. Confirm the changes and click OK.
                                                                                                          5. Choose Job Management > SQL Jobs to view the status of the SCALE_POOL SQL job.
                                                                                                            If the job status is Scaling, the elastic resource pool is scaling out. Wait until the job status changes to Finished.
                                                                                                            
-
                                                                                                          
-
                                                                                                          
-
                                                                                                          Scaling In
                                                                                                           
                                                                                                          By default, the minimum number of CUs is 16. That is, when the specifications of an elastic resource pool are 16 CUs, you cannot scale the pool down.
                                                                                                          
-
                                                                                                          
-
                                                                                                          1. In the navigation pane on the left, choose Resources > Resource Pool.
                                                                                                          2. Locate the elastic resource pool you want to scale in, click More in the Operation column, and select Modify Yearly/Monthly CU.
                                                                                                          3. On the Modify Yearly/Monthly CU page, set Operation to Scale-in and specify the number of CUs you want to decrease.
                                                                                                          4. Confirm the changes and click OK.
                                                                                                          5. Choose Job Management > SQL Jobs to view the status of the SCALE_POOL SQL job.
                                                                                                            If the job status is Scaling, the elastic resource pool is scaling in. Wait until the job status changes to Finished.
                                                                                                            
-
                                                                                                          
-
                                                                                                          
-
                                                                                                          
-
                                                                                                          
-
                                                                                                          
-
                                                                                                          Parent topic: Managing Elastic Resource Pools
                                                                                                          
-
                                                                                                          
-
                                                                                                          
-
diff --git a/docs/dli/umn/dli_01_0525.html b/docs/dli/umn/dli_01_0525.html
index 616edbc1a..4fd6ed900 100644
--- a/docs/dli/umn/dli_01_0525.html
+++ b/docs/dli/umn/dli_01_0525.html
@@ -1,14 +1,14 @@
 
 
 
                                                                                                          Managing Tags
                                                                                                          
-
                                                                                                          Tag Management
                                                                                                          A tag is a key-value pair that you can customize to identify cloud resources. It helps you to classify and search for cloud resources. A tag consists of a tag key and a tag value.
                                                                                                          
+
                                                                                                          Tag Management
                                                                                                          A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value.
                                                                                                          
 
                                                                                                          If you use tags in other cloud services, you are advised to create the same tag (key-value pairs) for cloud resources used by the same business to keep consistency.
                                                                                                          
 
                                                                                                          DLI supports the following two types of tags:
                                                                                                          
 
                                                                                                          • Resource tags: non-global tags created on DLI
                                                                                                          
-
                                                                                                          • Predefined tags: global tags created on Tag Management Service (TMS).
                                                                                                            
+
                                                                                                            • Predefined tags: global tags created on Tag Management Service (TMS).
                                                                                                              For details about predefined tags, see Tag Management Service User Guide.
                                                                                                              
 
                                                                                                            
 
                                                                                                            DLI allows you to add, modify, or delete tags for queues.
                                                                                                            
-
                                                                                                            1. In the left navigation pane of the DLI console, choose Resources > Resource Pool.
                                                                                                            2. In the Operation column of the queue, choose More > Tags.
                                                                                                            3. The tag management page is displayed, showing the tag information about the current queue.
                                                                                                            4. Click Add/Edit Tag. The Add/Edit Tag dialog is displayed. Enter a tag and a value, and click Add.
                                                                                                              
+
                                                                                                              1. In the left navigation pane of the DLI console, choose Resources > Resource Pool.
                                                                                                              2. In the Operation column of the queue, choose More > Tags.
                                                                                                              3. The tag management page is displayed, showing the tag information about the current queue.
                                                                                                              4. On the page that appears, click Add/Edit Tag in the upper left corner. Enter a tag and a value, and click Add.
                                                                                                                
 
                                                                                                                
diff --git a/docs/dli/umn/dli_01_0526.html b/docs/dli/umn/dli_01_0526.html
index e21007af0..d83d42b9c 100644
--- a/docs/dli/umn/dli_01_0526.html
+++ b/docs/dli/umn/dli_01_0526.html
@@ -7,7 +7,7 @@
 
                                                                                                                Procedure
                                                                                                                1. In the navigation pane on the left of the DLI console, choose Resources > Resource Pool.
                                                                                                                2. Select the desired elastic resource pool and choose More > Permissions in the Operation column. The User Permissions area displays the list of users who have permissions of elastic resource pools.
                                                                                                                  You can assign permissions to new users, modify permissions for users who already have some permissions of elastic resource pools, and revoke all permissions of a user on a pool.
                                                                                                                  
 
                                                                                                                  • Assign permissions to a new user.
                                                                                                                    A new user does not have permissions on the elastic resource pool.
                                                                                                                    1. Click Set Permission in the Operations column on User Permissions page. The Set Permission dialog box is displayed.
                                                                                                                    2. Set Username to the name of the desired IAM user, and select the required permissions for the user.
                                                                                                                    3. Click OK to.
                                                                                                                      Table 1 describes the related parameters.
                                                                                                                      
 
-
                                                                                                                Table 1 Tag parameters
                                                                                                                Parameter
                                                                                                                
                                                                                                                 		
 
                                                                                                                Description
                                                                                                                
@@ -21,7 +21,7 @@
 
                                                                                                                • Click the text box and select a predefined tag key from the drop-down list.
                                                                                                                  To add a predefined tag, you need to create one on TMS and then select it from the Tag key drop-down list. You can click View predefined tags to go to the Predefined Tags page of the TMS console. Then, click Create Tag in the upper corner of the page to create a predefined tag.
                                                                                                                  
 
                                                                                                                  
 
                                                                                                                
-
                                                                                                                • Enter a tag key in the text box.
                                                                                                                   NOTE: 
                                                                                                                  A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                                                  
+
                                                                                                                  • Enter a tag key in the text box.
                                                                                                                     NOTE: 
                                                                                                                    A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                                                    
 
                                                                                                                    
 
                                                                                                                  
 
@@ -29,7 +29,7 @@
 
                                                                                                                Tag value
                                                                                                                
                                                                                                                 		
 
                                                                                                                You can specify the tag value in either of the following ways:
                                                                                                                
-
                                                                                                                • Click the text box and select a predefined tag value from the drop-down list.
                                                                                                                • Enter a tag value in the text box.
                                                                                                                   NOTE: 
                                                                                                                  A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.
                                                                                                                  
+
                                                                                                                  • Click the text box and select a predefined tag value from the drop-down list.
                                                                                                                  • Enter a tag value in the text box.
                                                                                                                     NOTE: 
                                                                                                                    A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.
                                                                                                                    
 
                                                                                                                    
 
                                                                                                                  
 
                                                                                                                Table 1 Parameters
                                                                                                                Parameter
                                                                                                                
+
                                                                                                                
@@ -16,7 +16,7 @@
 
@@ -30,9 +30,9 @@
 
-
                                                                                                              5. To assign or revoke permissions of a user who has some permissions on the elastic resource pool, perform the following steps:
                                                                                                                1. In the list under User Permissions, select the user whose permissions need to be modified and click Set Permission in the Operation column.
                                                                                                                2. In the displayed Set Permission dialog box, modify the permissions of the user. Table 1 lists the detailed permission descriptions.
                                                                                                                  If Set Permission is gray, you are not allowed to change permissions on this elastic resource pool. You can apply to the administrator, elastic resource pool owner, or other authorized users for granting and revoking permissions.
                                                                                                                  
+
                                                                                                                3. To grant or revoke permissions for a user who already has certain permissions on a queue, perform the following steps:
                                                                                                                  1. In the list under User Permissions, select the user whose permissions need to be modified and click Set Permission in the Operation column.
                                                                                                                  2. In the displayed Set Permission dialog box, modify the permissions of the user. Table 1 lists the detailed permission descriptions.
                                                                                                                    If Set Permission is gray, you are not allowed to change permissions on this elastic resource pool. You can apply to the administrator, elastic resource pool owner, or other authorized users for granting and revoking permissions.
                                                                                                                    
 
                                                                                                                  3. Click OK.
                                                                                                                  
-
                                                                                                                4. To revoke all permissions of a user on an elastic resource pool, perform the following steps:
                                                                                                                  In the list under User Permissions, select the desired user whose permissions and click Set Permission in the Operation column. Click Yes in the Revoke Permission dialog box.
                                                                                                                  
+
                                                                                                                5. To revoke all permissions from a user, perform the following steps:
                                                                                                                  In the list under User Permissions, select the desired user whose permissions and click Set Permission in the Operation column. Click Yes in the Revoke Permission dialog box.
                                                                                                                  
 
                                                                                                                  6. 
 
                                                                                                                
 
diff --git a/docs/dli/umn/dli_01_0528.html b/docs/dli/umn/dli_01_0528.html
index e86963f9b..af73c043e 100644
--- a/docs/dli/umn/dli_01_0528.html
+++ b/docs/dli/umn/dli_01_0528.html
@@ -16,20 +16,22 @@
 
                                                                                                              6. Setting Queue Properties
                                                                                                                
 
                                                                                                                7. 
-
                                                                                                              7. Testing Address Connectivity
                                                                                                                
+
                                                                                                              8. Enabling Spark Native Operator Optimization
                                                                                                                
+
                                                                                                                9. 
+
                                                                                                              9. Testing the Network Connectivity Between a Queue and a Data Source
                                                                                                                
 
                                                                                                              10. Deleting a Queue
                                                                                                                
 
                                                                                                                11. 
-
                                                                                                              11. Auto Scaling of Standard Queues
                                                                                                                
+
                                                                                                              12. Enabling Elastic Scaling for a Queue in a Non-Elastic Resource Pool
                                                                                                                
 
                                                                                                                13. 
-
                                                                                                              13. Setting a Scheduled Auto Scaling Task for a Standard Queue
                                                                                                                
+
                                                                                                              14. Creating a Scheduled Elastic Scaling Task for a Queue in a Non-Elastic Resource Pool
                                                                                                                
 
                                                                                                                15. 
-
                                                                                                              15. Changing the CIDR Block for a Standard Queue
                                                                                                                
+
                                                                                                              16. Changing the CIDR Block of a Queue in a Non-Elastic Resource Pool
                                                                                                                
 
                                                                                                                17. 
-
                                                                                                                Parent topic: Creating an Elastic Resource Pool and Queues Within It
                                                                                                                
+
                                                                                                                Parent topic: Creating an Elastic Resource Pool and Creating Queues Within It
                                                                                                                
 
                                                                                                                
 
diff --git a/docs/dli/umn/dli_01_0529.html b/docs/dli/umn/dli_01_0529.html
index 58cee0404..089fa2b0a 100644
--- a/docs/dli/umn/dli_01_0529.html
+++ b/docs/dli/umn/dli_01_0529.html
@@ -4,15 +4,15 @@
 
                                                                                                                
 
diff --git a/docs/dli/umn/dli_01_0530.html b/docs/dli/umn/dli_01_0530.html
index 1e800bacd..d6a7e2f5d 100644
--- a/docs/dli/umn/dli_01_0530.html
+++ b/docs/dli/umn/dli_01_0530.html
@@ -6,7 +6,7 @@
 
                                                                                                                 
                                                                                                                Elastic resource pools support only Flink 1.10 or later. If jobs using Flink 1.7 run on a queue that is bound to an elastic resource pool, errors may occur due to incompatibility.
                                                                                                                
 
                                                                                                                
-
                                                                                                                Prerequisites
                                                                                                                • Both the elastic resource pool and queue are available.
                                                                                                                • The queue you want to bind must be a dedicated queue in pay-per-use billing mode.
                                                                                                                • No resources are frozen.
                                                                                                                • Only queues under the same enterprise project can be bound to an elastic resource pool.
                                                                                                                
+
                                                                                                                Notes and Constraints
                                                                                                                • Both the elastic resource pool and queue are available.
                                                                                                                • The queue you want to bind must be a dedicated queue in pay-per-use billing mode.
                                                                                                                • No resources are frozen.
                                                                                                                • Only queues under the same enterprise project can be bound to an elastic resource pool.
                                                                                                                
 
                                                                                                                
 
                                                                                                                Associating a Queue
                                                                                                                1. In the navigation pane on the left, choose Resources > Resource Pool.
                                                                                                                2. Locate the row that contains the desired elastic resource pool, click More in the Operation column, and select Associate Queue.
                                                                                                                3. In the displayed dialog box, select the desired queue and click OK.
                                                                                                                
 
                                                                                                                
diff --git a/docs/dli/umn/dli_01_0531.html b/docs/dli/umn/dli_01_0531.html
index 1cc1499c2..69c3dcd4e 100644
--- a/docs/dli/umn/dli_01_0531.html
+++ b/docs/dli/umn/dli_01_0531.html
@@ -1,12 +1,12 @@
 
 
-
                                                                                                                Using DLI to Submit a Flink OpenSource SQL Job to Query RDS for MySQL Data
                                                                                                                
+
                                                                                                                Submitting a Flink OpenSource SQL Job to Query RDS for MySQL Data Using DLI
                                                                                                                
 
                                                                                                                Scenario
                                                                                                                DLI Flink jobs can use other cloud services as data sources and sink streams for real-time compute.
                                                                                                                
 
                                                                                                                This example describes how to create and submit a Flink OpenSource SQL job that uses Kafka as the source stream and RDS as the sink stream.
                                                                                                                
 
                                                                                                                
 
                                                                                                                Procedure
                                                                                                                You need to create a Flink OpenSource SQL job that has a source stream and a sink stream. The source stream reads data from Kafka, and the sink stream writes data to RDS for MySQL. Procedure shows the process.
                                                                                                                
 
-
                                                                                                                Table 1 Parameter descriptions
                                                                                                                Parameter
                                                                                                                
                                                                                                                 		
 
                                                                                                                Description
                                                                                                                
 
                                                                                                                Username
                                                                                                                
                                                                                                                 		
 
                                                                                                                Name of the user you want to grant permissions to
                                                                                                                
-
                                                                                                                 NOTE: 
                                                                                                                The username must be an existing IAM username and has logged in to the DLI management console.
                                                                                                                
+
                                                                                                                 NOTE: 
                                                                                                                The username must be an existing IAM username and has been used to log in to the DLI management console.
                                                                                                                
 
                                                                                                                
 
                                                                                                                		
 
                                                                                                                
 
 
 
 
 
 
 
 
 
 
                                                                                                                
@@ -189,6 +201,8 @@
 
@@ -210,6 +224,7 @@
 
@@ -252,6 +267,7 @@
 
@@ -269,6 +285,7 @@
 
@@ -290,7 +307,7 @@
 
-
@@ -298,6 +315,9 @@
 
@@ -395,9 +415,9 @@
 
                                                                                                              17. Click Create Now.
                                                                                                                18. 
-
                                                                                                                Step 4: Create an Elastic Resource Pool and Add Queues to the Pool
                                                                                                                To create a Flink OpenSource SQL job, you must use your own queue as the existing default queue cannot be used. In this example, create an elastic resource pool named dli_resource_pool and a queue named dli_queue_01.
                                                                                                                
-
                                                                                                                1. Log in to the DLI management console.
                                                                                                                2. In the navigation pane on the left, choose Resources > Resource Pool.
                                                                                                                3. On the displayed page, click Buy Resource Pool in the upper right corner.
                                                                                                                4. On the displayed page, set the parameters.
                                                                                                                  Table 5 describes the parameters.
-
                                                                                                                Table 1 Procedure for using DLI to submit a Flink OpenSource SQL job to query RDS for MySQL data
                                                                                                                Procedure
                                                                                                                
+
                                                                                                                
@@ -27,7 +27,7 @@
 
-
@@ -42,7 +42,12 @@
 
-
+
+
+
@@ -75,7 +80,8 @@
 
-
@@ -96,7 +102,8 @@
 
-
@@ -111,6 +118,7 @@
 
@@ -118,6 +126,8 @@
 
@@ -147,7 +157,8 @@
 
-
@@ -162,7 +173,7 @@
 
                                                                                                                Table 1 Procedure for using DLI to submit a Flink OpenSource SQL job to query RDS for MySQL data
                                                                                                                Step
                                                                                                                
                                                                                                                 		
 
                                                                                                                Description
                                                                                                                
 
                                                                                                                Create an OBS bucket to store checkpoints, job logs, and debugging test data for the Flink OpenSource SQL job.
                                                                                                                
                                                                                                                 		
 
                                                                                                                Step 4: Create an Elastic Resource Pool and Add Queues to the Pool
                                                                                                                
+
                                                                                                                Step 4: Create an Elastic Resource Pool and Create Queues Within It
                                                                                                                
                                                                                                                 		
 
                                                                                                                Create compute resources required for submitting the Flink OpenSource SQL job.
                                                                                                                
 
                                                                                                                Create an enhanced datasource connection to connect the DLI elastic resource pool and the RDS for MySQL DB instance.
                                                                                                                
                                                                                                                 		
 
                                                                                                                Step 7: Create a Flink OpenSource SQL Job
                                                                                                                
+
                                                                                                                Step 7: Use DEW to Manage Access Credentials and Create an Agency That Allows DLI to Access DEW
                                                                                                                
+
                                                                                                                In cross-source analysis scenarios, use DEW to manage access credentials of data sources and create an agency that allows DLI to access DEW.
                                                                                                                
+
                                                                                                                Step 8: Create a Flink OpenSource SQL Job
                                                                                                                
                                                                                                                 		
 
                                                                                                                Once you have prepared a source stream and a sink stream, you can create a Flink OpenSource SQL job to analyze the data.
                                                                                                                
 
                                                                                                                
 
                                                                                                                AZ
                                                                                                                
 
                                                                                                                An AZ is a physical location that uses an independent power supply and network. AZs within the same region can communicate with each other over an intranet.
                                                                                                                
+
                                                                                                                An AZ is a physical region where resources have independent power supplies and networks. AZs are physically isolated but interconnected through an internal network.
                                                                                                                
+
                                                                                                                Select one AZ or a minimum of three AZs. The AZ setting is fixed once the instance is created.
                                                                                                                
                                                                                                                 		
 
                                                                                                                AZ 1, AZ 2, and AZ 3
                                                                                                                
 
                                                                                                                
 
                                                                                                                Broker Flavor
                                                                                                                
 
                                                                                                                Select a broker flavor based on service requirements.
                                                                                                                
+
                                                                                                                Select a broker flavor based on service requirements.
                                                                                                                
+
                                                                                                                Maximum number of partitions per broker × Number of brokers = Maximum number of partitions of an instance. Creating a topic fails when the total number of partitions for all topics exceeds the instance partition limit.
                                                                                                                
                                                                                                                 		
 
                                                                                                                kafka.2u4g.cluster.small
                                                                                                                
 
                                                                                                                Storage Space per Broker
                                                                                                                
                                                                                                                 		
 
                                                                                                                Select a disk type and specify the disk size. You cannot change the disk type once the instance is created.
                                                                                                                
+
                                                                                                                Options for Type are High I/O, Ultra-high I/O, General Purpose SSD, and Extreme SSD.
                                                                                                                
                                                                                                                 		
 
                                                                                                                High I/O | 100 GB
                                                                                                                
 
                                                                                                                VPC
                                                                                                                
                                                                                                                 		
 
                                                                                                                Select a created or shared VPC.
                                                                                                                
+
                                                                                                                A VPC can create an isolated virtual network for your Kafka instances, where you can configure and manage networks independently. To check or create a VPC, click Manage VPCs on the right to access the VPC console.
                                                                                                                
+
                                                                                                                The VPC you specify here cannot be changed once the Kafka instance is created.
                                                                                                                
                                                                                                                 		
 
                                                                                                                Select the VPC created in 1.
                                                                                                                
 
                                                                                                                
 
                                                                                                                Instance Name
                                                                                                                
 
                                                                                                                Enter an instance name based on the naming rule.
                                                                                                                
+
                                                                                                                Enter an instance name.
                                                                                                                
+
                                                                                                                The name must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
                                                                                                                
                                                                                                                 		
 
                                                                                                                kafka-dliflink
                                                                                                                
                                                                                                                 		
 
                                                                                                                
 
                                                                                                                
-
                                                                                                              18. Click Buy.
                                                                                                              19. Confirm that the instance information is correct, read and agree to the , and click Submit. It takes about 10 to 15 minutes to create an instance.
                                                                                                                20. 
+
                                                                                                              20. Click Buy.
                                                                                                              21. Click Submit. The process will take approximately 10 to 15 minutes.
                                                                                                                22. 
 
                                                                                                              22. Create a Kafka topic.
                                                                                                                1. Click the name of the created Kafka instance. The basic information page of the instance is displayed.
                                                                                                                2. Choose Topics in the navigation pane on the left. On the displayed page, click Create Topic. Configure the following parameters:
                                                                                                                  • Topic Name: For this example, enter testkafkatopic.
                                                                                                                  • Partitions: Set the value to 1.
                                                                                                                  • Replicas: Set the value to 1.
                                                                                                                  
 
                                                                                                                  Retain the default values for other parameters.
                                                                                                                  
 
                                                                                                                
@@ -182,6 +193,7 @@
 
                                                                                                                23. Region
                                                                                                                
                                                                                                                 		
 
                                                                                                                Select the region where DLI is.
                                                                                                                
+
                                                                                                                Products in different regions cannot communicate with each other through a private network. After a DB instance is created, the region cannot be changed. Exercise caution when selecting a region.
                                                                                                                
                                                                                                                 		
 
                                                                                                                _
                                                                                                                
 
                                                                                                                Instance Name
                                                                                                                
                                                                                                                 		
 
                                                                                                                Instance name
                                                                                                                
+
                                                                                                                The name can contain 4 to 64 characters and must start with a letter. Only letters (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.
                                                                                                                
+
                                                                                                                If you intend to create multiple DB instances and read replicas at a time, the allowed length for each instance name will change.
                                                                                                                
                                                                                                                 		
 
                                                                                                                rds-dliflink
                                                                                                                
 
                                                                                                                DB Instance Type
                                                                                                                
                                                                                                                 		
 
                                                                                                                Primary/standby mode of the DB instance
                                                                                                                
+
                                                                                                                • Primary/Standby: An HA architecture. In a primary/standby pair, each instance has the same instance class. When a primary instance is being created, a standby instance is provisioned along with it to provide data redundancy. The standby instance is invisible to you after being created.
                                                                                                                • Single: A single-node architecture is less expensive than a primary/standby DB pair. It is recommended for development and testing of microsites, and small- and medium-sized enterprises, or for learning about RDS.
                                                                                                                
                                                                                                                 		
 
                                                                                                                Primary/Standby
                                                                                                                
 
                                                                                                                Disk Encryption
                                                                                                                
                                                                                                                 		
 
                                                                                                                Determine whether to enable disk encryption.
                                                                                                                
+
                                                                                                                • Deselected: Encryption is not enabled.
                                                                                                                • Selected: Selecting it enhances data security but may slightly impact database read and write performance.
                                                                                                                
                                                                                                                 		
 
                                                                                                                Disabled
                                                                                                                
 
                                                                                                                Database Port
                                                                                                                
                                                                                                                 		
 
                                                                                                                Port 3306 is used by default.
                                                                                                                
+
                                                                                                                For RDS for MySQL instances, the value ranges from 1024 to 65535, excluding 12017, 33071, and 33062, which are reserved for RDS system use.
                                                                                                                
                                                                                                                 		
 
                                                                                                                3306
                                                                                                                
 
                                                                                                                
 
                                                                                                                Administrator
                                                                                                                
 
                                                                                                                root
                                                                                                                
+
                                                                                                                DB administrator. The default username is root.
                                                                                                                
                                                                                                                 		
 
                                                                                                                root
                                                                                                                
 
                                                                                                                Administrator Password
                                                                                                                
                                                                                                                 		
 
                                                                                                                Administrator password
                                                                                                                
+
                                                                                                                The password must consist of 8 to 32 characters and contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and the following special characters: ~!@#$%^*-_=+?,()&.| Enter a strong password and change it regularly to enhance security and prevent risks like brute-force attacks.
                                                                                                                
+
                                                                                                                If the password you provide is considered weak by the system, you will be prompted to provide a stronger password.
                                                                                                                
+
                                                                                                                Keep this password secure. The system cannot retrieve it.
                                                                                                                
                                                                                                                 		
 
                                                                                                                -
                                                                                                                
                                                                                                                 		
 
 
                                                                                                                Table 5 Parameters
                                                                                                                Parameter
                                                                                                                
+
                                                                                                                Step 4: Create an Elastic Resource Pool and Create Queues Within It
                                                                                                                To create a Flink OpenSource SQL job, you must use your own queue as the existing default queue cannot be used. In this example, create an elastic resource pool named dli_resource_pool and a queue named dli_queue_01.
                                                                                                                
+
                                                                                                                1. Log in to the DLI management console.
                                                                                                                2. In the navigation pane on the left, choose Resources > Resource Pool.
                                                                                                                3. On the displayed page, click Buy Resource Pool in the upper right corner.
                                                                                                                4. On the displayed page, set the parameters.
                                                                                                                  Table 5 describes the parameters.
+
                                                                                                                  
@@ -426,7 +446,7 @@
 
-
@@ -442,7 +462,7 @@
 
-
@@ -458,41 +478,41 @@
 
                                                                                                                  Table 5 Parameter descriptions
                                                                                                                  Parameter
                                                                                                                  
                                                                                                                   		
 
                                                                                                                  Description
                                                                                                                  
 
                                                                                                                  dli_resource_pool
                                                                                                                  
                                                                                                                   		
 
                                                                                                                  Specifications
                                                                                                                  
+
                                                                                                                  Type
                                                                                                                  
                                                                                                                   		
 
                                                                                                                  Specifications of the elastic resource pool
                                                                                                                  
 
                                                                                                                  
 
                                                                                                                  CIDR Block
                                                                                                                  
 
                                                                                                                  CIDR block the elastic resource pool belongs to. If you use an enhanced datasource connection, this CIDR block cannot overlap that of the data source. Once set, this CIDR block cannot be changed.
                                                                                                                  
+
                                                                                                                  CIDR block the elastic resource pool belongs to. If you use an enhanced datasource connection, this CIDR block cannot overlap that of the data source. Once set, this CIDR block cannot be changed.
                                                                                                                  
                                                                                                                   		
 
                                                                                                                  172.16.0.0/19
                                                                                                                  
 
                                                                                                                  
 
                                                                                                                  
 
                                                                                                                  
-
                                                                                                                5. Click Buy.
                                                                                                                6. Click Submit.
                                                                                                                7. In the elastic resource pool list, locate the pool you just created and click Add Queue in the Operation column.
                                                                                                                8. Set the basic parameters listed below.
+
                                                                                                                9. Click Buy.
                                                                                                                10. Click Submit.
                                                                                                                11. In the elastic resource pool list, locate the pool you just created and click Add Queue in the Operation column.
                                                                                                                12. Set the basic parameters listed below.
 
                                                                                                                  
-
-
-
-
-
-
-
-
                                                                                                                  Table 6 Basic parameters for adding a queue
                                                                                                                  Parameter
                                                                                                                  
 
                                                                                                                  Description
                                                                                                                  
+
                                                                                                                  Description
                                                                                                                  
 
                                                                                                                  Example Value
                                                                                                                  
+
                                                                                                                  Example Value
                                                                                                                  
                                                                                                                   		
 
                                                                                                                  
                                                                                                                   
 
                                                                                                                  Name
                                                                                                                  
 
                                                                                                                  Name of the queue to add
                                                                                                                  
+
                                                                                                                  Name of the queue to add
                                                                                                                  
 
                                                                                                                  dli_queue_01
                                                                                                                  
+
                                                                                                                  dli_queue_01
                                                                                                                  
                                                                                                                   		
 
                                                                                                                  
 
                                                                                                                  Type
                                                                                                                  
 
                                                                                                                  Type of the queue
                                                                                                                  
-
                                                                                                                  • To execute SQL jobs, select For SQL.
                                                                                                                  • To execute Flink or Spark jobs, select For general purpose.
                                                                                                                  
+
                                                                                                                  Type of the queue
                                                                                                                  
+
                                                                                                                  • To execute SQL jobs, select For SQL.
                                                                                                                  • To execute Flink or Spark jobs, select For general purpose.
                                                                                                                  
 
                                                                                                                  _
                                                                                                                  
+
                                                                                                                  For general purpose
                                                                                                                  
                                                                                                                   		
 
                                                                                                                  
 
                                                                                                                  Enterprise Project
                                                                                                                  
 
                                                                                                                  Select an enterprise project.
                                                                                                                  
+
                                                                                                                  Select an enterprise project for the elastic resource pool.
                                                                                                                  
 
                                                                                                                  default
                                                                                                                  
+
                                                                                                                  default
                                                                                                                  
                                                                                                                   		
 
                                                                                                                  
                                                                                                                   
 
                                                                                                                  
 
                                                                                                                  
-
                                                                                                                13. Click Next and configure scaling policies for the queue.
                                                                                                                  Click Create to add a scaling policy with varying priority, period, minimum CUs, and maximum CUs.
                                                                                                                  
+
                                                                                                                14. Click Next and configure scaling policies for the queue.
                                                                                                                  Click Create to add a scaling policy with varying priority, period, minimum CUs, and maximum CUs.
                                                                                                                  
 
                                                                                                                  
 
 
                                                                                                                  
-
-
-
                                                                                                                  Table 7 Scaling policy parameters
                                                                                                                  Parameter
                                                                                                                  
@@ -505,17 +525,17 @@
 
                                                                                                                  
 
                                                                                                                  Priority
                                                                                                                  
 
                                                                                                                  Priority of the scaling policy in the current elastic resource pool. A larger value indicates a higher priority. In this example, only one scaling policy is configured, so its priority is set to 1 by default.
                                                                                                                  
+
                                                                                                                  Priority of the scaling policy in the current elastic resource pool. A larger value indicates a higher priority. In this example, only one scaling policy is configured, so its priority is set to 1 by default.
                                                                                                                  
                                                                                                                   		
 
                                                                                                                  1
                                                                                                                  
                                                                                                                   		
 
                                                                                                                  
 
                                                                                                                  Period
                                                                                                                  
 
                                                                                                                  The first scaling policy is the default policy, and its Period parameter configuration cannot be deleted or modified.
                                                                                                                  
+
                                                                                                                  The first scaling policy is the default policy, and its Period parameter configuration cannot be deleted or modified.
                                                                                                                  
 
                                                                                                                  The period for the scaling policy is from 00 to 24.
                                                                                                                  
 
                                                                                                                  00–24
                                                                                                                  
+
                                                                                                                  00-24
                                                                                                                  
                                                                                                                   		
 
                                                                                                                  
 
                                                                                                                  Min CU
                                                                                                                  
@@ -535,31 +555,128 @@
 
                                                                                                                  
 
                                                                                                                  
 
                                                                                                                  
-
                                                                                                                15. Click OK.
                                                                                                                
+
                                                                                                              23. Click OK.
                                                                                                                24. 
 
                                                                                                                
 
                                                                                                                Step 5: Create an Enhanced Datasource Connection Between DLI and Kafka
                                                                                                                You need to create an enhanced datasource connection for the Flink OpenSource SQL job. For details, see "Datasource Connections" > "Creating an Enhanced Datasource Connection" in the Data Lake Insight User Guide.
                                                                                                                
 
                                                                                                                 
                                                                                                                • The CIDR block of the DLI queue bound with a datasource connection cannot overlap with the CIDR block of the data source.
                                                                                                                • Datasource connections cannot be created for the default queue.
                                                                                                                • To access a table across data sources, you need to use a queue bound to a datasource connection.
                                                                                                                
 
                                                                                                                
 
                                                                                                                1. Create a Kafka security group rule to allow access from the CIDR block of the DLI queue.
                                                                                                                  1. On the Kafka management console, click an instance name on the DMS for Kafka page. Basic information of the Kafka instance is displayed.
                                                                                                                  2. In the Connection pane, obtain the Instance Address (Private Network). In the Network pane, obtain the VPC and subnet of the instance.
                                                                                                                  3. Click the security group name in the Network pane. On the displayed page, click the Inbound Rules tab and add a rule to allow access from the DLI queue.
                                                                                                                    For example, if the CIDR block of the queue is 10.0.0.0/16, set Protocol to TCP, Type to IPv4, Source to 10.0.0.0/16, and click OK.
                                                                                                                    
 
                                                                                                                  
-
                                                                                                                2. Create an enhanced datasource connection to Kafka.
                                                                                                                  1. Log in to the DLI management console. In the navigation pane on the left, choose Datasource Connections. On the displayed page, click Create in the Enhanced tab.
                                                                                                                  2. In the displayed dialog box, set the following parameters: For details, see the following section:
                                                                                                                    • Connection Name: Name of the enhanced datasource connection For this example, enter dli_kafka.
                                                                                                                    • Resource Pool: Select the elastic resource pool created in Step 4: Create an Elastic Resource Pool and Add Queues to the Pool.
                                                                                                                    • VPC: Select the VPC of the Kafka instance.
                                                                                                                    • Subnet: Select the subnet of Kafka instance.
                                                                                                                    • Set other parameters as you need.
                                                                                                                    
+
                                                                                                                  3. Create an enhanced datasource connection to Kafka.
                                                                                                                    1. Log in to the DLI management console. In the navigation pane on the left, choose Datasource Connections. On the displayed page, click Create in the Enhanced tab.
                                                                                                                    2. In the displayed dialog box, set the following parameters: For details, see the following section:
                                                                                                                      • Connection Name: Name of the enhanced datasource connection For this example, enter dli_kafka.
                                                                                                                      • Resource Pool: Select the elastic resource pool created in Step 4: Create an Elastic Resource Pool and Create Queues Within It.
                                                                                                                      • VPC: Select the VPC of the Kafka instance.
                                                                                                                      • Subnet: Select the subnet of Kafka instance.
                                                                                                                      • Set other parameters as you need.
                                                                                                                      
 
                                                                                                                      Click OK. Click the name of the created datasource connection to view its status. You can perform subsequent steps only after the connection status changes to Active.
                                                                                                                      
-
                                                                                                                    3. Choose Resources > Queue Management and locate the queue created in Step 4: Create an Elastic Resource Pool and Add Queues to the Pool. In the Operation column, click More and select Test Address Connectivity.
                                                                                                                    4. In the displayed dialog box, enter Kafka instance address (private network):port in the Address box and click Test to check whether the instance is reachable. Note that multiple addresses must be tested separately.
                                                                                                                    
+
                                                                                                                  4. Choose Resources > Queue Management and locate the queue created in Step 4: Create an Elastic Resource Pool and Create Queues Within It. In the Operation column, click More and select Test Address Connectivity.
                                                                                                                  5. In the displayed dialog box, enter Kafka instance address (private network):port in the Address box and click Test to check whether the instance is reachable. Note that multiple addresses must be tested separately.
                                                                                                                  
 
                                                                                                                
 
                                                                                                                
 
                                                                                                                Step 6: Create an Enhanced Datasource Connection Between DLI and RDS
                                                                                                                1. Create an RDS security group rule to allow access from CIDR block of the DLI queue.
                                                                                                                  If the RDS DB instance and Kafka instance are in the same security group of the same VPC, skip this step. Access from the DLI queue has been allowed in 1.
                                                                                                                  1. Go to the RDS console, click the name of the target RDS for MySQL DB instance on the Instances page. Basic information of the instance is displayed.
                                                                                                                  2. In the Connection Information pane, obtain the floating IP address, database port, VPC, and subnet.
                                                                                                                  3. Click the security group name. On the displayed page, click the Inbound Rules tab and add a rule to allow access from the DLI queue. For example, if the CIDR block of the queue is 10.0.0.0/16, set Priority to 1, Action to Allow, Protocol to TCP, Type to IPv4, Source to 10.0.0.0/16, and click OK.
                                                                                                                  
 
                                                                                                                  
 
                                                                                                                2. Create an enhanced datasource connection to RDS.
                                                                                                                  If the RDS DB instance and Kafka instance are in the same VPC and subnet, skip this step. The enhanced datasource connection created in 2 has connected the subnet.
                                                                                                                  
-
                                                                                                                  If the two instances are in different VPCs or subnets, perform the following steps to create an enhanced datasource connection:
                                                                                                                  1. Log in to the DLI management console. In the navigation pane on the left, choose Datasource Connections. On the displayed page, click Create in the Enhanced tab.
                                                                                                                  2. In the displayed dialog box, set the following parameters: For details, see the following section:
                                                                                                                    • Connection Name: Name of the enhanced datasource connection For this example, enter dli_rds.
                                                                                                                    • Resource Pool: Select the name of the queue created in Step 4: Create an Elastic Resource Pool and Add Queues to the Pool.
                                                                                                                    • VPC: Select the VPC of the RDS DB instance.
                                                                                                                    • Subnet: Select the subnet of RDS DB instance.
                                                                                                                    • Set other parameters as you need.
                                                                                                                    
+
                                                                                                                    If the two instances are in different VPCs or subnets, perform the following steps to create an enhanced datasource connection:
                                                                                                                    1. Log in to the DLI management console. In the navigation pane on the left, choose Datasource Connections. On the displayed page, click Create in the Enhanced tab.
                                                                                                                    2. In the displayed dialog box, set the following parameters: For details, see the following section:
                                                                                                                      • Connection Name: Name of the enhanced datasource connection For this example, enter dli_rds.
                                                                                                                      • Resource Pool: Select the name of the queue created in Step 4: Create an Elastic Resource Pool and Create Queues Within It.
                                                                                                                      • VPC: Select the VPC of the RDS DB instance.
                                                                                                                      • Subnet: Select the subnet of RDS DB instance.
                                                                                                                      • Set other parameters as you need.
                                                                                                                      
 
                                                                                                                      Click OK. Click the name of the created datasource connection to view its status. You can perform subsequent steps only after the connection status changes to Active.
                                                                                                                      
-
                                                                                                                    3. Choose Resources > Queue Management and locate the queue created in Step 4: Create an Elastic Resource Pool and Add Queues to the Pool. In the Operation column, click More and select Test Address Connectivity.
                                                                                                                    4. In the displayed dialog box, enter Floating IP address:Database port of the RDS for MySQL DB instance in the Address box and click Test to check if the instance is reachable.
                                                                                                                    
+
                                                                                                                  3. Choose Resources > Queue Management and locate the queue created in Step 4: Create an Elastic Resource Pool and Create Queues Within It. In the Operation column, click More and select Test Address Connectivity.
                                                                                                                  4. In the displayed dialog box, enter Floating IP address:Database port of the RDS for MySQL DB instance in the Address box and click Test to check if the instance is reachable.
                                                                                                                  
 
                                                                                                                  
 
                                                                                                                
 
                                                                                                                
-
                                                                                                                Step 7: Create a Flink OpenSource SQL Job
                                                                                                                After the source and sink streams are prepared, you can create a Flink OpenSource SQL job.
                                                                                                                
-
                                                                                                                1. In the left navigation pane of the DLI management console, choose Job Management > Flink Jobs. The Flink Jobs page is displayed.
                                                                                                                2. In the upper right corner of the Flink Jobs page, click Create Job. Set the following parameters:
                                                                                                                  • Type: Flink OpenSource SQL
                                                                                                                  • Name: JobSample
                                                                                                                  • Description: Leave it blank.
                                                                                                                  • Template Name: Do not select any template.
                                                                                                                  
-
                                                                                                                3. Click OK to enter the editing page.
                                                                                                                4. Set job running parameters. The mandatory parameters are as follows:
                                                                                                                  • Queue: dli_queue_01
                                                                                                                  • Flink Version: Select 1.12.
                                                                                                                  • Save Job Log: Enable this function.
                                                                                                                  • OBS Bucket: Select an OBS bucket for storing job logs and grant access permissions of the OBS bucket as prompted.
                                                                                                                  • Enable Checkpointing: Enable this function.
                                                                                                                  
-
                                                                                                                  You do not need to set other parameters.
                                                                                                                  
+
                                                                                                                  Step 7: Use DEW to Manage Access Credentials and Create an Agency That Allows DLI to Access DEW
                                                                                                                  In cross-source analysis scenarios, you need to set attributes such as the username and password in the connector. However, information such as usernames and passwords is highly sensitive and needs to be encrypted to ensure user data privacy.
                                                                                                                  
+
                                                                                                                  Flink 1.15 allows for the use of DEW to manage credentials. Before running a job, create a custom agency and configure agency information within the job.
                                                                                                                  
+
                                                                                                                  Data Encryption Workshop (DEW) and Cloud Secret Management Service (CSMS) joint form a secure, reliable, and easy-to-use privacy data encryption and decryption solution. This example describes how a Flink OpenSource SQL job uses DEW to manage RDS access credentials.
                                                                                                                  
+
                                                                                                                  1. Create an agency for DLI to access DEW and complete authorization.
                                                                                                                  2. Create a shared secret in DEW.
                                                                                                                  3. Log in to the DEW management console.
                                                                                                                  4. In the navigation pane on the left, choose Cloud Secret Management Service > Secrets.
                                                                                                                  5. Click Create Secret. On the displayed page, configure basic secret information.
                                                                                                                    • Secret Name: Enter a secret name. In this example, the name is secretInfo.
                                                                                                                    • Secret Value: Enter the username and password for logging in to the RDS for MySQL DB instance.
                                                                                                                      • The key in the first line is MySQLUsername, and the value is the username for logging in to the DB instance.
                                                                                                                      • The key in the second line is MySQLPassword, and the value is the password for logging in to the DB instance.
                                                                                                                      
+
                                                                                                                    
+
                                                                                                                  6. Set other parameters as required and click OK.
                                                                                                                    
+
                                                                                                                  
+
                                                                                                                  
+
                                                                                                                  Step 8: Create a Flink OpenSource SQL Job
                                                                                                                  After the source and sink streams are prepared, you can create a Flink OpenSource SQL job.
                                                                                                                  
+
                                                                                                                  1. In the left navigation pane of the DLI management console, choose Job Management > Flink Jobs. The Flink Jobs page is displayed.
                                                                                                                  2. In the upper right corner of the Flink Jobs page, click Create Job.
                                                                                                                    Table 8 describes the parameters required for this example. For other parameters, retain the default values.
                                                                                                                    
+
+
                                                                                                                    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                    Table 8 Job parameters
                                                                                                                    Parameter
                                                                                                                    
+
                                                                                                                    Description
                                                                                                                    
+
                                                                                                                    Example Value
                                                                                                                    
+
                                                                                                                    Type
                                                                                                                    
+
                                                                                                                    Select Flink OpenSource SQL. This means you will need to start jobs by compiling SQL statements.
                                                                                                                    
+
                                                                                                                    Flink OpenSource SQL
                                                                                                                    
+
                                                                                                                    Name
                                                                                                                    
+
                                                                                                                    Job name. The value can contain up to 57 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
                                                                                                                    
+
                                                                                                                     NOTE: 
                                                                                                                    The job name must be globally unique.
                                                                                                                    
+
                                                                                                                    
+
                                                                                                                    JobSample
                                                                                                                    
+
                                                                                                                    
+
                                                                                                                    
+
                                                                                                                  3. Click OK to enter the editing page.
                                                                                                                  4. Set job running parameters.
                                                                                                                    Table 9 describes the mandatory parameters.
                                                                                                                    
+
+
                                                                                                                    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                    Table 9 Job running parameters
                                                                                                                    Parameter
                                                                                                                    
+
                                                                                                                    Description
                                                                                                                    
+
                                                                                                                    Example Value
                                                                                                                    
+
                                                                                                                    Queue
                                                                                                                    
+
                                                                                                                    Select a queue to run the job.
                                                                                                                    
+
                                                                                                                    dli_queue_01
                                                                                                                    
+
                                                                                                                    Flink Version
                                                                                                                    
+
                                                                                                                    Flink version used for job running. Flink versions have varying feature support.
                                                                                                                    
+
                                                                                                                    Flink 1.12
                                                                                                                    
+
                                                                                                                    OBS Bucket
                                                                                                                    
+
                                                                                                                    Select an OBS bucket to store job logs and checkpoints. If the OBS bucket you selected is unauthorized, click Authorize.
                                                                                                                    
+
                                                                                                                    _
                                                                                                                    
+
                                                                                                                    Save Job Log
                                                                                                                    
+
                                                                                                                    Whether to save job run logs to OBS.
                                                                                                                    
+
                                                                                                                    The logs are saved in Bucket name/jobs/logs/Directory starting with the job ID.
                                                                                                                    
+
                                                                                                                     CAUTION: 
                                                                                                                    You are advised to select this parameter. Otherwise, no run logs will be generated after the job is executed. If the job runs abnormally later, you will be unable to obtain the run logs for troubleshooting.
                                                                                                                    
+
                                                                                                                    
+
                                                                                                                    If selected, you need to set the following parameters:
                                                                                                                    
+
                                                                                                                    OBS Bucket: Select an OBS bucket to store job logs. If the OBS bucket you selected is unauthorized, click Authorize.
                                                                                                                    
+
                                                                                                                    If Enable Checkpointing and Save Job Log are both selected, you only need to authorize OBS once.
                                                                                                                    
+
                                                                                                                    Selected
                                                                                                                    
+
                                                                                                                    Enable Checkpointing
                                                                                                                    
+
                                                                                                                    Whether to enable job snapshots. If enabled, jobs can be restored from checkpoints.
                                                                                                                    
+
                                                                                                                    If selected, you need to set the following parameters:
                                                                                                                    • Checkpoint Interval: interval for creating checkpoints, in seconds. The value ranges from 1 to 999999, and the default value is 30.
                                                                                                                    • Checkpoint Mode: checkpointing mode, which can be set to either of the following values:
                                                                                                                      • At least once: Events are processed at least once.
                                                                                                                      • Exactly once: Events are processed only once.
                                                                                                                      
+
                                                                                                                    
+
                                                                                                                    
+
                                                                                                                    If you select Enable Checkpointing, you also need to set OBS Bucket.
                                                                                                                    
+
                                                                                                                    OBS Bucket: Select an OBS bucket to store your checkpoints. If the OBS bucket you selected is unauthorized, click Authorize.
                                                                                                                    
+
                                                                                                                    Checkpoints are saved in Bucket name/jobs/checkpoint/Directory starting with the job ID.
                                                                                                                     NOTE: 
                                                                                                                    If Enable Checkpointing and Save Job Log are both selected, you only need to authorize OBS once.
                                                                                                                    
+
                                                                                                                    
+
                                                                                                                    
+
                                                                                                                    Selected
                                                                                                                    
+
                                                                                                                    
+
                                                                                                                    
+
                                                                                                                    
 
                                                                                                                  5. Click Save.
                                                                                                                  6. Edit the Flink OpenSource SQL job.
                                                                                                                    In the SQL statement editing area, enter query and analysis statements as you need. The example statements are as follows. Note that the values of the parameters in bold must be changed according to the comments.
                                                                                                                    CREATE TABLE kafkaSource (
   order_id string,
   order_channel string,
@@ -599,7 +716,7 @@ CREATE TABLE jdbcSink (
 
 insert into jdbcSink select * from kafkaSource;
                                                                                                                    
 
                                                                                                                    
-
                                                                                                                  7. Click Check Semantics.
                                                                                                                  8. Click Start. On the displayed Start Flink Job page, confirm the job specifications and the price, and click Start Now to start the job.
                                                                                                                    After the job is started, the system automatically switches to the Flink Jobs page, and the created job is displayed in the job list. You can view the job status in the Status column. After a job is successfully submitted, Status of the job will change from Submitting to Running.
                                                                                                                    
+
                                                                                                                  9. Click Check Semantics.
                                                                                                                  10. Click Start. On the displayed Start Flink Job page, confirm the job specifications and the price and click Start Now to start the job.
                                                                                                                    After the job is started, the system automatically switches to the Flink Jobs page, and the created job is displayed in the job list. You can view the job status in the Status column. After a job is successfully submitted, Status of the job will change from Submitting to Running.
                                                                                                                    
 
                                                                                                                    If Status of a job is Submission failed or Running exception, the job fails to be submitted or fails to run. In this case, you can hover over the status icon to view the error details. You can click  to copy these details. Rectify the fault based on the error information and resubmit the job.
                                                                                                                    
 
                                                                                                                  11. Connect to the Kafka cluster and send the following test data to the Kafka topics:
                                                                                                                    {"order_id":"202103241000000001", "order_channel":"webShop", "order_time":"2021-03-24 10:00:00", "pay_amount":"100.00", "real_pay":"100.00", "pay_time":"2021-03-24 10:02:03", "user_id":"0001", "user_name":"Alice", "area_id":"330106"} 
 
diff --git a/docs/dli/umn/dli_01_0532.html b/docs/dli/umn/dli_01_0532.html
index b3c7fafda..60bc3f919 100644
--- a/docs/dli/umn/dli_01_0532.html
+++ b/docs/dli/umn/dli_01_0532.html
@@ -3,10 +3,10 @@
 
                                                                                                                    Viewing Scaling History
                                                                                                                    
 
                                                                                                                    Scenario
                                                                                                                    If you added a queue to or deleted one from an elastic resource pool, or you scaled an added queue, the CU quantity of the elastic resource pool may be changed. You can view historical CU changes of an elastic resource pool on the console.
                                                                                                                    
 
                                                                                                                    
-
                                                                                                                    Prerequisites
                                                                                                                    Currently, you can only view the historical records generated within the last 30 days on the console.
                                                                                                                    
+
                                                                                                                    Notes and Constraints
                                                                                                                    Currently, you can only view the historical records generated within the last 30 days on the console.
                                                                                                                    
 
                                                                                                                    
 
                                                                                                                    Viewing Scaling History of an Elastic Resource Pool
                                                                                                                    1. In the navigation pane on the left, choose Resources > Resource Pool.
                                                                                                                    2. Select the desired elastic resource pool and choose More > Expansion History in the Operation column.
                                                                                                                    3. On the displayed page, select a duration to view the CU usage.
                                                                                                                      You can view the number of CUs before and after a scaling, and the target number of CUs.
                                                                                                                      
-
                                                                                                                      The historical records can be displayed in charts or tables. Click  in the upper right corner to switch the display.
                                                                                                                      
+
                                                                                                                      The historical records can be displayed in charts or tables. Click  in the upper right corner to switch the display.
                                                                                                                      
 
                                                                                                                    
 
                                                                                                                    
 
                                                                                                                    
@@ -16,3 +16,10 @@
 
                                                                                                                    
 
                                                                                                                  
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_01_0535.html b/docs/dli/umn/dli_01_0535.html
index 27305fabc..7abcdb8db 100644
--- a/docs/dli/umn/dli_01_0535.html
+++ b/docs/dli/umn/dli_01_0535.html
@@ -4,7 +4,7 @@
 
                                                                                                                  Scenario
                                                                                                                  In actual job running, it is necessary to prioritize and ensure the normal running of important and urgent tasks due to their varying levels of importance and urgency. This requires providing the necessary compute resources for their normal operations.
                                                                                                                  
 
                                                                                                                  DLI offers a feature to set job priorities for each SQL job, which prioritizes the allocation of compute resources to higher priority jobs when resources are limited.
                                                                                                                  
 
                                                                                                                  
-
                                                                                                                  Notes
                                                                                                                  • You can assign a priority level of 1 to 10 for each job, with a larger value indicating a higher priority. Compute resources are preferentially allocated to high-priority jobs. That is, if compute resources required for high-priority jobs are insufficient, compute resources for low-priority jobs are reduced.
                                                                                                                  • Jobs running on a SQL queue have a default priority level of 3.
                                                                                                                  • To change the priority for a job, you must first stop the job, change the priority level, and then submit the job for the modification to take effect.
                                                                                                                  
+
                                                                                                                  Notes
                                                                                                                  • Priorities cannot be set for jobs running in queues within an elastic resource pool of the basic edition.
                                                                                                                  • You can assign a priority level of 1 to 10 for each job, with a larger value indicating a higher priority. Compute resources are preferentially allocated to high-priority jobs. That is, if compute resources required for high-priority jobs are insufficient, compute resources for low-priority jobs are reduced.
                                                                                                                  • Jobs running on a SQL queue have a default priority level of 3.
                                                                                                                  • To change the priority for a job, you must first stop the job, change the priority level, and then submit the job for the modification to take effect.
                                                                                                                  
 
                                                                                                                  
 
                                                                                                                  Setting the Priority for a SQL Job
                                                                                                                  Click Settings. In the Parameter Settings area, configure the following parameter. x indicates the priority value.
                                                                                                                  spark.sql.dli.job.priority=x
                                                                                                                  
 
                                                                                                                  
@@ -13,7 +13,7 @@
 
                                                                                                                  
 
 
diff --git a/docs/dli/umn/dli_01_0536.html b/docs/dli/umn/dli_01_0536.html
index 51f93ec3a..9610794c6 100644
--- a/docs/dli/umn/dli_01_0536.html
+++ b/docs/dli/umn/dli_01_0536.html
@@ -3,12 +3,17 @@
 
                                                                                                                  Configuring a DLI Job Bucket
                                                                                                                  
 
                                                                                                                  Before using DLI, you need to configure a DLI job bucket. The bucket is used to store temporary data generated during DLI job running, such as job logs and results.
                                                                                                                  
 
                                                                                                                  Configure a DLI job bucket on the Global Configuration > Project page of the DLI management console.
                                                                                                                  
+
                                                                                                                   
                                                                                                                  If you have enabled the function to save job results to a DLI job bucket for your SQL queue, make sure to configure the DLI job bucket before submitting SQL jobs. Failure to do so may result in SQL jobs not being submitted successfully. For details, refer to How Do I Check if Job Result Saving to a DLI Job Bucket Is Enabled for a SQL Queue?
                                                                                                                  
+
                                                                                                                  
 
                                                                                                                  Preparations
                                                                                                                  Before the configuration, create an OBS bucket or parallel file system (PFS).
                                                                                                                  
 
                                                                                                                  In big data scenarios, you are advised to create a PFS. PFS is a high-performance file system provided by OBS, with access latency in milliseconds. PFS can achieve a bandwidth performance of up to TB/s and millions of IOPS, which makes it ideal for processing high-performance computing (HPC) workloads.
                                                                                                                  
 
                                                                                                                  
-
                                                                                                                  Notes
                                                                                                                  • Do not use the OBS bucket for other purposes.
                                                                                                                  • The OBS bucket must be set and modified by the main account. Member users do not have the permission.
                                                                                                                  • If the bucket is not configured, you will not be able to view job logs.
                                                                                                                  • You can create lifecycle rules to automatically delete objects or change storage classes for objects that meet specified conditions.
                                                                                                                  • Inappropriate modifications of the job bucket may lead to loss of historical data.
                                                                                                                  
+
                                                                                                                  Notes
                                                                                                                  • Do not use the OBS bucket for other purposes.
                                                                                                                  • The OBS bucket must be set and modified by the main account. Member users do not have the permission.
                                                                                                                  • If the bucket is not configured, you will not be able to view job results and logs.
                                                                                                                  • You can create lifecycle rules to automatically delete objects or change storage classes for objects that meet specified conditions.
                                                                                                                  • Inappropriate modifications of the job bucket may lead to loss of historical data.
                                                                                                                  • If your SQL queue has been configured to save job results to a DLI job bucket, the system will write the results directly to the specified OBS bucket when executing a SQL job. Ensure the following preparations are completed before submitting the job:
                                                                                                                    • Configure DLI job bucket information before submitting a SQL job. Otherwise, the SQL job may fail to be submitted.
                                                                                                                    • Ensure that the user executing the SQL job has read and write permissions for the DLI job bucket. Otherwise, the job results cannot be properly saved or retrieved.
                                                                                                                      When executing a job, the system accesses the job bucket using the identity credentials of the user who submitted the job. If permissions are insufficient, it results in failure to save or retrieve the job results.
                                                                                                                      
+
                                                                                                                    
+
                                                                                                                    For details, refer to How Do I Check if Job Result Saving to a DLI Job Bucket Is Enabled for a SQL Queue?
                                                                                                                    
+
                                                                                                                  
 
                                                                                                                  
-
                                                                                                                  Procedure
                                                                                                                  1. In the navigation pane of the DLI console, choose Global Configuration > Project.
                                                                                                                  2. On the Project page, click  next to Job Bucket to configure bucket information.
                                                                                                                  3. Click  to view available buckets.
                                                                                                                  4. Select the bucket for storing the temporary data of the DLI job and click OK.
                                                                                                                    Temporary data generated during DLI job running will be stored in the OBS bucket.
                                                                                                                    
+
                                                                                                                    Procedure
                                                                                                                    1. In the navigation pane of the DLI console, choose Global Configuration > Project.
                                                                                                                    2. On the Project page, click  next to Job Bucket to configure bucket information.
                                                                                                                    3. Click  to view available buckets.
                                                                                                                    4. Select the bucket for storing the temporary data of the DLI job and click OK.
                                                                                                                      Temporary data generated during DLI job running will be stored in the OBS bucket.
                                                                                                                      
 
                                                                                                                    
 
                                                                                                                    
 
                                                                                                                  
@@ -18,3 +23,10 @@
 
                                                                                                                  
 
                                                                                                                  
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_01_0538.html b/docs/dli/umn/dli_01_0538.html
index 7f178e144..d56cc0fac 100644
--- a/docs/dli/umn/dli_01_0538.html
+++ b/docs/dli/umn/dli_01_0538.html
@@ -12,16 +12,18 @@
 
                                                                                                                  5. 
 
                                                                                                                5. Advantages
                                                                                                                  
 
                                                                                                                  6. 
-
                                                                                                                6. Application Scenarios
                                                                                                                  
+
                                                                                                                7. Use Cases
                                                                                                                  
 
                                                                                                                  8. 
 
                                                                                                                8. Notes and Constraints
                                                                                                                  
 
                                                                                                                  9. 
-
                                                                                                                9. Specifications
                                                                                                                  
+
                                                                                                                10. Compute Resource Types and Specifications
                                                                                                                  
 
                                                                                                                  11. 
-
                                                                                                                11. Permissions Management
                                                                                                                  
+
                                                                                                                12. Permission Management
                                                                                                                  
 
                                                                                                                  13. 
 
                                                                                                                13. Quotas
                                                                                                                  
 
                                                                                                                  14. 
+
                                                                                                                14. Related Services
                                                                                                                  
+
                                                                                                                  15. 
 
                                                                                                                15. Basic Concepts
                                                                                                                  
 
                                                                                                                  16. 
 
diff --git a/docs/dli/umn/dli_01_0550.html b/docs/dli/umn/dli_01_0550.html
index b2db12109..355e7e2fe 100644
--- a/docs/dli/umn/dli_01_0550.html
+++ b/docs/dli/umn/dli_01_0550.html
@@ -11,7 +11,7 @@
 
                                                                                                                  How Do I Apply for a Higher Quota?
                                                                                                                  The system does not support online quota adjustment. To increase a resource quota, dial the hotline or send an email to the customer service. We will process your application and inform you of the progress by phone call or email.
                                                                                                                  
 
                                                                                                                  Before dialing the hotline number or sending an email, ensure that the following information has been obtained:
                                                                                                                  
 
                                                                                                                  • Domain name, project name, and project ID
                                                                                                                    To obtain the preceding information, log in to the management console, click the username in the upper right corner, and choose My Credentials from the drop-down list.
                                                                                                                    
-
                                                                                                                  • Quota information, including:
                                                                                                                    • ServiceName
                                                                                                                    • Quota type
                                                                                                                    • Required quota
                                                                                                                    
+
                                                                                                                  • Quota information, including:
                                                                                                                    • Service name
                                                                                                                    • Quota type
                                                                                                                    • Required quota
                                                                                                                    
 
                                                                                                                  
 
                                                                                                                  Learn how to obtain the service hotline and email address.
                                                                                                                  
 
                                                                                                                  
diff --git a/docs/dli/umn/dli_01_0551.html b/docs/dli/umn/dli_01_0551.html
index 8ef448aaa..95e598119 100644
--- a/docs/dli/umn/dli_01_0551.html
+++ b/docs/dli/umn/dli_01_0551.html
@@ -10,7 +10,7 @@
 
                                                                                                                
 
 
diff --git a/docs/dli/umn/dli_01_0552.html b/docs/dli/umn/dli_01_0552.html
index 3322ce424..9b3b33211 100644
--- a/docs/dli/umn/dli_01_0552.html
+++ b/docs/dli/umn/dli_01_0552.html
@@ -1,14 +1,13 @@
 
 
-
                                                                                                                Managing Tags
                                                                                                                
-
                                                                                                                Tag Management
                                                                                                                A tag is a key-value pair that you can customize to identify cloud resources. It helps you to classify and search for cloud resources. A tag consists of a tag key and a tag value. If you use tags in other cloud services, you are advised to create the same tag (key-value pairs) for cloud resources used by the same business to keep consistency.
                                                                                                                
-
                                                                                                                DLI supports the following two types of tags:
                                                                                                                
-
                                                                                                                • Resource tags: non-global tags created on DLI
                                                                                                                
-
                                                                                                                • Predefined tags: global tags created on Tag Management Service (TMS).
                                                                                                                  
+
                                                                                                                  Managing Tags for Database Tables
                                                                                                                  
+
                                                                                                                  Tag Management
                                                                                                                  A tag is a user-defined key-value pair used to identify cloud resources, helping you classify and search for them. A tag consists of a tag key and a tag value. If you use tags in other cloud services, you are advised to create the same tag (key-value pairs) for cloud resources used by the same business to keep consistency.
                                                                                                                  
+
                                                                                                                  DLI supports the following two types of tags:
                                                                                                                  • Resource tags: indicate non-global tags created on DLI.
                                                                                                                  • Predefined tags: global tags created on Tag Management Service (TMS).
                                                                                                                    For details about predefined tags, see Tag Management Service User Guide.
                                                                                                                    
 
                                                                                                                  
+
                                                                                                                  
 
                                                                                                                  This section describes how to add, modify, and delete tags for databases and tables.
                                                                                                                  
 
                                                                                                                  
-
                                                                                                                  Database Tags
                                                                                                                  1. In the navigation pane on the left, choose Data Management > Databases and Tables.
                                                                                                                  2. Locate the row that contains the target database, and click More > Tags in the Operation column.
                                                                                                                  3. The tag management page is displayed, and the tags (if there are) are displayed.
                                                                                                                  4. On the displayed page, click Add/Edit Tag. The Add/Edit Tag dialog box is displayed.
                                                                                                                    Enter a tag key and a tag value in the text boxes and click Add.
+
                                                                                                                    Database Tags
                                                                                                                    1. In the navigation pane on the left, choose Data Management > Databases and Tables.
                                                                                                                    2. Locate the row that contains the target database, and click More > Tags in the Operation column.
                                                                                                                    3. The tag management page is displayed, and tags (if any) are also displayed.
                                                                                                                    4. On the displayed page, click Add/Edit Tag. The Add/Edit Tag dialog box is displayed.
                                                                                                                      Enter a tag key and a tag value in the text boxes and click Add.
 
                                                                                                                      
@@ -43,7 +42,7 @@
 
                                                                                                                    5. Click OK. The database tag is added.
                                                                                                                      To delete a tag, click Delete in the Operation column of the target tag.
                                                                                                                      
 
                                                                                                                      6. 
-
                                                                                                                      Table Tags
                                                                                                                      1. In the navigation pane on the left, choose Data Management > Databases and Tables.
                                                                                                                      2. Click a database name to view the tables in the database.
                                                                                                                      3. Locate the row that contains the target table and click More > Tag in the Operation column.
                                                                                                                      4. The tag management page is displayed, and the tags (if there are) are displayed.
                                                                                                                      5. On the displayed page, click Add/Edit Tag. The Add/Edit Tag dialog box is displayed.
                                                                                                                        Enter a tag key and a tag value in the text boxes and click Add
+
                                                                                                                        Table Tags
                                                                                                                        1. In the navigation pane on the left, choose Data Management > Databases and Tables.
                                                                                                                        2. Click a database name to view the tables in the database.
                                                                                                                        3. Locate the row that contains the target table and click More > Tag in the Operation column.
                                                                                                                        4. The tag management page is displayed, and tags (if any) are also displayed.
                                                                                                                        5. On the displayed page, click Add/Edit Tag. The Add/Edit Tag dialog box is displayed.
                                                                                                                          Enter a tag key and a tag value in the text boxes and click Add
 
                                                                                                                      Table 1 Tag parameters
                                                                                                                      Parameter
                                                                                                                      
                                                                                                                       		
 
                                                                                                                      Description
                                                                                                                      
@@ -21,7 +20,7 @@
 
                                                                                                                      • Click the text box for tag key and select a predefined tag key from the drop-down list.
                                                                                                                        To add a predefined tag, you need to create one on TMS and then select it from the Tag key drop-down list. You can click View predefined tags to go to the Predefined Tags page of the TMS console. Then, click Create Tag in the upper corner of the page to create a predefined tag.
                                                                                                                        
 
                                                                                                                        
 
                                                                                                                      
-
                                                                                                                      • Enter a tag key in the text box.
                                                                                                                         NOTE: 
                                                                                                                        A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                                                        
+
                                                                                                                        • Enter a tag key in the text box.
                                                                                                                           NOTE: 
                                                                                                                          A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                                                          
 
                                                                                                                          
 
                                                                                                                        
 
@@ -29,7 +28,7 @@
 
                                                                                                                      Tag value
                                                                                                                      
                                                                                                                       		
 
                                                                                                                      You can specify the tag value in either of the following ways:
                                                                                                                      
-
                                                                                                                      • Click the tag value text box and select a predefined tag value from the drop-down list.
                                                                                                                      • Enter a tag value in the text box.
                                                                                                                         NOTE: 
                                                                                                                        A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.
                                                                                                                        
+
                                                                                                                        • Click the tag value text box and select a predefined tag value from the drop-down list.
                                                                                                                        • Enter a tag value in the text box.
                                                                                                                           NOTE: 
                                                                                                                          A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.
                                                                                                                          
 
                                                                                                                          
 
                                                                                                                        
 
                                                                                                                      		
 
                                                                                                                      
@@ -64,7 +63,7 @@
 
diff --git a/docs/dli/umn/dli_01_0553.html b/docs/dli/umn/dli_01_0553.html
index 243bb5349..18e01e29a 100644
--- a/docs/dli/umn/dli_01_0553.html
+++ b/docs/dli/umn/dli_01_0553.html
@@ -3,7 +3,7 @@
 
                                                                                                                      Deleting an Enhanced Datasource Connection
                                                                                                                      Scenario
                                                                                                                      Delete an enhanced datasource connection that is no longer used on the console.
                                                                                                                      
 
                                                                                                                      
-
                                                                                                                      Procedure
                                                                                                                      1. Log in to the DLI management console.
                                                                                                                      2. In the left navigation pane, choose Datasource Connections.
                                                                                                                      3. On the Enhanced tab page displayed, locate the enhanced datasource connection to be deleted and click Delete in the Operation column.
                                                                                                                      4. In the dialog box displayed, click Yes.
                                                                                                                      
+
                                                                                                                      Procedure
                                                                                                                      1. Log in to the DLI management console.
                                                                                                                      2. In the navigation pane on the left, choose Datasource Connections.
                                                                                                                      3. On the Enhanced tab page displayed, locate the enhanced datasource connection to be deleted and click Delete in the Operation column.
                                                                                                                      4. In the dialog box displayed, click Yes.
                                                                                                                      
 
                                                                                                                      
 
                                                                                                                      
 
                                                                                                                      
diff --git a/docs/dli/umn/dli_01_0555.html b/docs/dli/umn/dli_01_0555.html
new file mode 100644
index 000000000..9647f129c
--- /dev/null
+++ b/docs/dli/umn/dli_01_0555.html
@@ -0,0 +1,19 @@
+
+
+
                                                                                                                      Unbinding an Enhanced Datasource Connection from an Elastic Resource Pool
                                                                                                                      
+
                                                                                                                      Scenario
                                                                                                                      Unbind an enhanced datasource connection from an elastic resource pool that does not need to access a data source through an enhanced datasoruce connection.
                                                                                                                      
+
                                                                                                                      
+
                                                                                                                      Notes and Constraints
                                                                                                                      If the status of the VPC peering connection created for binding an enhanced datasource connection to an elastic resource pool is Failed, the elastic resource pool cannot be unbound.
                                                                                                                      
+
                                                                                                                      
+
                                                                                                                      Procedure
                                                                                                                      1. Log in to the DLI management console.
                                                                                                                      2. In the navigation pane on the left, choose Datasource Connections.
                                                                                                                      3. On the Enhanced tab page displayed, use either of the following methods to unbind an enhanced datasource connection from an elastic resource pool:
                                                                                                                        • Method 1:
                                                                                                                          1. Locate your desired enhanced datasource connection, click More in the Operation column, and select Unbind Resource Pool.
                                                                                                                          2. In the Unbind Resource Pool dialog box, select the resource pool to be unbound for Resource Pool.
                                                                                                                          3. Click OK.
                                                                                                                          
+
                                                                                                                        • Method 2:
                                                                                                                          1. Click your desired enhanced datasource connection in the list.
                                                                                                                          2. Locate your desired resource pool and click Unbind Resource Pool in the Operation column.
                                                                                                                          3. Click OK.
                                                                                                                          
+
                                                                                                                        
+
                                                                                                                      
+
                                                                                                                      
+
                                                                                                                      
+
+
diff --git a/docs/dli/umn/dli_01_0556.html b/docs/dli/umn/dli_01_0556.html
index 22158a6fd..a55bf126c 100644
--- a/docs/dli/umn/dli_01_0556.html
+++ b/docs/dli/umn/dli_01_0556.html
@@ -3,9 +3,9 @@
 
                                                                                                                      Deleting the Route for an Enhanced Datasource Connection
                                                                                                                      
 
                                                                                                                      Scenario
                                                                                                                      Delete a route that is no longer used.
                                                                                                                      
 
                                                                                                                      
-
                                                                                                                      Constraints
                                                                                                                      A custom route table cannot be deleted if it is associated with a subnet.
                                                                                                                      
+
                                                                                                                      Notes and Constraints
                                                                                                                      A custom route table cannot be deleted if it is associated with a subnet.
                                                                                                                      
 
                                                                                                                      
-
                                                                                                                      Procedure
                                                                                                                      1. Log in to the DLI management console.
                                                                                                                      2. In the left navigation pane, choose Datasource Connections.
                                                                                                                      3. On the Enhanced tab page displayed, locate the row containing the enhanced connection from which the route needs to be deleted, and delete the route.
                                                                                                                        • Method 1:
                                                                                                                          1. On the Enhanced tab page displayed, locate the enhanced connection from which the route needs to be deleted and click Manage Route in the Operation column.
                                                                                                                          2. Locate the route to be deleted and click Delete in the Operation column.
                                                                                                                          3. In the dialog box displayed, click OK.
                                                                                                                          
+
                                                                                                                          Procedure
                                                                                                                          1. Log in to the DLI management console.
                                                                                                                          2. In the navigation pane on the left, choose Datasource Connections.
                                                                                                                          3. On the displayed Enhanced tab, locate the enhanced datasource connection where you want to delete a route and then delete a route.
                                                                                                                            • Method 1:
                                                                                                                              1. On the Enhanced tab, locate the enhanced datasource connection where you want to delete a route and click Manage Route in its Operation column.
                                                                                                                              2. Locate the route to be deleted and click Delete in the Operation column.
                                                                                                                              3. In the dialog box displayed, click OK.
                                                                                                                              
 
                                                                                                                            • Method 2:
                                                                                                                              1. On the Enhanced tab page displayed, locate the enhanced connection from which the route needs to be deleted, click More in the Operation column, and select Delete Route.
                                                                                                                              2. In the Delete Route dialog box displayed, confirm the route information.
                                                                                                                              3. Click Yes.
                                                                                                                              
 
                                                                                                                            
 
                                                                                                                          
diff --git a/docs/dli/umn/dli_01_0558.html b/docs/dli/umn/dli_01_0558.html
index b2b82a612..d09d0a961 100644
--- a/docs/dli/umn/dli_01_0558.html
+++ b/docs/dli/umn/dli_01_0558.html
@@ -9,7 +9,7 @@
 
                                                                                                                        • Upload the authentication credential to the OBS bucket.
                                                                                                                          
 
                                                                                                                        • Create a datasource authentication.
                                                                                                                          1. Log in to the DLI management console.
                                                                                                                          2. Choose Datasource Connections. On the page displayed, click Datasource Authentication.
                                                                                                                          3. Click Create.
                                                                                                                            Configure Kerberos authentication parameters according to Table 1.
                                                                                                                            
 
-
                                                                                                                      Table 2 Tag parameters
                                                                                                                      Parameter
                                                                                                                      
                                                                                                                       		
 
                                                                                                                      Description
                                                                                                                      
@@ -53,10 +52,10 @@
 
                                                                                                                      Tag key
                                                                                                                      
                                                                                                                       		
 
                                                                                                                      You can specify the tag key in either of the following ways:
                                                                                                                      
-
                                                                                                                      • Click the text box for tag key and select a predefined tag key from the drop-down list.
                                                                                                                        To add a predefined tag, you need to create one on TMS and then select it from the Tag key drop-down list. You can click View predefined tags to go to the Predefined Tags page of the TMS console. Then, click Create Tag in the upper corner of the page to create a predefined tag.
                                                                                                                        
+
                                                                                                                        • Click the text box for tag key and select a predefined tag key from the drop-down list.
                                                                                                                          To add a predefined tag, you need to create one on TMS and then select it from the Tag key drop-down list. You can click View predefined tags to go to the Predefined Tags page of the TMS console. Then, click Create Tag in the upper corner of the page to create a predefined tag.
                                                                                                                          
 
                                                                                                                          
 
                                                                                                                        
-
                                                                                                                        • Enter a tag key in the text box.
                                                                                                                           NOTE: 
                                                                                                                          A tag key can contain a maximum of 128 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                                                          
+
                                                                                                                          • Enter a tag key in the text box.
                                                                                                                             NOTE: 
                                                                                                                            A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_.
                                                                                                                            
 
                                                                                                                            
 
                                                                                                                          
 
                                                                                                                      Tag value
                                                                                                                      
                                                                                                                       		
 
                                                                                                                      You can specify the tag value in either of the following ways:
                                                                                                                      
-
                                                                                                                      • Click the tag value text box and select a predefined tag value from the drop-down list.
                                                                                                                      • Enter a tag value in the text box.
                                                                                                                         NOTE: 
                                                                                                                        A tag value can contain a maximum of 255 characters. Only letters, numbers, spaces, and special characters (_.:+-@) are allowed.
                                                                                                                        
+
                                                                                                                        • Click the tag value text box and select a predefined tag value from the drop-down list.
                                                                                                                        • Enter a tag value in the text box.
                                                                                                                           NOTE: 
                                                                                                                          A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed.
                                                                                                                          
 
                                                                                                                          
 
                                                                                                                        
 
                                                                                                                      		
 
                                                                                                                      Table 1 Parameters
                                                                                                                      Parameter
                                                                                                                      
+
                                                                                                                      
@@ -23,7 +23,7 @@
 
                                                                                                                      Table 1 Parameter descriptions
                                                                                                                      Parameter
                                                                                                                      
                                                                                                                       		
 
                                                                                                                      Description
                                                                                                                      
 
                                                                                                                      Authentication Certificate
                                                                                                                      
                                                                                                                       		
 
                                                                                                                      Name of the datasource authentication to be created.
                                                                                                                      
-
                                                                                                                      • The name can contain only digits, letters, and underscores (_), but cannot contain only digits or start with an underscore (_).
                                                                                                                      • The name can contain a maximum of 128 characters.
                                                                                                                      • It is recommended that the name contain the MRS security cluster name to distinguish security authentication information of different clusters.
                                                                                                                      
+
                                                                                                                      • The name can contain only digits, letters, and underscores (_), but cannot contain only digits or start with an underscore (_).
                                                                                                                      • The value can contain a maximum of 128 characters.
                                                                                                                      • It is recommended that the name contain the MRS security cluster name to distinguish security authentication information of different clusters.
                                                                                                                      
                                                                                                                       		
 
                                                                                                                      
 
                                                                                                                      Username
                                                                                                                      
diff --git a/docs/dli/umn/dli_01_0559.html b/docs/dli/umn/dli_01_0559.html
index b3c584be8..b86b6a072 100644
--- a/docs/dli/umn/dli_01_0559.html
+++ b/docs/dli/umn/dli_01_0559.html
@@ -5,7 +5,7 @@
 
 
                                                                                                                      Procedure
                                                                                                                      1. Create a datasource authentication.
                                                                                                                        1. Log in to the DLI management console.
                                                                                                                        2. Choose Datasource Connections. On the page displayed, click Datasource Authentication.
                                                                                                                        3. Click Create.
                                                                                                                          Configure authentication parameters according to Table 1.
                                                                                                                          
 
-
                                                                                                                          Table 1 Parameters
                                                                                                                          Parameter
                                                                                                                          
+
                                                                                                                          
diff --git a/docs/dli/umn/dli_01_0560.html b/docs/dli/umn/dli_01_0560.html
index 8c3ac841d..2a1cfdd44 100644
--- a/docs/dli/umn/dli_01_0560.html
+++ b/docs/dli/umn/dli_01_0560.html
@@ -7,12 +7,12 @@
 
                                                                                                                          Procedure
                                                                                                                          1. Download the authentication credential.
                                                                                                                            • DMS Kafka
                                                                                                                              1. Log in to the DMS (for Kafka) console and click a Kafka instance to access its details page.
                                                                                                                              2. In the connection information, find the SSL certificate and click Download.
                                                                                                                                Decompress the downloaded kafka-certs package to obtain the client.jks and phy_ca.crt files.
                                                                                                                                
 
                                                                                                                              
-
                                                                                                                            • MRS Kafka
                                                                                                                              1. Log in to MRS Manager.
                                                                                                                              2. Choose System > Permission > User.
                                                                                                                              3. Click More, select Download Authentication Credential, save the file, and decompress it to obtain the truststore file.
                                                                                                                              
+
                                                                                                                            • MRS Kafka
                                                                                                                              1. Log in to MRS Manager.
                                                                                                                              2. Choose System > Permission > User.
                                                                                                                              3. Click More, select Download Authentication Credential, save the file, and decompress it to obtain the truststore file.
                                                                                                                              
 
                                                                                                                            
 
                                                                                                                          2. Upload the authentication credential to the OBS bucket.
                                                                                                                            
 
                                                                                                                          3. Create a datasource authentication.
                                                                                                                            1. Log in to the DLI management console.
                                                                                                                            2. Choose Datasource Connections. On the page displayed, click Datasource Authentication.
                                                                                                                            3. Click Create.
                                                                                                                              Configure Kafka authentication parameters according to Table 1.
                                                                                                                              
 
-
                                                                                                                          Table 1 Parameter descriptions
                                                                                                                          Parameter
                                                                                                                          
                                                                                                                           		
 
                                                                                                                          Description
                                                                                                                          
                                                                                                                           		
 
                                                                                                                          Table 1 Parameters
                                                                                                                          Parameter
                                                                                                                          
+
                                                                                                                          
@@ -26,7 +26,7 @@
 
-
                                                                                                                          Table 1 Parameter descriptions
                                                                                                                          Parameter
                                                                                                                          
                                                                                                                           		
 
                                                                                                                          Description
                                                                                                                          
 
                                                                                                                          Authentication Certificate
                                                                                                                          
                                                                                                                           		
 
                                                                                                                          Name of the datasource authentication to be created. 
                                                                                                                          
-
                                                                                                                          • The name can contain only digits, letters, and underscores (_), but cannot contain only digits or start with an underscore (_).
                                                                                                                          • The name can contain a maximum of 128 characters.
                                                                                                                          
+
                                                                                                                          • The name can contain only digits, letters, and underscores (_), but cannot contain only digits or start with an underscore (_).
                                                                                                                          • The value can contain a maximum of 128 characters.
                                                                                                                          
                                                                                                                           		
 
                                                                                                                          
 
                                                                                                                          Truststore Path
                                                                                                                          
diff --git a/docs/dli/umn/dli_01_0561.html b/docs/dli/umn/dli_01_0561.html
index 68d69fcba..51650bae3 100644
--- a/docs/dli/umn/dli_01_0561.html
+++ b/docs/dli/umn/dli_01_0561.html
@@ -1,8 +1,8 @@
 
 
 
                                                                                                                          Overview
                                                                                                                          
-
                                                                                                                          What Is Datasource Authentication?
                                                                                                                          When analyzing across multiple sources, you are advised not to configure authentication information directly in a job as it can lead to password leakage. Instead, you are advised to use either Data Encryption Workshop (DEW) or datasource authentication provided by DLI to securely store data source authentication information.
                                                                                                                          
-
                                                                                                                          • DEW is a comprehensive cloud-based encryption service that addresses data security, key security, and complex key management issues. You are advised to use DEW to store authentication information for data sources.
                                                                                                                            You are advised to use DEW to store authentication information of data sources when Spark 3.3.1 or later and Flink 1.15 or later jobs access data sources using datasource connections. This will help you address issues related to data security, key security, and complex key management. For details, see Using DEW to Manage Access Credentials for Data Sources.
                                                                                                                            
+
                                                                                                                            What Is Datasource Authentication?
                                                                                                                            When analyzing across multiple sources, you are advised not to configure authentication information directly in a job as it can lead to password leakage. Instead, you are advised to use either DEW or datasource authentication provided by DLI to securely store data source authentication information.
                                                                                                                            
+
                                                                                                                            • DEW is a comprehensive cloud-based encryption service designed to address challenges related to data security, key security, and the complexities of key management. You are advised to use DEW to store authentication information for data sources.
                                                                                                                              You are advised to use DEW to store authentication information of data sources when Spark 3.3.1 or later and Flink 1.15 or later jobs access data sources using datasource connections. This will help you address issues related to data security, key security, and complex key management. For details, see Managing Data Source Access Credentials Using DEW.
                                                                                                                              
 
                                                                                                                            • Datasource authentication is used to manage authentication information for accessing specified data sources. After datasource authentication is configured, you do not need to repeatedly configure data source authentication information in jobs, improving data source authentication security while enabling DLI to securely access data sources.
                                                                                                                              When SQL and Flink 1.12 jobs access data sources using datasource connections, use DLI's datasource authentication feature to manage data source access credentials.
                                                                                                                              
 
                                                                                                                            
 
                                                                                                                            This section describes how to use datasource authentication provided by DLI.
                                                                                                                            
@@ -47,8 +47,8 @@
 
                                                                                                                          		
 
                                                                                                                          CSS
                                                                                                                          
 
                                                                                                                          The CSS cluster version must be 6.5.4 or later.
                                                                                                                          
-
                                                                                                                          The security mode has been enabled for the CSS cluster.
                                                                                                                          
+
                                                                                                                          The cluster version is 6.5.4 or later.
                                                                                                                          
+
                                                                                                                          The security mode has been enabled for the cluster.
                                                                                                                          
                                                                                                                           		
 
                                                                                                                          
 
                                                                                                                          Password
                                                                                                                          
diff --git a/docs/dli/umn/dli_01_0563.html b/docs/dli/umn/dli_01_0563.html
index b3876d59a..95d876813 100644
--- a/docs/dli/umn/dli_01_0563.html
+++ b/docs/dli/umn/dli_01_0563.html
@@ -2,39 +2,123 @@
 
 
                                                                                                                          Setting Queue Properties
                                                                                                                          
 
                                                                                                                          Scenario
                                                                                                                          DLI allows you to set properties for queues.
                                                                                                                          
-
                                                                                                                          You can set Spark driver parameters to improve the scheduling efficiency of queues.
                                                                                                                          
+
                                                                                                                          You can currently set the following property parameters:
                                                                                                                          
+
                                                                                                                          • Spark driver parameters: Set them to improve the scheduling efficiency of queues.
                                                                                                                          • Set Result Saving Policy: Set it to determine whether to save job results for queues to a DLI job bucket.
                                                                                                                          • Enable Spark Native operator optimization: Enable the Spark Native engine feature to improve Spark SQL job performance and reduce CPU and memory consumption.
                                                                                                                          
 
                                                                                                                          This section describes how to set queue properties on the management console.
                                                                                                                          
 
                                                                                                                          
-
                                                                                                                          Notes and Constraints
                                                                                                                          • Only SQL queues of the Spark engine support configuring queue properties.
                                                                                                                          • Setting queue properties is only supported after the queue has been created.
                                                                                                                          • Currently, only queue properties related to the Spark driver can be set.
                                                                                                                          • Queue properties cannot be set in batches.
                                                                                                                          • For a queue in an elastic resource pool, if the minimum CUs of the queue is less than 16 CUs, both Max. Spark Driver Instances and Max. Prestart Spark Driver Instances set in the queue properties do not apply.
                                                                                                                          
-
                                                                                                                          
-
                                                                                                                          Procedure
                                                                                                                          1. In the navigation pane of the DLI management console, choose Resources > Queue Management.
                                                                                                                          2. Locate the queue for which you want to set properties, click More in the Operation column, and select Set Property.
                                                                                                                          3. Go to the queue property setting page and set property parameters. Table 1 describes the property parameters.
-
                                                                                                                            Table 1 Queue properties
                                                                                                                            Property
                                                                                                                            
+
                                                                                                                            Notes and Constraints
                                                                                                                            • Queue properties can only be set for SQL queues of the Spark engine in an elastic resource pool of the standard edition.
                                                                                                                            • You cannot set queue properties in batches.
                                                                                                                            • The constraints on different queue properties vary. For details, see Table 1.
+
                                                                                                                              
-
-
+
-
-
-
+
-
-
-
+
-
-
-
+
+
+
+
                                                                                                                              Table 1 Constraints on queue properties
                                                                                                                              Property
                                                                                                                              
 
                                                                                                                              Description
                                                                                                                              
+
                                                                                                                              Phase Where You Can Set This Property
                                                                                                                              
 
                                                                                                                              Value Range
                                                                                                                              
+
                                                                                                                              Constraint
                                                                                                                              
+
                                                                                                                              Helpful Link
                                                                                                                              
                                                                                                                               		
 
                                                                                                                              
 
                                                                                                                              Max. Spark Driver Instances
                                                                                                                              
+
                                                                                                                              Spark driver parameters of a queue
                                                                                                                              
 
                                                                                                                              Maximum number of Spark drivers can be started on this queue, including the Spark driver that is prestarted and the Spark driver that runs jobs.
                                                                                                                              
+
                                                                                                                              You can set this property only after a queue is created.
                                                                                                                              
 
                                                                                                                              • For a 16-CU queue, the value is 2.
                                                                                                                              • For a queue that has more than 16 CUs, the value range is [2, queue CUs/16].
                                                                                                                              • If the minimum CUs of the queue is less than 16 CUs, this configuration item does not apply.
                                                                                                                              
+
                                                                                                                              For a queue in an elastic resource pool, if the minimum number of CUs of the queue is fewer than 16 CUs, both Max. Spark Driver Instances and Max. Prestart Spark Driver Instances set in the queue properties do not apply.
                                                                                                                              
+
                                                                                                                              Procedure
                                                                                                                              
                                                                                                                               		
 
                                                                                                                              Max. Prestart Spark Driver Instances
                                                                                                                              
+
                                                                                                                              Job result saving policy
                                                                                                                              
 
                                                                                                                              Maximum number of Spark drivers can be prestarted on this queue. When the number of Spark drivers that run jobs exceeds the value of Max. Concurrency per Instance, the jobs are allocated to the Spark drivers that are prestarted.
                                                                                                                              
+
                                                                                                                              You can set this property only after a queue is created.
                                                                                                                              
 
                                                                                                                              • For a 16-CU queue, the value range is 0 to 1.
                                                                                                                              • For a queue that has more than 16 CUs, the value range is [2, queue CUs/16].
                                                                                                                              • If the minimum CUs of the queue is less than 16 CUs, this configuration item does not apply.
                                                                                                                              
+
                                                                                                                              After the Set Result Saving Policy is enabled, that is, job results are saved to a DLI job bucket, you must configure the DLI job bucket before submitting SQL jobs. Failure to do so may result in SQL jobs not being submitted successfully.
                                                                                                                              
+
                                                                                                                              Procedure
                                                                                                                              
                                                                                                                               		
 
                                                                                                                              Max. Concurrency per Instance
                                                                                                                              
+
                                                                                                                              Enabling Spark Native operator optimization
                                                                                                                              
 
                                                                                                                              Maximum number of jobs can be concurrently executed by a Spark driver. When the number of jobs exceeds the value of this parameter, the jobs are allocated to other Spark drivers.
                                                                                                                              
+
                                                                                                                              • Creating queues within an elastic resource pool
                                                                                                                              • Setting queue properties after queue creation
                                                                                                                              
 
                                                                                                                              1–32
                                                                                                                              
+
                                                                                                                              For created queues, if you change the Spark Native setting (enabled/disabled) through the DLI management console or API, you need to restart the queue for the modification to take effect.
                                                                                                                              
+
                                                                                                                              • To enable the Spark Native engine for a queue in an elastic resource pool, the following conditions must be met simultaneously:
                                                                                                                                • Type of an elastic resource pool: Standard
                                                                                                                                • Type of a queue: For SQL
                                                                                                                                • Spark version: Spark 3.3.1 or later
                                                                                                                                
+
                                                                                                                              • For the default queue, when Spark 3.3.1 or later is used, Spark Native is disabled by default.
                                                                                                                              • To disable Spark Native for a job, configure spark.gluten.enabled=false in the job parameters to disable Spark Native at the job level.
                                                                                                                              
+
                                                                                                                              Enabling Spark Native Operator Optimization
                                                                                                                              
+
                                                                                                                              
+
                                                                                                                              
+
                                                                                                                            
+
                                                                                                                            
+
                                                                                                                            Procedure
                                                                                                                            1. In the navigation pane on the left of the DLI management console, choose Resources > Queue Management.
                                                                                                                            2. Locate the queue for which you want to set properties, click More in the Operation column, and select Set Property.
                                                                                                                            3. Go to the queue property setting page and set property parameters. Table 2 describes the property parameters.
+
                                                                                                                              
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
@@ -42,6 +126,11 @@
 
                                                                                                                            4. Click OK.
                                                                                                                              5. 
+
                                                                                                                              How Do I Check if Job Result Saving to a DLI Job Bucket Is Enabled for a SQL Queue?
                                                                                                                              • Method 1: View the result path on the SQL job details page.
                                                                                                                                1. Log in to the DLI console. In the navigation pane on the left, choose Job Management > SQL Jobs.
                                                                                                                                2. Locate a desired SQL job and click  next to the queue name to expand the job details.
                                                                                                                                3. Check the result path in the job details.
                                                                                                                                  • If the result path displays a custom DLI job bucket, the feature of saving job results to a DLI job bucket is enabled for the queue running the job.
                                                                                                                                  • If the result path is not displayed in the job details, the feature is not enabled for the queue running the job.
                                                                                                                                  
+
                                                                                                                                
+
                                                                                                                              • Method 2: Check whether the feature of saving job results to a job bucket is enabled in the SQL queue properties.
                                                                                                                                1. Log in to the DLI management console. In the navigation pane on the left, choose Resources > Queue Management.
                                                                                                                                2. Locate the queue for which you want to set properties, click More in the Operation column, and select Set Property.
                                                                                                                                3. On the Set Property dialog box that appears, check whether the feature is enabled.
                                                                                                                                
+
                                                                                                                              
+
                                                                                                                              
 
                                                                                                                              
diff --git a/docs/dli/umn/dli_01_0567.html b/docs/dli/umn/dli_01_0567.html
index fb2502bce..45b6ddb10 100644
--- a/docs/dli/umn/dli_01_0567.html
+++ b/docs/dli/umn/dli_01_0567.html
@@ -4,7 +4,7 @@
 
                                                                                                                              
 
                                                                                                                              
 
                                                                                                                                
-
                                                                                                                              • Using a Custom Image to Enhance the Job Running Environment
                                                                                                                                
+
                                                                                                                              • Enhancing the Job Runtime Environment Using a Custom Image
                                                                                                                                
 
                                                                                                                                • 
 
                                                                                                                              • Managing DLI Global Variables
                                                                                                                                
 
                                                                                                                                • 
diff --git a/docs/dli/umn/dli_01_0612.html b/docs/dli/umn/dli_01_0612.html
new file mode 100644
index 000000000..ab80b14a5
--- /dev/null
+++ b/docs/dli/umn/dli_01_0612.html
@@ -0,0 +1,396 @@
+
+
+
                                                                                                                                Creating a SQL Inspection Rule
                                                                                                                                
+
                                                                                                                                What Is SQL Inspection?
                                                                                                                                There are numerous SQL engines in the big data field, which bring diversity to the solutions but also expose some issues such as varying quality of SQL input statements, difficult SQL problem localization, and excessive resource consumption by large SQL statements.
                                                                                                                                
+
                                                                                                                                Poor quality SQL can have unforeseeable impacts on data analysis platforms, affecting system performance or platform stability.
                                                                                                                                
+
                                                                                                                                DLI offers this feature to allow you to create inspection rules for the Spark SQL engine. This helps prevent common issues like large or low-quality SQL statements by providing pre-event information, blocking, and in-event circuit breaker. You do not need to change your SQL submission method or syntax, so it is easy to implement without affecting service operations.
                                                                                                                                
+
                                                                                                                                • You can configure SQL inspection rules in a visualized manner and also have the ability to query and modify these rules.
                                                                                                                                • During query execution and response, each SQL engine proactively inspects SQL statements based on the rules.
                                                                                                                                • Administrators can choose to display hints on, intercept, or block SQL statements. The system logs SQL inspection events in real time for SQL audit. O&M engineers can analyze the logs, assess the quality of SQL statements on the live network, identify potential risks, and take preventive measures.
                                                                                                                                
+
                                                                                                                                This section describes how to create a SQL inspection rule to enhance SQL defense capabilities.
                                                                                                                                
+
                                                                                                                                
+
                                                                                                                                Notes and Constraints of DLI SQL Inspection Rules
                                                                                                                                • SQL inspection is only supported by Spark 3.3.x or later.
                                                                                                                                • Only one inspection rule can be created for an action or a queue.
                                                                                                                                • Each rule can be associated with a maximum of 50 SQL queues.
                                                                                                                                • A maximum of 1,000 rules can be created for each project.
                                                                                                                                • Do not delete the preset system inspection rules of DLI.
                                                                                                                                • You are advised not to delete the default rules created by DLI to prevent queue resources from being used up by large SQL jobs.
                                                                                                                                  Default system rules include Scan files number, Scan partitions number, Shuffle data(GB), Count(distinct) occurrences, and Not in<Subquery>. For details, see Table 2.
                                                                                                                                  
+
                                                                                                                                
+
                                                                                                                                
+
                                                                                                                                Creating a SQL Inspection Rule
                                                                                                                                You can create SQL inspection rules for specified SQL queues on the SQL Inspector page. The system will prompt, block, or perform circuit breaking on SQL requests that trigger the rules.
                                                                                                                                
+
                                                                                                                                 
                                                                                                                                When creating or modifying a SQL inspection rule, evaluate the appropriateness of enabling the rules and setting the threshold based on the service scenario. This will help avoid the negative impact of unreasonable inspection rules blocking or performing circuit breaking on relevant SQL requests on the services.
                                                                                                                                
+
                                                                                                                                
+
                                                                                                                                1. Log in to the DLI management console.
                                                                                                                                2. In the navigation pane on the left, choose Global Configuration > SQL Inspector.
                                                                                                                                3. On the displayed SQL Inspector page, click Create Rule in the upper right corner. In the Create Rule dialog box, set parameters based on the table below.
+
                                                                                                                              Table 2 Queue properties
                                                                                                                              Property Type
                                                                                                                              
+
                                                                                                                              Property
                                                                                                                              
+
                                                                                                                              API Parameter
                                                                                                                              
+
                                                                                                                              Description
                                                                                                                              
+
                                                                                                                              Value Range
                                                                                                                              
+
                                                                                                                              Spark driver type
                                                                                                                              
+
                                                                                                                              Max. Spark Driver Instances
                                                                                                                              
+
                                                                                                                              computeEngine.maxInstance
                                                                                                                              
+
                                                                                                                              Maximum number of Spark drivers can be started on this queue, including the Spark driver that is prestarted and the Spark driver that runs jobs.
                                                                                                                              
+
                                                                                                                              • For a 16-CU queue, the value is 2.
                                                                                                                              • For a queue that has more than 16 CUs, the value range is [2, queue CUs/16].
                                                                                                                              • If the minimum number of CUs of the queue is fewer than 16 CUs, this configuration item does not apply.
                                                                                                                              
+
                                                                                                                              Max. Prestart Spark Driver Instances
                                                                                                                              
+
                                                                                                                              computeEngine.maxPrefetchInstance
                                                                                                                              
+
                                                                                                                              Maximum number of Spark drivers can be prestarted on this queue. When the number of Spark drivers that run jobs exceeds the value of Max. Concurrency per Instance, the jobs are allocated to the Spark drivers that are prestarted.
                                                                                                                              
+
                                                                                                                              • For a 16-CU queue, the value range is 0 to 1.
                                                                                                                              • For a queue that has more than 16 CUs, the value range is [2, queue CUs/16].
                                                                                                                              • If the minimum number of CUs of the queue is fewer than 16 CUs, this configuration item does not apply.
                                                                                                                              
+
                                                                                                                              Max. Concurrency per Instance
                                                                                                                              
+
                                                                                                                              job.maxConcurrent
                                                                                                                              
+
                                                                                                                              Maximum number of jobs can be concurrently executed by a Spark driver. When the number of jobs exceeds the value of this parameter, the jobs are allocated to other Spark drivers.
                                                                                                                              
+
                                                                                                                              1–32
                                                                                                                              
+
                                                                                                                              Job result saving policy
                                                                                                                              
+
                                                                                                                              Set Result Saving Policy
                                                                                                                              
+
                                                                                                                              job.saveJobResultToJobBucket
                                                                                                                              
+
                                                                                                                              Whether to save job results to a DLI job bucket.
                                                                                                                              
+
                                                                                                                              This parameter is only available for Spark SQL queues.
                                                                                                                              
+
                                                                                                                              Once enabled, this feature cannot be disabled, and job results of a queue are consistently saved to the DLI job bucket you configure.
                                                                                                                              
+
                                                                                                                              Before enabling this feature, make sure you have configured a DLI job bucket. For how to configure a DLI job bucket, see Configuring a DLI Job Bucket.
                                                                                                                              
+
                                                                                                                              To check if you have enabled the function to save SQL job results to a DLI job bucket, refer to How Do I Check if Job Result Saving to a DLI Job Bucket Is Enabled for a SQL Queue?
                                                                                                                              
+
                                                                                                                              You are advised to enable the feature of saving job results to DLI job buckets to more effectively manage and store SQL job query results.
                                                                                                                              
+
                                                                                                                              N/A
                                                                                                                              
+
                                                                                                                              Enabling Spark Native operator optimization
                                                                                                                              
+
                                                                                                                              DLI Spark Native Acceleration
                                                                                                                              
+
                                                                                                                              computeEngine.spark.nativeEnabled
                                                                                                                              
+
                                                                                                                              Enabling Spark Native can improve the performance of Spark SQL jobs, reducing CPU and memory consumption.
                                                                                                                              
+
                                                                                                                              For more information, see Enabling Spark Native Operator Optimization.
                                                                                                                              
+
                                                                                                                              Enabled or disabled
                                                                                                                              
                                                                                                                               		
 
                                                                                                                              
                                                                                                                               
 
 
 
 
                                                                                                                              
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                              Table 1 Parameters for creating a SQL inspection rule
                                                                                                                              Parameter
                                                                                                                              
+
                                                                                                                              Description
                                                                                                                              
+
                                                                                                                              Rule Name
                                                                                                                              
+
                                                                                                                              Name of a SQL inspection rule
                                                                                                                              
+
                                                                                                                              System Rules
                                                                                                                              
+
                                                                                                                              Select an inspection rule. For details about the system inspection rules supported by DLI, see SQL Inspection System Rules That DLI Supports.
                                                                                                                              
+
                                                                                                                              Queues
                                                                                                                              
+
                                                                                                                              Select the queues the rules are bound to.
                                                                                                                              
+
                                                                                                                              Description
                                                                                                                              
+
                                                                                                                              Enter a rule description.
                                                                                                                              
+
                                                                                                                              Rule Action
                                                                                                                              
+
                                                                                                                              Actions that the current SQL inspection rule supports.
                                                                                                                              
+
                                                                                                                              SQL rules support the following types of actions:
                                                                                                                              
+
                                                                                                                              • Info: Record logs and provide a hint for handling the SQL request. If the rule has parameters, you need to configure the threshold.
                                                                                                                              • Block: Intercept the SQL request that meets the rule. If the rule has parameters, you need to configure the threshold.
                                                                                                                              • Circuit Breaker: Perform circuit breaking on the SQL request that meets the inspection rules. If the rule has parameters, you need to configure the threshold.
                                                                                                                              
+
                                                                                                                              
+
                                                                                                                              
+
                                                                                                                            5. Click OK.
                                                                                                                              View the added inspection rule on the SQL Inspector page. The rule takes effect dynamically.
                                                                                                                              
+
                                                                                                                              To modify a rule, click Modify in its Operation column.
                                                                                                                              
+
                                                                                                                            
+
                                                                                                                            
+
                                                                                                                            SQL Inspection System Rules That DLI Supports
                                                                                                                            This part describes the system inspection rules supported by DLI. For details, see Table 2.
                                                                                                                            
+
                                                                                                                            • Default system rules are SQL inspection rules automatically created by DLI when a queue is created. These rules are bound to the queue and cannot be deleted.
                                                                                                                            • Default system rules include Scan files number, Scan partitions number, Shuffle data(GB), Count(distinct) occurrences, and Not in<Subquery>.
                                                                                                                            • Only one inspection rule can be created for an action or a queue.
                                                                                                                            • For every supported action, a default system rule is created. For example, when a queue is created, a Scan files number rule is automatically created for both the Info and Block actions.
                                                                                                                            • Different engine versions support different inspection rules.
                                                                                                                              To view the engine version of a queue, choose Resources > Queue Management in the navigation pane on the left, select the queue, double-click the pane at the bottom of the page, and check the value of Default Version.
                                                                                                                              
+
                                                                                                                            
+
+
                                                                                                                            
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                            Table 2 System inspection rules supported by DLI
                                                                                                                            Rule ID
                                                                                                                            
+
                                                                                                                            Rule Name
                                                                                                                            
+
                                                                                                                            Description
                                                                                                                            
+
                                                                                                                            Type
                                                                                                                            
+
                                                                                                                            Applicable Engine
                                                                                                                            
+
                                                                                                                            Action
                                                                                                                            
+
                                                                                                                            Value
                                                                                                                            
+
                                                                                                                            Default System Rule
                                                                                                                            
+
                                                                                                                            Example SQL Statement
                                                                                                                            
+
                                                                                                                            Supported Engine Version
                                                                                                                            
+
                                                                                                                            dynamic_0001
                                                                                                                            
+
                                                                                                                            Scan files number
                                                                                                                            
+
                                                                                                                            Maximum number of files to be scanned
                                                                                                                            
+
                                                                                                                            Dynamic
                                                                                                                            
+
                                                                                                                            Spark
                                                                                                                            
+
                                                                                                                            HetuEngine
                                                                                                                            
+
                                                                                                                            Info
                                                                                                                            
+
                                                                                                                            Block
                                                                                                                            
+
                                                                                                                            Value range: 1–2000000
                                                                                                                            
+
                                                                                                                            Default value: 200000
                                                                                                                            
+
                                                                                                                            Yes
                                                                                                                            
+
                                                                                                                            N/A
                                                                                                                            
+
                                                                                                                            Spark 3.3.1
                                                                                                                            
+
                                                                                                                            dynamic_0002
                                                                                                                            
+
                                                                                                                            Scan partitions number
                                                                                                                            
+
                                                                                                                            Maximum number of partitions involved in the operations (select, delete, update, and alter) that can be performed on a table
                                                                                                                            
+
                                                                                                                            Dynamic
                                                                                                                            
+
                                                                                                                            Spark
                                                                                                                            
+
                                                                                                                            Info
                                                                                                                            
+
                                                                                                                            Block
                                                                                                                            
+
                                                                                                                            Value range: 1–500000
                                                                                                                            
+
                                                                                                                            Default value: 5000
                                                                                                                            
+
                                                                                                                            Yes
                                                                                                                            
+
                                                                                                                            select * from Partitioned table
                                                                                                                            
+
                                                                                                                            Spark 3.3.1
                                                                                                                            
+
                                                                                                                            running_0002
                                                                                                                            
+
                                                                                                                            Memory used(MB)
                                                                                                                            
+
                                                                                                                            Peak memory usage of the SQL statement
                                                                                                                            
+
                                                                                                                            Running
                                                                                                                            
+
                                                                                                                            Spark
                                                                                                                            
+
                                                                                                                            Circuit Breaker
                                                                                                                            
+
                                                                                                                            Value range: 1–8388608
                                                                                                                            
+
                                                                                                                            No
                                                                                                                            
+
                                                                                                                            N/A
                                                                                                                            
+
                                                                                                                            Spark 3.3.1
                                                                                                                            
+
                                                                                                                            running_0003
                                                                                                                            
+
                                                                                                                            Run time(S)
                                                                                                                            
+
                                                                                                                            Maximum running duration of the SQL statement
                                                                                                                            
+
                                                                                                                            Running
                                                                                                                            
+
                                                                                                                            Spark
                                                                                                                            
+
                                                                                                                            Circuit Breaker
                                                                                                                            
+
                                                                                                                            Unit: second
                                                                                                                            
+
                                                                                                                            Value range: 1–43200
                                                                                                                            
+
                                                                                                                            No
                                                                                                                            
+
                                                                                                                            N/A
                                                                                                                            
+
                                                                                                                            Spark 3.3.1
                                                                                                                            
+
                                                                                                                            running_0004
                                                                                                                            
+
                                                                                                                            Scan data(GB)
                                                                                                                            
+
                                                                                                                            Maximum amount of data to be scanned
                                                                                                                            
+
                                                                                                                            Running
                                                                                                                            
+
                                                                                                                            Spark
                                                                                                                            
+
                                                                                                                            Circuit Breaker
                                                                                                                            
+
                                                                                                                            Unit: GB
                                                                                                                            
+
                                                                                                                            Value range: 1–10240
                                                                                                                            
+
                                                                                                                            No
                                                                                                                            
+
                                                                                                                            N/A
                                                                                                                            
+
                                                                                                                            Spark 3.3.1
                                                                                                                            
+
                                                                                                                            running_0005
                                                                                                                            
+
                                                                                                                            Shuffle data(GB)
                                                                                                                            
+
                                                                                                                            Maximum amount of data to be shuffled
                                                                                                                            
+
                                                                                                                            Running
                                                                                                                            
+
                                                                                                                            Spark
                                                                                                                            
+
                                                                                                                            Circuit Breaker
                                                                                                                            
+
                                                                                                                            Unit: GB
                                                                                                                            
+
                                                                                                                            Value range: 1–10240
                                                                                                                            
+
                                                                                                                            Default value: 2048
                                                                                                                            
+
                                                                                                                            Yes
                                                                                                                            
+
                                                                                                                            N/A
                                                                                                                            
+
                                                                                                                            Spark 3.3.1
                                                                                                                            
+
                                                                                                                            Spark 2.4.5
                                                                                                                            
+
                                                                                                                            static_0001
                                                                                                                            
+
                                                                                                                            Count(distinct) occurrences
                                                                                                                            
+
                                                                                                                            Maximum number of occurrences of count(distinct) in the SQL statement
                                                                                                                            
+
                                                                                                                            Static
                                                                                                                            
+
                                                                                                                            Spark
                                                                                                                            
+
                                                                                                                            Info
                                                                                                                            
+
                                                                                                                            Block
                                                                                                                            
+
                                                                                                                            Value range: 1–100
                                                                                                                            
+
                                                                                                                            Default value: 10
                                                                                                                            
+
                                                                                                                            Yes
                                                                                                                            
+
                                                                                                                            SELECT COUNT(DISTINCT deviceId), COUNT(DISTINCT collDeviceId)
                                                                                                                            
+
                                                                                                                            FROM table
                                                                                                                            
+
                                                                                                                            GROUP BY deviceName, collDeviceName, collCurrentVersion;
                                                                                                                            
+
                                                                                                                            Spark 3.3.1
                                                                                                                            
+
                                                                                                                            static_0002
                                                                                                                            
+
                                                                                                                            Not in<Subquery>
                                                                                                                            
+
                                                                                                                            Check whether not in <subquery> is used in the SQL statement.
                                                                                                                            
+
                                                                                                                            Static
                                                                                                                            
+
                                                                                                                            Spark
                                                                                                                            
+
                                                                                                                            Info
                                                                                                                            
+
                                                                                                                            Block
                                                                                                                            
+
                                                                                                                            Value range: Yes, No
                                                                                                                            
+
                                                                                                                            Default value: Yes
                                                                                                                            
+
                                                                                                                            Yes
                                                                                                                            
+
                                                                                                                            SELECT *
                                                                                                                            
+
                                                                                                                            FROM Orders o
                                                                                                                            
+
                                                                                                                            WHERE Orders.Order_ID not in (Select Order_ID
                                                                                                                            
+
                                                                                                                            FROM HeldOrders h
                                                                                                                            
+
                                                                                                                            where h.order_id = o.order_id);
                                                                                                                            
+
                                                                                                                            Spark 3.3.1
                                                                                                                            
+
                                                                                                                            static_0003
                                                                                                                            
+
                                                                                                                            Join occurrences
                                                                                                                            
+
                                                                                                                            Maximum number of joins in the SQL statement
                                                                                                                            
+
                                                                                                                            Static
                                                                                                                            
+
                                                                                                                            Spark
                                                                                                                            
+
                                                                                                                            Info
                                                                                                                            
+
                                                                                                                            Block
                                                                                                                            
+
                                                                                                                            Value range: 1–50
                                                                                                                            
+
                                                                                                                            No
                                                                                                                            
+
                                                                                                                            SELECT name, text FROM table_1 JOIN table_2 ON table_1.Id = table_2.Id
                                                                                                                            
+
                                                                                                                            Spark 3.3.1
                                                                                                                            
+
                                                                                                                            static_0004
                                                                                                                            
+
                                                                                                                            Union occurrences
                                                                                                                            
+
                                                                                                                            Maximum number of union all times in the SQL statement
                                                                                                                            
+
                                                                                                                            Static
                                                                                                                            
+
                                                                                                                            Spark
                                                                                                                            
+
                                                                                                                            Info
                                                                                                                            
+
                                                                                                                            Block
                                                                                                                            
+
                                                                                                                            Value range: 1–100
                                                                                                                            
+
                                                                                                                            No
                                                                                                                            
+
                                                                                                                            select * from tables t1
                                                                                                                            
+
                                                                                                                            union all select * from tables t2
                                                                                                                            
+
                                                                                                                            union all select * from tables t3
                                                                                                                            
+
                                                                                                                            Spark 3.3.1
                                                                                                                            
+
                                                                                                                            static_0005
                                                                                                                            
+
                                                                                                                            Subquery nesting layers
                                                                                                                            
+
                                                                                                                            Maximum number of subquery nesting layers
                                                                                                                            
+
                                                                                                                            Static
                                                                                                                            
+
                                                                                                                            Spark
                                                                                                                            
+
                                                                                                                            Info
                                                                                                                            
+
                                                                                                                            Block
                                                                                                                            
+
                                                                                                                            Value range: 1–20
                                                                                                                            
+
                                                                                                                            No
                                                                                                                            
+
                                                                                                                            select * from (
                                                                                                                            
+
                                                                                                                            with temp1 as (select * from tables)
                                                                                                                            
+
                                                                                                                            select * from temp1);
                                                                                                                            
+
                                                                                                                            Spark 3.3.1
                                                                                                                            
+
                                                                                                                            static_0006
                                                                                                                            
+
                                                                                                                            Sql size(KB)
                                                                                                                            
+
                                                                                                                            Maximum size of a SQL file
                                                                                                                            
+
                                                                                                                            Static
                                                                                                                            
+
                                                                                                                            Spark
                                                                                                                            
+
                                                                                                                            Info
                                                                                                                            
+
                                                                                                                            Block
                                                                                                                            
+
                                                                                                                            Unit: KB
                                                                                                                            
+
                                                                                                                            Value range: 1–1024
                                                                                                                            
+
                                                                                                                            No
                                                                                                                            
+
                                                                                                                            N/A
                                                                                                                            
+
                                                                                                                            Spark 3.3.1
                                                                                                                            
+
                                                                                                                            static_0007
                                                                                                                            
+
                                                                                                                            Cartesian product
                                                                                                                            
+
                                                                                                                            Limitation of Cartesian products when multiple tables are being associated
                                                                                                                            
+
                                                                                                                            Static
                                                                                                                            
+
                                                                                                                            Spark
                                                                                                                            
+
                                                                                                                            Info
                                                                                                                            
+
                                                                                                                            Block
                                                                                                                            
+
                                                                                                                            Value range: 0–1
                                                                                                                            
+
                                                                                                                            No
                                                                                                                            
+
                                                                                                                            select * from A,B;
                                                                                                                            
+
                                                                                                                            Spark 3.3.1
                                                                                                                            
+
                                                                                                                            
+
                                                                                                                            
+
                                                                                                                            
+
+
+
diff --git a/docs/dli/umn/dli_01_0616.html b/docs/dli/umn/dli_01_0616.html
index db4eb5845..3105f2db1 100644
--- a/docs/dli/umn/dli_01_0616.html
+++ b/docs/dli/umn/dli_01_0616.html
@@ -2,7 +2,7 @@
 
 
                                                                                                                            Creating a Custom DLI Agency
                                                                                                                            
 
                                                                                                                            When Flink 1.15, Spark 3.3, or a later version is used to execute jobs and the required agency is not included in the DLI system agency dli_management_agency, you need to create an agency on the IAM console and add information about the new agency to the job configuration. dli_management_agency contains the permissions required for datasource operations, message notifications, and user authorization operations. For other agency permission requirements, you need to create custom DLI agencies. For details about dli_management_agency, see DLI Agency Overview.
                                                                                                                            
-
                                                                                                                            This section walks you through on how to create a custom agency, complete service authorization, and add information about the new agency to the job configuration.
                                                                                                                            
+
                                                                                                                            This section walks you through how to create a custom agency, complete service authorization, and add information about the new agency to the job configuration.
                                                                                                                            
 
                                                                                                                            DLI Custom Agency Scenarios
                                                                                                                            
 
                                                                                                                            
@@ -55,11 +55,11 @@
 
                                                                                                                            Table 1 DLI custom agency scenarios
                                                                                                                            Scenario
                                                                                                                            
 
                                                                                                                            
 
                                                                                                                            
 
                                                                                                                            
-
                                                                                                                            Procedure
                                                                                                                            Figure 1 Process of creating a custom agency
                                                                                                                            
+
                                                                                                                            Procedure
                                                                                                                            Figure 1 Process of creating a custom agency
                                                                                                                            
 
                                                                                                                            
 
                                                                                                                            Notes and Constraints
                                                                                                                            • The custom agency name cannot be the default agency names dli_admin_agency, dli_management_agency, or dli_data_clean_agency. It must be unique.
                                                                                                                            • The name of the agency that allows DLI to clear data according to the lifecycle of a table must be dli_data_clean_agency.
                                                                                                                            • Custom agencies can be configured only for jobs executed by engines like Flink 1.15, Spark 3.3.1 (Spark general queue scenario), or later versions.
                                                                                                                            • Once the agency permissions are updated, your dli_admin_agency will be upgraded to dli_management_agency. This new agency will have the necessary permissions for datasource operations, notifications, and user authorization operations. If you have other agency permission needs, you will need to create custom agencies. For details about dli_management_agency, see DLI Agency Overview.
                                                                                                                            • Common scenarios for creating an agency: DLI is allowed to read and write data from and to OBS, dump logs, and read and write Flink checkpoints. DLI is allowed to access DEW to obtain data access credentials and access catalogs to obtain metadata. For details about agency permissions in these scenarios, see Agency Permission Policies in Common Scenarios.
                                                                                                                            
 
                                                                                                                            
-
                                                                                                                            Step 1: Create a Cloud Service Agency on the IAM Console and Grant Permissions
                                                                                                                            1. Log in to the management console.
                                                                                                                            2. In the upper right corner of the page, hover over the username and select Identity and Access Management.
                                                                                                                            3. In the navigation pane of the IAM console, choose Agencies.
                                                                                                                            4. On the displayed page, click Create Agency.
                                                                                                                            5. On the Create Agency page, set the following parameters:
                                                                                                                              • Agency Name: Enter an agency name, for example, dli_obs_agency_access.
                                                                                                                              • Agency Type: Select Cloud service.
                                                                                                                              • Cloud Service: This parameter is available only when you select Cloud service for Agency Type. Select Data Lake Insight (DLI) from the drop-down list.
                                                                                                                              • Validity Period: Select Unlimited.
                                                                                                                              • Description: You can enter Agency with OBS OperateAccess permissions. This parameter is optional.
                                                                                                                              
+
                                                                                                                              Step 1: Create a Cloud Service Agency on the IAM Console and Grant Permissions
                                                                                                                              1. Log in to the management console.
                                                                                                                              2. In the upper right corner of the page, hover over the username and select Identity and Access Management.
                                                                                                                              3. In the navigation pane of the IAM console, choose Agencies.
                                                                                                                              4. On the displayed page, click Create Agency.
                                                                                                                              5. On the Create Agency page, set the following parameters:
                                                                                                                                • Agency Name: Enter an agency name, for example, dli_obs_agency_access.
                                                                                                                                • Agency Type: Select Cloud service.
                                                                                                                                • Cloud Service: This parameter is available only when you select Cloud service for Agency Type. Select Data Lake Insight (DLI) from the drop-down list.
                                                                                                                                • Validity Period: Select Unlimited.
                                                                                                                                • Description: You can enter Agency with OBS OperateAccess permissions. This parameter is optional.
                                                                                                                                
 
                                                                                                                              6. Click Next.
                                                                                                                              7. Click the agency name. On the displayed page, click the Permissions tab. Click Authorize. On the displayed page, click Create Policy.
                                                                                                                              8. Configure policy information.
                                                                                                                                1. Enter a policy name, for example, dli-obs-agency.
                                                                                                                                2. Select JSON.
                                                                                                                                3. In the Policy Content area, paste a custom policy.
                                                                                                                                  In this example, the permissions allow access and usage of OBS in various scenarios. For DLI Flink jobs, this includes downloading OBS objects, obtaining OBS/GaussDB(DWS) data sources (foreign tables), transferring logs, using savepoints, and enabling checkpointing. For DLI Spark jobs, the permissions allow downloading OBS objects and reading/writing OBS foreign tables.
                                                                                                                                  
 
                                                                                                                                  For how to configure common agency permissions for Flink jobs, see Agency Permission Policies in Common Scenarios.
                                                                                                                                  {
     "Version": "1.1",
@@ -108,17 +108,17 @@
 
                                                                                                                                4. Click OK.
                                                                                                                                  It takes 15 to 30 minutes for the authorization to be in effect.
                                                                                                                                  
 
                                                                                                                                
 
                                                                                                                              
-
                                                                                                                              Step 2: Set Agency Permissions for a Job
                                                                                                                              When Flink 1.15, Spark 3.3, or a later version is used to execute jobs, you need to add information about the new agency to the job configuration.
                                                                                                                              
+
                                                                                                                              Step 2: Set Agency Permissions for a Job
                                                                                                                              When Spark 3.3.1, Flink 1.15, or a later version is used to execute jobs, you need to add information about the new agency to the job configuration.
                                                                                                                              
 
                                                                                                                              Otherwise, If you do not specify an agency for Spark 3.3.1 jobs, the jobs cannot use OBS. If you do not specify an agency for a Flink 1.15 job, checkpointing cannot be enabled, savepoints cannot be used, logs cannot be transferred, and data sources such as OBS and GaussDB(DWS) cannot be used.
                                                                                                                              
 
                                                                                                                               
                                                                                                                              • You can only specify an agency for Flink 1.15 and Spark 3.3.1 jobs running on queues in an elastic resource pool.
                                                                                                                              • After specifying an agency for a job, be careful when modifying the permissions granted to the agency. Any changes made may impact the job's normal operation.
                                                                                                                              
 
                                                                                                                              
-
                                                                                                                              • Specifying an agency for a Flink Jar job
                                                                                                                                1. Log in to the DLI console. In the navigation pane, choose Job Management > Flink Jobs.
                                                                                                                                2. Select a desired job and click Edit in the Operation column.
                                                                                                                                3. In the job configuration area on the right, configure agency information.
                                                                                                                                  • Flink Version: Select 1.15.
                                                                                                                                  • Runtime Configuration: Configure the key-value information of the new agency. The key is fixed to flink.dli.job.agency.name, and the value is the custom agency name.
                                                                                                                                    In this example, set the key-value information to flink.dli.job.agency.name=dli_obs_agency_access.
                                                                                                                                    
+
                                                                                                                                    • Specifying an agency for a Flink Jar job
                                                                                                                                      1. Log in to the DLI console. In the navigation pane, choose Job Management > Flink Jobs.
                                                                                                                                      2. Select a desired job and click Edit in the Operation column.
                                                                                                                                      3. In the job configuration area on the right, configure agency information.
 
                                                                                                                                      
-
                                                                                                                                    • Specifying an agency for a Flink OpenSource SQL job
                                                                                                                                      1. Log in to the DLI console. In the navigation pane, choose Job Management > Flink Jobs.
                                                                                                                                      2. Select a desired job and click Edit in the Operation column.
                                                                                                                                      3. In the job configuration area on the right, configure agency information.
                                                                                                                                        • On the Running Parameters tab, ensure that the selected Flink version is 1.15.
                                                                                                                                        • Click Runtime Configuration. Configure the key-value information of the new agency. The key is fixed to flink.dli.job.agency.name, and the value is the custom agency name.
                                                                                                                                          In this example, set the key-value information to flink.dli.job.agency.name=dli_obs_agency_access.
                                                                                                                                          
+
                                                                                                                                        • Specifying an agency for a Flink OpenSource SQL job
                                                                                                                                          1. Log in to the DLI console. In the navigation pane, choose Job Management > Flink Jobs.
                                                                                                                                          2. Select a desired job and click Edit in the Operation column.
                                                                                                                                          3. In the job configuration area on the right, configure agency information.
 
                                                                                                                                          
-
                                                                                                                                        • Specifying an agency for a Spark job
                                                                                                                                          1. Log in to the DLI console. In the navigation pane, choose Job Management > Spark Jobs.
                                                                                                                                          2. Select the target job and click Edit in the Operation column.
                                                                                                                                          3. In the job configuration area on the right, configure agency information.
                                                                                                                                            • Ensure that the selected Spark version is 3.3.1.
                                                                                                                                            • In the Spark Arguments(--conf) area, configure the key-value information of the new agency. The key is fixed to spark.dli.job.agency.name, and the value is the custom agency name.
                                                                                                                                              In this example, set the key-value information to spark.dli.job.agency.name=dli_obs_agency_access.
                                                                                                                                              
+
                                                                                                                                            • Specifying an agency for a Spark job
                                                                                                                                              1. Log in to the DLI console. In the navigation pane, choose Job Management > Spark Jobs.
                                                                                                                                              2. Select a desired job and click Edit in the Operation column.
                                                                                                                                              3. In the job configuration area on the right, configure agency information.
 
                                                                                                                                              
 
                                                                                                                                            
@@ -130,3 +130,10 @@
 
                                                                                                                              
 
                                                                                                                              
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_01_0618.html b/docs/dli/umn/dli_01_0618.html
index c571e90d3..7c21009f5 100644
--- a/docs/dli/umn/dli_01_0618.html
+++ b/docs/dli/umn/dli_01_0618.html
@@ -1,44 +1,44 @@
 
 
 
                                                                                                                              Configuring DLI Agency Permissions
                                                                                                                              
-
                                                                                                                              To use DLI, you must first configure permissions.
                                                                                                                              
-
                                                                                                                              This section applies to the following scenarios:
                                                                                                                              
+
                                                                                                                              Scenarios of dli_management_agency
                                                                                                                              Before using DLI, configure DLI agency permissions. This section describes the scenarios and steps for configuring DLI agency permissions (dli_management_agency).
                                                                                                                              
 
                                                                                                                              • If you use DLI for the first time, configure DLI agency permissions by referring to this section.
                                                                                                                                DLI needs to work with other cloud services. You must grant DLI basic operation permissions of these services so that DLI can access them and perform resource O&M operations on your behalf.
                                                                                                                                
-
                                                                                                                              • If you are still using the previous-generation agency dli_admin_agency, update it by referring to this section.
                                                                                                                                To balance practical business needs with the risk of excessive delegation, DLI upgraded its system agency to achieve more granular control over permissions. The previous dli_admin_agency was upgraded to dli_management_agency, which includes permissions for accessing IAM user information, datasource operations, and message notifications. This effectively prevents uncontrolled permission issues related to the services associated with DLI. After the upgrade, the DLI agency is more flexible and more suitable for scenario-based agency customization for medium- and large-sized enterprises.
                                                                                                                                
+
                                                                                                                              • If you are currently using the older DLI agency dli_admin_agency, follow the instructions in this section to upgrade it to the newer version, dli_management_agency.
                                                                                                                                To balance practical business needs with the risk of excessive delegation, DLI upgraded its system agency to achieve more granular control over permissions. The previous dli_admin_agency was upgraded to dli_management_agency, which includes permissions for accessing IAM user information, datasource operations, and message notifications. This effectively prevents uncontrolled permission issues related to the services associated with DLI. After the upgrade, the DLI agency is more flexible and more suitable for scenario-based agency customization for medium- and large-sized enterprises.
                                                                                                                                
 
                                                                                                                              
 
                                                                                                                              After agency permissions are configured, the dli_management_agency agency is generated on the Agencies page of the IAM console. Do not delete this default system agency. Otherwise, the permissions included in the agency will be automatically revoked. The system cannot obtain IAM user information, access network resources required by datasource connections, or access SMN to send notifications.
                                                                                                                              
-
                                                                                                                              Notes and Constraints
                                                                                                                              • Only the tenant account or a member account of user group admin can authorize the service.
                                                                                                                              • DLI authorization needs to be conducted by project. The permissions of required agencies must be updated separately in each project. This means you need to switch to the corresponding project and then update the agency by following the instructions provided in this section.
                                                                                                                              
+
                                                                                                                              
+
                                                                                                                              Notes and Constraints
                                                                                                                              • Only the tenant account or a member account of user group admin can authorize the service.
                                                                                                                              • DLI authorization (dli_management_agency) needs to be conducted by project. The permissions of required agencies must be updated separately in each project. This means you need to switch to the corresponding project and then update the agency by following the instructions provided in this section.
                                                                                                                              
 
                                                                                                                              
 
                                                                                                                              Updating DLI Agency Permissions (dli_management_agency)
                                                                                                                              1. In the navigation pane of the DLI console, choose Global Configuration > Service Authorization.
                                                                                                                              2. On the displayed page, select permissions for scenarios.
                                                                                                                                Click  on a permission card to view its detailed permission policies.
                                                                                                                                
 
                                                                                                                                Table 1 describes these agencies.
-
                                                                                                                                Table 1 Permissions contained in the dli_management_agency agency
                                                                                                                                Use Case
                                                                                                                                
+
                                                                                                                                
-
-
-
-
-
-
-
-
-
-
-
@@ -53,11 +53,11 @@
 
                                                                                                                              3. Select the policies to be included in dli_management_agency and click Update.
                                                                                                                              4. View and understand the notes for updating the agency and click OK. The DLI agency permissions are updated.
                                                                                                                                • The system upgrades your dli_admin_agency to dli_management_agency.
                                                                                                                                • To maintain compatibility with existing job agency permission requirements, dli_admin_agency will still be listed in the IAM agency list even after the update.
                                                                                                                                • Do not delete the agency created by the system by default.
                                                                                                                                
 
                                                                                                                                5. 
-
                                                                                                                                Follow-Up Operations
                                                                                                                                In addition to the permissions provided by dli_management_agency, you need to create an agency on the IAM console and add information about the new agency to the job configuration for scenarios like allowing DLI to read and write data from and to OBS to transfer logs, or allowing DLI to access DEW to obtain data access credentials. For details, see Creating a Custom DLI Agency and Agency Permission Policies in Common Scenarios.
                                                                                                                                
+
                                                                                                                                Follow-up Operations
                                                                                                                                In addition to the permissions provided by dli_management_agency, you need to create an agency on the IAM console and add information about the new agency to the job configuration for scenarios like allowing DLI to read and write data from and to OBS to transfer logs, or allowing DLI to access DEW to obtain data access credentials. For details, see Creating a Custom DLI Agency and Agency Permission Policies in Common Scenarios.
                                                                                                                                
 
                                                                                                                                • When Flink 1.15, Spark 3.3.1 (Spark general queue scenario), or a later version is used to execute jobs, you need to create an agency on the IAM console.
                                                                                                                                • If the engine version is earlier than Flink 1.15, dli_admin_agency is used by default during job execution. If the engine version is earlier than Spark 3.3.1, user authentication information (AK/SK and security token) is used during job execution.
                                                                                                                                  This means that jobs whose engine versions are earlier than Flink 1.15 or Spark 3.3.1 are not affected by the update of agency permissions and do not require custom agencies.
                                                                                                                                  
 
                                                                                                                                
 
                                                                                                                                Common service scenarios where you need to create an agency:
                                                                                                                                
-
                                                                                                                                • Data cleanup agency required for clearing data according to the lifecycle of a table and clearing lakehouse table data. You need to create a DLI agency named dli_data_clean_agency on IAM and grant permissions to it. You need to create an agency and customize permissions for it. However, the agency name is fixed to dli_data_clean_agency.
                                                                                                                                • Tenant Administrator permissions are required to access data from OBS to execute Flink jobs on DLI, for example, obtaining OBS data sources, log dump (including bucket authorization), checkpointing enabling, and job import and export.
                                                                                                                                • The AK/SK required by DLI Flink jobs is stored in DEW. To allow DLI to access DEW data during job execution, you need to create an agency to delegate the permissions to operate on DEW data to DLI.
                                                                                                                                • To allow DLI to access DLI catalogs to retrieve metadata when executing jobs, you need to create a new agency that grants DLI catalog data operation permissions to DLI. This will enable DLI to access DLI catalogs on your behalf.
                                                                                                                                • Cloud data required by DLI Flink jobs is stored in LakeFormation. To allow DLI to access catalogs to retrieve metadata during job execution, you need to create an agency to delegate the permissions to operate on catalog data to DLI.
                                                                                                                                
+
                                                                                                                                • Data cleanup agency required for clearing data according to the lifecycle of a table and clearing lakehouse table data. You need to create a DLI agency named dli_data_clean_agency on IAM and grant permissions to it. You need to create an agency and customize permissions for it. However, the agency name is fixed to dli_data_clean_agency.
                                                                                                                                • Tenant Administrator permissions are required to access data from OBS to execute Flink jobs on DLI, for example, obtaining OBS data sources, log dump (including bucket authorization), checkpointing enabling, and job import and export.
                                                                                                                                • The AK/SK required by DLI Flink jobs is stored in DEW. To allow DLI to access DEW data during job execution, you need to create an agency to delegate the permissions to operate on DEW data to DLI.
                                                                                                                                • To allow DLI to access DLI catalogs to retrieve metadata when executing jobs, you need to create an agency that grants DLI catalog data operation permissions to DLI. This will enable DLI to access DLI catalogs on your behalf.
                                                                                                                                • Cloud data required by DLI Flink jobs is stored in LakeFormation. To allow DLI to access catalogs to retrieve metadata during job execution, you need to create an agency to delegate the permissions to operate on catalog data to DLI.
                                                                                                                                
 
                                                                                                                                When creating an agency, you cannot use the default agency names dli_admin_agency, dli_management_agency, or dli_data_clean_agency. It must be unique.
                                                                                                                                
 
                                                                                                                                For more information about custom agency operations, see Creating a Custom DLI Agency and Agency Permission Policies in Common Scenarios.
                                                                                                                                
 
                                                                                                                                
diff --git a/docs/dli/umn/dli_01_0621.html b/docs/dli/umn/dli_01_0621.html
index 4095bf484..790199097 100644
--- a/docs/dli/umn/dli_01_0621.html
+++ b/docs/dli/umn/dli_01_0621.html
@@ -4,17 +4,17 @@
 
                                                                                                                                Store the data results of analyzed SQL jobs in a specified location in the desired format.
                                                                                                                                
 
                                                                                                                                By default, DLI stores SQL job results in its job bucket. You can also download job results to a local host or export job results to a specified OBS bucket.
                                                                                                                                
 
                                                                                                                                Exporting Job Results to the DLI Job Bucket
                                                                                                                                DLI specifies a default OBS bucket for storing job results. You can configure the bucket information on the Global Configuration > Project page of the DLI management console. Once a job is complete, the system automatically stores its results to this bucket.
                                                                                                                                
-
                                                                                                                                The following conditions must be met if you want to read job results from the DLI job bucket:
                                                                                                                                • You have configured the job bucket on the Global Configuration > Project page of the DLI management console by referring to Configuring a DLI Job Bucket.
                                                                                                                                • You have submitted a service ticket to request the whitelisting of the feature that allows writing job results to buckets.
                                                                                                                                • The user who executes jobs has been granted read and write permissions either on the job bucket or on the jobs/result path of the job bucket.
                                                                                                                                
+
                                                                                                                                The following conditions must be met if you want to read job results from the DLI job bucket:
                                                                                                                                • You have configured the job bucket on the Global Configuration > Project page of the DLI management console by referring to Configuring a DLI Job Bucket.
                                                                                                                                • The feature of writing query results to buckets is in the limited use phase. To use this feature, submit a service ticket.
                                                                                                                                • The user who executes jobs has been granted read and write permissions either on the job bucket or on the jobs/result path of the job bucket.
                                                                                                                                
 
                                                                                                                                
 
                                                                                                                                
 
                                                                                                                                Exporting Job Results to a Specified Location in Another Bucket
                                                                                                                                In addition to storing job results in the default bucket, you can also export them to a specified location in another bucket, increasing the flexibility of job result management and making it easier to organize and manage them.
                                                                                                                                
 
                                                                                                                                On the console, you can only view a maximum of 1,000 job results. To view additional results, you can export them to an OBS path. The procedure is as follows:
                                                                                                                                
 
                                                                                                                                You can export job results on either the SQL Jobs or the SQL Editor page.
                                                                                                                                
-
                                                                                                                                • SQL Jobs page: In the navigation pane on the left, choose Job Management > SQL Jobs. On the displayed page, locate the row containing a desired job, click More in the Operation column, and select Export Result.
                                                                                                                                • SQL Editor page: In the navigation pane on the left, choose SQL Editor. On the displayed page, once query statements are successfully executed, click  next to the View Result tab to export job results.
                                                                                                                                
+
                                                                                                                                • SQL Jobs page: In the navigation pane on the left, choose Job Management > SQL Jobs. On the displayed page, locate the row containing a desired job, click More in the Operation column, and select Export Result.
                                                                                                                                • SQL Editor page: In the navigation pane on the left, choose SQL Editor. On the displayed page, once query statements are successfully executed, click  next to the View Result tab to export job results.
                                                                                                                                
 
                                                                                                                                 
                                                                                                                                • If there are no numerical columns in the query results, job results cannot be exported.
                                                                                                                                • Ensure that the user who exports job results has the read and write permissions on the OBS bucket.
                                                                                                                                
 
                                                                                                                                
 
-
                                                                                                                                Table 1 Permissions contained in the dli_management_agency agency
                                                                                                                                Use Case
                                                                                                                                
 
                                                                                                                                Agency
                                                                                                                                
+
                                                                                                                                Agency
                                                                                                                                
 
                                                                                                                                Description
                                                                                                                                
+
                                                                                                                                Description
                                                                                                                                
                                                                                                                                 		
 
                                                                                                                                
 
                                                                                                                                Basic usage
                                                                                                                                
+
                                                                                                                                Basic usage
                                                                                                                                
 
                                                                                                                                IAM ReadOnlyAccess
                                                                                                                                
+
                                                                                                                                IAM ReadOnlyAccess
                                                                                                                                
 
                                                                                                                                To authorize IAM users who have not logged in to DLI, you need to obtain their information. So, the permissions contained in the IAM ReadOnlyAccess policy are required.
                                                                                                                                
+
                                                                                                                                To authorize IAM users who have not logged in to DLI, you need to obtain their information. So, the permissions contained in the IAM ReadOnlyAccess policy are required.
                                                                                                                                
 
                                                                                                                                IAM ReadOnlyAccess is a global policy. Make sure you select this policy. If you do not select it, all its permissions will become invalid in all regions, and the system cannot obtain IAM user information.
                                                                                                                                
                                                                                                                                 		
 
                                                                                                                                Datasource
                                                                                                                                
+
                                                                                                                                Datasource
                                                                                                                                
 
                                                                                                                                DLI Datasource Connections Agency Access
                                                                                                                                
+
                                                                                                                                DLI Datasource Connections Agency Access
                                                                                                                                
 
                                                                                                                                Permissions to access and use VPCs, subnets, routes, and VPC peering connections
                                                                                                                                
+
                                                                                                                                Permissions to access and use VPCs, subnets, routes, and VPC peering connections
                                                                                                                                
                                                                                                                                 		
 
                                                                                                                                O&M
                                                                                                                                
+
                                                                                                                                O&M
                                                                                                                                
 
                                                                                                                                DLI Notification Agency Access
                                                                                                                                
+
                                                                                                                                DLI Notification Agency Access
                                                                                                                                
 
                                                                                                                                Permissions to send notifications through SMN when a job fails to be executed
                                                                                                                                
+
                                                                                                                                Permissions to send notifications through SMN when a job fails to be executed
                                                                                                                                
                                                                                                                                 		
 
                                                                                                                                
                                                                                                                                 
 
                                                                                                                                Table 1 Parameters
                                                                                                                                Parameter
                                                                                                                                
+
                                                                                                                                
@@ -96,7 +96,14 @@
 
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_01_0622.html b/docs/dli/umn/dli_01_0622.html
index a2a474d5d..5deef41a4 100644
--- a/docs/dli/umn/dli_01_0622.html
+++ b/docs/dli/umn/dli_01_0622.html
@@ -1,41 +1,41 @@
 
 
-
                                                                                                                                Viewing Basic Information
                                                                                                                                
+
                                                                                                                                Checking Basic Information
                                                                                                                                After creating an elastic resource pool, you can check and manage it on the management console.
                                                                                                                                
 
                                                                                                                                This section describes how to check basic information about an elastic resource pool on the management console, including the VPC CIDR block, IPv6 CIDR block, and creation time.
                                                                                                                                
 
                                                                                                                                Procedure
                                                                                                                                1. Log in to the DLI management console.
                                                                                                                                2. In the navigation pane on the left, choose Resources > Resource Pool.
                                                                                                                                3. On the displayed page, select the elastic resource pool you want to check.
                                                                                                                                  • In the upper right corner of the list page, click  to customize the columns to display and set the rules for displaying the table content and the Operation column.
                                                                                                                                  • In the search box above the list, you can filter the required elastic resource pool by name or tag.
                                                                                                                                  
-
                                                                                                                                4. Click  to expand the basic information card of the elastic resource pool and view detailed information about the pool.
                                                                                                                                  These details will include the name of the pool, the user who created it, the date it was created, the VPC CIDR block, and whether IPv6 is enabled. If IPv6 is enabled, the subnet's IPv6 CIDR block will also be displayed.
                                                                                                                                  
-
                                                                                                                                  For the definitions of actual CUs, used CUs, CU range, and specifications of the elastic resource pool, refer to Actual CUs, Used CUs, CU Range, and Specifications of an Elastic Resource Pool.
                                                                                                                                  
+
                                                                                                                                5. Click  to expand the basic information card of the elastic resource pool and view detailed information about the pool.
                                                                                                                                  These details include the name of the pool, the user who created it, the date it was created, and the VPC CIDR block.
                                                                                                                                  
+
                                                                                                                                  For the definitions of actual CUs, used CUs, CU range, and specifications of the elastic resource pool, refer to Actual CUs, Used CUs, CU Range, and Specifications of an Elastic Resource Pool.
                                                                                                                                  
 
                                                                                                                                
 
                                                                                                                                
-
                                                                                                                                Actual CUs, Used CUs, CU Range, and Specifications of an Elastic Resource Pool
                                                                                                                                • Actual CUs: number of CUs that can be allocated in the elastic resource pool.
                                                                                                                                  • Formula for calculating actual CUs:
                                                                                                                                    • Actual CUs = min{sum(maximum CUs of the queue), maximum CUs of the elastic resource pool}.
                                                                                                                                    • The calculation result must be a multiple of 16 CUs. If it is not exactly divisible by 16, round up to the nearest multiple.
                                                                                                                                    
-
                                                                                                                                  • Example of actual CU allocation:
                                                                                                                                    In Table 1, the calculation process for the actual allocation of CUs in an elastic resource pool is as follows:
                                                                                                                                    
-
                                                                                                                                    1. Calculate the sum of maximum CUs of the queues: sum(maximum CUs) = 32 + 56 = 88 CUs.
                                                                                                                                    2. Compare the sum of maximum CUs of the queues with the maximum CUs of the elastic resource pool and take the smaller value: min{88 CUs, 112 CUs} = 88 CUs.
                                                                                                                                    3. Check if 88 CUs is a multiple of 16 CUs. Since 88 is not divisible by 16, round up to 96 CUs.
-
                                                                                                                                Table 1 Parameter descriptions
                                                                                                                                Parameter
                                                                                                                                
                                                                                                                                 		
 
                                                                                                                                Mandatory
                                                                                                                                
                                                                                                                                 		
 
 
                                                                                                                                Table 1 Example of actual CU allocation of an elastic resource pool
                                                                                                                                Scenario
                                                                                                                                
+
                                                                                                                                Actual CUs, Used CUs, CU Range, and Specifications of an Elastic Resource Pool
                                                                                                                                • Actual CUs: actual size of resources currently allocated to the elastic resource pool (in CUs).
                                                                                                                                  • When there is no queue in the resource pool, the actual CUs are equal to the minimum CUs when the elastic resource pool is created.
                                                                                                                                  • When there are queues in the resource pool, the formula for calculating actual CUs is:
                                                                                                                                    • Actual CUs = max{(min[sum(maximum CUs of queues), maximum CUs of the elastic resource pool]), minimum CUs of the elastic resource pool}.
                                                                                                                                    • The calculation result must be a multiple of 16 CUs. If it cannot be exactly divided by 16 CUs, round up to the nearest multiple.
                                                                                                                                    
+
                                                                                                                                  • Scaling out or in an elastic resource pool means adjusting the actual CUs of the resource pool. Refer to Scaling Out or In an Elastic Resource Pool.
                                                                                                                                  • Example of actual CU allocation:
                                                                                                                                    In Table 1, the calculation process for the actual allocation of CUs in an elastic resource pool is as follows:
                                                                                                                                    
+
                                                                                                                                    1. Calculate the sum of maximum CUs of the queues: sum(maximum CUs) = 32 + 56 = 88 CUs.
                                                                                                                                    2. Compare the sum of maximum CUs of the queues with the maximum CUs of the elastic resource pool and take the smaller value: min{88 CUs, 112 CUs} = 88 CUs.
                                                                                                                                    3. Compare the value with the minimum CUs of the elastic resource pool and take the larger value: max(88 CUs, 64 CUs) = 88 CUs.
                                                                                                                                    4. Check if 88 CUs is a multiple of 16 CUs. Since 88 is not divisible by 16, round up to 96 CUs.
+
                                                                                                                                      
-
-
-
-
-
-
-
-
-
@@ -43,7 +43,7 @@
 
-
                                                                                                                                    5. Used CUs: CUs that have been used by jobs or tasks. These CU resources may be currently engaged in computing tasks and therefore temporarily unavailable.
                                                                                                                                    6. CU range: CU settings are used to control the maximum and minimum CU ranges for elastic resource pools to avoid unlimited resource scaling.
                                                                                                                                      • The total minimum CUs of all queues in an elastic resource pool must be no more than the minimum CUs of the pool.
                                                                                                                                      • The maximum CUs of any queue in an elastic resource pool must be no more than the maximum CUs of the pool.
                                                                                                                                      • An elastic resource pool should at least ensure that all queues in it can run with the minimum CUs and should try to ensure that all queues in it can run with the maximum CUs.
                                                                                                                                      
+
                                                                                                                                    7. Used CUs: CUs that have been used by jobs or tasks. These resources may be executing computing tasks.
                                                                                                                                    8. CU range: CU settings are used to control the maximum and minimum CU ranges for elastic resource pools to avoid unlimited resource scaling.
                                                                                                                                      • The total minimum CUs of all queues in an elastic resource pool must be no more than the minimum CUs of the pool.
                                                                                                                                      • The maximum CUs of any queue in an elastic resource pool must be no more than the maximum CUs of the pool.
                                                                                                                                      • An elastic resource pool should at least ensure that all queues in it can run with the minimum CUs and should try to ensure that all queues in it can run with the maximum CUs.
                                                                                                                                      • When expanding the specifications of an elastic resource pool, the minimum value of the CU range is linked to the specifications of the elastic resource pool. After changing the specifications of the elastic resource pool, the minimum value of the CU range is modified to match the specifications.
                                                                                                                                      
 
                                                                                                                                    9. Specifications: The minimum CUs selected during elastic resource pool purchase are elastic resource pool specifications. 
                                                                                                                                      10. 
diff --git a/docs/dli/umn/dli_01_0623.html b/docs/dli/umn/dli_01_0623.html
index b35a3fc8e..6cf257324 100644
--- a/docs/dli/umn/dli_01_0623.html
+++ b/docs/dli/umn/dli_01_0623.html
@@ -2,10 +2,10 @@
 
 
                                                                                                                                      Viewing Basic Information About an Enhanced Datasource Connection
                                                                                                                                      After creating an enhanced datasource connection, you can view and manage it on the management console.
                                                                                                                                      
-
                                                                                                                                      This section describes how to view basic information about an enhanced datasource connection on the management console, including whether the enhanced datasource connection supports IPv6, host information, and more.
                                                                                                                                      
+
                                                                                                                                      This section describes how to view basic information about an enhanced datasource connection on the management console, including the enhanced datasource connection's host information and more.
                                                                                                                                      
 
                                                                                                                                      Procedure
                                                                                                                                      1. Log in to the DLI management console.
                                                                                                                                      2. In the navigation pane on the left, choose Datasource Connections.
                                                                                                                                      3. On the displayed Enhanced tab, locate the enhanced datasource connection whose basic information you want to view.
                                                                                                                                        • In the upper right corner of the list page, click  to customize the columns to display and set the rules for displaying the table content and the Operation column.
                                                                                                                                        • In the search box above the list, you can filter the required enhanced datasource connection by name or tag.
                                                                                                                                        
 
                                                                                                                                      4. Click  to expand details about the enhanced datasource connection.
                                                                                                                                        You can view the following information:
                                                                                                                                        
-
                                                                                                                                        1. IPv6 Support: If you selected a subnet with IPv6 enabled when creating the enhanced datasource connection, then your enhanced datasource connection will support IPv6.
                                                                                                                                        2. Host Information: When accessing an MRS HBase cluster, you need to configure the host name (domain name) and the corresponding IP address of the instance. For details, see Modifying Host Information in an Elastic Resource Pool.
                                                                                                                                        
+
 
                                                                                                                                      
 
                                                                                                                                      
 
                                                                                                                                      
diff --git a/docs/dli/umn/dli_01_0625.html b/docs/dli/umn/dli_01_0625.html
index 0143c5db2..c8e96fe60 100644
--- a/docs/dli/umn/dli_01_0625.html
+++ b/docs/dli/umn/dli_01_0625.html
@@ -11,7 +11,7 @@
 
                                                                                                                                    10. Changing the Table Owner on the DLI Console
                                                                                                                                      
 
                                                                                                                                      11. 
-
                                                                                                                                    11. Importing OBS Data to DLI
                                                                                                                                      
+
                                                                                                                                    12. Importing OBS Data to a DLI Table
                                                                                                                                      
 
                                                                                                                                    13. Exporting DLI Table Data to OBS
                                                                                                                                      
 
                                                                                                                                      14. 
@@ -20,7 +20,7 @@
 
                                                                                                                                      
-
                                                                                                                                      Parent topic: Creating Databases and Tables
                                                                                                                                      
+
                                                                                                                                      Parent topic: Creating a Data Directory, Database, and Table
                                                                                                                                      
 
                                                                                                                                      
 
diff --git a/docs/dli/umn/dli_01_0626.html b/docs/dli/umn/dli_01_0626.html
index 8591baf39..65a8083ee 100644
--- a/docs/dli/umn/dli_01_0626.html
+++ b/docs/dli/umn/dli_01_0626.html
@@ -1,7 +1,8 @@
 
                                                                                                                                      Deleting a Table on the DLI Console
                                                                                                                                      
-
                                                                                                                                      You can delete tables as needed.
                                                                                                                                      
+
                                                                                                                                      You can delete an unused data table from the DLI console: when a data table is no longer needed, such as after a test data table has completed testing; if a data table has errors or anomalies that cannot be fixed; when there is a need to reorganize the data structure, such as by modifying table designs; or if a data table is idle and has no practical use.
                                                                                                                                      
+
                                                                                                                                      This section describes how to delete a data table on the DLI management console.
                                                                                                                                      
 
                                                                                                                                      Precautions
                                                                                                                                      • Databases or tables that are being used for running jobs cannot be deleted.
                                                                                                                                      • Only administrators, table owners, and users with table deletion permission can delete tables.
                                                                                                                                         
                                                                                                                                        Deleted data tables cannot be restored. Exercise caution when performing this operation.
                                                                                                                                        
 
                                                                                                                                        
 
                                                                                                                                      
diff --git a/docs/dli/umn/dli_01_0631.html b/docs/dli/umn/dli_01_0631.html
new file mode 100644
index 000000000..0795237e3
--- /dev/null
+++ b/docs/dli/umn/dli_01_0631.html
@@ -0,0 +1,21 @@
+
+
+
+  
                                                                                                                                      Migrating Data from External Data Sources to DLI
                                                                                                                                      
+
+  
                                                                                                                                      
+
                                                                                                                                      
+
+
+
diff --git a/docs/dli/umn/dli_01_0632.html b/docs/dli/umn/dli_01_0632.html
new file mode 100644
index 000000000..a8a193ed0
--- /dev/null
+++ b/docs/dli/umn/dli_01_0632.html
@@ -0,0 +1,314 @@
+
+
+
                                                                                                                                      Overview of Data Migration Scenarios
                                                                                                                                      
+
                                                                                                                                      To centrally analyze and manage scattered data from various systems, you can utilize migration tools like Cloud Data Migration (CDM) to migrate the data to DLI. Once the migration is complete, you can submit DLI jobs to analyze the data.
                                                                                                                                      
+
                                                                                                                                      CDM supports multiple types of data sources, such as databases, data warehouses, and files. You can configure data source migration tasks on the GUI to enhance the efficiency of data migration and integration.
                                                                                                                                      
+
                                                                                                                                      Figure 1 Migrating data to DLI
                                                                                                                                      
+
                                                                                                                                      Data Type Mapping
                                                                                                                                      Refer to Table 1 for data type mapping between data sources and destinations during data migration between DLI and other cloud services and platforms. This will aid in data type conversion and mapping.
                                                                                                                                      
+
+
                                                                                                                                      Table 1 Example of actual CU allocation of an elastic resource pool
                                                                                                                                      Scenario
                                                                                                                                      
 
                                                                                                                                      Resource
                                                                                                                                      
+
                                                                                                                                      Resource Type
                                                                                                                                      
 
                                                                                                                                      CU Range
                                                                                                                                      
+
                                                                                                                                      CU Range
                                                                                                                                      
                                                                                                                                       		
 
                                                                                                                                      
 
                                                                                                                                      New elastic resource pool: 64–112 CUs
                                                                                                                                      
-
                                                                                                                                      Queues A and B are created within the elastic resource pool. The CU ranges of the two queues are:
                                                                                                                                      
-
                                                                                                                                      • CU range of queue A: 16–32 CUs
                                                                                                                                      • CU range of queue B: 16–56 CUs
                                                                                                                                      
+
                                                                                                                                      New elastic resource pool: 64–112 CUs
                                                                                                                                      
+
                                                                                                                                      Queues A and B are created within the elastic resource pool. The CU ranges of the two queues are:
                                                                                                                                      
+
                                                                                                                                      • CU range of queue A: 16–32 CUs
                                                                                                                                      • CU range of queue B: 16–56 CUs
                                                                                                                                      
 
                                                                                                                                      Elastic resource pool
                                                                                                                                      
+
                                                                                                                                      Elastic resource pool
                                                                                                                                      
 
                                                                                                                                      64–112 CUs
                                                                                                                                      
+
                                                                                                                                      64–112 CUs
                                                                                                                                      
                                                                                                                                       		
 
                                                                                                                                      Queue A
                                                                                                                                      
+
                                                                                                                                      Queue A
                                                                                                                                      
 
                                                                                                                                      16–32 CUs
                                                                                                                                      
+
                                                                                                                                      16–32 CUs
                                                                                                                                      
                                                                                                                                       		
 
                                                                                                                                      Queue B
                                                                                                                                      
+
                                                                                                                                      Queue B
                                                                                                                                      
 
                                                                                                                                      16–56 CUs
                                                                                                                                      
+
                                                                                                                                      16-56CUS
                                                                                                                                      
                                                                                                                                       		
 
                                                                                                                                      
                                                                                                                                       
 
 
 
 
 
 
 
 
 
 
 
 
                                                                                                                                      
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                      Table 1 Data type mapping
                                                                                                                                      MySQL
                                                                                                                                      
+
                                                                                                                                      Hive
                                                                                                                                      
+
                                                                                                                                      GaussDB(DWS)
                                                                                                                                      
+
                                                                                                                                      Oracle
                                                                                                                                      
+
                                                                                                                                      PostgreSQL
                                                                                                                                      
+
                                                                                                                                      Hologres
                                                                                                                                      
+
                                                                                                                                      DLI Spark
                                                                                                                                      
+
                                                                                                                                      CHAR
                                                                                                                                      
+
                                                                                                                                      CHAR
                                                                                                                                      
+
                                                                                                                                      CHAR
                                                                                                                                      
+
                                                                                                                                      CHAR
                                                                                                                                      
+
                                                                                                                                      CHAR
                                                                                                                                      
+
                                                                                                                                      CHAR
                                                                                                                                      
+
                                                                                                                                      CHAR
                                                                                                                                      
+
                                                                                                                                      VARCHAR
                                                                                                                                      
+
                                                                                                                                      VARCHAR
                                                                                                                                      
+
                                                                                                                                      VARCHAR
                                                                                                                                      
+
                                                                                                                                      VARCHAR
                                                                                                                                      
+
                                                                                                                                      VARCHAR
                                                                                                                                      
+
                                                                                                                                      VARCHAR
                                                                                                                                      
+
                                                                                                                                      VARCHAR/STRING
                                                                                                                                      
+
                                                                                                                                      DECIMAL
                                                                                                                                      
+
                                                                                                                                      DECIMAL
                                                                                                                                      
+
                                                                                                                                      NUMERIC
                                                                                                                                      
+
                                                                                                                                      NUMERIC
                                                                                                                                      
+
                                                                                                                                      NUMERIC
                                                                                                                                      
+
                                                                                                                                      DECIMAL
                                                                                                                                      
+
                                                                                                                                      DECIMAL
                                                                                                                                      
+
                                                                                                                                      INT
                                                                                                                                      
+
                                                                                                                                      INT
                                                                                                                                      
+
                                                                                                                                      INTEGER
                                                                                                                                      
+
                                                                                                                                      NUMBER
                                                                                                                                      
+
                                                                                                                                      INTEGER
                                                                                                                                      
+
                                                                                                                                      INTEGER
                                                                                                                                      
+
                                                                                                                                      INT
                                                                                                                                      
+
                                                                                                                                      BIGINT
                                                                                                                                      
+
                                                                                                                                      BIGINT
                                                                                                                                      
+
                                                                                                                                      BIGINT
                                                                                                                                      
+
                                                                                                                                      NUMBER
                                                                                                                                      
+
                                                                                                                                      BIGINT
                                                                                                                                      
+
                                                                                                                                      BIGINT
                                                                                                                                      
+
                                                                                                                                      BIGINT/LONG
                                                                                                                                      
+
                                                                                                                                      TINYINT
                                                                                                                                      
+
                                                                                                                                      TINYINT
                                                                                                                                      
+
                                                                                                                                      SMALLINT
                                                                                                                                      
+
                                                                                                                                      NUMBER
                                                                                                                                      
+
                                                                                                                                      SMALLINT
                                                                                                                                      
+
                                                                                                                                      SMALLINT
                                                                                                                                      
+
                                                                                                                                      TINYINT
                                                                                                                                      
+
                                                                                                                                      SMALLINT
                                                                                                                                      
+
                                                                                                                                      SMALLINT
                                                                                                                                      
+
                                                                                                                                      SMALLINT
                                                                                                                                      
+
                                                                                                                                      NUMBER
                                                                                                                                      
+
                                                                                                                                      SMALLINT
                                                                                                                                      
+
                                                                                                                                      SMALLINT
                                                                                                                                      
+
                                                                                                                                      SMALLINT/SHORT
                                                                                                                                      
+
                                                                                                                                      BINARY
                                                                                                                                      
+
                                                                                                                                      BINARY
                                                                                                                                      
+
                                                                                                                                      BYTEA
                                                                                                                                      
+
                                                                                                                                      RAW
                                                                                                                                      
+
                                                                                                                                      BYTEA
                                                                                                                                      
+
                                                                                                                                      BYTEA
                                                                                                                                      
+
                                                                                                                                      BINARY
                                                                                                                                      
+
                                                                                                                                      VARBINARY
                                                                                                                                      
+
                                                                                                                                      BINARY
                                                                                                                                      
+
                                                                                                                                      BYTEA
                                                                                                                                      
+
                                                                                                                                      RAW
                                                                                                                                      
+
                                                                                                                                      BYTEA
                                                                                                                                      
+
                                                                                                                                      BYTEA
                                                                                                                                      
+
                                                                                                                                      BINARY
                                                                                                                                      
+
                                                                                                                                      FLOAT
                                                                                                                                      
+
                                                                                                                                      FLOAT
                                                                                                                                      
+
                                                                                                                                      FLOAT4
                                                                                                                                      
+
                                                                                                                                      FLOAT
                                                                                                                                      
+
                                                                                                                                      DOUBLE
                                                                                                                                      
+
                                                                                                                                      FLOAT4
                                                                                                                                      
+
                                                                                                                                      FLOAT
                                                                                                                                      
+
                                                                                                                                      DOUBLE
                                                                                                                                      
+
                                                                                                                                      DOUBLE
                                                                                                                                      
+
                                                                                                                                      FLOAT8
                                                                                                                                      
+
                                                                                                                                      FLOAT
                                                                                                                                      
+
                                                                                                                                      REAL/DOUBLE
                                                                                                                                      
+
                                                                                                                                      FLOAT8
                                                                                                                                      
+
                                                                                                                                      DOUBLE
                                                                                                                                      
+
                                                                                                                                      DATE
                                                                                                                                      
+
                                                                                                                                      DATE
                                                                                                                                      
+
                                                                                                                                      TIMESTAMP
                                                                                                                                      
+
                                                                                                                                      DATE
                                                                                                                                      
+
                                                                                                                                      DATE
                                                                                                                                      
+
                                                                                                                                      DATE
                                                                                                                                      
+
                                                                                                                                      DATE
                                                                                                                                      
+
                                                                                                                                      TIME
                                                                                                                                      
+
                                                                                                                                      Not supported (use String instead)
                                                                                                                                      
+
                                                                                                                                      TIME
                                                                                                                                      
+
                                                                                                                                      DATE
                                                                                                                                      
+
                                                                                                                                      TIME
                                                                                                                                      
+
                                                                                                                                      TIME
                                                                                                                                      
+
                                                                                                                                      Not supported (use String instead)
                                                                                                                                      
+
                                                                                                                                      DATETIME
                                                                                                                                      
+
                                                                                                                                      TIMESTAMP
                                                                                                                                      
+
                                                                                                                                      TIMESTAMP
                                                                                                                                      
+
                                                                                                                                      TIME
                                                                                                                                      
+
                                                                                                                                      TIME
                                                                                                                                      
+
                                                                                                                                      TIMESTAMP
                                                                                                                                      
+
                                                                                                                                      TIMESTAMP
                                                                                                                                      
+
                                                                                                                                      TINYINT
                                                                                                                                      
+
                                                                                                                                      TINYINT
                                                                                                                                      
+
                                                                                                                                      BOOLEAN
                                                                                                                                      
+
                                                                                                                                      Not supported
                                                                                                                                      
+
                                                                                                                                      TINYINT
                                                                                                                                      
+
                                                                                                                                      BOOLEAN
                                                                                                                                      
+
                                                                                                                                      BOOLEAN
                                                                                                                                      
+
                                                                                                                                      Not supported (use TEXT instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use String instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use TEXT instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use VARCHAR instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use TEXT instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use TEXT instead)
                                                                                                                                      
+
                                                                                                                                      ARRAY
                                                                                                                                      
+
                                                                                                                                      Not supported (use TEXT instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use String instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use TEXT instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use VARCHAR instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use TEXT instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use TEXT instead)
                                                                                                                                      
+
                                                                                                                                      MAP
                                                                                                                                      
+
                                                                                                                                      Not supported (use TEXT instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use String instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use TEXT instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use VARCHAR instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use TEXT instead)
                                                                                                                                      
+
                                                                                                                                      Not supported (use TEXT instead)
                                                                                                                                      
+
                                                                                                                                      STRUCT
                                                                                                                                      
+
                                                                                                                                      
+
                                                                                                                                      
+
                                                                                                                                       
                                                                                                                                      If a service does not support a standard data type, you can use the recommended data type.
                                                                                                                                      
+
                                                                                                                                      
+
                                                                                                                                
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_01_0633.html b/docs/dli/umn/dli_01_0633.html
new file mode 100644
index 000000000..5379b8d06
--- /dev/null
+++ b/docs/dli/umn/dli_01_0633.html
@@ -0,0 +1,172 @@
+
+
+
                                                                                                                                Using CDM to Migrate Data to DLI
                                                                                                                                
+
                                                                                                                                On its GUI, CDM enables you to create data migration tasks from multiple data sources to a data lake.
                                                                                                                                
+
                                                                                                                                This section describes how to use CDM to migrate data from data sources to DLI.
                                                                                                                                
+
                                                                                                                                Figure 1 Process of migrating data to DLI using CDM
                                                                                                                                
+
                                                                                                                                Step 1: Create a CDM Cluster
                                                                                                                                A CDM cluster is used to execute data migration jobs that migrate data from data sources to DLI.
                                                                                                                                
+
                                                                                                                                1. Log in to the DataArts Studio management console and access the page for creating a CDM cluster.
                                                                                                                                2. Set cluster parameters.
                                                                                                                                  • You are advised to set the region, VPC, subnet, security group, and enterprise project to be the same as those of the data source and DLI.
                                                                                                                                  • Once a cluster is created, its specifications cannot be modified. If you need to use higher specifications, you will need to create a cluster.
                                                                                                                                  
+
                                                                                                                                  For more information about CDM cluster parameters, see DataArts Studio User Guide.
                                                                                                                                  
+
                                                                                                                                3. Click Buy Now.
                                                                                                                                4. Confirm the settings and click Submit. The system starts to create a CDM cluster. You can check the creation progress on the Cluster Management page.
                                                                                                                                
+
                                                                                                                                
+
                                                                                                                                Step 2: Create a Data Connection Between the Data Source and CDM
                                                                                                                                This step uses the MySQL data source as an example to describe how to create a data connection between the data source and CDM.
                                                                                                                                
+
                                                                                                                                1. In the navigation pane on the left of the CDM console, choose Cluster Management. Locate the cdm-aff1 cluster created in Step 1: Create a CDM Cluster.
                                                                                                                                2. Click Job Management in the Operation column.
                                                                                                                                3. Click the Link Management tab then Create Link.
                                                                                                                                1. Select RDS for MySQL and click Next to set the link parameters.
                                                                                                                                  Click Show Advanced Attributes to show optional parameters.
                                                                                                                                  
+
                                                                                                                                  Retain the default values for the optional parameters and set the mandatory parameters based on Table 1.
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 1 MySQL link parameters
                                                                                                                                  Parameter
                                                                                                                                  
+
                                                                                                                                  Description
                                                                                                                                  
+
                                                                                                                                  Example Value
                                                                                                                                  
+
                                                                                                                                  Name
                                                                                                                                  
+
                                                                                                                                  Enter a unique link name.
                                                                                                                                  
+
                                                                                                                                  mysqllink
                                                                                                                                  
+
                                                                                                                                  Database Server
                                                                                                                                  
+
                                                                                                                                  IP address or domain name of the MySQL database
                                                                                                                                  
+
                                                                                                                                  -
                                                                                                                                  
+
                                                                                                                                  Port
                                                                                                                                  
+
                                                                                                                                  Port number of the MySQL database
                                                                                                                                  
+
                                                                                                                                  3306
                                                                                                                                  
+
                                                                                                                                  Database Name
                                                                                                                                  
+
                                                                                                                                  Name of the MySQL database
                                                                                                                                  
+
                                                                                                                                  sqoop
                                                                                                                                  
+
                                                                                                                                  Username
                                                                                                                                  
+
                                                                                                                                  User who has the read, write, and delete permissions on the MySQL database
                                                                                                                                  
+
                                                                                                                                  admin
                                                                                                                                  
+
                                                                                                                                  Password
                                                                                                                                  
+
                                                                                                                                  Password of the user
                                                                                                                                  
+
                                                                                                                                  -
                                                                                                                                  
+
                                                                                                                                  Use Local API
                                                                                                                                  
+
                                                                                                                                  Whether to use the local API of the database for acceleration. (The system attempts to enable the local_infile system variable of the MySQL database.)
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Use Agent
                                                                                                                                  
+
                                                                                                                                  This parameter does not need to be set as the agent function will be unavailable soon.
                                                                                                                                  
+
                                                                                                                                  -
                                                                                                                                  
+
                                                                                                                                  local_infile Character Set
                                                                                                                                  
+
                                                                                                                                  When using local_infile to import data to MySQL, you can set the encoding format.
                                                                                                                                  
+
                                                                                                                                  utf8
                                                                                                                                  
+
                                                                                                                                  Driver Version
                                                                                                                                  
+
                                                                                                                                  Before connecting CDM to a relational database, you need to upload the JDK 8 .jar driver of the relational database. Download the MySQL driver 5.1.48 from https://downloads.mysql.com/archives/c-j/, obtain mysql-connector-java-5.1.48.jar, and upload it.
                                                                                                                                  
+
                                                                                                                                  -
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                2. Click Test to check whether the parameters are correctly configured. If the test is successful, click Save to create the link and return to the Links page.
                                                                                                                                
+
                                                                                                                                
+
                                                                                                                                Step 3: Create a Data Connection Between CDM and DLI
                                                                                                                                1. In the navigation pane on the left of the CDM console, choose Cluster Management. Locate the cdm-aff1 cluster created in Step 1: Create a CDM Cluster.
                                                                                                                                2. Click Job Management in the Operation column.
                                                                                                                                3. Click the Link Management tab then Create Link.
                                                                                                                                1. Select Data Lake Insight for Data Warehouse and click Next. On the displayed page, set DLI link parameters.
                                                                                                                                  Click Show Advanced Attributes to show optional parameters. Retain the default values. Table 2 describes the mandatory parameters.
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 2 DLI link parameters
                                                                                                                                  Parameter
                                                                                                                                  
+
                                                                                                                                  Description
                                                                                                                                  
+
                                                                                                                                  Example Value
                                                                                                                                  
+
                                                                                                                                  Name
                                                                                                                                  
+
                                                                                                                                  Link name, which should be defined based on the data source type, so it is easier to remember what the link is for
                                                                                                                                  
+
                                                                                                                                  dlilink
                                                                                                                                  
+
                                                                                                                                  Access Key
                                                                                                                                  
+
                                                                                                                                  AK/SK required for authentication during access to the DLI database.
                                                                                                                                  
+
                                                                                                                                  You need to create an access key for the current account and obtain an AK/SK pair.
                                                                                                                                  
+
                                                                                                                                  -
                                                                                                                                  
+
                                                                                                                                  Secret Key
                                                                                                                                  
+
                                                                                                                                  -
                                                                                                                                  
+
                                                                                                                                  Project ID
                                                                                                                                  
+
                                                                                                                                  Project ID of the region where DLI is
                                                                                                                                  
+
                                                                                                                                  -
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                2. Click Test to check whether the parameters are correctly configured. If the test is successful, click Save to create the link and return to the Links page.
                                                                                                                                
+
                                                                                                                                
+
                                                                                                                                Step 4: Create a Data Migration Job on CDM
                                                                                                                                After establishing the data connection between the data source and CDM, as well as between CDM and DLI, you need to create a data migration job to migrate the data from the data source to DLI.
                                                                                                                                
+
                                                                                                                                1. On the Cluster Management page, locate the cdm-aff1 cluster created in Step 1: Create a CDM Cluster.
                                                                                                                                2. Click Job Management in the Operation column.
                                                                                                                                3. Click the Table/File Migration tab, click Create Job, and configure basic job information.
                                                                                                                                  • Job Name: Enter a unique job name, for example, mysql2dli.
                                                                                                                                  • Source job parameters
                                                                                                                                    • Source Link Name: Select the MySQL link mysqllink.
                                                                                                                                    • Use SQL: Select No.
                                                                                                                                    • Schema/Tablespace: Select the MySQL database from which the table is to be exported.
                                                                                                                                    • Table Name: Select the table from which data is to be exported.
                                                                                                                                    • Retain the default values for other parameters.
                                                                                                                                    
+
                                                                                                                                  • Destination job parameters
                                                                                                                                    • Destination Link Name: Select the DLI link dlilink.
                                                                                                                                    • Schema/Tablespace: Select the schema to which data is to be imported.
                                                                                                                                    • Auto Table Creation: Select Auto creation. If the table specified by Table Name does not exist, CDM automatically creates the table in DLI.
                                                                                                                                    • Table Name: Select the table to which data is to be imported.
                                                                                                                                    • Advanced Attributes > Extend Field Length: Select Yes.
                                                                                                                                    • Retain the default values for other parameters.
                                                                                                                                    
+
                                                                                                                                  
+
                                                                                                                                4. Click Next. The Map Field tab page is displayed. CDM automatically maps the fields in the source and destination data tables. You need to check if the field mapping is correct.
                                                                                                                                  • If the mapping is incorrect, click the row where the field is located and hold down the left mouse button to drag the field to adjust the mapping.
                                                                                                                                  • When importing data into DLI, you must manually choose the distribution columns. You are advised to select the distribution columns based on the following principles:
                                                                                                                                    1. Use the primary key as the distribution column.
                                                                                                                                    2. If multiple data segments are combined as primary keys, specify all primary keys as the distribution column.
                                                                                                                                    3. In the scenario where no primary key is available, if no distribution column is selected, DWS uses the first column as the distribution column by default. As a result, data skew risks exist.
                                                                                                                                    
+
                                                                                                                                  • To convert the content of the source fields, perform the operations in this step. In this example, field conversion is not required.
                                                                                                                                  
+
                                                                                                                                5. Click Next and set task parameters. Typically, retain the default values for all parameters.
                                                                                                                                  In this step, you can configure the following optional features:
                                                                                                                                  • Retry Upon Failure: If the job fails to be executed, you can determine whether to automatically retry. Retain the default value Never.
                                                                                                                                  • Group: Select the group to which the job belongs. The default group is DEFAULT. On the Job Management page, jobs can be displayed, started, or exported by group.
                                                                                                                                  • Schedule Execution: Determine whether to automatically execute the job at a scheduled time. Retain the default value No.
                                                                                                                                  • Concurrent Extractors: Enter the number of concurrent extractors. An appropriate value improves migration efficiency. Retain the default value 1.
                                                                                                                                  • Write Dirty Data: Specify this parameter if data that fails to be processed or filtered out during job execution needs to be written to OBS for future viewing. Before writing dirty data, create an OBS link on the CDM console. Retain the default value No, meaning dirty data is not recorded.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                6. Click Save and Run. CDM starts to execute the job immediately.
                                                                                                                                
+
                                                                                                                                
+
                                                                                                                                Step 5: View Data Migration Results
                                                                                                                                This step describes how to view a job's execution results and its historical information within the past 90 days, including the number of written rows, read rows, written bytes, written files, and log information.
                                                                                                                                
+
                                                                                                                                • Viewing the status of the migration job on CDM
                                                                                                                                  1. On the Cluster Management page, locate the cdm-aff1 cluster created in Step 1: Create a CDM Cluster.
                                                                                                                                  2. Click Job Management in the Operation column.
                                                                                                                                  3. Locate the mysql2dli job created in Step 4: Create a Data Migration Job on CDM and check its execution status. If the job status is Succeeded, the migration is successful.
                                                                                                                                  
+
                                                                                                                                
+
                                                                                                                                • Viewing data migration results on DLI
                                                                                                                                  1. After the CDM migration job is complete, log in to the DLI management console.
                                                                                                                                  2. In the navigation pane on the left, choose SQL Editor.
                                                                                                                                    Set Engine to Spark, Queues to the created SQL queue, and Databases to the created database. Run the following DLI table query statement to check whether the MySQL data has been successfully migrated to the DLI table:
                                                                                                                                    select * from tablename;
                                                                                                                                    
+
                                                                                                                                    
+
                                                                                                                                  
+
                                                                                                                                
+
                                                                                                                                
+
                                                                                                                                
+
+
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_01_0634.html b/docs/dli/umn/dli_01_0634.html
index 7d34ff539..e853ca370 100644
--- a/docs/dli/umn/dli_01_0634.html
+++ b/docs/dli/umn/dli_01_0634.html
@@ -12,16 +12,12 @@
 
 
                                                                                                                              5. Configuring the Network Connection Between DLI and Data Sources (Enhanced Datasource Connection)
                                                                                                                                
 
                                                                                                                                6. 
-
                                                                                                                              6. Using DEW to Manage Access Credentials for Data Sources
                                                                                                                                
+
                                                                                                                              7. Managing Data Source Access Credentials Using DEW
                                                                                                                                
 
                                                                                                                                8. 
 
                                                                                                                              8. Using DLI Datasource Authentication to Manage Access Credentials for Data Sources
                                                                                                                                
 
                                                                                                                                9. 
 
                                                                                                                              9. Managing Enhanced Datasource Connections
                                                                                                                                
 
                                                                                                                                10. 
 
-
-
                                                                                                                                
-
                                                                                                                                Parent topic: Data Migration and Transmission
                                                                                                                                
-
                                                                                                                                
 
 
diff --git a/docs/dli/umn/dli_01_0635.html b/docs/dli/umn/dli_01_0635.html
index 9f16ea3a5..be696acaa 100644
--- a/docs/dli/umn/dli_01_0635.html
+++ b/docs/dli/umn/dli_01_0635.html
@@ -4,7 +4,7 @@
 
                                                                                                                                To read and write external data sources when running DLI jobs, two conditions must be met:
                                                                                                                                
 
                                                                                                                                • Establish network connectivity between DLI and the external data source to ensure that the DLI queue is connected to the data source network.
                                                                                                                                • Securely store the access credentials for the data source to ensure authentication security and facilitate secure DLI access to the data source.
                                                                                                                                
 
                                                                                                                                This section describes how to configure DLI to read and write external data sources.
                                                                                                                                
-
                                                                                                                                • Configure network connection between DLI and the data source by referring to Configuring the Network Connection Between DLI and Data Sources (Enhanced Datasource Connection).
                                                                                                                                • Manage credentials for DLI to access data sources.
                                                                                                                                  • Spark 3.3.1 or later and Flink 1.15 or later jobs accessing data sources using datasource connections
                                                                                                                                    • You are advised to use Data Encryption Workshop (DEW) to store authentication information of data sources, addressing data security, key security, and complex key management issues.
                                                                                                                                      For details, see Using DEW to Manage Access Credentials for Data Sources.
                                                                                                                                      
+
diff --git a/docs/dli/umn/dli_01_0636.html b/docs/dli/umn/dli_01_0636.html
index f797b62b5..8c837a32c 100644
--- a/docs/dli/umn/dli_01_0636.html
+++ b/docs/dli/umn/dli_01_0636.html
@@ -1,30 +1,13 @@
 
 
-
                                                                                                                                      Using DEW to Manage Access Credentials for Data Sources
                                                                                                                                      
-
                                                                                                                                      When using DLI to submit jobs that involve reading and writing data from external sources, it is crucial to securely access these sources by properly storing their access credentials. This ensures the authentication of the data source and enables secure access by DLI. DEW is a comprehensive cloud-based encryption service that addresses data security, key security, and complex key management issues. This section describes how to use DEW to store authentication information for a data source.
                                                                                                                                      
-
                                                                                                                                      
-
                                                                                                                                      Creating a Shared Secret in DEW
                                                                                                                                      This example describes how to configure a credential for accessing RDS DB instances in a DLI job and store the credential in DEW.
                                                                                                                                      1. Log in to the DEW management console.
                                                                                                                                      2. In the navigation pane on the left, choose Cloud Secret Management Service > Secrets.
                                                                                                                                      3. Click Create Secret. On the displayed page, configure basic secret information.
                                                                                                                                        • Secret Name: Enter a secret name. In this example, the name is secretInfo.
                                                                                                                                        • Secret Value: Enter the username and password for logging in to the RDS for MySQL DB instance.
                                                                                                                                          • The key in the first line is MySQLUsername, and the value is the username for logging in to the DB instance.
                                                                                                                                          • The key in the second line is MySQLPassword, and the value is the password for logging in to the DB instance.
                                                                                                                                          
-
                                                                                                                                        
-
                                                                                                                                      4. Set other parameters as required and click OK.
                                                                                                                                        
-
                                                                                                                                      
-
                                                                                                                                      
-
                                                                                                                                      
-
                                                                                                                                      Using the Secret Created in DEW in a DLI Job
                                                                                                                                      This part uses a Flink job as an example to describe how to use credentials created in DEW.
                                                                                                                                      
-
                                                                                                                                      WITH (  
- 'connector' = 'jdbc',  
-  'url? = 'jdbc:mysql://MySQLAddress:MySQLPort/flink',--flink is the MySQL database where the orders table locates.
- 'table-name' = 'orders',  
- 'username' = 'MySQLUsername',  -- Shared secret in DEW whose name is secretInfo and version is v1. The key MySQLUsername defines the secret value. The value is the user's sensitive information.
- 'password' = 'MySQLPassword',  -- Shared secret in DEW whose name is secretInfo and version is v1. The key MySQLPassword defines the secret value. The value is the user's sensitive information.
- 'sink.buffer-flush.max-rows' = '1',
- 'dew.endpoint'='kms.xxxx.com', --Endpoint information for the DEW service being used
- 'dew.csms.secretName'='secretInfo', --Name of the DEW shared secret
- 'dew.csms.decrypt.fields'='username,password', --The password field value must be decrypted and replaced using DEW secret management.
- 'dew.csms.version'='v1'
-);
                                                                                                                                      
-
                                                                                                                                      
-
                                                                                                                                      
+
                                                                                                                                      Managing Data Source Access Credentials Using DEW
                                                                                                                                      
+
                                                                                                                                      
 
                                                                                                                                      
+
+
 
                                                                                                                                      
 
                                                                                                                                      Parent topic: Configuring DLI to Read and Write Data from and to External Data Sources
                                                                                                                                      
 
                                                                                                                                      
diff --git a/docs/dli/umn/dli_01_0637.html b/docs/dli/umn/dli_01_0637.html
index 0f55c753c..a1bcdb22e 100644
--- a/docs/dli/umn/dli_01_0637.html
+++ b/docs/dli/umn/dli_01_0637.html
@@ -8,7 +8,7 @@
 
                                                                                                                                      
 
                                                                                                                                      Prerequisites
                                                                                                                                      Before the configuration, create an OBS bucket or parallel file system (PFS). In big data scenarios, you are advised to create a PFS. PFS is a high-performance file system provided by OBS, with access latency in milliseconds. PFS can achieve a bandwidth performance of up to TB/s and millions of IOPS, which makes it ideal for processing high-performance computing (HPC) workloads.
                                                                                                                                      
 
                                                                                                                                      
-
                                                                                                                                      Configuring a Bucket for DLI Jobs
                                                                                                                                      1. In the navigation pane of the DLI console, choose Global Configuration > Project.
                                                                                                                                      2. On the Project page, click  next to Job Bucket to configure bucket information.
                                                                                                                                      3. Click  to view available buckets.
                                                                                                                                      4. In the displayed OBS dialog box, click the name of a bucket or search for and click a bucket name and then click OK. In the Set Job Bucket dialog box, click OK.
                                                                                                                                        Temporary data generated during DLI job running will be stored in the OBS bucket.
                                                                                                                                        
+
                                                                                                                                        Configuring a Bucket for DLI Jobs
                                                                                                                                        1. In the navigation pane of the DLI console, choose Global Configuration > Project.
                                                                                                                                        2. On the Project page, click  next to Job Bucket to configure bucket information.
                                                                                                                                        3. Click  to view available buckets.
                                                                                                                                        4. In the displayed OBS dialog box, click the name of a bucket or search for and click a bucket name and then click OK. In the Set Job Bucket dialog box, click OK.
                                                                                                                                          Temporary data generated during DLI job running will be stored in the OBS bucket.
                                                                                                                                          
 
                                                                                                                                        
 
                                                                                                                                        
 
                                                                                                                                        Querying Logs for SQL Jobs
                                                                                                                                        1. Log in to the DLI console. In the navigation pane on the left, choose Job Management > SQL Jobs.
                                                                                                                                        2. Select the SQL job whose jobs you want to query, click More in the Operation column, and select View Log.
                                                                                                                                          The system automatically switches to the log path of the DLI job bucket.
                                                                                                                                          
@@ -17,7 +17,14 @@
 
                                                                                                                                        
 
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_01_0638.html b/docs/dli/umn/dli_01_0638.html
index 081d0edb4..06d7b4d64 100644
--- a/docs/dli/umn/dli_01_0638.html
+++ b/docs/dli/umn/dli_01_0638.html
@@ -12,7 +12,7 @@
 
                                                                                                                                      
 
 
diff --git a/docs/dli/umn/dli_01_0650.html b/docs/dli/umn/dli_01_0650.html
index ee1a0d79f..d10d537a0 100644
--- a/docs/dli/umn/dli_01_0650.html
+++ b/docs/dli/umn/dli_01_0650.html
@@ -6,7 +6,7 @@
 
                                                                                                                                       
                                                                                                                                      You can set the priority for Flink 1.12 or later jobs.
                                                                                                                                      
 
                                                                                                                                      
 
                                                                                                                                
-
                                                                                                                                Notes
                                                                                                                                • You can assign a priority level of 1 to 10 for each job, with a larger value indicating a higher priority. Compute resources are preferentially allocated to high-priority jobs. That is, if compute resources required for high-priority jobs are insufficient, compute resources for low-priority jobs are reduced.
                                                                                                                                • Flink jobs running on a general-purpose queue have a default priority level of 5.
                                                                                                                                • The job priority change will only be in effect once the job has been stopped, edited, and resubmitted.
                                                                                                                                • You can set the priority for Flink jobs only after enabling dynamic scaling by setting flink.dli.job.scale.enable to true. For details, see Enabling Dynamic Scaling for Flink Jobs.
                                                                                                                                • To change the priority for a job, you must first stop the job, change the priority level, and then submit the job for the modification to take effect.
                                                                                                                                
+
                                                                                                                                Notes
                                                                                                                                • Priorities cannot be set for jobs running in queues within an elastic resource pool of the basic edition.
                                                                                                                                • You can assign a priority level of 1 to 10 for each job, with a larger value indicating a higher priority. Compute resources are preferentially allocated to high-priority jobs. That is, if compute resources required for high-priority jobs are insufficient, compute resources for low-priority jobs are reduced.
                                                                                                                                • Flink jobs running on a general-purpose queue have a default priority level of 5.
                                                                                                                                • The job priority change will only be in effect once the job has been stopped, edited, and resubmitted.
                                                                                                                                • You can set the priority for Flink jobs only after enabling dynamic scaling by setting flink.dli.job.scale.enable to true. For details, see Enabling Dynamic Scaling for Flink Jobs.
                                                                                                                                • To change the priority for a job, you must first stop the job, change the priority level, and then submit the job for the modification to take effect.
                                                                                                                                
 
                                                                                                                                
 
                                                                                                                                Setting the Priority for a Flink OpenSource SQL Job
                                                                                                                                1. Log in to the DLI management console.
                                                                                                                                2. In the navigation pane on the left, choose Job Management > Flink Jobs.
                                                                                                                                3. Select the job for which you want to set the priority and click Edit in the Operation column.
                                                                                                                                4. On the far right of the displayed page, click Runtime Configuration.
                                                                                                                                5. Enter statements in the text box to enable dynamic scaling and then set the job priority.
                                                                                                                                   
                                                                                                                                  To set the priority for Flink jobs, you must first enable dynamic scaling by setting flink.dli.job.scale.enable to true.
                                                                                                                                  
 
                                                                                                                                  For more parameter settings, see Enabling Dynamic Scaling for Flink Jobs.
                                                                                                                                  
diff --git a/docs/dli/umn/dli_01_0651.html b/docs/dli/umn/dli_01_0651.html
index 59fa8da7a..32a2207e5 100644
--- a/docs/dli/umn/dli_01_0651.html
+++ b/docs/dli/umn/dli_01_0651.html
@@ -8,7 +8,7 @@
 
                                                                                                                                  
 
                                                                                                                                  Prerequisites
                                                                                                                                  Before the configuration, create an OBS bucket or parallel file system (PFS). In big data scenarios, you are advised to create a PFS. PFS is a high-performance file system provided by OBS, with access latency in milliseconds. PFS can achieve a bandwidth performance of up to TB/s and millions of IOPS, which makes it ideal for processing high-performance computing (HPC) workloads.
                                                                                                                                  
 
                                                                                                                                  
-
                                                                                                                                  Configuring a Bucket for DLI Jobs
                                                                                                                                  1. In the navigation pane of the DLI console, choose Global Configuration > Project.
                                                                                                                                  2. On the Project page, click  next to Job Bucket to configure bucket information.
                                                                                                                                  3. Click  to view available buckets.
                                                                                                                                  4. In the displayed OBS dialog box, click the name of a bucket or search for and click a bucket name and then click OK. In the Set Job Bucket dialog box, click OK.
                                                                                                                                    Temporary data generated during DLI job running will be stored in the OBS bucket.
                                                                                                                                    
+
                                                                                                                                    Configuring a Bucket for DLI Jobs
                                                                                                                                    1. In the navigation pane of the DLI console, choose Global Configuration > Project.
                                                                                                                                    2. On the Project page, click  next to Job Bucket to configure bucket information.
                                                                                                                                    3. Click  to view available buckets.
                                                                                                                                    4. In the displayed OBS dialog box, click the name of a bucket or search for and click a bucket name and then click OK. In the Set Job Bucket dialog box, click OK.
                                                                                                                                      Temporary data generated during DLI job running will be stored in the OBS bucket.
                                                                                                                                      
 
                                                                                                                                    
 
                                                                                                                                    
 
                                                                                                                                    Viewing Commit Logs
                                                                                                                                    You can check commit logs to locate commit faults.
                                                                                                                                    
@@ -17,9 +17,12 @@
 
                                                                                                                                    Viewing Run Logs
                                                                                                                                    You can check run logs to locate job running faults.
                                                                                                                                    
 
                                                                                                                                    1. In the navigation pane of the DLI console, choose Job Management > Flink Jobs.
                                                                                                                                    2. Click the name of the Flink job whose commit logs you want to check.
                                                                                                                                    3. Click the Run Log tab and check the JobManager and TaskManager information of the running job.
                                                                                                                                      JobManager and TaskManager information is updated every minute. By default, the run logs generated in the last minute are displayed.
                                                                                                                                      
 
                                                                                                                                      If you have configured an OBS bucket to store job logs, you can access it to download and check historical logs.
                                                                                                                                      
-
                                                                                                                                      If the job is not running, you cannot check Task Manager information.
                                                                                                                                      
+
                                                                                                                                      If the job is not running, you cannot check TaskManager information.
                                                                                                                                      
 
                                                                                                                                    
 
                                                                                                                                    
+
                                                                                                                                    Viewing the Log List
                                                                                                                                    You can view historical job files by viewing the Flink job log list.
                                                                                                                                    
+
                                                                                                                                    1. In the navigation pane of the DLI console, choose Job Management > Flink Jobs.
                                                                                                                                    2. Click the name of your desired job.
                                                                                                                                    3. On the Logs tab page, choose Job Manager and Task Manager separately to view their logs.
                                                                                                                                    
+
                                                                                                                                    
 
                                                                                                                                    
 
                                                                                                                                    
 
                                                                                                                                    
@@ -27,3 +30,10 @@
 
                                                                                                                                    
 
                                                                                                                                    
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_01_0652.html b/docs/dli/umn/dli_01_0652.html
index a6614def7..40eaaa805 100644
--- a/docs/dli/umn/dli_01_0652.html
+++ b/docs/dli/umn/dli_01_0652.html
@@ -6,7 +6,7 @@
 
                                                                                                                                     
                                                                                                                                    You can set the priority for Spark 2.4.5 or later jobs.
                                                                                                                                    
 
                                                                                                                                    
 
                                                                                                                                  
-
                                                                                                                                  Notes
                                                                                                                                  • You can assign a priority level of 1 to 10 for each job, with a larger value indicating a higher priority. Compute resources are preferentially allocated to high-priority jobs. That is, if compute resources required for high-priority jobs are insufficient, compute resources for low-priority jobs are reduced.
                                                                                                                                  • Spark jobs running on a general-purpose queue have a default priority level of 3.
                                                                                                                                  • To change the priority for a job, you must first stop the job, change the priority level, and then submit the job for the modification to take effect.
                                                                                                                                  
+
                                                                                                                                  Notes
                                                                                                                                  • Priorities cannot be set for jobs running in queues within an elastic resource pool of the basic edition.
                                                                                                                                  • You can assign a priority level of 1 to 10 for each job, with a larger value indicating a higher priority. Compute resources are preferentially allocated to high-priority jobs. That is, if compute resources required for high-priority jobs are insufficient, compute resources for low-priority jobs are reduced.
                                                                                                                                  • Spark jobs running on a general-purpose queue have a default priority level of 3.
                                                                                                                                  • To change the priority for a job, you must first stop the job, change the priority level, and then submit the job for the modification to take effect.
                                                                                                                                  
 
                                                                                                                                  
 
                                                                                                                                  Procedure
                                                                                                                                  Enter the following statement in the Spark Arguments(--conf) text box, where x indicates the priority value:
                                                                                                                                  
 
                                                                                                                                  spark.dli.job.priority=x
                                                                                                                                  
@@ -15,7 +15,7 @@
 
                                                                                                                                  
 
 
diff --git a/docs/dli/umn/dli_01_0661.html b/docs/dli/umn/dli_01_0661.html
index a7b4e3f8d..da67210de 100644
--- a/docs/dli/umn/dli_01_0661.html
+++ b/docs/dli/umn/dli_01_0661.html
@@ -1,16 +1,13 @@
 
 
-
-  
                                                                                                                                  Data Migration and Transmission
                                                                                                                                  
-
-  
                                                                                                                                  
+
                                                                                                                                  Data Import and Migration
                                                                                                                                  
+
                                                                                                                                  
 
                                                                                                                                  
-
 
diff --git a/docs/dli/umn/dli_01_0662.html b/docs/dli/umn/dli_01_0662.html
index 18b7b0fec..97c5100f0 100644
--- a/docs/dli/umn/dli_01_0662.html
+++ b/docs/dli/umn/dli_01_0662.html
@@ -1,16 +1,28 @@
 
 
 
                                                                                                                                  Overview
                                                                                                                                  
-
                                                                                                                                  Importing Data to OBS
                                                                                                                                  DLI enables direct access to data stored in OBS for query and analysis, eliminating the need for data migration.
                                                                                                                                  
+
                                                                                                                                  Importing Data to an OBS Table
                                                                                                                                  DLI enables direct access to data stored in OBS for query and analysis, eliminating the need for data migration.
                                                                                                                                  
 
                                                                                                                                  To begin using DLI for data analysis, just import your local data into OBS.
                                                                                                                                  
 
                                                                                                                                  
+
                                                                                                                                  Migrating Data to DLI
                                                                                                                                  To centrally analyze and manage scattered data from various systems, you can utilize migration tools like Cloud Data Migration (CDM) to migrate the data to DLI. Once the migration is complete, you can submit DLI jobs to analyze the data.
                                                                                                                                  
+
                                                                                                                                  CDM supports multiple types of data sources, such as databases, data warehouses, and files. You can configure data source migration tasks on the GUI to enhance the efficiency of data migration and integration.
                                                                                                                                  
+
                                                                                                                                  For details, see Migrating Data from External Data Sources to DLI.
                                                                                                                                  
+
                                                                                                                                  Figure 1 Migrating data to DLI
                                                                                                                                  
+
                                                                                                                                  
 
                                                                                                                                  Configuring DLI to Read and Write External Data Sources
                                                                                                                                  If you prefer not to import data into OBS or DLI tables, DLI offers cross-source access capabilities, allowing you to connect to data sources for analysis without the need to migrate the data.
                                                                                                                                  
 
                                                                                                                                  For details, see Configuring DLI to Read and Write External Data Sources.
                                                                                                                                  
 
                                                                                                                                  
 
                                                                                                                                  
 
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_01_0664.html b/docs/dli/umn/dli_01_0664.html
deleted file mode 100644
index 319faf50a..000000000
--- a/docs/dli/umn/dli_01_0664.html
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
                                                                                                                                  Using AOM to Monitor DLI
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
-
diff --git a/docs/dli/umn/dli_01_0665.html b/docs/dli/umn/dli_01_0665.html
deleted file mode 100644
index 49a86821b..000000000
--- a/docs/dli/umn/dli_01_0665.html
+++ /dev/null
@@ -1,118 +0,0 @@
-
-
-
                                                                                                                                  Connecting DLI to AOM's Prometheus Monitoring
                                                                                                                                  
-
                                                                                                                                  AOM's Prometheus Monitoring is a comprehensive solution that integrates with the open source Prometheus ecosystem. It supports monitoring of various types of components, provides pre-configured monitoring dashboards, and offers fully managed Prometheus services. It uses Prometheus monitoring to collect, store, and display data from monitored objects, making it suitable for collecting and processing time series databases, especially for monitoring Flink jobs.
                                                                                                                                  
-
                                                                                                                                  This section describes how to connect DLI to AOM Prometheus for monitoring.
                                                                                                                                  
-
                                                                                                                                  Notes
                                                                                                                                  • Only Flink 1.15 supports the connection to AOM's Prometheus Monitoring.
                                                                                                                                  • A general-purpose AOM Prometheus cluster has been created.
                                                                                                                                  • Only common AOM Prometheus instances are supported.
                                                                                                                                  • After an elastic resource pool is connected to a Prometheus instance, the metrics of all newly submitted Flink 1.15 jobs in the elastic resource pool are reported to the bound Prometheus instance. Only basic metrics are reported by default. To report all metrics, set the metrics.reporter.remote.report-all-metrics parameter in Configuration Items for Connecting DLI to AOM's Prometheus Monitoring.
                                                                                                                                  • The default reporting interval for DLI Flink metrics is 30 seconds, resulting in a slight delay in metric reporting. To adjust the reporting interval, set the metrics.reporter.remote.interval parameter in Configuration Items for Connecting DLI to AOM's Prometheus Monitoring.
                                                                                                                                    To prevent frequent metric reporting, you are advised not to set this parameter to a small value. The recommended interval is 30 seconds.
                                                                                                                                    
-
                                                                                                                                  • In Flink 1.15 or later, after an elastic resource pool is unbound from a Prometheus instance, metrics for new jobs are no longer reported to that instance. However, metrics for submitted jobs will continue to be reported until those jobs are completed.
                                                                                                                                  • In Flink 1.15 or later, if the bound Prometheus instance is changed, metrics for new jobs will be reported to the new instance. However, metrics for submitted jobs will continue to be reported to the original instance until those jobs are completed.
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  Step 1: Create an AOM Prometheus Instance
                                                                                                                                  1. Log in to the AOM 2.0 management console.
                                                                                                                                  2. In the navigation pane on the left, choose Prometheus Monitoring > Instances. On the displayed page, click Add Prometheus Instance.
                                                                                                                                  3. Set the instance name, enterprise project, and instance type.
-
                                                                                                                                    
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                                                                                    Table 1 Creating a Prometheus instance
                                                                                                                                    Parameter
                                                                                                                                    
-
                                                                                                                                    Description
                                                                                                                                    
-
                                                                                                                                    Instance Name
                                                                                                                                    
-
                                                                                                                                    Prometheus instance name.
                                                                                                                                    
-
                                                                                                                                    Enterprise Project
                                                                                                                                    
-
                                                                                                                                    Enterprise project name.
                                                                                                                                    
-
                                                                                                                                    • If you have not changed the default value ALL for Enterprise Project in the left navigation pane of the console, select an enterprise project from the drop-down list on this panel.
                                                                                                                                    • If you have manually chosen a value other than ALL for Enterprise Project, this parameter is automatically populated and cannot be modified.
                                                                                                                                    
-
                                                                                                                                    Instance Type
                                                                                                                                    
-
                                                                                                                                    Type of the Prometheus instance. Select Common Prometheus Instance.
                                                                                                                                    
-
                                                                                                                                    
-
                                                                                                                                    
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  Step 2: Bind an Elastic Resource to an AOM Prometheus Cluster
                                                                                                                                  1. Log in to the DLI management console. In the navigation pane on the left, choose Resources > Resource Pool.
                                                                                                                                  2. Locate the elastic resource pool you want to bind, click More in the Operation column, and select Prometheus > Bind Prometheus Instance.
                                                                                                                                  3. In the dialog box that appears, select the Prometheus cluster created in Step 1: Create an AOM Prometheus Instance.
                                                                                                                                  4. Click OK.
                                                                                                                                    Once bound, monitoring metrics for newly submitted jobs are reported to AOM and billed based on AOM billing rules.
                                                                                                                                    
-
                                                                                                                                     
                                                                                                                                    To bind an elastic resource pool to a Prometheus instance, you must have the permission to access AOM Prometheus. Otherwise, your binding fails.
                                                                                                                                    
-
                                                                                                                                    The permissions include:
                                                                                                                                    • aom:prometheusInstances:list
                                                                                                                                    • aom:metric:list
                                                                                                                                    • aom:metric:get
                                                                                                                                    
-
                                                                                                                                    
-
                                                                                                                                    
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  Step 3: Create and Submit a Flink Job
                                                                                                                                  Create a Flink job by referring to Creating a Flink OpenSource SQL Job.
                                                                                                                                  
-
                                                                                                                                  Set Flink Version to 1.15. Only Flink 1.15 or later supports AOM monitoring.
                                                                                                                                  
-
                                                                                                                                  After approximately 30 seconds of running the job, the system reports the job's monitoring metrics to the AOM Prometheus instance.
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  Step 4: View Monitoring Metrics on the AOM Dashboard
                                                                                                                                  For the Prometheus monitoring metrics supported by DLI, see Basic Monitoring Metrics Reported by DLI to Prometheus.
                                                                                                                                  
-
                                                                                                                                  Open an AOM dashboard to view monitoring metrics. You can use either of the following methods to switch to the AOM console:
                                                                                                                                  • Method 1: Switching from the DLI management console to AOM's Dashboard page
                                                                                                                                    1. Log in to the DLI management console. In the navigation pane on the left, choose Job Management > Flink Jobs.
                                                                                                                                    2. On the displayed page, click the name of the job whose monitoring metrics you want to view.
                                                                                                                                    3. On the Job Details tab, click More in the upper right corner and select Prometheus Monitoring.
                                                                                                                                      AOM's Dashboard page is displayed.
                                                                                                                                      
-
                                                                                                                                    
-
                                                                                                                                  • Method 2: Viewing monitoring metrics on AOM's preset dashboard
                                                                                                                                    1. Log in to the AOM 2.0 management console.
                                                                                                                                    2. In the navigation pane on the left, choose Dashboard > Dashboard.
                                                                                                                                      In the navigation pane of the Dashboard page, choose System > Applications. On the displayed page, find the dashboard with type of DLI_FLINK.
                                                                                                                                      
-
                                                                                                                                    3. Click the name of the dashboard to access its details.
                                                                                                                                    4. Configure filter criteria to view detailed monitoring metrics.
                                                                                                                                      By default, all metrics of the current Prometheus instance is displayed. To view metrics for a specific elastic resource pool, job, or even a specific job submission, you need to apply filters based on your specific needs.
-
                                                                                                                                      
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                                                                                      Table 2 Monitoring metrics
                                                                                                                                      Filter
                                                                                                                                      
-
                                                                                                                                      Description
                                                                                                                                      
-
                                                                                                                                      Prometheus Instance
                                                                                                                                      
-
                                                                                                                                      If you filter metrics by Prometheus instance, all metrics of the instance are displayed.
                                                                                                                                      
-
                                                                                                                                      Resource Pool
                                                                                                                                      
-
                                                                                                                                      If you filter metrics by elastic resource pool, all metrics of the elastic resource pool are displayed.
                                                                                                                                      
-
                                                                                                                                      DLI-flink-jobId
                                                                                                                                      
-
                                                                                                                                      If you filter metrics by DLI Flink job ID, all metrics of the current DLI Flink job are displayed.
                                                                                                                                      
-
                                                                                                                                      You can query the DLI Flink job ID on the Job Management > Flink Jobs page of the DLI console.
                                                                                                                                      
-
                                                                                                                                      DLI-flink-job name
                                                                                                                                      
-
                                                                                                                                      If you filter metrics by DLI Flink job name, all metrics of the current DLI Flink job are displayed.
                                                                                                                                      
-
                                                                                                                                      You can query the DLI Flink job name on the Job Management > Flink Jobs page of the DLI console.
                                                                                                                                      
-
                                                                                                                                      jobId
                                                                                                                                      
-
                                                                                                                                      If you filter metrics by DLI Flink job ID, you can only view the metrics of the current Flink job.
                                                                                                                                      
-
                                                                                                                                      • View the job ID through the FlinkUI.
                                                                                                                                      • View the job ID by searching for keywords in the Flink JobManager log.
                                                                                                                                      
-
                                                                                                                                      
-
                                                                                                                                      
-
                                                                                                                                      
-
                                                                                                                                    
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  (Optional) Step 5: Configure Alarm Notifications for Prometheus Monitoring
                                                                                                                                  To stay updated on the monitoring status of Prometheus and take prompt action, you need to configure alarm notifications. SMN offers flexible message push capabilities, allowing you to send Prometheus alarm events to various endpoints, enabling multi-channel alarm notifications. This step walks you through how to configure alarm notifications for Prometheus monitoring.
                                                                                                                                  
-
                                                                                                                                  1. Create an SMN topic and add a subscription to the topic.
                                                                                                                                    1. Create an SMN topic.
                                                                                                                                      1. Log in to the SMN management console.
                                                                                                                                      2. In the navigation pane on the left, choose Topic Management > Topics.
                                                                                                                                      3. On the displayed Topics page, click Create Topic in the upper right corner.
                                                                                                                                      4. Set topic parameters.
                                                                                                                                        Set Topic Name and Display Name. 
                                                                                                                                        
-
                                                                                                                                      5. In Topic Name, enter a topic name. In Display Name, enter a display name.
                                                                                                                                      
-
                                                                                                                                    2. Add a subscription to the topic.
                                                                                                                                      To receive messages published to a topic, you need to add subscription endpoints to that topic.
                                                                                                                                      
-
                                                                                                                                      1. Log in to the SMN management console.
                                                                                                                                      2. In the navigation pane on the left, choose Topic Management > Topics.
                                                                                                                                      3. On the displayed Topics page, locate the topic to which you want to add a subscription and click Add Subscription in the Operation column.
                                                                                                                                      4. In the Add Subscription slide-out panel, select a protocol from the Protocol drop-down list.
                                                                                                                                      5. In Endpoint, enter a subscription endpoint.
                                                                                                                                        Once you have added a subscription, SMN will send a confirmation message to the subscription endpoint, which includes a link for confirming the subscription. The subscription confirmation link is valid for 48 hours. Make sure to confirm your subscription on your mobile phone, mailbox, or other endpoints within this time frame.
                                                                                                                                        
-
                                                                                                                                      
-
                                                                                                                                    
-
                                                                                                                                  2. Create an alarm action rule on the AOM management console.
                                                                                                                                    You can create an alarm action rule and associate it with an SMN topic and a message template. If the log, resource, or metric data meets the alarm condition, the system sends an alarm notification based on the associated SMN topic and message template.
                                                                                                                                    
-
                                                                                                                                    Ensure that you have created an SMN topic and added subscriptions to the topic.
                                                                                                                                    
-
                                                                                                                                    1. Log in to the AOM 2.0 console.
                                                                                                                                    2. In the navigation pane on the left, choose Alarm Management > Alarm Action Rules.
                                                                                                                                    3. On the displayed Action Rules tab, click Create.
                                                                                                                                    4. In the slide-out panel, set the rule name, rule type, and action.
                                                                                                                                      When the alarm conditions corresponding to the resources are triggered, the system sends alarm notifications based on the associated SMN topics and message templates.
                                                                                                                                      
-
                                                                                                                                    
-
                                                                                                                                  3. Create a metric alarm rule.
                                                                                                                                    You can set threshold conditions in metric alarm rules for resource metrics. When a metric value meets a threshold condition, a threshold alarm will be triggered. If there is no metric data available, an insufficient data event will be reported.
                                                                                                                                    
-
                                                                                                                                    The following uses creating a metric alarm rule from all metrics as an example.
                                                                                                                                    
-
                                                                                                                                    1. Log in to the AOM 2.0 console.
                                                                                                                                    2. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
                                                                                                                                    3. Click Create. 
                                                                                                                                    4. Set basic information and details about the alarm rule.
                                                                                                                                      • When configuring alarm rules, the Prometheus instance selected should be the one associated with the elastic resource pool where the job requiring alarm notifications is located.
                                                                                                                                      • Configure advanced settings. The Action Taken for Insufficient Data parameter in the Advanced Settings area is available only when Select from all metrics is selected for Configuration Mode. You are advised to enable Action Taken for Insufficient Data. This determines how the system will handle the absence or insufficient availability of metric data during the configured monitoring period.
                                                                                                                                      • Action rule for alarm notifications: You are advised to enable Action Rule for alarm notification to ensure that alarms can be notified by email or SMS. Select the alarm action rule configured in 2.
                                                                                                                                      
-
                                                                                                                                    
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  Parent topic: Using AOM to Monitor DLI
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
diff --git a/docs/dli/umn/dli_01_0666.html b/docs/dli/umn/dli_01_0666.html
deleted file mode 100644
index 7e2ba9c12..000000000
--- a/docs/dli/umn/dli_01_0666.html
+++ /dev/null
@@ -1,110 +0,0 @@
-
-
-
                                                                                                                                  Configuration Items for Connecting DLI to AOM's Prometheus Monitoring
                                                                                                                                  
-
                                                                                                                                  When connecting DLI to AOM's Prometheus Monitoring, the system automatically configures the parameters listed in table 1 in Configuration Items for Connecting DLI to AOM's Prometheus Monitoring. If the default configurations do not meet your requirements, you can manually configure the following parameters on the Runtime Configuration tab on the right of the Flink job's editing page. Your configurations are preferred.
                                                                                                                                  
-
-
                                                                                                                                  
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                                                                                  Table 1 Configuration items for Connecting DLI to AOM Prometheus Monitoring
                                                                                                                                  Parameter
                                                                                                                                  
-
                                                                                                                                  Mandatory
                                                                                                                                  
-
                                                                                                                                  Default Value
                                                                                                                                  
-
                                                                                                                                  Data Type
                                                                                                                                  
-
                                                                                                                                  Default Value
                                                                                                                                  
-
                                                                                                                                  Description
                                                                                                                                  
-
                                                                                                                                  metrics.reporter.remote.interval
                                                                                                                                  
-
                                                                                                                                  Yes
                                                                                                                                  
-
                                                                                                                                  None
                                                                                                                                  
-
                                                                                                                                  Duration
                                                                                                                                  
-
                                                                                                                                  30 SECONDS
                                                                                                                                  
-
                                                                                                                                  Metric reporting period, which is recommended to be 30 seconds. If you set it to a smaller value, the metric is frequently reported.
                                                                                                                                  
-
                                                                                                                                  metrics.reporter.remote.remote-write-url
                                                                                                                                  
-
                                                                                                                                  Yes
                                                                                                                                  
-
                                                                                                                                  None
                                                                                                                                  
-
                                                                                                                                  String
                                                                                                                                  
-
                                                                                                                                  -
                                                                                                                                  
-
                                                                                                                                  Remote write URL of AOM Prometheus common instances.
                                                                                                                                  
-
                                                                                                                                  You do not need to manually add https:// to the URL when configuring it. The system will automatically include https:// in the URL.
                                                                                                                                  
-
                                                                                                                                  Example configuration:
                                                                                                                                  
-
                                                                                                                                  aom-internal-access.{regionId}.xxxxx.com:8xx3/v1/{projectId}/{prometheusId}/push
                                                                                                                                  
-
                                                                                                                                  metrics.reporter.remote.report-all-metrics
                                                                                                                                  
-
                                                                                                                                  No
                                                                                                                                  
-
                                                                                                                                  false
                                                                                                                                  
-
                                                                                                                                  Boolean
                                                                                                                                  
-
                                                                                                                                  false
                                                                                                                                  
-
                                                                                                                                  Whether all metrics are reported. The default value is false, indicating that only basic metrics are reported.
                                                                                                                                  
-
                                                                                                                                  metrics.reporter.remote.pool-name
                                                                                                                                  
-
                                                                                                                                  No
                                                                                                                                  
-
                                                                                                                                  None
                                                                                                                                  
-
                                                                                                                                  String
                                                                                                                                  
-
                                                                                                                                  -
                                                                                                                                  
-
                                                                                                                                  Add the name of the elastic resource pool where the current job is located as a tag to the metric.
                                                                                                                                  
-
                                                                                                                                  metrics.reporter.remote.dli-job-id
                                                                                                                                  
-
                                                                                                                                  No
                                                                                                                                  
-
                                                                                                                                  None
                                                                                                                                  
-
                                                                                                                                  String
                                                                                                                                  
-
                                                                                                                                  -
                                                                                                                                  
-
                                                                                                                                  Add the ID of the current DLI Flink job as a tag to the metric.
                                                                                                                                  
-
                                                                                                                                  metrics.reporter.remote.dli-job-name
                                                                                                                                  
-
                                                                                                                                  No
                                                                                                                                  
-
                                                                                                                                  None
                                                                                                                                  
-
                                                                                                                                  String
                                                                                                                                  
-
                                                                                                                                  -
                                                                                                                                  
-
                                                                                                                                  Add the name of the current DLI Flink job as a tag to the metric.
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  Parent topic: Using AOM to Monitor DLI
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
diff --git a/docs/dli/umn/dli_01_0667.html b/docs/dli/umn/dli_01_0667.html
deleted file mode 100644
index 4e9699eca..000000000
--- a/docs/dli/umn/dli_01_0667.html
+++ /dev/null
@@ -1,436 +0,0 @@
-
-
-
                                                                                                                                  Basic Monitoring Metrics Reported by DLI to Prometheus
                                                                                                                                  
-
                                                                                                                                  Table 1 lists the basic monitoring metrics that are reported by DLI to Prometheus. AOM Prometheus can store these basic metrics for free.
                                                                                                                                  
-
-
                                                                                                                                  
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
                                                                                                                                  Table 1 Basic monitoring metrics reported by DLI to Prometheus
                                                                                                                                  Monitoring Metric
                                                                                                                                  
-
                                                                                                                                  Description
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_CPU_Load
                                                                                                                                  
-
                                                                                                                                  JobManager CPU load
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_CPU_Time
                                                                                                                                  
-
                                                                                                                                  JobManager CPU usage
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_CPU_Load
                                                                                                                                  
-
                                                                                                                                  TaskManager CPU load
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_CPU_Time
                                                                                                                                  
-
                                                                                                                                  TaskManager CPU usage
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_Heap_Used
                                                                                                                                  
-
                                                                                                                                  Used heap memory of JobManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_Heap_Committed
                                                                                                                                  
-
                                                                                                                                  Available JVM heap memory of JobManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_Heap_Max
                                                                                                                                  
-
                                                                                                                                  Maximum heap memory available for memory management in JobManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_NonHeap_Used
                                                                                                                                  
-
                                                                                                                                  Used off-heap memory of JobManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_NonHeap_Committed
                                                                                                                                  
-
                                                                                                                                  Available JVM off-heap memory of JobManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_NonHeap_Max
                                                                                                                                  
-
                                                                                                                                  Maximum off-heap memory available for memory management in JobManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_Metaspace_Used
                                                                                                                                  
-
                                                                                                                                  Used memory of the JobManager metaspace memory pool
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_Metaspace_Committed
                                                                                                                                  
-
                                                                                                                                  Available JVM memory of the JobManager metaspace memory pool
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_Metaspace_Max
                                                                                                                                  
-
                                                                                                                                  Maximum memory available in the JobManager metaspace memory pool
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_Direct_Count
                                                                                                                                  
-
                                                                                                                                  Number of buffers in the direct buffer pool of JobManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_Direct_MemoryUsed
                                                                                                                                  
-
                                                                                                                                  Memory for the direct buffer pool in JobManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_Direct_TotalCapacity
                                                                                                                                  
-
                                                                                                                                  Total capacity of all buffers in the direct buffer pool of JobManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_Mapped_Count
                                                                                                                                  
-
                                                                                                                                  Number of buffers in the mapped buffer pool of JobManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_Mapped_MemoryUsed
                                                                                                                                  
-
                                                                                                                                  Memory for the mapped buffer pool in JobManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Memory_Mapped_TotalCapacity
                                                                                                                                  
-
                                                                                                                                  Total capacity of all buffers in the mapped buffer pool of JobManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_Flink_Memory_Managed_Used
                                                                                                                                  
-
                                                                                                                                  Managed memory that has been used in JobManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_Flink_Memory_Managed_Total
                                                                                                                                  
-
                                                                                                                                  Total managed memory of JobManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_Heap_Used
                                                                                                                                  
-
                                                                                                                                  Used heap memory of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_Heap_Committed
                                                                                                                                  
-
                                                                                                                                  Available JVM heap memory of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_Heap_Max
                                                                                                                                  
-
                                                                                                                                  Maximum heap memory available for memory management in TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_NonHeap_Used
                                                                                                                                  
-
                                                                                                                                  Used off-heap memory of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_NonHeap_Committed
                                                                                                                                  
-
                                                                                                                                  Available JVM off-heap memory of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_NonHeap_Max
                                                                                                                                  
-
                                                                                                                                  Maximum off-heap memory available for memory management in TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_Metaspace_Used
                                                                                                                                  
-
                                                                                                                                  Used memory of the TaskManager metaspace memory pool
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_Metaspace_Committed
                                                                                                                                  
-
                                                                                                                                  Available JVM memory of the TaskManager metaspace memory pool
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_Metaspace_Max
                                                                                                                                  
-
                                                                                                                                  Maximum memory available in the TaskManager metaspace memory pool
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_Direct_Count
                                                                                                                                  
-
                                                                                                                                  Number of buffers in the direct buffer pool of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_Direct_MemoryUsed
                                                                                                                                  
-
                                                                                                                                  Memory for the direct buffer pool in TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_Direct_TotalCapacity
                                                                                                                                  
-
                                                                                                                                  Total capacity of all buffers in the direct buffer pool of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_Mapped_Count
                                                                                                                                  
-
                                                                                                                                  Number of buffers in the mapped buffer pool of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_Mapped_MemoryUsed
                                                                                                                                  
-
                                                                                                                                  Memory for the mapped buffer pool in TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Memory_Mapped_TotalCapacity
                                                                                                                                  
-
                                                                                                                                  Total capacity of all buffers in the mapped buffer pool of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_Flink_Memory_Managed_Used
                                                                                                                                  
-
                                                                                                                                  Managed memory that has been used in TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_Flink_Memory_Managed_Total
                                                                                                                                  
-
                                                                                                                                  Total managed memory of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_Threads_Count
                                                                                                                                  
-
                                                                                                                                  Total number of active threads in JobManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_Threads_Count
                                                                                                                                  
-
                                                                                                                                  Total number of active threads in TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_GarbageCollector_ConcurrentMarkSweep_Count
                                                                                                                                  
-
                                                                                                                                  Number of garbage collection (GC) times of the JobManager Concurrent Mark Sweep (CMS) collector
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_GarbageCollector_ConcurrentMarkSweep_Time
                                                                                                                                  
-
                                                                                                                                  Total time required for the JobManager CMS collector to collect garbage
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_GarbageCollector_ParNew_Count
                                                                                                                                  
-
                                                                                                                                  Number of GCs in JobManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_GarbageCollector_ParNew_Time
                                                                                                                                  
-
                                                                                                                                  Time taken for each GC in JobManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_GarbageCollector_ConcurrentMarkSweep_Count
                                                                                                                                  
-
                                                                                                                                  Number of GCs of the CMS collector in TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_GarbageCollector_ConcurrentMarkSweep_Time
                                                                                                                                  
-
                                                                                                                                  Total time required for the TaskManager CMS collector to collect garbage
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_GarbageCollector_ParNew_Count
                                                                                                                                  
-
                                                                                                                                  Number of GCs in TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_GarbageCollector_ParNew_Time
                                                                                                                                  
-
                                                                                                                                  Time taken for each GC in TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_ClassLoader_ClassesLoaded
                                                                                                                                  
-
                                                                                                                                  Total number of classes that JobManager has loaded since JVM startup
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_Status_JVM_ClassLoader_ClassesUnloaded
                                                                                                                                  
-
                                                                                                                                  Total number of classes that JobManager has unloaded since JVM startup
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_ClassLoader_ClassesLoaded
                                                                                                                                  
-
                                                                                                                                  Total number of classes that TaskManager has loaded since JVM startup
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_JVM_ClassLoader_ClassesUnloaded
                                                                                                                                  
-
                                                                                                                                  Total number of classes that TaskManager has unloaded since JVM startup
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_Network_AvailableMemorySegments
                                                                                                                                  
-
                                                                                                                                  Number of unused memory segments of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_Network_TotalMemorySegments
                                                                                                                                  
-
                                                                                                                                  Total number of allocated memory segments of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_Shuffle_Netty_AvailableMemorySegments
                                                                                                                                  
-
                                                                                                                                  Number of unused memory segments of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_Shuffle_Netty_UsedMemorySegments
                                                                                                                                  
-
                                                                                                                                  Number of used memory segments of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_Shuffle_Netty_TotalMemorySegments
                                                                                                                                  
-
                                                                                                                                  Number of allocated memory segments of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_Shuffle_Netty_AvailableMemory
                                                                                                                                  
-
                                                                                                                                  Unused memory of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_Shuffle_Netty_UsedMemory
                                                                                                                                  
-
                                                                                                                                  Used memory of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_Status_Shuffle_Netty_TotalMemory
                                                                                                                                  
-
                                                                                                                                  Allocated memory of TaskManager
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_job_numRestarts
                                                                                                                                  
-
                                                                                                                                  Total number of restarts since job submission
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_job_lastCheckpointDuration
                                                                                                                                  
-
                                                                                                                                  Time taken for the latest checkpoint completion
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_job_lastCheckpointSize
                                                                                                                                  
-
                                                                                                                                  Size of the latest checkpoint (may differ from lastCheckpointFullSize if incremental checkpoints are enabled or logs are changed)
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_job_numberOfInProgressCheckpoints
                                                                                                                                  
-
                                                                                                                                  Number of checkpoints in progress
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_job_numberOfCompletedCheckpoints
                                                                                                                                  
-
                                                                                                                                  Number of completed checkpoints
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_job_numberOfFailedCheckpoints
                                                                                                                                  
-
                                                                                                                                  Number of failed checkpoints
                                                                                                                                  
-
                                                                                                                                  flink_jobmanager_job_totalNumberOfCheckpoints
                                                                                                                                  
-
                                                                                                                                  Total number of checkpoints
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_numBytesOut
                                                                                                                                  
-
                                                                                                                                  Total number of bytes output by a task
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_numBytesOutPerSecond
                                                                                                                                  
-
                                                                                                                                  Total number of bytes output by a task per second
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_isBackPressured
                                                                                                                                  
-
                                                                                                                                  Whether a backpressure occurs
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_numRecordsIn
                                                                                                                                  
-
                                                                                                                                  Total number of records received by a task
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_numRecordsInPerSecond
                                                                                                                                  
-
                                                                                                                                  Total number of records received by a task per second
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_numBytesIn
                                                                                                                                  
-
                                                                                                                                  Number of bytes received by a task
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_numBytesInPerSecond
                                                                                                                                  
-
                                                                                                                                  Number of bytes received by a task per second
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_numRecordsOut
                                                                                                                                  
-
                                                                                                                                  Total number of records sent by a task
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_numRecordsOutPerSecond
                                                                                                                                  
-
                                                                                                                                  Total number of records sent by a task per second
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_operator_numRecordsIn
                                                                                                                                  
-
                                                                                                                                  Total number of records received by an operator
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_operator_numRecordsInPerSecond
                                                                                                                                  
-
                                                                                                                                  Total number of records received by an operator per second
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_operator_numRecordsOut
                                                                                                                                  
-
                                                                                                                                  Total number of records sent by an operator
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_operator_numRecordsOutPerSecond
                                                                                                                                  
-
                                                                                                                                  Total number of records sent by an operator per second
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_operator_sourceIdleTime
                                                                                                                                  
-
                                                                                                                                  Idle duration of the source
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_operator_currentEmitEventTimeLag
                                                                                                                                  
-
                                                                                                                                  Time interval between event time and the time the data leaves the source
                                                                                                                                  
-
                                                                                                                                  flink_taskmanager_job_task_operator_pendingRecords
                                                                                                                                  
-
                                                                                                                                  Number of data records not yet pulled by the source
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  Parent topic: Using AOM to Monitor DLI
                                                                                                                                  
-
                                                                                                                                  
-
                                                                                                                                  
-
diff --git a/docs/dli/umn/dli_01_0671.html b/docs/dli/umn/dli_01_0671.html
new file mode 100644
index 000000000..bdae5e759
--- /dev/null
+++ b/docs/dli/umn/dli_01_0671.html
@@ -0,0 +1,19 @@
+
+
+
+  
                                                                                                                                  Managing Data Catalogs on the DLI Console
                                                                                                                                  
+
+  
                                                                                                                                  
+
                                                                                                                                  
+
+
+
diff --git a/docs/dli/umn/dli_01_0672.html b/docs/dli/umn/dli_01_0672.html
new file mode 100644
index 000000000..08618a729
--- /dev/null
+++ b/docs/dli/umn/dli_01_0672.html
@@ -0,0 +1,144 @@
+
+
+
                                                                                                                                  Configuring Data Catalog Permissions on the DLI Console
                                                                                                                                  
+
                                                                                                                                  Scenario
                                                                                                                                  • DLI data catalogs support authorization on the DLI console or authentication through IAM. By setting permissions, you can grant varying data catalog permissions to different users.
                                                                                                                                  • Administrators and data catalog owners (users who create data catalogs on DLI) have all data catalog permissions by default. You do not need to set permissions for them, and other users cannot modify their data catalog permissions.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Precautions
                                                                                                                                  • Data catalog permissions are non-inherited permissions, meaning they apply only to the current data catalog. Databases and tables within the data catalog cannot inherit any permissions from it.
                                                                                                                                  • Data catalog owners or users with the Assign catalog access to specified users permission can grant permissions to data catalogs.
                                                                                                                                  • If you create a data catalog with the same name after deleting an existing one, the permissions will not be inherited and must be regranted to users.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Data Catalog Permissions
                                                                                                                                  You can also use IAM to grant data catalog permissions to specified users. For details about data catalog permissions, see Table 1.
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 1 Data catalog permissions
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  Permission Set (service:resource:action)
                                                                                                                                  
+
                                                                                                                                  Authorization on the DLI Console
                                                                                                                                  
+
                                                                                                                                  API-based Authorization
                                                                                                                                  
+
                                                                                                                                  IAM-based Authorization
                                                                                                                                  
+
                                                                                                                                  Unbinding a data catalog
                                                                                                                                  
+
                                                                                                                                  dli:catalog:unbind
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Querying data catalog binding details
                                                                                                                                  
+
                                                                                                                                  dli:catalog:get
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Granting permissions
                                                                                                                                  
+
                                                                                                                                  dli: catalog: grantPrivilege
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Revoking permissions
                                                                                                                                  
+
                                                                                                                                  dli: catalog: revokePrivilege
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Viewing permissions of other users
                                                                                                                                  
+
                                                                                                                                  dli: catalog: showPrivileges
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Binding a data catalog
                                                                                                                                  
+
                                                                                                                                  dli:catalog:bind
                                                                                                                                  
+
                                                                                                                                  Not supported
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Querying the data catalog binding list
                                                                                                                                  
+
                                                                                                                                  dli:catalog:list
                                                                                                                                  
+
                                                                                                                                  Not supported
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  Supported
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Granting Data Catalog Permissions to a New User on the DLI Management Console
                                                                                                                                  Grant permissions to a new user or project that previously did not have permissions on this data catalog.
                                                                                                                                  1. In the navigation pane on the left of the management console, choose SQL Editor.
                                                                                                                                  2. On the displayed Catalog tab, locate the data catalog you want to view, click , and select Permissions.
                                                                                                                                  3. On the displayed page, click Grant Permission in the upper right corner. In the dialog box that appears, enter the username you want to grant permissions to and select required permissions. For details about the permissions, see Table 2.
+
                                                                                                                                    
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                    Table 2 Parameter descriptions
                                                                                                                                    Parameter
                                                                                                                                    
+
                                                                                                                                    Description
                                                                                                                                    
+
                                                                                                                                    Username
                                                                                                                                    
+
                                                                                                                                    Name of an IAM user you wish to grant permissions to.
                                                                                                                                     NOTE: 
                                                                                                                                    The username must be an existing IAM username and has been used to log in to the DLI management console.
                                                                                                                                    
+
                                                                                                                                    
+
                                                                                                                                    
+
                                                                                                                                    Permission
                                                                                                                                    
+
                                                                                                                                    Selecting a permission grants it to a user, while deselecting a permission revokes it from the user.
                                                                                                                                    
+
                                                                                                                                    Data catalog permissions are non-inherited permissions, meaning they apply only to the current data catalog. Databases and tables within the data catalog cannot inherit any permissions from it.
                                                                                                                                    • Unbind catalogs: permission to unbind the data catalog from DLI.
                                                                                                                                    • Query the details of bound catalogs: permission to view data catalog binding information. This permission is required if you need to use the data catalog when submitting jobs.
                                                                                                                                    • Assign catalog access to specified users: permission to grant permissions on a data catalog to specified users.
                                                                                                                                    • Revoke catalog access from specified users: permission to revoke permissions on a data catalog from specified users.
                                                                                                                                    • View catalog access rights for other users: permission to view the permissions of other users in the current data catalog.
                                                                                                                                    
+
                                                                                                                                    
+
                                                                                                                                    
+
                                                                                                                                    
+
                                                                                                                                  4. Click OK.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Modifying Permissions on a Data Catalog
                                                                                                                                  If a user has certain permissions on a data catalog, you can modify or revoke those permissions for the user.
                                                                                                                                  
+
                                                                                                                                   
                                                                                                                                  If the options in Set Permission are gray, the corresponding account does not have the permission to modify the data catalog. You can request the Assign catalog access to specified users and Revoke catalog access from specified users permissions from administrators, data catalog owners, or other authorized users with permission-granting permissions.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  1. On the User Permissions page, locate the user you wish to set permissions for.
                                                                                                                                    • If the user is an IAM user, you can set permissions for it.
                                                                                                                                    • If the user is already an administrator, you can only view the permissions information.
                                                                                                                                    
+
                                                                                                                                  2. In the Operation column of the IAM user or project, click Set Permission. The Set Permission dialog box appears.
                                                                                                                                    For details about data catalog permissions, see Table 2.
                                                                                                                                    
+
                                                                                                                                  3. Select or deselect the permissions and click OK.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
+
diff --git a/docs/dli/umn/dli_01_0685.html b/docs/dli/umn/dli_01_0685.html
new file mode 100644
index 000000000..6070c499f
--- /dev/null
+++ b/docs/dli/umn/dli_01_0685.html
@@ -0,0 +1,73 @@
+
+
+
                                                                                                                                  Enabling Spark Native Operator Optimization
                                                                                                                                  
+
                                                                                                                                  Scenario
                                                                                                                                  Spark Native is a core component of Apache Spark designed to enhance the performance of Spark SQL computations. By utilizing vectorized C++ acceleration libraries, it accelerates the performance of Spark operators. Enabling Spark Native can improve the performance of Spark SQL jobs, reducing CPU and memory consumption.
                                                                                                                                  
+
                                                                                                                                  After enabling Spark Native in a queue, it currently supports optimization for Scan and Filter operators.
                                                                                                                                  
+
                                                                                                                                  • Scan: The Scan operator is typically triggered by query statements, such as select * from test_table.
                                                                                                                                    The following conditions support enabling Native:
                                                                                                                                    • Hive tables and datasource tables in Parquet format
                                                                                                                                    • Datasource tables in ORC format
                                                                                                                                    
+
                                                                                                                                    
+
                                                                                                                                  • Filter: The Filter operator is typically triggered by WHERE clauses, such as select * from test_table where id = xxx.
                                                                                                                                  
+
                                                                                                                                   
                                                                                                                                  Using the EXPLAIN statement, you can view the types of operators triggered by SQL commands, for example, Explain select * from test_table.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  This section describes how to enable Spark Native operator optimization.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Notes and Constraints
                                                                                                                                  • To enable the Spark Native engine for a queue in an elastic resource pool, the following conditions must be met simultaneously:
                                                                                                                                    • Type of an elastic resource pool: Standard
                                                                                                                                    • Type of a queue: For SQL
                                                                                                                                    • Spark version: Spark 3.3.1 or later
                                                                                                                                    
+
                                                                                                                                  • For the default queue, when Spark 3.3.1 or later is used, Spark Native is disabled by default.
                                                                                                                                  • To disable Spark Native for a job, configure spark.gluten.enabled=false in the job parameters to disable Spark Native at the job level.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Enabling Spark Native Operator Optimization
                                                                                                                                  
+
                                                                                                                                  • For SQL queues in an existing elastic resource pool, you can enable Spark Native by setting queue properties.
                                                                                                                                    1. In the navigation pane on the left of the DLI management console, choose Resources > Queue Management.
                                                                                                                                    2. Locate the queue for which you want to set properties, click More in the Operation column, and select Set Property.
                                                                                                                                    3. Go to the queue property setting page and set property parameters. Table 1 describes the property parameters.
                                                                                                                                       
                                                                                                                                      For created queues, if you change the Spark Native setting (enabled/disabled) through the DLI management console or API, you need to restart the queue for the modification to take effect.
                                                                                                                                      
+
                                                                                                                                      
+
+
                                                                                                                                      
+
+
+
+
+
+
+
+
+
+
                                                                                                                                      Table 1 Queue properties
                                                                                                                                      Property
                                                                                                                                      
+
                                                                                                                                      Description
                                                                                                                                      
+
                                                                                                                                      Example Value
                                                                                                                                      
+
                                                                                                                                      DLI Spark Native Acceleration
                                                                                                                                      
+
                                                                                                                                      Enabling Spark Native can improve the performance of Spark SQL jobs, reducing CPU and memory consumption.
                                                                                                                                      
+
                                                                                                                                      Enabled
                                                                                                                                      
+
                                                                                                                                      
+
                                                                                                                                      
+
                                                                                                                                    4. Click OK.
                                                                                                                                    
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Disabling Spark Native Operator Optimization
                                                                                                                                  • Disable Spark Native for SQL queues in an elastic resource pool.
                                                                                                                                    1. In the navigation pane on the left of the DLI management console, choose Resources > Queue Management.
                                                                                                                                    2. Locate the queue for which you want to set properties, click More in the Operation column, and select Set Property.
                                                                                                                                    3. Go to the queue property setting page and set property parameters. Table 2 describes the property parameters.
+
                                                                                                                                      
+
+
+
+
+
+
+
+
+
+
                                                                                                                                      Table 2 Queue properties
                                                                                                                                      Property
                                                                                                                                      
+
                                                                                                                                      Description
                                                                                                                                      
+
                                                                                                                                      Example Value
                                                                                                                                      
+
                                                                                                                                      DLI Spark Native Acceleration
                                                                                                                                      
+
                                                                                                                                      Enabling Spark Native can improve the performance of Spark SQL jobs, reducing CPU and memory consumption.
                                                                                                                                      
+
                                                                                                                                      Disabled
                                                                                                                                      
+
                                                                                                                                      
+
                                                                                                                                      
+
                                                                                                                                    4. Click OK.
                                                                                                                                    
+
                                                                                                                                  • Disable Spark Native for a specified job when a queue has Spark Native enabled.
                                                                                                                                    After Spark Native is enabled for a SQL queue, if you want to disable Spark Native for a particular job running in the queue,
                                                                                                                                    
+
                                                                                                                                    add spark.gluten.enabled=false to the parameter settings of the SQL job to disable Spark Native.
                                                                                                                                    
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Parent topic: Managing Queues
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
diff --git a/docs/dli/umn/dli_01_0686.html b/docs/dli/umn/dli_01_0686.html
new file mode 100644
index 000000000..00d2e61b4
--- /dev/null
+++ b/docs/dli/umn/dli_01_0686.html
@@ -0,0 +1,57 @@
+
+
+
                                                                                                                                  Scaling Out or In an Elastic Resource Pool
                                                                                                                                  
+
                                                                                                                                  Scaling out or in an elastic resource pool essentially means adjusting the actual CUs of the resource pool.
                                                                                                                                  
+
                                                                                                                                  In an elastic resource pool:
                                                                                                                                  
+
                                                                                                                                  • Actual CUs: actual size of resources currently allocated to the elastic resource pool (in CUs). That is, the number of compute resources actually owned.
                                                                                                                                  • Elastic resource pool scaling out: It involves increasing the actual CUs, meaning increasing the number of compute resources within the resource pool. The upper limit for this expansion corresponds to the maximum value specified in the CU range of the elastic resource pool.
                                                                                                                                  • Elastic resource pool scaling in: It involves decreasing the actual CUs, meaning decreasing the number of compute resources within the resource pool. The lower limit for this reduction corresponds to the minimum value specified in the CU range of the elastic resource pool.
                                                                                                                                  
+
                                                                                                                                  That is, the actual CUs of the elastic resource pool dynamically change between the minimum value and the maximum value of the CU range.
                                                                                                                                  
+
                                                                                                                                  For more information about basic concepts of elastic resource pools, see Basic Concepts.
                                                                                                                                  
+
                                                                                                                                  Notes and Constraints
                                                                                                                                  • Creating or deleting queues within an elastic resource pool triggers elastic resource scaling.
                                                                                                                                  • Scaling in an elastic resource pool may affect nodes containing shuffle data, leading to the recomputation of Spark tasks. This causes automatic retries for Spark and SQL jobs, and if the retries exceed the limit, the job execution fails, requiring you to rerun the job.
                                                                                                                                  • Spark 2.3 jobs need to be upgraded to a later Spark version to support dynamic scale-in of the jobs while they are running.
                                                                                                                                  • Spark Streaming and Flink jobs cannot be scaled in while they are running. To perform a scale-in, suspend the jobs or migrate them to another elastic resource pool.
                                                                                                                                  • Scale-out and scale-in triggered by the following operations take effect at the next full hour after the operations are performed:
                                                                                                                                    • Adjusting the CU range of a queue
                                                                                                                                    • Modifying the specifications of an elastic resource pool
                                                                                                                                    • Setting CUs for an elastic resource pool
                                                                                                                                    
+
                                                                                                                                  • You can add queues to adjust the actual CUs of an elastic resource pool. The adjustment takes effect immediately.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Triggering Methods for Scaling Out or In an Elastic Resource Pool
                                                                                                                                  
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 1 Triggering methods for scaling out or in an elastic resource pool
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  Actual CU Change
                                                                                                                                  
+
                                                                                                                                  Trigger Method
                                                                                                                                  
+
                                                                                                                                  Scaling out
                                                                                                                                  
+
                                                                                                                                  Actual CUs increase.
                                                                                                                                  
+
                                                                                                                                  max{(min[sum(maximum CUs of queues), maximum CUs of the elastic resource pool]), minimum CUs of the elastic resource pool} > current actual CUs, the system automatically scales out.
                                                                                                                                  
+
                                                                                                                                  Scaling in
                                                                                                                                  
+
                                                                                                                                  Actual CUs decrease.
                                                                                                                                  
+
                                                                                                                                  max{(min[sum(maximum CUs of queues), maximum CUs of the elastic resource pool]), minimum CUs of the elastic resource pool} < current actual CUs, the system automatically scales in.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  For details, see Figure 1.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Formula for Calculating Actual CUs of an Elastic Resource Pool
                                                                                                                                  The actual CUs of an elastic resource pool must meet the following requirements:
                                                                                                                                  
+
                                                                                                                                  • Meet the demands of all queues.
                                                                                                                                  • Ensure that it does not exceed the upper limit of the CUs of the elastic resource pool.
                                                                                                                                  • Ensure that it is not below the lower limit of the CUs of the elastic resource pool.
                                                                                                                                  
+
                                                                                                                                  Figure 1 Formula for calculating actual cus of an elastic resource pool
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Parent topic: Managing Elastic Resource Pools
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_01_0687.html b/docs/dli/umn/dli_01_0687.html
new file mode 100644
index 000000000..87c61ec9c
--- /dev/null
+++ b/docs/dli/umn/dli_01_0687.html
@@ -0,0 +1,18 @@
+
+
+
                                                                                                                                  Overview
                                                                                                                                  
+
                                                                                                                                  When submitting Flink or Spark jobs through DLI to access external data sources (such as OBS and Kafka), there is a risk of plaintext exposure if AK/SK, usernames/passwords are directly embedded in the job code or parameter configurations.
                                                                                                                                  
+
                                                                                                                                  To securely store data source access credentials, ensure data source authentication safety, and facilitate secure access to data sources by DLI, you are advised to use DEW for managing data source access credentials. DLI employs "agency + temporary credentials" to safely retrieve data source access credentials.
                                                                                                                                  
+
                                                                                                                                  DEW is a comprehensive cloud-based encryption service designed to address challenges related to data security, key security, and the complexities of key management.
                                                                                                                                  
+
                                                                                                                                  This section describes how to use DEW to store data source authentication information across various job types.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Notes and Constraints
                                                                                                                                  You are advised to use DEW for storing data source authentication information exclusively when Spark 3.3.1 or later and Flink 1.15 or later jobs access data sources using datasoure connections.
                                                                                                                                  
+
                                                                                                                                  When SQL and Flink 1.12 jobs access data sources using datasource connections, use DLI's datasource authentication feature to manage data source access credentials. For details, see Using DLI Datasource Authentication to Manage Access Credentials for Data Sources.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
+
diff --git a/docs/dli/umn/dli_01_0689.html b/docs/dli/umn/dli_01_0689.html
new file mode 100644
index 000000000..6703c0d02
--- /dev/null
+++ b/docs/dli/umn/dli_01_0689.html
@@ -0,0 +1,20 @@
+
+
+
                                                                                                                                  DLI Permission Management
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
+
diff --git a/docs/dli/umn/dli_01_0690.html b/docs/dli/umn/dli_01_0690.html
new file mode 100644
index 000000000..10dc5c0c6
--- /dev/null
+++ b/docs/dli/umn/dli_01_0690.html
@@ -0,0 +1,82 @@
+
+
+
                                                                                                                                  Overview
                                                                                                                                  
+
                                                                                                                                  The permission management function of DLI itself primarily applies to the permission control of internal DLI resources, rather than relying on the unified identity authentication management of IAM.
                                                                                                                                  
+
                                                                                                                                  DLI is a region- and project-level service. Therefore, DLI authorization is based on the region and project level.
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 1 Basic concepts of DLI authorization
                                                                                                                                  Type
                                                                                                                                  
+
                                                                                                                                  Description
                                                                                                                                  
+
                                                                                                                                  User initiating the authorization operation
                                                                                                                                  
+
                                                                                                                                  The user initiating the authorization operation is typically an administrator or an authorizer with managerial privileges. They are tasked with deciding which permissions may be granted and granting these permissions to IAM users.
                                                                                                                                  
+
                                                                                                                                  The user initiating the authorization operation must possess adequate authorization permissions to ensure the execution of the authorization act.
                                                                                                                                  
+
                                                                                                                                  Authorized entity
                                                                                                                                  
+
                                                                                                                                  An authorized entity refers to the recipient of the granted permissions, which could be a user or a project. Once explicitly authorized within the DLI system, the authorized entity gains the ability to perform operations on specific DLI resources.
                                                                                                                                  
+
                                                                                                                                  Resource
                                                                                                                                  
+
                                                                                                                                  Resources refer to the DLI resources accessible through authorization, including elastic resource pools, queues, data catalogs, databases, tables, and jobs.
                                                                                                                                  
+
                                                                                                                                  These resources are the operational objects available to users within the DLI environment.
                                                                                                                                  
+
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  An operation signifies the specific actions that a user or role can perform on a principal resource.
                                                                                                                                  
+
                                                                                                                                  Operations are intrinsically linked to the type of entity. Distinct entity types accommodate varying sets of operations. For example, for table resources, supported operations include reading, writing, and querying.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  DLI categorizes authorization into three types based on the objects of permissions: user authorization, cross-project authorization, and cross-tenant project authorization.
                                                                                                                                  
+
                                                                                                                                  • User authorization: Achieves precise allocation of user permissions by managing IAM users within the same account.
                                                                                                                                  • Cross-project authorization: Enables resource sharing among sub-projects under the same account and within the same region-specific project, enhancing resource utilization.
                                                                                                                                  • Cross-tenant project authorization: Facilitates resource collaboration between different accounts within the same region-specific project.
                                                                                                                                  
+
                                                                                                                                  These authorization types address diverse service scenario needs through detailed configurations of the authorized entities, resources, and operations, ensuring secure and compliant data access and operations.
                                                                                                                                  
+
                                                                                                                                  Table 2 outlines the applicable scope and resource types for DLI's user authorization, cross-project authorization, and cross-tenant project authorization.
                                                                                                                                  
+
                                                                                                                                  Authorization Types of DLI Permissions
                                                                                                                                  
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 2 Authorization types of DLI permissions
                                                                                                                                  Type
                                                                                                                                  
+
                                                                                                                                  Description
                                                                                                                                  
+
                                                                                                                                  User authorization
                                                                                                                                  
+
                                                                                                                                  In DLI, the master account manages the permissions of all users under the account. Users can be created through IAM, and corresponding roles or policies can be assigned based on the users' job functions and service requirements, achieving fine-grained management of user permissions.
                                                                                                                                  
+
                                                                                                                                  For example, developers can be granted permission to use DLI resources but not to delete them, ensuring secure usage within the scope of resource safety.
                                                                                                                                  
+
                                                                                                                                  Cross-project authorization
                                                                                                                                  
+
                                                                                                                                  Cross-project authorization allows resources from one project (for example, project A) to be granted to another project (for example, project B), enabling resource sharing. This type of authorization facilitates resource sharing among sub-projects under the same account and region-specific project.
                                                                                                                                  
+
                                                                                                                                  Resource types supporting cross-project authorization include:
                                                                                                                                  
+
                                                                                                                                  • Database
                                                                                                                                  • Table
                                                                                                                                  • Enhanced datasource connection
                                                                                                                                  
+
                                                                                                                                  Through cross-project authorization, sub-projects (for example, project A_1) can use resources from parent projects (for example, project A), enhancing resource efficiency and fulfilling service requirements.
                                                                                                                                  
+
                                                                                                                                  Cross-tenant project authorization (authorization within the same region-specific project)
                                                                                                                                  
+
                                                                                                                                  Cross-tenant project authorization involves resource sharing between two different accounts (for example, account A and account B). Account A can grant resources to account B, with the condition that this authorization occurs within the same project.
                                                                                                                                  
+
                                                                                                                                  Resource types supporting cross-tenant project authorization include:
                                                                                                                                  
+
                                                                                                                                  • Database
                                                                                                                                  • Table
                                                                                                                                  • Enhanced datasource connection
                                                                                                                                  
+
                                                                                                                                  Through cross-tenant project authorization, users from different accounts can share resources within the same project, facilitating more flexible resource management and collaboration.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Parent topic: DLI Permission Management
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
diff --git a/docs/dli/umn/dli_01_0691.html b/docs/dli/umn/dli_01_0691.html
new file mode 100644
index 000000000..680e66f6d
--- /dev/null
+++ b/docs/dli/umn/dli_01_0691.html
@@ -0,0 +1,3144 @@
+
+
+
                                                                                                                                  DLI Permissions
                                                                                                                                  
+
                                                                                                                                  Elastic Resource Pool
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 1 Elastic resource pool permission set
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  Description
                                                                                                                                  
+
                                                                                                                                  DLI Privileges
                                                                                                                                  
+
                                                                                                                                  Authorizable Through DLI Console (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorizable Through API (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorization Object
                                                                                                                                  
+
                                                                                                                                  Updating an elastic resource pool
                                                                                                                                  
+
                                                                                                                                  Updates the description of an elastic resource pool.
                                                                                                                                  
+
                                                                                                                                  UPDATE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Managing resources
                                                                                                                                  
+
                                                                                                                                  Adds queues, deletes queues, and configures scaling policies for queues in an elastic resource pool.
                                                                                                                                  
+
                                                                                                                                  RESOURCE_MANAGEMENT
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting an elastic resource pool
                                                                                                                                  
+
                                                                                                                                  Deletes an elastic resource pool.
                                                                                                                                  
+
                                                                                                                                  DROP
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Granting permissions
                                                                                                                                  
+
                                                                                                                                  Grants elastic resource pool permissions to other users.
                                                                                                                                  
+
                                                                                                                                  GRANT_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Revoking permissions
                                                                                                                                  
+
                                                                                                                                  Revokes the elastic resource pool permissions of other users, but not the pool owner.
                                                                                                                                  
+
                                                                                                                                  REVOKE_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Viewing permissions of other users
                                                                                                                                  
+
                                                                                                                                  Views the elastic resource pool permissions of other users.
                                                                                                                                  
+
                                                                                                                                  SHOW_PRIVILEGES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Creating an elastic resource pool
                                                                                                                                  
+
                                                                                                                                  Creates elastic resource pools.
                                                                                                                                  
+
                                                                                                                                  CREATE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  All resources (*)
                                                                                                                                  
+
                                                                                                                                  Querying the elastic resource pool list
                                                                                                                                  
+
                                                                                                                                  Views all elastic resource pools.
                                                                                                                                  
+
                                                                                                                                  LIST
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  All resources (*)
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Queue
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 2 Queue permission set (queues in elastic resource pools)
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  Description
                                                                                                                                  
+
                                                                                                                                  DLI Privileges
                                                                                                                                  
+
                                                                                                                                  Authorizable Through DLI Console (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorizable Through API (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorization Object
                                                                                                                                  
+
                                                                                                                                  Deleting a queue
                                                                                                                                  
+
                                                                                                                                  Deletes a queue.
                                                                                                                                  
+
                                                                                                                                  DROP_QUEUE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Submitting a job
                                                                                                                                  
+
                                                                                                                                  Submits jobs to a queue.
                                                                                                                                  
+
                                                                                                                                  SUBMIT_JOB
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Terminating a job
                                                                                                                                  
+
                                                                                                                                  Terminates the jobs submitted to a queue.
                                                                                                                                  
+
                                                                                                                                  CANCEL_JOB
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Granting permissions
                                                                                                                                  
+
                                                                                                                                  Grants queue permissions to other users.
                                                                                                                                  
+
                                                                                                                                  GRANT_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Revoking permissions
                                                                                                                                  
+
                                                                                                                                  Revokes the queue permissions of other users, but not the queue owner.
                                                                                                                                  
+
                                                                                                                                  REVOKE_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Viewing permissions of other users
                                                                                                                                  
+
                                                                                                                                  Views the queue permissions of other users.
                                                                                                                                  
+
                                                                                                                                  SHOW_PRIVILEGES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Restarting a queue
                                                                                                                                  
+
                                                                                                                                  Restarts a queue.
                                                                                                                                  
+
                                                                                                                                  RESTART
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Changing specifications
                                                                                                                                  
+
                                                                                                                                  Changes queue specifications.
                                                                                                                                  
+
                                                                                                                                  SCALE_QUEUE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Creating a queue
                                                                                                                                  
+
                                                                                                                                  Creates queues.
                                                                                                                                  
+
                                                                                                                                  CREATE_QUEUE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  All resources (*)
                                                                                                                                  
+
                                                                                                                                  Querying the queue list
                                                                                                                                  
+
                                                                                                                                  Queries the queue list.
                                                                                                                                  
+
                                                                                                                                  LIST_QUEUES
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  All resources (*)
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Database
                                                                                                                                  
+
                                                                                                                                  Permission type:
                                                                                                                                  • Non-inheritable permissions: Permissions that are directly granted to databases and are neither inherited from parent objects nor passed down to child objects. These permissions are independent of the permission settings of other objects and are only valid for specified objects.
                                                                                                                                  • Inheritable permissions: Permissions that are inherited from parent objects or can be passed down to child objects. For example, if an inheritable permission is granted to a database, the tables in the database will inherit the permission.
                                                                                                                                  
+
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 3 Database permission set
                                                                                                                                  Type
                                                                                                                                  
+
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  Description
                                                                                                                                  
+
                                                                                                                                  DLI Privileges
                                                                                                                                  
+
                                                                                                                                  Authorizable Through DLI Console (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorizable Through API (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorization Object
                                                                                                                                  
+
                                                                                                                                  Non-inheritable permission
                                                                                                                                  
+
                                                                                                                                  Showing all tables
                                                                                                                                  
+
                                                                                                                                  Shows all tables in a database.
                                                                                                                                  
+
                                                                                                                                  DISPLAY_ALL_TABLES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Showing a database
                                                                                                                                  
+
                                                                                                                                  Shows information about a database.
                                                                                                                                  
+
                                                                                                                                  DISPLAY_DATABASE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting a database
                                                                                                                                  
+
                                                                                                                                  Deletes a database.
                                                                                                                                  
+
                                                                                                                                  DROP_DATABASE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Creating a table
                                                                                                                                  
+
                                                                                                                                  Creates tables in a database.
                                                                                                                                  
+
                                                                                                                                  CREATE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Creating a view
                                                                                                                                  
+
                                                                                                                                  Creates views in a database.
                                                                                                                                  
+
                                                                                                                                  CREATE_VIEW
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Explaining SQL statements as an execution plan
                                                                                                                                  
+
                                                                                                                                  Executes explain statements.
                                                                                                                                  
+
                                                                                                                                  EXPLAIN
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Creating a role
                                                                                                                                  
+
                                                                                                                                  Creates roles in a database.
                                                                                                                                  
+
                                                                                                                                  CREATE_ROLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting a role
                                                                                                                                  
+
                                                                                                                                  Deletes roles from a database.
                                                                                                                                  
+
                                                                                                                                  DROP_ROLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Showing a role
                                                                                                                                  
+
                                                                                                                                  Shows the roles of a user.
                                                                                                                                  
+
                                                                                                                                  SHOW_ROLES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Binding a role
                                                                                                                                  
+
                                                                                                                                  Binds roles in a database.
                                                                                                                                  
+
                                                                                                                                  GRANT_ROLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Unbinding a role
                                                                                                                                  
+
                                                                                                                                  Unbinds roles in a database.
                                                                                                                                  
+
                                                                                                                                  REVOKE_ROLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Showing the binding relationships between all roles and users
                                                                                                                                  
+
                                                                                                                                  Shows the binding relationships between all roles and users.
                                                                                                                                  
+
                                                                                                                                  SHOW_USERS
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Creating a function
                                                                                                                                  
+
                                                                                                                                  Creates functions in a database.
                                                                                                                                  
+
                                                                                                                                  CREATE_FUNCTION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting a function
                                                                                                                                  
+
                                                                                                                                  Deletes functions from a database.
                                                                                                                                  
+
                                                                                                                                  DROP_FUNCTION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Showing all functions
                                                                                                                                  
+
                                                                                                                                  Shows all functions in a database.
                                                                                                                                  
+
                                                                                                                                  SHOW_FUNCTIONS
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Showing function details
                                                                                                                                  
+
                                                                                                                                  Shows details about a function.
                                                                                                                                  
+
                                                                                                                                  DESCRIBE_FUNCTION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Granting permissions
                                                                                                                                  
+
                                                                                                                                  Grants database permissions to other users.
                                                                                                                                  
+
                                                                                                                                  GRANT_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Revoking permissions
                                                                                                                                  
+
                                                                                                                                  Revokes the database permissions of other users, but not the database owner.
                                                                                                                                  
+
                                                                                                                                  REVOKE_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Viewing permissions of other users
                                                                                                                                  
+
                                                                                                                                  Views the database permissions of other users.
                                                                                                                                  
+
                                                                                                                                  SHOW_PRIVILEGES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Updating a database
                                                                                                                                  
+
                                                                                                                                  Updates the metadata of a database.
                                                                                                                                  
+
                                                                                                                                  UPDATE_DATABASE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Obtaining database information
                                                                                                                                  
+
                                                                                                                                  Obtains details of a database.
                                                                                                                                  
+
                                                                                                                                  GET_DATABASE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Describing a database
                                                                                                                                  
+
                                                                                                                                  Checks comments of a database.
                                                                                                                                  
+
                                                                                                                                  DESCRIBE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Viewing all tables in a database
                                                                                                                                  
+
                                                                                                                                  Lists all tables in a database.
                                                                                                                                  
+
                                                                                                                                  LIST_TABLES
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Querying details about a specified function
                                                                                                                                  
+
                                                                                                                                  Queries details about a specified function.
                                                                                                                                  
+
                                                                                                                                  GET_FUNCTION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Listing all available functions in a database
                                                                                                                                  
+
                                                                                                                                  Lists all available functions in a database.
                                                                                                                                  
+
                                                                                                                                  LIST_FUNCTIONS
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Allowing Spark applications to access metadata
                                                                                                                                  
+
                                                                                                                                  Allows Spark applications to access metadata.
                                                                                                                                  
+
                                                                                                                                  SPARK_APP_ACCESS_META
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Inheritable permission
                                                                                                                                  
+
                                                                                                                                  Querying tables
                                                                                                                                  
+
                                                                                                                                  Retrieves data records from a table.
                                                                                                                                  
+
                                                                                                                                  SELECT
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Showing table information
                                                                                                                                  
+
                                                                                                                                  Shows the column names and data types of a table.
                                                                                                                                  
+
                                                                                                                                  DESCRIBE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Showing the table creation statement
                                                                                                                                  
+
                                                                                                                                  Shows SQL statements for creating a table.
                                                                                                                                  
+
                                                                                                                                  SHOW_CREATE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Dropping a table
                                                                                                                                  
+
                                                                                                                                  Drops tables and their data.
                                                                                                                                  
+
                                                                                                                                  DROP_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Clearing table data
                                                                                                                                  
+
                                                                                                                                  Deletes all data in a table but retains the table structure.
                                                                                                                                  
+
                                                                                                                                  TRUNCATE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Renaming a table
                                                                                                                                  
+
                                                                                                                                  Renames tables.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_RENAME
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Inserting table data
                                                                                                                                  
+
                                                                                                                                  Adds data records to a table.
                                                                                                                                  
+
                                                                                                                                  INSERT_INTO_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Overwriting a table
                                                                                                                                  
+
                                                                                                                                  Inserts new data and overwrites the original data in a table.
                                                                                                                                  
+
                                                                                                                                  INSERT_OVERWRITE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Adding a column
                                                                                                                                  
+
                                                                                                                                  Adds columns to a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_ADD_COLUMNS
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Accessing metadata
                                                                                                                                  
+
                                                                                                                                  Allows Spark applications to read metadata.
                                                                                                                                  
+
                                                                                                                                  SPARK_APP_ACCESS_META
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Viewing permissions of other users
                                                                                                                                  
+
                                                                                                                                  Lists a user's or role's permissions.
                                                                                                                                  
+
                                                                                                                                  SHOW_PRIVILEGES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Granting permissions
                                                                                                                                  
+
                                                                                                                                  Grants permissions to a user or role.
                                                                                                                                  
+
                                                                                                                                  GRANT_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Revoking permissions
                                                                                                                                  
+
                                                                                                                                  Revokes permissions from a user or role.
                                                                                                                                  
+
                                                                                                                                  REVOKE_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Collecting table statistics
                                                                                                                                  
+
                                                                                                                                  Collects statistics about a table.
                                                                                                                                  
+
                                                                                                                                  ANALYZE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Adding a partition
                                                                                                                                  
+
                                                                                                                                  Adds partitions to a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_ADD_PARTITION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting a partition
                                                                                                                                  
+
                                                                                                                                  Removes partitions from a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_DROP_PARTITION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Setting the partition path
                                                                                                                                  
+
                                                                                                                                  Modifies the storage location of table data.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_SET_LOCATION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Renaming a table partition
                                                                                                                                  
+
                                                                                                                                  Renames partitions.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_RENAME_PARTITION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Restoring a table partition
                                                                                                                                  
+
                                                                                                                                  Restores lost or damaged partitions.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_RECOVER_PARTITION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Showing all partitions
                                                                                                                                  
+
                                                                                                                                  Lists all partitions of a table.
                                                                                                                                  
+
                                                                                                                                  SHOW_PARTITIONS
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Updating table data
                                                                                                                                  
+
                                                                                                                                  Modifies data records in a table.
                                                                                                                                  
+
                                                                                                                                  UPDATE_TABLE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Dropping a table column
                                                                                                                                  
+
                                                                                                                                  Removes one or more columns from a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_DROP_COLUMNS
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Modifying a table column
                                                                                                                                  
+
                                                                                                                                  Changes the column name, data type, and other attributes.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_CHANGE_COLUMN
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Setting the table storage location
                                                                                                                                  
+
                                                                                                                                  Specifies a new path for storing table data.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_SET_LOCATION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Setting table attributes
                                                                                                                                  
+
                                                                                                                                  Modifies the metadata attribute of a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_SET_PROPERTIES
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Querying table information
                                                                                                                                  
+
                                                                                                                                  Queries the structure and metadata of a table.
                                                                                                                                  
+
                                                                                                                                  GET_TABLE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Showing the table structure
                                                                                                                                  
+
                                                                                                                                  Shows the column names and data types of a table.
                                                                                                                                  
+
                                                                                                                                  DISPLAY_TABLE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Creating a partition
                                                                                                                                  
+
                                                                                                                                  Creates partition structures for a table.
                                                                                                                                  
+
                                                                                                                                  CREATE_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting a partition
                                                                                                                                  
+
                                                                                                                                  Removes partitions from a table.
                                                                                                                                  
+
                                                                                                                                  DROP_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Updating a partition
                                                                                                                                  
+
                                                                                                                                  Modifies metadata or data of a partition.
                                                                                                                                  
+
                                                                                                                                  UPDATE_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Querying partition information
                                                                                                                                  
+
                                                                                                                                  Queries details about a partition.
                                                                                                                                  
+
                                                                                                                                  GET_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Listing partitions
                                                                                                                                  
+
                                                                                                                                  Shows all partitions of a table.
                                                                                                                                  
+
                                                                                                                                  LIST_PARTITIONS
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Modifying a view
                                                                                                                                  
+
                                                                                                                                  Updates the definition or attributes of a view.
                                                                                                                                  
+
                                                                                                                                  ALTER_VIEW
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Migrating data
                                                                                                                                  
+
                                                                                                                                  Migrates data from one location to another.
                                                                                                                                  
+
                                                                                                                                  DATA_MIGRATION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Modifying an object
                                                                                                                                  
+
                                                                                                                                  Modifies the attributes or structure of a database object.
                                                                                                                                  
+
                                                                                                                                  ALTER
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Updating data
                                                                                                                                  
+
                                                                                                                                  Modifies the data in a table.
                                                                                                                                  
+
                                                                                                                                  UPDATE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting data
                                                                                                                                  
+
                                                                                                                                  Deletes data records from a table.
                                                                                                                                  
+
                                                                                                                                  DELETE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Other
                                                                                                                                  
+
                                                                                                                                  Creating a database
                                                                                                                                  
+
                                                                                                                                  Creates a database instance.
                                                                                                                                  
+
                                                                                                                                  CREATE_DATABASE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  All resources (*)
                                                                                                                                  
+
                                                                                                                                  Listing databases
                                                                                                                                  
+
                                                                                                                                  Shows all available databases.
                                                                                                                                  
+
                                                                                                                                  LIST_DATABASES
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  All resources (*)
                                                                                                                                  
+
                                                                                                                                  Showing all databases
                                                                                                                                  
+
                                                                                                                                  Lists all databases in the system.
                                                                                                                                  
+
                                                                                                                                  DISPLAY_ALL_DATABASES
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  All resources (*)
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 4 Database project/Cross-tenant project permission set
                                                                                                                                  Type
                                                                                                                                  
+
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  Description
                                                                                                                                  
+
                                                                                                                                  DLI Privileges
                                                                                                                                  
+
                                                                                                                                  Authorizable Through DLI Console (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorizable Through API (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorization Object
                                                                                                                                  
+
                                                                                                                                  Non-inheritable permission
                                                                                                                                  
+
                                                                                                                                  Deleting a database
                                                                                                                                  
+
                                                                                                                                  Deletes a specified database and all its content.
                                                                                                                                  
+
                                                                                                                                  DROP_DATABASE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Creating a table
                                                                                                                                  
+
                                                                                                                                  Creates a table and defines columns and data types.
                                                                                                                                  
+
                                                                                                                                  CREATE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Creating a view
                                                                                                                                  
+
                                                                                                                                  Creates virtual tables based on SQL query definitions.
                                                                                                                                  
+
                                                                                                                                  CREATE_VIEW
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Explaining SQL statements as an execution plan
                                                                                                                                  
+
                                                                                                                                  Shows the execution plans of a SQL query.
                                                                                                                                  
+
                                                                                                                                  EXPLAIN
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Creating a role
                                                                                                                                  
+
                                                                                                                                  Creates roles for permission management.
                                                                                                                                  
+
                                                                                                                                  CREATE_ROLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Deleting a role
                                                                                                                                  
+
                                                                                                                                  Deletes roles and their associated permissions.
                                                                                                                                  
+
                                                                                                                                  DROP_ROLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Showing a role
                                                                                                                                  
+
                                                                                                                                  Lists all roles in the system.
                                                                                                                                  
+
                                                                                                                                  SHOW_ROLES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Binding a role
                                                                                                                                  
+
                                                                                                                                  Assigns roles to a user or group.
                                                                                                                                  
+
                                                                                                                                  GRANT_ROLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Unbinding a role
                                                                                                                                  
+
                                                                                                                                  Removes roles from a user or group.
                                                                                                                                  
+
                                                                                                                                  REVOKE_ROLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Showing the binding relationships between all roles and users
                                                                                                                                  
+
                                                                                                                                  Lists all users in the system.
                                                                                                                                  
+
                                                                                                                                  SHOW_USERS
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Creating a function
                                                                                                                                  
+
                                                                                                                                  Creates user-defined functions.
                                                                                                                                  
+
                                                                                                                                  CREATE_FUNCTION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Deleting a function
                                                                                                                                  
+
                                                                                                                                  Deletes specified functions.
                                                                                                                                  
+
                                                                                                                                  DROP_FUNCTION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Showing all functions
                                                                                                                                  
+
                                                                                                                                  Lists all functions in the system.
                                                                                                                                  
+
                                                                                                                                  SHOW_FUNCTIONS
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Showing function details
                                                                                                                                  
+
                                                                                                                                  Shows the definition and parameters of a function.
                                                                                                                                  
+
                                                                                                                                  DESCRIBE_FUNCTION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Inheritable permission
                                                                                                                                  
+
                                                                                                                                  Querying tables
                                                                                                                                  
+
                                                                                                                                  Retrieves data records from a table.
                                                                                                                                  
+
                                                                                                                                  SELECT
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Showing table information
                                                                                                                                  
+
                                                                                                                                  Shows the column names and data types of a table.
                                                                                                                                  
+
                                                                                                                                  DESCRIBE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Showing the table creation statement
                                                                                                                                  
+
                                                                                                                                  Shows SQL statements for creating a table.
                                                                                                                                  
+
                                                                                                                                  SHOW_CREATE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Dropping a table
                                                                                                                                  
+
                                                                                                                                  Drops tables and their data.
                                                                                                                                  
+
                                                                                                                                  DROP_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Clearing table data
                                                                                                                                  
+
                                                                                                                                  Deletes all data in a table but retains the table structure.
                                                                                                                                  
+
                                                                                                                                  TRUNCATE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Renaming a table
                                                                                                                                  
+
                                                                                                                                  Renames tables.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_RENAME
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Inserting table data
                                                                                                                                  
+
                                                                                                                                  Adds data records to a table.
                                                                                                                                  
+
                                                                                                                                  INSERT_INTO_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Overwriting a table
                                                                                                                                  
+
                                                                                                                                  Inserts new data and overwrites the original data in a table.
                                                                                                                                  
+
                                                                                                                                  INSERT_OVERWRITE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Adding a column
                                                                                                                                  
+
                                                                                                                                  Adds columns to a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_ADD_COLUMNS
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Accessing metadata
                                                                                                                                  
+
                                                                                                                                  Allows Spark applications to read metadata.
                                                                                                                                  
+
                                                                                                                                  SPARK_APP_ACCESS_META
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Viewing permissions of other users
                                                                                                                                  
+
                                                                                                                                  Lists a user's or role's permissions.
                                                                                                                                  
+
                                                                                                                                  SHOW_PRIVILEGES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Getting permissions
                                                                                                                                  
+
                                                                                                                                  Grants permissions to a user or role.
                                                                                                                                  
+
                                                                                                                                  GRANT_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Revoking permissions
                                                                                                                                  
+
                                                                                                                                  Revokes permissions from a user or role.
                                                                                                                                  
+
                                                                                                                                  REVOKE_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Collecting table statistics
                                                                                                                                  
+
                                                                                                                                  Collects statistics about a table.
                                                                                                                                  
+
                                                                                                                                  ANALYZE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Adding a partition
                                                                                                                                  
+
                                                                                                                                  Adds partitions to a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_ADD_PARTITION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Deleting a partition
                                                                                                                                  
+
                                                                                                                                  Removes partitions from a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_DROP_PARTITION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Setting the partition path
                                                                                                                                  
+
                                                                                                                                  Modifies the storage location of table data.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_SET_LOCATION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Renaming a table partition
                                                                                                                                  
+
                                                                                                                                  Renames partitions.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_RENAME_PARTITION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Restoring a table partition
                                                                                                                                  
+
                                                                                                                                  Restores lost or damaged partitions.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_RECOVER_PARTITION
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  Showing all partitions
                                                                                                                                  
+
                                                                                                                                  Lists all partitions of a table.
                                                                                                                                  
+
                                                                                                                                  SHOW_PARTITIONS
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single project or cross-tenant project
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Table
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 5 Table permission set (non-inheritable permission)
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  Description
                                                                                                                                  
+
                                                                                                                                  DLI Privileges
                                                                                                                                  
+
                                                                                                                                  Authorizable Through DLI Console (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorizable Through API (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorization Object
                                                                                                                                  
+
                                                                                                                                  Showing a table
                                                                                                                                  
+
                                                                                                                                  Shows the column names and data types of a table.
                                                                                                                                  
+
                                                                                                                                  DISPLAY_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Querying tables
                                                                                                                                  
+
                                                                                                                                  Retrieves data records from a table.
                                                                                                                                  
+
                                                                                                                                  SELECT
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Showing table information
                                                                                                                                  
+
                                                                                                                                  Shows the column names and data types of a table.
                                                                                                                                  
+
                                                                                                                                  DESCRIBE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Showing the table creation statement
                                                                                                                                  
+
                                                                                                                                  Shows SQL statements for creating a table.
                                                                                                                                  
+
                                                                                                                                  SHOW_CREATE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Dropping a table
                                                                                                                                  
+
                                                                                                                                  Drops tables and their data.
                                                                                                                                  
+
                                                                                                                                  DROP_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Clearing table data
                                                                                                                                  
+
                                                                                                                                  Deletes all data in a table but retains the table structure.
                                                                                                                                  
+
                                                                                                                                  TRUNCATE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Renaming a table
                                                                                                                                  
+
                                                                                                                                  Renames tables.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_RENAME
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Inserting table data
                                                                                                                                  
+
                                                                                                                                  Adds data records to a table.
                                                                                                                                  
+
                                                                                                                                  INSERT_INTO_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Overwriting a table
                                                                                                                                  
+
                                                                                                                                  Inserts new data and overwrites the original data in a table.
                                                                                                                                  
+
                                                                                                                                  INSERT_OVERWRITE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Adding a column
                                                                                                                                  
+
                                                                                                                                  Adds columns to a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_ADD_COLUMNS
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Accessing metadata
                                                                                                                                  
+
                                                                                                                                  Allows Spark applications to read metadata.
                                                                                                                                  
+
                                                                                                                                  SPARK_APP_ACCESS_META
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Viewing permissions of other users
                                                                                                                                  
+
                                                                                                                                  Lists a user's or role's permissions.
                                                                                                                                  
+
                                                                                                                                  SHOW_PRIVILEGES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Granting permissions
                                                                                                                                  
+
                                                                                                                                  Grants permissions to a user or role.
                                                                                                                                  
+
                                                                                                                                  GRANT_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Revoking permissions
                                                                                                                                  
+
                                                                                                                                  Revokes permissions from a user or role.
                                                                                                                                  
+
                                                                                                                                  REVOKE_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Collecting table statistics
                                                                                                                                  
+
                                                                                                                                  Collects statistics about a table.
                                                                                                                                  
+
                                                                                                                                  ANALYZE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Updating table data
                                                                                                                                  
+
                                                                                                                                  Modifies data records in a table.
                                                                                                                                  
+
                                                                                                                                  UPDATE_TABLE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Dropping a table column
                                                                                                                                  
+
                                                                                                                                  Removes one or more columns from a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_DROP_COLUMNS
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Modifying a table column
                                                                                                                                  
+
                                                                                                                                  Changes the column name, data type, and other attributes.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_CHANGE_COLUMN
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Setting the table storage location
                                                                                                                                  
+
                                                                                                                                  Specifies a new path for storing table data.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_SET_LOCATION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Setting table attributes
                                                                                                                                  
+
                                                                                                                                  Modifies the metadata attribute of a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_SET_PROPERTIES
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Querying table information
                                                                                                                                  
+
                                                                                                                                  Queries the structure and metadata of a table.
                                                                                                                                  
+
                                                                                                                                  GET_TABLE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Creating a partition
                                                                                                                                  
+
                                                                                                                                  Creates partition structures for a table.
                                                                                                                                  
+
                                                                                                                                  CREATE_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting a partition
                                                                                                                                  
+
                                                                                                                                  Removes partitions from a table.
                                                                                                                                  
+
                                                                                                                                  DROP_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Updating a partition
                                                                                                                                  
+
                                                                                                                                  Modifies metadata or data of a partition.
                                                                                                                                  
+
                                                                                                                                  UPDATE_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Querying partition information
                                                                                                                                  
+
                                                                                                                                  Queries details about a partition.
                                                                                                                                  
+
                                                                                                                                  GET_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Listing partitions
                                                                                                                                  
+
                                                                                                                                  Shows all partitions of a table.
                                                                                                                                  
+
                                                                                                                                  LIST_PARTITIONS
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Modifying a view
                                                                                                                                  
+
                                                                                                                                  Updates the definition or attributes of a view.
                                                                                                                                  
+
                                                                                                                                  ALTER_VIEW
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Migrating data
                                                                                                                                  
+
                                                                                                                                  Migrates data from one location to another.
                                                                                                                                  
+
                                                                                                                                  DATA_MIGRATION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Modifying an object
                                                                                                                                  
+
                                                                                                                                  Modifies the attributes or structure of a database object.
                                                                                                                                  
+
                                                                                                                                  ALTER
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Updating data
                                                                                                                                  
+
                                                                                                                                  Modifies the data in a table.
                                                                                                                                  
+
                                                                                                                                  UPDATE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting data
                                                                                                                                  
+
                                                                                                                                  Deletes data records from a table.
                                                                                                                                  
+
                                                                                                                                  DELETE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Adding a partition
                                                                                                                                  
+
                                                                                                                                  Adds partitions to a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_ADD_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting a partition
                                                                                                                                  
+
                                                                                                                                  Removes partitions from a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_DROP_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Renaming a partition
                                                                                                                                  
+
                                                                                                                                  Renames partitions.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_RENAME_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Restoring a partition
                                                                                                                                  
+
                                                                                                                                  Restores lost or damaged partitions.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_RECOVER_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 6 Table project authorization/Cross-tenant project authorization permission set (non-inheritable permission)
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  Description
                                                                                                                                  
+
                                                                                                                                  DLI Privileges
                                                                                                                                  
+
                                                                                                                                  Authorizable Through DLI Console (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorizable Through API (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorization Object
                                                                                                                                  
+
                                                                                                                                  Querying tables
                                                                                                                                  
+
                                                                                                                                  Retrieves data records from a table.
                                                                                                                                  
+
                                                                                                                                  SELECT
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Showing table information
                                                                                                                                  
+
                                                                                                                                  Shows the column names and data types of a table.
                                                                                                                                  
+
                                                                                                                                  DESCRIBE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Showing the table creation statement
                                                                                                                                  
+
                                                                                                                                  Shows SQL statements for creating a table.
                                                                                                                                  
+
                                                                                                                                  SHOW_CREATE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Dropping a table
                                                                                                                                  
+
                                                                                                                                  Drops tables and their data.
                                                                                                                                  
+
                                                                                                                                  DROP_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Clearing table data
                                                                                                                                  
+
                                                                                                                                  Deletes all data in a table but retains the table structure.
                                                                                                                                  
+
                                                                                                                                  TRUNCATE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Renaming a table
                                                                                                                                  
+
                                                                                                                                  Renames tables.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_RENAME
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Inserting table data
                                                                                                                                  
+
                                                                                                                                  Adds data records to a table.
                                                                                                                                  
+
                                                                                                                                  INSERT_INTO_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Overwriting a table
                                                                                                                                  
+
                                                                                                                                  Inserts new data and overwrites the original data in a table.
                                                                                                                                  
+
                                                                                                                                  INSERT_OVERWRITE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Adding a column
                                                                                                                                  
+
                                                                                                                                  Adds columns to a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_ADD_COLUMNS
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Accessing metadata
                                                                                                                                  
+
                                                                                                                                  Allows Spark applications to read metadata.
                                                                                                                                  
+
                                                                                                                                  SPARK_APP_ACCESS_META
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Viewing permissions of other users
                                                                                                                                  
+
                                                                                                                                  Lists a user's or role's permissions.
                                                                                                                                  
+
                                                                                                                                  SHOW_PRIVILEGES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Granting permissions
                                                                                                                                  
+
                                                                                                                                  Grants permissions to a user or role.
                                                                                                                                  
+
                                                                                                                                  GRANT_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Revoking permissions
                                                                                                                                  
+
                                                                                                                                  Revokes permissions from a user or role.
                                                                                                                                  
+
                                                                                                                                  REVOKE_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Collecting table statistics
                                                                                                                                  
+
                                                                                                                                  Collects statistics about a table.
                                                                                                                                  
+
                                                                                                                                  ANALYZE_TABLE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Updating table data
                                                                                                                                  
+
                                                                                                                                  Modifies data records in a table.
                                                                                                                                  
+
                                                                                                                                  UPDATE_TABLE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Dropping a table column
                                                                                                                                  
+
                                                                                                                                  Removes one or more columns from a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_DROP_COLUMNS
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Modifying a table column
                                                                                                                                  
+
                                                                                                                                  Changes the column name, data type, and other attributes.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_CHANGE_COLUMN
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Setting the table storage location
                                                                                                                                  
+
                                                                                                                                  Specifies a new path for storing table data.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_SET_LOCATION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Setting table attributes
                                                                                                                                  
+
                                                                                                                                  Modifies the metadata attribute of a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_SET_PROPERTIES
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Querying table information
                                                                                                                                  
+
                                                                                                                                  Queries the structure and metadata of a table.
                                                                                                                                  
+
                                                                                                                                  GET_TABLE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Creating a partition
                                                                                                                                  
+
                                                                                                                                  Creates partition structures for a table.
                                                                                                                                  
+
                                                                                                                                  CREATE_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting a partition
                                                                                                                                  
+
                                                                                                                                  Removes partitions from a table.
                                                                                                                                  
+
                                                                                                                                  DROP_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Updating a partition
                                                                                                                                  
+
                                                                                                                                  Modifies metadata or data of a partition.
                                                                                                                                  
+
                                                                                                                                  UPDATE_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Querying partition information
                                                                                                                                  
+
                                                                                                                                  Queries details about a partition.
                                                                                                                                  
+
                                                                                                                                  GET_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Listing partitions
                                                                                                                                  
+
                                                                                                                                  Shows all partitions of a table.
                                                                                                                                  
+
                                                                                                                                  LIST_PARTITIONS
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Modifying a view
                                                                                                                                  
+
                                                                                                                                  Updates the definition or attributes of a view.
                                                                                                                                  
+
                                                                                                                                  ALTER_VIEW
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Migrating data
                                                                                                                                  
+
                                                                                                                                  Migrates data from one location to another.
                                                                                                                                  
+
                                                                                                                                  DATA_MIGRATION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Modifying an object
                                                                                                                                  
+
                                                                                                                                  Modifies the attributes or structure of a database object.
                                                                                                                                  
+
                                                                                                                                  ALTER
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Updating data
                                                                                                                                  
+
                                                                                                                                  Modifies the data in a table.
                                                                                                                                  
+
                                                                                                                                  UPDATE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting data
                                                                                                                                  
+
                                                                                                                                  Deletes data records from a table.
                                                                                                                                  
+
                                                                                                                                  DELETE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Adding a partition
                                                                                                                                  
+
                                                                                                                                  Adds partitions to a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_ADD_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting a partition
                                                                                                                                  
+
                                                                                                                                  Removes partitions from a table.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_DROP_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Renaming a partition
                                                                                                                                  
+
                                                                                                                                  Renames partitions.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_RENAME_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Restoring a partition
                                                                                                                                  
+
                                                                                                                                  Restores lost or damaged partitions.
                                                                                                                                  
+
                                                                                                                                  ALTER_TABLE_RECOVER_PARTITION
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Column
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 7 Column permission set
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  Description
                                                                                                                                  
+
                                                                                                                                  DLI Privileges
                                                                                                                                  
+
                                                                                                                                  Authorizable Through DLI Console (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorizable Through API (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorization Object
                                                                                                                                  
+
                                                                                                                                  Querying a column
                                                                                                                                  
+
                                                                                                                                  Searches for columns.
                                                                                                                                  
+
                                                                                                                                  SELECT
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Flink Job
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 8 Flink job permission set
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  Description
                                                                                                                                  
+
                                                                                                                                  DLI Privileges
                                                                                                                                  
+
                                                                                                                                  Authorizable Through DLI Console (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorizable Through API (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorization Object
                                                                                                                                  
+
                                                                                                                                  Viewing job details
                                                                                                                                  
+
                                                                                                                                  Queries details about a specified Flink job.
                                                                                                                                  
+
                                                                                                                                  GET
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Updating a job
                                                                                                                                  
+
                                                                                                                                  Modifies specified Flink jobs.
                                                                                                                                  
+
                                                                                                                                  UPDATE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting a job
                                                                                                                                  
+
                                                                                                                                  Deletes specified Flink jobs.
                                                                                                                                  
+
                                                                                                                                  DELETE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Starting a job
                                                                                                                                  
+
                                                                                                                                  Starts Flink jobs.
                                                                                                                                  
+
                                                                                                                                  START
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Stopping a job
                                                                                                                                  
+
                                                                                                                                  Stops Flink jobs.
                                                                                                                                  
+
                                                                                                                                  STOP
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Exporting a job
                                                                                                                                  
+
                                                                                                                                  Exports Flink jobs to a specified location.
                                                                                                                                  
+
                                                                                                                                  EXPORT
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Granting permissions
                                                                                                                                  
+
                                                                                                                                  Grants permissions to Flink jobs.
                                                                                                                                  
+
                                                                                                                                  GRANT_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Revoking permissions
                                                                                                                                  
+
                                                                                                                                  Revokes permissions from Flink jobs.
                                                                                                                                  
+
                                                                                                                                  REVOKE_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Viewing permissions of other users
                                                                                                                                  
+
                                                                                                                                  Lists a user's permissions.
                                                                                                                                  
+
                                                                                                                                  SHOW_PRIVILEGES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Creating a Flink job
                                                                                                                                  
+
                                                                                                                                  Creates Flink jobs.
                                                                                                                                  
+
                                                                                                                                  CREATE
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  All resources (*)
                                                                                                                                  
+
                                                                                                                                  Listing all Flink jobs
                                                                                                                                  
+
                                                                                                                                  Shows all Flink jobs in the system.
                                                                                                                                  
+
                                                                                                                                  LIST_ALL
                                                                                                                                  
+
                                                                                                                                  No
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  All resources (*)
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Package and Package Group
                                                                                                                                  
+
                                                                                                                                  A package inherits all the permissions of its package group.
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 9 Package permission set
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  DLI Privileges
                                                                                                                                  
+
                                                                                                                                  Authorizable Through DLI Console (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorizable Through API (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorization Object
                                                                                                                                  
+
                                                                                                                                  Using a package
                                                                                                                                  
+
                                                                                                                                  USE_RESOURCE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Updating a package
                                                                                                                                  
+
                                                                                                                                  UPDATE_RESOURCE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Querying a package
                                                                                                                                  
+
                                                                                                                                  GET_RESOURCE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting a package
                                                                                                                                  
+
                                                                                                                                  DELETE_RESOURCE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Granting permissions
                                                                                                                                  
+
                                                                                                                                  GRANT_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Revoking permissions
                                                                                                                                  
+
                                                                                                                                  REVOKE_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Viewing permissions of other users
                                                                                                                                  
+
                                                                                                                                  SHOW_PRIVILEGES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 10 Package group permission set
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  DLI Privileges
                                                                                                                                  
+
                                                                                                                                  Authorizable Through DLI Console (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorizable Through API (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorization Object
                                                                                                                                  
+
                                                                                                                                  Using a group
                                                                                                                                  
+
                                                                                                                                  USE_GROUP
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Updating a group
                                                                                                                                  
+
                                                                                                                                  UPDATE_GROUP
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Querying a group
                                                                                                                                  
+
                                                                                                                                  GET_GROUP
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting a group
                                                                                                                                  
+
                                                                                                                                  DELETE_GROUP
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Granting permissions
                                                                                                                                  
+
                                                                                                                                  GRANT_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Revoking permissions
                                                                                                                                  
+
                                                                                                                                  REVOKE_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Viewing permissions of other users
                                                                                                                                  
+
                                                                                                                                  SHOW_PRIVILEGES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Datasource Authentication
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 11 Datasource authentication permission set
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  DLI Privileges
                                                                                                                                  
+
                                                                                                                                  Authorizable Through DLI Console (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorizable Through API (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorization Object
                                                                                                                                  
+
                                                                                                                                  Using datasource authentication
                                                                                                                                  
+
                                                                                                                                  USE_AUTH
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Updating datasource authentication
                                                                                                                                  
+
                                                                                                                                  UPDATE_AUTH
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting datasource authentication
                                                                                                                                  
+
                                                                                                                                  DROP_AUTH
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Granting permissions
                                                                                                                                  
+
                                                                                                                                  GRANT_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Revoking permissions
                                                                                                                                  
+
                                                                                                                                  REVOKE_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Viewing permissions of other users
                                                                                                                                  
+
                                                                                                                                  SHOW_PRIVILEGES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Enhanced Datasource Connection
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 12 Enhanced datasource connection cross-project authorization permission set
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  DLI Privileges
                                                                                                                                  
+
                                                                                                                                  Authorizable Through DLI Console (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorizable Through API (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorization Object
                                                                                                                                  
+
                                                                                                                                  Binding a queue
                                                                                                                                  
+
                                                                                                                                  BIND_QUEUE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Global Variable
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 13 Global variable permission set
                                                                                                                                  Operation
                                                                                                                                  
+
                                                                                                                                  DLI Privileges
                                                                                                                                  
+
                                                                                                                                  Authorizable Through DLI Console (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorizable Through API (Yes/No)
                                                                                                                                  
+
                                                                                                                                  Authorization Object
                                                                                                                                  
+
                                                                                                                                  Updating a global variable
                                                                                                                                  
+
                                                                                                                                  UPDATE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Deleting a global variable
                                                                                                                                  
+
                                                                                                                                  DELETE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Granting permissions
                                                                                                                                  
+
                                                                                                                                  GRANT_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Revoking permissions
                                                                                                                                  
+
                                                                                                                                  REVOKE_PRIVILEGE
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  Viewing permissions of other users
                                                                                                                                  
+
                                                                                                                                  SHOW_PRIVILEGES
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Yes
                                                                                                                                  
+
                                                                                                                                  Single resource
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Parent topic: DLI Permission Management
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
diff --git a/docs/dli/umn/dli_01_0692.html b/docs/dli/umn/dli_01_0692.html
new file mode 100644
index 000000000..297285070
--- /dev/null
+++ b/docs/dli/umn/dli_01_0692.html
@@ -0,0 +1,62 @@
+
+
+
                                                                                                                                  DLI Authorization Operation Guide
                                                                                                                                  
+
                                                                                                                                  Scenario
                                                                                                                                  This section describes how to authorize resources on the DLI console.
                                                                                                                                  
+
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 1 DLI resource authorization methods
                                                                                                                                  Resource
                                                                                                                                  
+
                                                                                                                                  Reference
                                                                                                                                  
+
                                                                                                                                  Elastic resource pool
                                                                                                                                  
+
                                                                                                                                  Managing Permissions
                                                                                                                                  
+
                                                                                                                                  Queue
                                                                                                                                  
+
                                                                                                                                  Queue Permission Management
                                                                                                                                  
+
                                                                                                                                  Data catalog
                                                                                                                                  
+
                                                                                                                                  Configuring Data Catalog Permissions on the DLI Console
                                                                                                                                  
+
                                                                                                                                  Database
                                                                                                                                  
+
                                                                                                                                  Configuring Database Permissions on the DLI Console
                                                                                                                                  
+
                                                                                                                                  Table
                                                                                                                                  
+
                                                                                                                                  Configuring Table Permissions on the DLI Console
                                                                                                                                  
+
                                                                                                                                  Package and package group
                                                                                                                                  
+
                                                                                                                                  Configuring DLI Package Permissions
                                                                                                                                  
+
                                                                                                                                  Global variable
                                                                                                                                  
+
                                                                                                                                  Managing DLI Global Variables
                                                                                                                                  
+
                                                                                                                                  Enhanced datasource connection
                                                                                                                                  
+
                                                                                                                                  Enhanced Connection Permission Management
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Parent topic: DLI Permission Management
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
diff --git a/docs/dli/umn/dli_01_0693.html b/docs/dli/umn/dli_01_0693.html
new file mode 100644
index 000000000..9f936966c
--- /dev/null
+++ b/docs/dli/umn/dli_01_0693.html
@@ -0,0 +1,47 @@
+
+
+
                                                                                                                                  IAM Authorization Entity
                                                                                                                                  
+
                                                                                                                                  In IAM, authorization entities are primarily categorized into users and user groups. Integration with enterprise projects enables resource isolation by group and facilitates refined permission management.
                                                                                                                                  
+
                                                                                                                                  IAM Authorization Entity
                                                                                                                                  
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 1 IAM authorization entities
                                                                                                                                  Type
                                                                                                                                  
+
                                                                                                                                  Description
                                                                                                                                  
+
                                                                                                                                  User
                                                                                                                                  
+
                                                                                                                                  The user you create using a master account in IAM. Each IAM user has their own identity credentials (password and access keys) and can use cloud resources after being granted permissions. IAM users do not own any resources.
                                                                                                                                  
+
                                                                                                                                  • You can grant specific permission policies to IAM users to define their scope of operations on resources.
                                                                                                                                  • You can add IAM users to user groups, and they can inherit the permissions of the user groups.
                                                                                                                                  • You can associate IAM users with enterprise projects for more fine-grained permission management.
                                                                                                                                  
+
                                                                                                                                  User group
                                                                                                                                  
+
                                                                                                                                  A user group is a collection of IAM users. You can create user groups and add IAM users to them to quickly grant permissions to the users.
                                                                                                                                  
+
                                                                                                                                  • You can grant permission policies to a user group, and all users in the group automatically inherit these permissions.
                                                                                                                                  • You can associate user groups with enterprise projects for resource isolation and permission control.
                                                                                                                                  • You can create user groups with nested structures to further refine permission management.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Enterprise Project
                                                                                                                                  An enterprise project is a resource grouping management function, designed to partition resources into distinct logical units for grouped isolation and access control.
                                                                                                                                  
+
                                                                                                                                  When using IAM authorization, associating IAM authorization entities (users and user groups) with enterprise projects effectively achieves grouped resource isolation and refined permission control.
                                                                                                                                  
+
                                                                                                                                  Example: Use enterprise projects to group and isolate DLI resource pools and grant different user groups the permissions to access the corresponding enterprise projects.
                                                                                                                                  
+
                                                                                                                                  An enterprise has two project teams A and B. Project team A and project team B use distinct elastic resource pools and databases. To ensure effective isolation of resources and data, the enterprise plans to use IAM to control access permissions to different resources, ensuring that users in project team A can only access resources corresponding to project team A, and users in project team B can only access resources corresponding to project team B.
                                                                                                                                  
+
                                                                                                                                  1. Create enterprise projects and associate elastic resource pools and databases with the enterprise projects.
                                                                                                                                    Create enterprise project A and associate the resources used by project team A with enterprise project A.
                                                                                                                                    
+
                                                                                                                                    Create enterprise project B and associate the resources used by project team B with enterprise project B.
                                                                                                                                    
+
                                                                                                                                  2. Create user groups.
                                                                                                                                    Create user group A and add users in project team A to user group A.
                                                                                                                                    
+
                                                                                                                                    Create user group B and add users in project team B to user group B.
                                                                                                                                    
+
                                                                                                                                  3. Grant permissions to user groups.
                                                                                                                                    Grant permissions to user group A. On the Select Scope page, select Enterprise projects, and select enterprise project A created in 1.
                                                                                                                                    
+
                                                                                                                                    Grant permissions to user group B. On the Select Scope page, select Enterprise projects, and select enterprise project B created in 1.
                                                                                                                                    
+
                                                                                                                                  
+
                                                                                                                                  In this way, enterprises can group and isolate resources for refined permission control. This ensures both secure and efficient resource utilization.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Parent topic: IAM Permission Management
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
diff --git a/docs/dli/umn/dli_01_0695.html b/docs/dli/umn/dli_01_0695.html
new file mode 100644
index 000000000..d1ab51446
--- /dev/null
+++ b/docs/dli/umn/dli_01_0695.html
@@ -0,0 +1,157 @@
+
+
+
                                                                                                                                  Example Use Case: Creating a User Group and Granting Permissions for Using DLI Elastic Resource Pools and Databases
                                                                                                                                  
+
                                                                                                                                  Description
                                                                                                                                  An e-commerce company conducts data analysis operations in region A. The marketing department's employees, user 1 and user 2, along with the technical department's employees, user 3 and user 4, need to use DLI elastic resource pools and databases to accomplish various tasks.
                                                                                                                                  
+
                                                                                                                                  • Add the marketing department employees to user group G1 and the technical department employees to user group G2.
                                                                                                                                    Figure 1 Adding users to user groups
                                                                                                                                    
+
                                                                                                                                  • Associate compute resource E1 and database DB1 with enterprise project A to store sales data and user behavior data.
                                                                                                                                  • Associate compute resource E2 and database DB2 with enterprise project B to store system logs and server performance data.
                                                                                                                                    Figure 2 Associating resources with enterprise projects
                                                                                                                                    
+
                                                                                                                                  
+
                                                                                                                                  User 1 in the marketing department needs to perform in-depth analysis on sales data. To delete invalid data in a timely manner, user 1 must have the permission to delete resources in enterprise project A.
                                                                                                                                  
+
                                                                                                                                  User 2 in the marketing department is responsible for evaluating the effectiveness of marketing activities and needs to have the permission to delete related data resources to ensure data timeliness.
                                                                                                                                  
+
                                                                                                                                  User 3 in the technical department focuses on system log analysis and only needs to read and use resources in enterprise project B.
                                                                                                                                  
+
                                                                                                                                  User 4 in the technical department is responsible for monitoring server performance and performing read-only operations on related resources.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Authorization Scheme Analysis
                                                                                                                                  Based on the preceding service requirements, combined with the DLI service permissions, IAM permission management, and enterprise project management methods, there are two authorization schemes to choose from:
                                                                                                                                  
+
                                                                                                                                  Scheme 1: Grant access permissions to corresponding enterprise project resources to user groups G1 and G2 through IAM, and separately grant resource deletion permissions to user 1 and user 2.
                                                                                                                                  
+
                                                                                                                                  Scheme 2: Through the permission management method provided by DLI, individually set different resource usage permissions according to the specific job requirements of each user.
                                                                                                                                  
+
                                                                                                                                  This section details the operational steps for both scheme 1 and scheme 2.
                                                                                                                                  
+
                                                                                                                                  When submitting jobs using elastic resource pools, you need to have the permission to use queues. In this example, we take the submission and cancellation of jobs for queues in the elastic resource pool as an example.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Scheme 1: Use IAM to Grant Enterprise User Groups A and B Different Resource Permissions
                                                                                                                                  When submitting jobs using elastic resource pools, you need to have the permission to use queues. In this example, we take the submission and cancellation of jobs for queues in the elastic resource pool as an example.
                                                                                                                                  
+
                                                                                                                                  Prerequisites: You have added users to user groups and associated resources with enterprise projects.
                                                                                                                                  
+
                                                                                                                                  1. Create a custom IAM policy Policy_A to grant the permission to access resources E1 and DB1 under enterprise project A.
                                                                                                                                    Example policy content:
                                                                                                                                    {
+    "Version": "1.1",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "dli:elasticresourcepool:resourceManagement",
+                "dli:queue:submitJob",
+                "dli:queue:cancelJob",
+                "dli:database:list"
+            ],
+            "Resource": [
+                "dli:*:*:elasticresourcepool:elasticresourcepools.E1",
+                "dli:*:*:database:databases.DB1"
+            ]
+        }
+    ]
+}
                                                                                                                                    
+
                                                                                                                                    
+
                                                                                                                                  2. Create a custom IAM policy Policy_B to grant the permission to access resources E2 and DB2 under enterprise project B.
                                                                                                                                    Example policy content:
                                                                                                                                    {
+    "Version": "1.1",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "dli:elasticresourcepool:resourceManagement",
+                "dli:queue:submitJob",
+                "dli:queue:cancelJob",
+                "dli:database:list"
+            ],
+            "Resource": [
+                "dli:*:*:elasticresourcepool:elasticresourcepools.E2",
+                "dli:*:*:database:databases.DB2"
+            ]
+        }
+    ]
+}
                                                                                                                                    
+
                                                                                                                                    
+
                                                                                                                                  3. Create Policy_C to grant the resource deletion permission to user 1 and user 2.
                                                                                                                                    Example policy content:
                                                                                                                                    
+
                                                                                                                                    {
+    "Version": "1.1",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "dli:elasticresourcepool:drop",
+                "dli:database:dropDatabase"
+            ],
+            "Resource": [
+                "dli:*:*:elasticresourcepool:elasticresourcepool.E1",
+                "dli:*:*:database:databases.DB1"
+            ]
+        }
+    ]
+}
                                                                                                                                    
+
                                                                                                                                  4. Grant permissions to user groups.
                                                                                                                                    In the user group list, click Authorize in the Operation column of the user groups.
                                                                                                                                    
+
                                                                                                                                    • Selecting a policy:
                                                                                                                                      Apply Policy_A to user group G1.
                                                                                                                                      
+
                                                                                                                                      Apply Policy_B to user group G2.
                                                                                                                                      
+
                                                                                                                                      Apply the deletion permission policy Policy_C to user 1 and user 2, respectively.
                                                                                                                                      
+
                                                                                                                                    • Selecting the minimum authorization scope
                                                                                                                                      When authorizing user group G1, associate the authorization scope with enterprise project A.
                                                                                                                                      
+
                                                                                                                                      When authorizing user group G2, associate the authorization scope with enterprise project B.
                                                                                                                                      
+
                                                                                                                                      When granting the deletion permission to user 1 and user 2, associate the authorization scope with enterprise project A.
                                                                                                                                      
+
                                                                                                                                    
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Solution 2: Authorizing Different Permissions for Users User 1, User 2, User 3, and User 4 Using DLI Resources
                                                                                                                                  Prerequisites: You have added users to user groups and associated resources with enterprise projects.
                                                                                                                                  
+
                                                                                                                                  The permissions here are only examples. Select the permissions as required.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Log in to the DLI management console, find the corresponding resources, and use the user authorization function of DLI to grant appropriate permissions to each user.
                                                                                                                                  
+
                                                                                                                                  • Elastic resource pool E1
                                                                                                                                    • User 1: Submit jobs, terminate jobs, and delete queues.
                                                                                                                                    • User 2: Submit jobs, terminate jobs, and delete queues.
                                                                                                                                    
+
                                                                                                                                  • Elastic resource pool E2
                                                                                                                                    • User 3: Submit jobs and terminate jobs.
                                                                                                                                    • User 4: Submit jobs and terminate jobs.
                                                                                                                                    
+
                                                                                                                                  • Database DB1
                                                                                                                                    • User 1: Display all tables, show databases, delete databases, query tables, insert data, rewrite data, fill in columns, add partitions, delete partitions, update table data, update data, and delete data.
                                                                                                                                    • User 2: Display all tables, show databases, delete databases, query tables, insert data, rewrite data, fill in columns, add partitions, delete partitions, update table data, update data, and delete data.
                                                                                                                                    
+
                                                                                                                                  • Database DB2
                                                                                                                                    • User 3: Display all tables, show databases, query tables, insert data, rewrite data, fill in columns, add partitions, delete partitions, update table data, update data, and delete data.
                                                                                                                                    • User 4: Display all tables, show databases, query tables, insert data, rewrite data, fill in columns, add partitions, delete partitions, update table data, update data, and delete data.
                                                                                                                                    
+
                                                                                                                                  
+
                                                                                                                                  Scheme Comparison
                                                                                                                                  • Scheme 1: The IAM user group authorization method is more suitable for scenarios that require batch management of user permissions. By combining user groups and policies, it efficiently allocates permissions while facilitating subsequent management.
                                                                                                                                  • Scheme 2: The DLI user-level authorization method is better suited for scenarios where fine-grained permission management for each user is needed. It can meet complex service requirements but comes with relatively higher management costs.
                                                                                                                                  
+
+
                                                                                                                                  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                  Table 1 Scheme comparison
                                                                                                                                  Item
                                                                                                                                  
+
                                                                                                                                  Scheme 1: IAM User Group Authorization
                                                                                                                                  
+
                                                                                                                                  Scheme 2: DLI User-Level Authorization
                                                                                                                                  
+
                                                                                                                                  User authorization complexity
                                                                                                                                  
+
                                                                                                                                  Based on user groups, suitable for batch management.
                                                                                                                                  
+
                                                                                                                                  Based on individual users, suitable for fine-grained permission control.
                                                                                                                                  
+
                                                                                                                                  Permission configuration complexity
                                                                                                                                  
+
                                                                                                                                  Centralized policy management, lower complexity.
                                                                                                                                  
+
                                                                                                                                  Independent configuration per user, higher complexity.
                                                                                                                                  
+
                                                                                                                                  Resource isolation
                                                                                                                                  
+
                                                                                                                                  Isolated by enterprise projects, ideal for multi-team environments.
                                                                                                                                  
+
                                                                                                                                  Flexible cross-project authorization, suitable for collaborative scenarios.
                                                                                                                                  
+
                                                                                                                                  Delete permission management
                                                                                                                                  
+
                                                                                                                                  Separate delete permission configuration at the user level.
                                                                                                                                  
+
                                                                                                                                  Delete permission directly selected in resource authorization.
                                                                                                                                  
+
                                                                                                                                  Use case
                                                                                                                                  
+
                                                                                                                                  Large organizations managing resources across teams
                                                                                                                                  
+
                                                                                                                                  Small teams or scenarios requiring differentiated permissions
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Parent topic: DLI Permission Management
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_03_0032.html b/docs/dli/umn/dli_03_0032.html
index 71657ecfa..62901e820 100644
--- a/docs/dli/umn/dli_03_0032.html
+++ b/docs/dli/umn/dli_03_0032.html
@@ -4,7 +4,7 @@
 
                                                                                                                                  How Do I Apply for a Higher Quota?
                                                                                                                                  The system does not support online quota adjustment. To increase a resource quota, dial the hotline or send an email to the customer service. We will process your application and inform you of the progress by phone call or email.
                                                                                                                                  
 
                                                                                                                                  Before dialing the hotline number or sending an email, ensure that the following information has been obtained:
                                                                                                                                  
 
                                                                                                                                  • Domain name, project name, and project ID
                                                                                                                                    To obtain the preceding information, log in to the management console, click the username in the upper right corner, and choose My Credentials from the drop-down list.
                                                                                                                                    
-
                                                                                                                                  • Quota information, including:
                                                                                                                                    • ServiceName
                                                                                                                                    • Quota type
                                                                                                                                    • Required quota
                                                                                                                                    
+
                                                                                                                                  • Quota information, including:
                                                                                                                                    • Service name
                                                                                                                                    • Quota type
                                                                                                                                    • Required quota
                                                                                                                                    
 
                                                                                                                                  
 
                                                                                                                                  Learn how to obtain the service hotline and email address.
                                                                                                                                  
 
                                                                                                                                  
diff --git a/docs/dli/umn/dli_03_0044.html b/docs/dli/umn/dli_03_0044.html
index 13fce0fd4..7a7765683 100644
--- a/docs/dli/umn/dli_03_0044.html
+++ b/docs/dli/umn/dli_03_0044.html
@@ -31,7 +31,7 @@ private void initConf() {
         e.printStackTrace();
     }
 }
-
                                                                                                                                  Figure 1 Example relative path configuration
                                                                                                                                  
+
                                                                                                                                  Figure 1 Example relative path configuration
                                                                                                                                  
 
                                                                                                                                6. Example of using an absolute path:
                                                                                                                                  Absolute path: confPath = userData/kafka-sink.conf / path = /opt/data1/hadoop/tmp/usercache/omm/appcache/application_xxx_0015/container_xxx_0015_01_000002/userData/client.truststore.jks
 @Override
 public void open(Configuration parameters) throws Exception {
@@ -60,7 +60,7 @@ private void initConf() {
         e.printStackTrace();
     }
 }
                                                                                                                                  
-
                                                                                                                                  Figure 2 Example absolute path configuration
                                                                                                                                  
+
                                                                                                                                  Figure 2 Example absolute path configuration
                                                                                                                                  
 
                                                                                                                                  7. 
 
 
                                                                                                                                
@@ -71,3 +71,10 @@ private void initConf() {
 
                                                                                                                                
 
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_03_0047.html b/docs/dli/umn/dli_03_0047.html
index 39076b898..cc8232a43 100644
--- a/docs/dli/umn/dli_03_0047.html
+++ b/docs/dli/umn/dli_03_0047.html
@@ -3,7 +3,7 @@
 
                                                                                                                                How Do I Resolve the "communication link failure" Error When Using a Newly Created Datasource Connection That Appears to Be Activated?
                                                                                                                                
 
                                                                                                                                Possible Causes
                                                                                                                                The network connectivity is abnormal. Check whether the security group is correctly selected and whether the VPC is correctly configured.
                                                                                                                                
 
                                                                                                                                
-
                                                                                                                                Solution
                                                                                                                                Example: When you create an RDS datasource connection, the system displays the error message Communication link failure.
                                                                                                                                
+
                                                                                                                                Solution
                                                                                                                                Example: When you create an RDS datasource connection, the system displays the error message Communication link failure.
                                                                                                                                
 
                                                                                                                                1. Delete the original datasource connection and create a new one. When you create a connection, ensure that the selected Security Group, VPC, Subnet, and Destination Address are the same as those in RDS.
                                                                                                                                   
                                                                                                                                  Select a correct Service Type. In this example, select RDS.
                                                                                                                                  
 
                                                                                                                                  
 
                                                                                                                                  
diff --git a/docs/dli/umn/dli_03_0091.html b/docs/dli/umn/dli_03_0091.html
index 436a87a9e..d1b894d05 100644
--- a/docs/dli/umn/dli_03_0091.html
+++ b/docs/dli/umn/dli_03_0091.html
@@ -3,7 +3,7 @@
 
                                                                                                                                  How Do I View DLI SQL Logs?
                                                                                                                                  
 
                                                                                                                                  Scenario
                                                                                                                                  You can view SQL job logs for routine O&M.
                                                                                                                                  
 
                                                                                                                                  
-
                                                                                                                                  Procedure
                                                                                                                                  1. Obtain the ID of the DLI job executed on the DataArts Studio console.
                                                                                                                                    Figure 1 Job ID
                                                                                                                                    
+
                                                                                                                                    Procedure
                                                                                                                                    1. Obtain the ID of the DLI job executed on the DataArts Studio console.
                                                                                                                                      Figure 1 Job ID
                                                                                                                                      
 
                                                                                                                                    2. On the DLI console, choose Job Management > SQL Jobs.
                                                                                                                                    3. On the SQL Jobs page, enter the job ID.
                                                                                                                                    4. In the Operation column of the target job, choose More > View Log and download the logs to your PC.
                                                                                                                                    5. Search for job ID in the downloaded logs to view the execution logs.
                                                                                                                                    
 
                                                                                                                                    
 
                                                                                                                                  
@@ -13,3 +13,10 @@
 
                                                                                                                                  
 
                                                                                                                                
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_03_0092.html b/docs/dli/umn/dli_03_0092.html
index ffc23e2b9..f0b197f16 100644
--- a/docs/dli/umn/dli_03_0092.html
+++ b/docs/dli/umn/dli_03_0092.html
@@ -1,7 +1,8 @@
 
 
 
                                                                                                                                How Do I Specify an OBS Path When Creating an OBS Table?
                                                                                                                                
-
                                                                                                                                Scenario
                                                                                                                                When creating an OBS table, you must specify a table path in the database. The path format is as follows: obs://xxx/database name/table name.
                                                                                                                                
+
                                                                                                                                Scenario
                                                                                                                                When creating an OBS table, you must specify a table path in the database.
                                                                                                                                
+
                                                                                                                                The path format is as follows: obs://xxx/database name/table name.
                                                                                                                                
 
                                                                                                                                
 
                                                                                                                                Correct Example
                                                                                                                                CREATE TABLE `di_seller_task_activity_30d` (`user_id` STRING COMMENT' user ID...) SORTED as parquet
 LOCATION 'obs://akc-bigdata/akdc.db/di_seller_task_activity_30d'
                                                                                                                                
diff --git a/docs/dli/umn/dli_03_0093.html b/docs/dli/umn/dli_03_0093.html
index 149faa7a8..c72b9f13b 100644
--- a/docs/dli/umn/dli_03_0093.html
+++ b/docs/dli/umn/dli_03_0093.html
@@ -3,7 +3,7 @@
 
                                                                                                                                How Do I Do When Data Skew Occurs During the Execution of a SQL Job?
                                                                                                                                
 
                                                                                                                                What Is Data Skew?
                                                                                                                                Data skew is a common issue during the execution of SQL jobs. When data is unevenly distributed, some compute nodes process significantly more data than others, which can impact the efficiency of the entire computation process.
                                                                                                                                
 
                                                                                                                                For example, if you notice that a SQL query is taking a long time to execute, you can check its status in SparkUI. See Figure 1. If you see a stage that has been running for over 20 minutes with only one task remaining, it is likely due to data skew.
                                                                                                                                
-
                                                                                                                                Figure 1 Data skew example
                                                                                                                                
+
                                                                                                                                Figure 1 Data skew example
                                                                                                                                
 
                                                                                                                                
 
                                                                                                                                Common Data Skew Scenarios
                                                                                                                                • Group By aggregation skew
                                                                                                                                  During the execution of Group By aggregation, if some grouping keys have significantly more data than others, the larger groups will consume more compute resources and time during the aggregation process, resulting in slower processing speeds and data skew.
                                                                                                                                  
 
                                                                                                                                • JOIN operation skew
                                                                                                                                  During table JOIN operations, if the keys involved in the JOIN are unevenly distributed in one of the tables, a large amount of data will be concentrated in a few tasks while others have already completed, causing data skew.
                                                                                                                                  
@@ -51,3 +51,10 @@ spark.sql.adaptive.skewedPartitionMaxSplits:10
 
                                                                                                                                
 
                                                                                                                                
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_03_0102.html b/docs/dli/umn/dli_03_0102.html
index b5dffc202..227ffd6d5 100644
--- a/docs/dli/umn/dli_03_0102.html
+++ b/docs/dli/umn/dli_03_0102.html
@@ -7,10 +7,10 @@
 
                                                                                                                                
 
                                                                                                                                Viewing Real-Time Resource Usage of a Spark Job
                                                                                                                                Perform the following operations to view the number of running CUs occupied by a Spark job in real time:
                                                                                                                                
 
                                                                                                                                
-
                                                                                                                                1. Log in to the DLI console. In the navigation pane, choose Job Management > Spark Jobs. In the job list, locate the target job and click SparkUI in the Operation column.
                                                                                                                                2. On the Spark UI page, view the real-time running resources of the Spark job.
                                                                                                                                  Figure 1 SparkUI
                                                                                                                                  
+
                                                                                                                                  1. Log in to the DLI console. In the navigation pane, choose Job Management > Spark Jobs. In the job list, locate the target job and click SparkUI in the Operation column.
                                                                                                                                  2. On the Spark UI page, view the real-time running resources of the Spark job.
                                                                                                                                    Figure 1 SparkUI
                                                                                                                                    
 
                                                                                                                                  3. On the Spark UI page, view the original configuration of the Spark job (available only to new clusters).
                                                                                                                                    On the Spark UI page, click Environment to view Driver and Executor information.
                                                                                                                                    
-
                                                                                                                                    Figure 2 Driver information
                                                                                                                                    
-
                                                                                                                                    Figure 3 Executor information
                                                                                                                                    
+
                                                                                                                                    Figure 2 Driver information
                                                                                                                                    
+
                                                                                                                                    Figure 3 Executor information
                                                                                                                                    
 
                                                                                                                                  
 
                                                                                                                                
 
                                                                                                                                
@@ -19,3 +19,10 @@
 
                                                                                                                                
 
                                                                                                                                
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_03_0106.html b/docs/dli/umn/dli_03_0106.html
index c51abd275..355bd5c27 100644
--- a/docs/dli/umn/dli_03_0106.html
+++ b/docs/dli/umn/dli_03_0106.html
@@ -16,7 +16,7 @@
 
                                                                                                                                In this scenario, the performance bottleneck is the source, and the performance is mainly affected by the data read speed. In this case, you can increase the number of Kafka partitions and the number of concurrent sources to solve the problem.
                                                                                                                                
 
                                                                                                                              10. The following figure shows that the back pressure of an operator is high, and its subsequent concurrent operators do not have back pressure.
                                                                                                                                
 
                                                                                                                                In this scenario, the performance bottleneck is Vertex2 or Vertex3. To find out the specific bottleneck operator, enable inPoolUsage monitoring on the Flink UI page. If the inPoolUsage for operator concurrency is 100% for a long time, the corresponding operator is likely to be the performance bottleneck. In this case, you check the operator for further optimization.
                                                                                                                                
-
                                                                                                                                Figure 1 inPoolUsage monitoring
                                                                                                                                
+
                                                                                                                                Figure 1 inPoolUsage monitoring
                                                                                                                                
 
                                                                                                                                11. 
 
                                                                                                                                
 
                                                                                                                                Performance Tuning
                                                                                                                                • Rocksdb state tuning
                                                                                                                                  Top N sorting, window aggregate calculation, and stream-stream join involve a large number of status operations. You can optimize the performance of state operations to improve the overall performance. You can try any of the following optimization methods:
                                                                                                                                  
@@ -43,3 +43,10 @@
 
                                                                                                                                
 
                                                                                                                                
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_03_0115.html b/docs/dli/umn/dli_03_0115.html
index 52fe270ed..680c2f3d9 100644
--- a/docs/dli/umn/dli_03_0115.html
+++ b/docs/dli/umn/dli_03_0115.html
@@ -3,9 +3,7 @@
 
                                                                                                                                What Are the Differences Between MRS Spark and DLI Spark?
                                                                                                                                
 
                                                                                                                                Both DLI and MRS support Spark, but there are some differences in service mode, interface, application scenarios, and performance characteristics.
                                                                                                                                
 
                                                                                                                                • The Spark component of DLI is fully managed. You can only use it through its APIs.
                                                                                                                                  This mode reduces the O&M burden and allows you to focus more on data processing and analysis tasks.
                                                                                                                                  
-
                                                                                                                                  .
                                                                                                                                  
 
                                                                                                                                • The Spark component of MRS is built on the VM in an MRS cluster. You can adjust and optimize Spark according to your actual needs and make API calls to use it.
                                                                                                                                  This mode provides higher freedom and customization, and is suitable for users with experience in big data processing.
                                                                                                                                  
-
                                                                                                                                  
 
                                                                                                                                
 
                                                                                                                                
 
                                                                                                                                
diff --git a/docs/dli/umn/dli_03_0136.html b/docs/dli/umn/dli_03_0136.html
index 5562433af..562e93609 100644
--- a/docs/dli/umn/dli_03_0136.html
+++ b/docs/dli/umn/dli_03_0136.html
@@ -56,6 +56,9 @@
 
                                                                                                                                
 
                                                                                                                                
 
+
                                                                                                                                Related Operation: How Do I Restore a Job from a Checkpoint?
                                                                                                                                Since the Flink checkpoint and savepoint generation mechanisms and formats are consistent, you can restore the Flink job from the latest successful checkpoint in OBS. Specifically, in the Flink job list, locate the desired Flink job, click More in the Operation column, and select Import Savepoint to import the checkpoint.
                                                                                                                                
+
                                                                                                                                1. Log in to the DLI console. In the navigation pane on the left, choose Job Management > Flink Jobs.
                                                                                                                                2. Locate the row that contains the target Flink job and click Import Savepoint in the Operation column.
                                                                                                                                3. In the displayed dialog box, select the OBS bucket path storing the checkpoint. The checkpoint save path is Bucket name/jobs/checkpoint/Directory starting with the job ID. Click OK.
                                                                                                                                4. Restart the Flink job again. The job will be restored fom the checkpoint path.
                                                                                                                                
+
                                                                                                                                
 
 
                                                                                                                                
 
                                                                                                                                
diff --git a/docs/dli/umn/dli_03_0186.html b/docs/dli/umn/dli_03_0186.html
index 89b68e698..f214e0094 100644
--- a/docs/dli/umn/dli_03_0186.html
+++ b/docs/dli/umn/dli_03_0186.html
@@ -3,9 +3,9 @@
 
                                                                                                                                How Do I Configure Network Connectivity Between a DLI Queue and a Data Source?
                                                                                                                                
 
                                                                                                                                • Configuring the Connection Between a DLI Queue and a Data Source in a Private Network
                                                                                                                                  If your DLI job needs to connect to a data source, for example, MRS, RDS, CSS, Kafka, or GaussDB(DWS), you need to enable the network between DLI and the data source.
                                                                                                                                  
 
                                                                                                                                  An enhanced datasource connection uses VPC peering to directly connect the VPC networks of the desired data sources for point-to-point data exchanges.
                                                                                                                                  
-
                                                                                                                                  Figure 1 Configuration process
                                                                                                                                  
+
                                                                                                                                  Figure 1 Configuration process
                                                                                                                                  
 
                                                                                                                                • Configuring the Connection Between a DLI Queue and a Data Source in the Internet
                                                                                                                                  You can configure SNAT rules and add routes to the public network to enable communications between a queue and the Internet.
                                                                                                                                  
-
                                                                                                                                  Figure 2 Configuration process
                                                                                                                                  
+
                                                                                                                                  Figure 2 Configuration process
                                                                                                                                  
 
                                                                                                                                
 
                                                                                                                                
 
                                                                                                                                
@@ -14,3 +14,10 @@
 
                                                                                                                                
 
                                                                                                                                
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_03_0196.html b/docs/dli/umn/dli_03_0196.html
index 7424598f9..5efcd2583 100644
--- a/docs/dli/umn/dli_03_0196.html
+++ b/docs/dli/umn/dli_03_0196.html
@@ -15,13 +15,13 @@
 
                                                                                                                              11. If there are too many small files, rectify the fault by referring to How Do I Merge Small Files?.
                                                                                                                                12. 
 
                                                                                                                                
 
                                                                                                                                Cause 2: There is a broadcast table.
                                                                                                                                
-
                                                                                                                                1. Log in to the DLI console. In the navigation pane, choose Job Management > SQL Jobs.
                                                                                                                                2. On the SQL Jobs page, locate the row that contains the target job and click  to view the job details and obtain the job ID.
                                                                                                                                3. In the Operation column of the job, click Spark UI.
                                                                                                                                4. On the displayed page, choose SQL from the menu bar. Click the hyperlink in the Description column of the row that contains the job ID.
                                                                                                                                5. View the DAG of the job to check whether the BroadcastNestedLoopJoin node exists.
                                                                                                                                  Figure 1 DAG
                                                                                                                                  
+
                                                                                                                                  1. Log in to the DLI console. In the navigation pane, choose Job Management > SQL Jobs.
                                                                                                                                  2. On the SQL Jobs page, locate the row that contains the target job and click  to view the job details and obtain the job ID.
                                                                                                                                  3. In the Operation column of the job, click Spark UI.
                                                                                                                                  4. On the displayed page, choose SQL from the menu bar. Click the hyperlink in the Description column of the row that contains the job ID.
                                                                                                                                  5. View the DAG of the job to check whether the BroadcastNestedLoopJoin node exists.
                                                                                                                                    Figure 1 DAG
                                                                                                                                    
 
                                                                                                                                  6. If the BroadcastNestedLoopJoin node exists, refer to Why Does a SQL Job That Has Join Operations Stay in the Running State? to rectify the fault.
                                                                                                                                  
 
 
                                                                                                                                  Possible Cause 2: Data Skew
                                                                                                                                  Check whether the problem is caused by data skew.
                                                                                                                                  
-
                                                                                                                                  1. Log in to the DLI console. In the navigation pane, choose Job Management > SQL Jobs.
                                                                                                                                  2. On the SQL Jobs page, locate the row that contains the target job and click  to view the job details and obtain the job ID.
                                                                                                                                  3. In the Operation column of the job, click Spark UI.
                                                                                                                                  4. On the displayed page, choose SQL from the menu bar. Click the hyperlink in the Description column of the row that contains the job ID.
                                                                                                                                    
-
                                                                                                                                  5. View the running status of the current stage in the Active Stage table on the displayed page. Click the hyperlink in the Description column.
                                                                                                                                    
-
                                                                                                                                  6. View the Launch Time and Duration of each task.
                                                                                                                                  7. Click Duration to sort tasks. Check whether the overall job duration is prolonged because a task has taken a long time.
                                                                                                                                    According to Figure 2, when data skew occurs, the data volume of shuffle reads of a task is much greater than that of other tasks. 
                                                                                                                                    Figure 2 Data skew
                                                                                                                                    
+
                                                                                                                                    1. Log in to the DLI console. In the navigation pane, choose Job Management > SQL Jobs.
                                                                                                                                    2. On the SQL Jobs page, locate the row that contains the target job and click  to view the job details and obtain the job ID.
                                                                                                                                    3. In the Operation column of the job, click Spark UI.
                                                                                                                                    4. On the displayed page, choose SQL from the menu bar. Click the hyperlink in the Description column of the row that contains the job ID.
                                                                                                                                      
+
                                                                                                                                    5. View the running status of the current stage in the Active Stage table on the displayed page. Click the hyperlink in the Description column.
                                                                                                                                      
+
                                                                                                                                    6. View the Launch Time and Duration of each task.
                                                                                                                                    7. Click Duration to sort tasks. Check whether the overall job duration is prolonged because a task has taken a long time.
                                                                                                                                      According to Figure 2, when data skew occurs, the data volume of shuffle reads of a task is much greater than that of other tasks. 
                                                                                                                                      Figure 2 Data skew
                                                                                                                                      
 
                                                                                                                                      
 
                                                                                                                                    
 
                                                                                                                                    Cause locating and solution
                                                                                                                                    
@@ -38,3 +38,10 @@ SELECT count(1) as count,num from lefttbl  group by lefttbl.num ORDER BY count d
 
                                                                                                                                    
 
                                                                                                                                  
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_03_0211.html b/docs/dli/umn/dli_03_0211.html
index 49350e7b7..42643c967 100644
--- a/docs/dli/umn/dli_03_0211.html
+++ b/docs/dli/umn/dli_03_0211.html
@@ -32,6 +32,8 @@
 
                                                                                                                                  6. 
 
                                                                                                                                6. How Can I Resolve Data Inconsistencies When Importing Data from DLI to OBS?
                                                                                                                                  
 
                                                                                                                                  7. 
+
                                                                                                                                7. Why Is a Hudi Table Not Displayed on the DLI Console?
                                                                                                                                  
+
                                                                                                                                  8. 
 
 
 
                                                                                                                                  
diff --git a/docs/dli/umn/dli_03_0217.html b/docs/dli/umn/dli_03_0217.html
index dfe9f9c4a..f7b3a3e0c 100644
--- a/docs/dli/umn/dli_03_0217.html
+++ b/docs/dli/umn/dli_03_0217.html
@@ -21,6 +21,8 @@
 
 
                                                                                                                                8. How Do I Read Uploaded Files for a Spark Jar Job?
                                                                                                                                  
 
                                                                                                                                  9. 
+
                                                                                                                                9. Why Are View Attributes Empty in Spark 3.3.1 Client?
                                                                                                                                  
+
                                                                                                                                  10. 
 
                                                                                                                                10. Why Can't I Find the Specified Python Environment After Adding the Python Package?
                                                                                                                                  
 
                                                                                                                                  11. 
 
                                                                                                                                11. Why Is a Spark Jar Job Stuck in the Submitting State?
                                                                                                                                  
diff --git a/docs/dli/umn/dli_03_0218.html b/docs/dli/umn/dli_03_0218.html
index c4a6dfef8..505607b69 100644
--- a/docs/dli/umn/dli_03_0218.html
+++ b/docs/dli/umn/dli_03_0218.html
@@ -19,6 +19,10 @@
 
                                                                                                                                  12. 
 
                                                                                                                                12. Why Does Using DataSource Syntax to Create an OBS Table of Avro Type Fail When Accessing Metadata With Spark 2.3.x?
                                                                                                                                  
 
                                                                                                                                  13. 
+
                                                                                                                                13. How Do I Resolve the "Input argument to rand must be a constant" Error in Spark 3.3.1 SQL Statements?
                                                                                                                                  
+
                                                                                                                                  14. 
+
                                                                                                                                14. When Using Spark 3.3.1 Client to Create a View and Perform a Join Query, an Error Occurs Stating "Not allowed to create a permanent view" When Attempting to Write the Data
                                                                                                                                  
+
                                                                                                                                  15. 
 
 
 
                                                                                                                                  
diff --git a/docs/dli/umn/dli_03_0236.html b/docs/dli/umn/dli_03_0236.html
index 6736f41ab..30eea3106 100644
--- a/docs/dli/umn/dli_03_0236.html
+++ b/docs/dli/umn/dli_03_0236.html
@@ -2,9 +2,9 @@
 
 
                                                                                                                                  Why Is the Flink Job Abnormal Due to Heartbeat Timeout Between JobManager and TaskManager?
                                                                                                                                  
 
                                                                                                                                  Symptom
                                                                                                                                  JobManager and TaskManager heartbeats timed out. As a result, the Flink job is abnormal.
                                                                                                                                  
-
                                                                                                                                  Figure 1 Error information
                                                                                                                                  
+
                                                                                                                                  Figure 1 Error information
                                                                                                                                  
 
                                                                                                                                  
-
                                                                                                                                  Possible Causes
                                                                                                                                  1. Check whether the network is intermittently disconnected and whether the cluster load is high.
                                                                                                                                  2. If Full GC occurs frequently, check the code to determine whether memory leakage occurs.
                                                                                                                                    Figure 2 Full GC
                                                                                                                                    
+
                                                                                                                                    Possible Causes
                                                                                                                                    1. Check whether the network is intermittently disconnected and whether the cluster load is high.
                                                                                                                                    2. If Full GC occurs frequently, check the code to determine whether memory leakage occurs.
                                                                                                                                      Figure 2 Full GC
                                                                                                                                      
 
                                                                                                                                    
 
                                                                                                                                    
 
                                                                                                                                    Handling Procedure
                                                                                                                                    • If Full GC occurs frequently, check the code to determine whether memory leakage occurs.
                                                                                                                                    • Allocate more resources for a single TaskManager.
                                                                                                                                    
@@ -17,3 +17,10 @@
 
                                                                                                                                    
 
                                                                                                                                  
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_03_0253.html b/docs/dli/umn/dli_03_0253.html
index c6d18a504..d62309367 100644
--- a/docs/dli/umn/dli_03_0253.html
+++ b/docs/dli/umn/dli_03_0253.html
@@ -6,8 +6,8 @@
 Detail: Failing row contains (400070309, 9.00, 25, null, 2020-09-22, 2020-09-23 04:30:01.741).
 
                                                                                                                                  
 
                                                                                                                                  
-
                                                                                                                                  Cause Analysis
                                                                                                                                  1. The CIR field in the source table is of the DOUBLE type.
                                                                                                                                    Figure 1 Creation statement of the source table
                                                                                                                                    
-
                                                                                                                                  2. The field type in the target table is DECIMAL(9,6).
                                                                                                                                    Figure 2 Creation statement of the target table
                                                                                                                                    
+
                                                                                                                                    Cause Analysis
                                                                                                                                    1. The CIR field in the source table is of the DOUBLE type.
                                                                                                                                      Figure 1 Creation statement of the source table
                                                                                                                                      
+
                                                                                                                                    2. The field type in the target table is DECIMAL(9,6).
                                                                                                                                      Figure 2 Creation statement of the target table
                                                                                                                                      
 
                                                                                                                                    3. View the source table data. The CTR value that causes the problem is 1675, which exceed the precision (9 – 6 = 3 digits) of the DECIMAL(9,6) type. A null value was generated when the double value was converted to the decimal value, and the insert operation failed.
                                                                                                                                    
 
                                                                                                                                    
 
                                                                                                                                    Procedure
                                                                                                                                    Change the precision of the decimal data defined in the target table.
                                                                                                                                    
@@ -19,3 +19,10 @@ Detail: Failing row contains (400070309, 9.00, 25, null, 2020-09-22, 2020-09-23
 
                                                                                                                                    
 
                                                                                                                                  
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_03_0273.html b/docs/dli/umn/dli_03_0273.html
new file mode 100644
index 000000000..b28e0c68a
--- /dev/null
+++ b/docs/dli/umn/dli_03_0273.html
@@ -0,0 +1,16 @@
+
+
+
                                                                                                                                  When Using Spark 3.3.1 Client to Create a View and Perform a Join Query, an Error Occurs Stating "Not allowed to create a permanent view" When Attempting to Write the Data
                                                                                                                                  
+
                                                                                                                                  Symptom
                                                                                                                                  When using Spark 3.3.1 client to create a subquery view with aggregate functions, an error occurs when attempting to write the data, stating "Not allowed to create a permanent view without explicitly assigning an alias for expression count".
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Cause Analysis
                                                                                                                                  To address schema compatibility issues caused by inconsistent default aliases in different version views, Spark 3.2.0 added constraints on views, resulting in errors when creating views and performing JOIN queries.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Solution
                                                                                                                                  To maintain consistency with versions earlier than Spark 3.2.0, the issue can be resolved by setting the client parameter spark.sql.legacy.allowAutoGeneratedAliasForView to true.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Parent topic: Spark Job O&M
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
diff --git a/docs/dli/umn/dli_03_0275.html b/docs/dli/umn/dli_03_0275.html
index 2fcd97286..5cdcc7720 100644
--- a/docs/dli/umn/dli_03_0275.html
+++ b/docs/dli/umn/dli_03_0275.html
@@ -2,7 +2,7 @@
 
 
                                                                                                                                  Why Does Using DataSource Syntax to Create an OBS Table of Avro Type Fail When Accessing Metadata With Spark 2.3.x?
                                                                                                                                  
 
                                                                                                                                  Symptom
                                                                                                                                  I failed to use the DataSource syntax to create an OBS table in Avro format when selecting Spark to access metadata.
                                                                                                                                  
-
                                                                                                                                  Figure 1 Failed to create an OBS table in Avro format
                                                                                                                                  
+
                                                                                                                                  Figure 1 Failed to create an OBS table in Avro format
                                                                                                                                  
 
                                                                                                                                  
 
                                                                                                                                  Possible Causes
                                                                                                                                  Spark 2.3.x does not support creating OBS tables in Avro format.
                                                                                                                                  
 
                                                                                                                                  
@@ -15,3 +15,10 @@
 
                                                                                                                                  
 
                                                                                                                                  
 
+
+
\ No newline at end of file
diff --git a/docs/dli/umn/dli_03_0277.html b/docs/dli/umn/dli_03_0277.html
new file mode 100644
index 000000000..d8a8f5d09
--- /dev/null
+++ b/docs/dli/umn/dli_03_0277.html
@@ -0,0 +1,163 @@
+
+
+
                                                                                                                                  Why Is a Hudi Table Not Displayed on the DLI Console?
                                                                                                                                  
+
                                                                                                                                  Symptom
                                                                                                                                  The Hudi table created using Flink SQL statements is not displayed on the DLI console, making it impossible to manage or perform query operations on the table through the console.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Possible Causes
                                                                                                                                  By default, a Hive catalog is used for data management on the DLI console. However, the metadata of the Hudi table is not correctly synchronized to Hive catalog. The metadata management of Hudi tables is independent of Hive. Therefore, additional configurations are required to ensure that the metadata of Hudi tables can be identified and synchronized by the Hive catalog.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Solution
                                                                                                                                  Hudi table persistence refers to the process of synchronizing metadata and data information of Hudi tables and saving the information to the metadata storage of Hive so that Hive can identify and manage these tables.
                                                                                                                                  
+
                                                                                                                                  • SQL job
                                                                                                                                    If only SQL is used to perform operations on Hudi data, you do not need to configure additional persistence parameters as SQL jobs inherently provide read and write support for Hudi data.
                                                                                                                                    
+
                                                                                                                                  • Flink OpenSource SQL job
                                                                                                                                    To persist the metadata of the Hudi table to the Hive Catalog of DLI, you need to add certain specific configuration parameters when creating the Hudi table. These parameters are used to instruct Hudi to synchronize the metadata to the Hive Catalog.
                                                                                                                                    
+
                                                                                                                                    Table 1 describes the parameters.
                                                                                                                                    
+
+
                                                                                                                                    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                    Table 1 Persistence parameters configured when creating a Hudi result table
                                                                                                                                    Parameter
                                                                                                                                    
+
                                                                                                                                    Description
                                                                                                                                    
+
                                                                                                                                    hive_sync.enable
                                                                                                                                    
+
                                                                                                                                    Whether to enable synchronization of table information to Hive.
                                                                                                                                    
+
                                                                                                                                    Set this parameter to true when you need to synchronize the metadata of the Hudi table to the Hive metadata storage to allow access to the Hudi table through the Hive query tool or within the data management page of the DLI console.
                                                                                                                                    
+
                                                                                                                                    • true: Hudi will synchronize the table's metadata (for example, table structure, partition information) to Hive.
                                                                                                                                    • false: Table information will not be synchronized to Hive.
                                                                                                                                    
+
                                                                                                                                    Enabling table information synchronization to Hive will use catalog-related permissions. Agency permissions for accessing the catalog must also be configured.
                                                                                                                                    
+
                                                                                                                                    hive_sync.mode
                                                                                                                                    
+
                                                                                                                                    Method for synchronizing metadata from the Hudi table to Hive.
                                                                                                                                    
+
                                                                                                                                    Select an appropriate synchronization method as needed.
                                                                                                                                    
+
                                                                                                                                    • jdbc: Synchronizes metadata by connecting to Hive Server through JDBC.
                                                                                                                                    • hms: Directly interacts with the Hive Metastore through the Hive meta client to synchronize metadata.
                                                                                                                                    • hiveql: Synchronizes metadata by executing Hive QL statements.
                                                                                                                                    
+
                                                                                                                                    hive_sync.table
                                                                                                                                    
+
                                                                                                                                    Name of the table synchronized to Hive. The metadata of the Hudi table will be synchronized to this Hive table.
                                                                                                                                    
+
                                                                                                                                    hive_sync.db
                                                                                                                                    
+
                                                                                                                                    Name of the database synchronized to Hive. The metadata of the Hudi table will be synchronized to the table in the Hive database.
                                                                                                                                    
+
                                                                                                                                    hive_sync.support_timestamp
                                                                                                                                    
+
                                                                                                                                    Whether to support timestamps. This parameter is used to ensure that the timestamp field can be correctly processed when metadata of the Hudi table is synchronized to Hive.
                                                                                                                                    
+
                                                                                                                                    You are advised to set it to true.
                                                                                                                                    
+
                                                                                                                                    
+
                                                                                                                                    
+
                                                                                                                                  • Spark Jar job
                                                                                                                                    When performing operations on Hudi data in Spark Jar, you also need to set some parameters to implement persistence and synchronization to Hive.
                                                                                                                                    
+
                                                                                                                                    Table 2 describes the parameters.
                                                                                                                                    
+
+
                                                                                                                                    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                                                                                                                    Table 2 Parameters for synchronizing Spark Jar jobs to Hive tables
                                                                                                                                    Parameter
                                                                                                                                    
+
                                                                                                                                    Description
                                                                                                                                    
+
                                                                                                                                    Default Value
                                                                                                                                    
+
                                                                                                                                    hoodie.datasource.hive_sync.enable
                                                                                                                                    
+
                                                                                                                                    Whether to synchronize Hudi tables to Hive. When using the metadata service provided by DLI, configuring this parameter means synchronizing to the metadata of DLI.
                                                                                                                                    
+
                                                                                                                                    You are advised to set it to true to use the metadata service to manage Hudi tables.
                                                                                                                                    
+
                                                                                                                                    true
                                                                                                                                    
+
                                                                                                                                    hoodie.datasource.hive_sync.database
                                                                                                                                    
+
                                                                                                                                    Name of the database to be synchronized to Hive.
                                                                                                                                    
+
                                                                                                                                    default
                                                                                                                                    
+
                                                                                                                                    hoodie.datasource.hive_sync.table
                                                                                                                                    
+
                                                                                                                                    Name of the table to be synchronized to Hive. Set this parameter to the value of hoodie.datasource.write.table.name.
                                                                                                                                    
+
                                                                                                                                    unknown
                                                                                                                                    
+
                                                                                                                                    hoodie.datasource.hive_sync.partition_fields
                                                                                                                                    
+
                                                                                                                                    Hive partition columns.
                                                                                                                                    
+
                                                                                                                                    ""
                                                                                                                                    
+
                                                                                                                                    hoodie.datasource.hive_sync.partition_extractor_class
                                                                                                                                    
+
                                                                                                                                    Class used to extract Hudi partition column values and convert them into Hive partition columns.
                                                                                                                                    
+
                                                                                                                                    org.apache.hudi.hive.SlashEncodedDayPartitionValueExtractor
                                                                                                                                    
+
                                                                                                                                    hoodie.datasource.hive_sync.support_timestamp
                                                                                                                                    
+
                                                                                                                                    If the Hudi table contains a field of the timestamp type, set this parameter to true to synchronize the timestamp type to the Hive metadata.
                                                                                                                                    
+
                                                                                                                                    The default value is false, indicating that the timestamp type is converted to bigint during synchronization by default. In this case, an error may occur when you query a Hudi table that contains a field of the timestamp type using SQL statements.
                                                                                                                                    
+
                                                                                                                                    true
                                                                                                                                    
+
                                                                                                                                    hoodie.datasource.hive_sync.fast_sync
                                                                                                                                    
+
                                                                                                                                    Methods for synchronizing Hudi partitions to Hive.
                                                                                                                                    
+
                                                                                                                                    • If this parameter is set to true, add partition if not exist is used to synchronize Hive tables based on the partitions filtered out in the Hudi table.
                                                                                                                                    • If this parameter is set to false, check whether the partitions to be synchronized exist in the Hive table. If not, synchronize the partitions into the Hive table.
                                                                                                                                    
+
                                                                                                                                    true
                                                                                                                                    
+
                                                                                                                                    hoodie.datasource.hive_sync.mode
                                                                                                                                    
+
                                                                                                                                    The method for synchronizing Hudi tables to Hive tables. When using the metadata service provided by DLI, this must be set to hms:
                                                                                                                                    
+
                                                                                                                                    • hms: synchronizes metadata through the Hive metastore client.
                                                                                                                                    • jdbc: synchronizes metadata through the Hive JDBC mode. (Not supported by the DLI metadata service.)
                                                                                                                                    • hiveql: synchronizes metadata by running the hive ql command. (Not supported by the DLI metadata service.)
                                                                                                                                    
+
                                                                                                                                    hms
                                                                                                                                    
+
                                                                                                                                    hoodie.datasource.hive_sync.username
                                                                                                                                    
+
                                                                                                                                    Username specified when synchronizing Hive using JDBC.
                                                                                                                                    
+
                                                                                                                                    hive
                                                                                                                                    
+
                                                                                                                                    hoodie.datasource.hive_sync.password
                                                                                                                                    
+
                                                                                                                                    Password specified when synchronizing Hive using JDBC.
                                                                                                                                    
+
                                                                                                                                    hive
                                                                                                                                    
+
                                                                                                                                    hoodie.datasource.hive_sync.jdbcurl
                                                                                                                                    
+
                                                                                                                                    JDBC URL specified for connecting to Hive.
                                                                                                                                    
+
                                                                                                                                    ""
                                                                                                                                    
+
                                                                                                                                    hoodie.datasource.hive_sync.use_jdbc
                                                                                                                                    
+
                                                                                                                                    Whether to use Hive JDBC to synchronize Hudi table information to Hive. You are advised to set this parameter to false. When set to false, the JDBC connection-related configuration will be invalid.
                                                                                                                                    
+
                                                                                                                                    true
                                                                                                                                    
+
                                                                                                                                    
+
                                                                                                                                    
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Parent topic: DLI Databases and Tables
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
diff --git a/docs/dli/umn/dli_03_0278.html b/docs/dli/umn/dli_03_0278.html
new file mode 100644
index 000000000..e5ef0df69
--- /dev/null
+++ b/docs/dli/umn/dli_03_0278.html
@@ -0,0 +1,15 @@
+
+
+
                                                                                                                                  How Do I Resolve the "Input argument to rand must be a constant" Error in Spark 3.3.1 SQL Statements?
                                                                                                                                  
+
                                                                                                                                  Symptom
                                                                                                                                  When the rand function is used in SQL statements of Spark 3.3.1, the error message "Input argument to rand must be a constant" is displayed.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Solution
                                                                                                                                  In Spark 3.3.1, the rand function requires constant parameters.
                                                                                                                                  
+
                                                                                                                                  To fix this error, update the parameters in the rand function within the SQL statements to constant parameters and rerun the SQL statements.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Parent topic: Spark Job O&M
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
diff --git a/docs/dli/umn/dli_03_0279.html b/docs/dli/umn/dli_03_0279.html
new file mode 100644
index 000000000..75aba14e5
--- /dev/null
+++ b/docs/dli/umn/dli_03_0279.html
@@ -0,0 +1,17 @@
+
+
+
                                                                                                                                  Why Are View Attributes Empty in Spark 3.3.1 Client?
                                                                                                                                  
+
                                                                                                                                  Symptom
                                                                                                                                  When running a job with Spark 3.3.1, certain fields have empty default attribute values when queried in the view attribute on the client. In contrast, when using Spark 3.1.1, these fields have null default attribute values.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Root Cause Analysis
                                                                                                                                  Starting from Spark 3.3.0, the open-source community has upgraded the CreateViewStatement syntax and adjusted the syntax calling interface version to prevent null pointer exceptions when querying view attributes. However, this change caused the DESC TABLE command to display an empty string for the comment attribute if not configured.
                                                                                                                                  
+
                                                                                                                                  This issue affects all operations involving default view attribute configurations in the Spark 3.3.1 client.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Solution
                                                                                                                                  If using the REST interface to call view queries, adjust the service logic to handle empty string results when executing jobs with Spark 3.3.1.
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  Parent topic: Spark Job Development
                                                                                                                                  
+
                                                                                                                                  
+
                                                                                                                                  
+
diff --git a/docs/dli/umn/dli_07_0002.html b/docs/dli/umn/dli_07_0002.html
index 5b980c33b..e108c1257 100644
--- a/docs/dli/umn/dli_07_0002.html
+++ b/docs/dli/umn/dli_07_0002.html
@@ -1,19 +1,19 @@
 
 
-
                                                                                                                                  Application Scenarios
                                                                                                                                  
+
                                                                                                                                  Use Cases
                                                                                                                                  
 
                                                                                                                                  DLI is applicable to large-scale log analysis, federated analysis of heterogeneous data sources, and big data ETL processing.
                                                                                                                                  
 
                                                                                                                                  Large-scale Log Analysis
                                                                                                                                  • Gaming operations data analysis
                                                                                                                                    Different departments of a game company analyze daily new logs via the game data analysis platform to obtain required metrics and make decision based on the obtained metric data. For example, the operation department obtains required metric data, such as new players, active players, retention rate, churn rate, and payment rate, to learn the current game status and determine follow-up actions. The placement department obtains the channel sources of new players and active players to determine the platforms for placement in the next cycle.
                                                                                                                                    
 
                                                                                                                                  
 
                                                                                                                                  • Advantages
                                                                                                                                    • Efficient Spark programming model: DLI directly ingests data from DIS and performs preprocessing such as data cleaning. You only need to edit the processing logic, without paying attention to the multi-thread model.
                                                                                                                                    • Ease of use: You can use standard SQL statements to compile metric analysis logic without paying attention to the complex distributed computing platform.
                                                                                                                                    
 
                                                                                                                                  
 
                                                                                                                                  
-
                                                                                                                                  Federated Analysis of Heterogeneous Data Sources
                                                                                                                                  • Digital service transformation for car companies
                                                                                                                                    In the face of new competition pressures and changes in travel services, car companies build the IoV cloud platform and IVI OS to streamline Internet applications and vehicle use scenarios, completing digital service transformation for car companies. This delivers better travel experience for vehicle owners, increases the competitiveness of car companies, and promotes sales growth. For example, DLI can be used to collect and analyze daily vehicle metric data (such as batteries, engines, tire pressure, and airbags), and give maintenance suggestions to vehicle owners in time.
                                                                                                                                    
+
                                                                                                                                    Federated Analysis of Heterogeneous Data Sources
                                                                                                                                    • Digital service transformation of automotive enterprises
                                                                                                                                      Facing new competition pressures in the market and continuous transformation of travel services, automotive enterprises build the IoV cloud platform and vehicle OS to streamline Internet applications and vehicle use cases and complete digital transformation for automotive enterprises. In this way, they can provide better smart travel experience for vehicle owners, improve their competitiveness, and promote sales growth. For example, DLI can be used to collect and analyze daily vehicle indicator data (such as battery, engine, tire pressure, and airbag health status) and provide maintenance suggestions to vehicle owners in a timely manner.
                                                                                                                                      
 
                                                                                                                                    • Advantages
                                                                                                                                      • No need for migration in multi-source data analysis: RDS stores the basic information about vehicles and vehicle owners, table store  saves real-time vehicle location and health status, and GaussDB(DWS) stores periodic metric statistics. DLI allows federated analysis on data from multiple sources without data migration.
                                                                                                                                      • Tiered data storage: Car companies need to retain all historical data to support auditing and other services that require infrequent data access. Warm and cold data is stored in OBS and frequently accessed data is stored in GaussDB(DWS), reducing the overall storage cost.
                                                                                                                                      • Rapid and agile alarm triggering: There are no special requirements for the CPU, memory, hard disk space, and bandwidth.
                                                                                                                                      
 
                                                                                                                                    
 
                                                                                                                                    
 
                                                                                                                                    Big Data ETL Processing
                                                                                                                                    • Carrier big data analysis
                                                                                                                                      Carriers typically require petabytes, or even exabytes of data storage, for both structured (base station details) and unstructured (messages and communications) data. They need to be able to access the data with extremely low data latency. It is a major challenge to extract value from this data efficiently. DLI provides multi-mode engines such as batch processing and stream processing to break down data silos and perform unified data analysis.
                                                                                                                                      
 
                                                                                                                                    
-
                                                                                                                                    • Advantages
                                                                                                                                      • Big data ETL: You can enjoy TB to EB-level data governance capabilities to quickly perform ETL processing on massive carrier data. Distributed datasets are provided for batch processing.
                                                                                                                                      • High Throughput, Low Latency: DLI uses the Dataflow model of Apache Flink, a real-time computing framework. High-performance computing resources are provided to consume data from your created Kafka, DMS Kafka, and MRS Kafka clusters. A single CU processes 1,000 to 20,000 messages per second.
                                                                                                                                      
+
                                                                                                                                      • Advantages
                                                                                                                                        • Big data ETL: You can enjoy TB to EB-level data governance capabilities to quickly perform ETL processing on massive carrier data. Distributed datasets are provided for batch processing.
                                                                                                                                        • High throughput and low latency: The Apache Flink dataflow model is used with high-performance compute resources to consume data from user-created Kafka, MRS-Kafka, and DMS-Kafka. A single CU can process 1,000 to 20,000 messages per second.
                                                                                                                                        
 
                                                                                                                                      
 
                                                                                                                                    
 
                                                                                                                                  
diff --git a/docs/dli/umn/dli_07_0003.html b/docs/dli/umn/dli_07_0003.html
index 3e9975eb0..ab00e3320 100644
--- a/docs/dli/umn/dli_07_0003.html
+++ b/docs/dli/umn/dli_07_0003.html
@@ -1,38 +1,38 @@
 
 
 
                                                                                                                                  Basic Concepts
                                                                                                                                  
-
                                                                                                                                  Use Elastic Resource Pool
                                                                                                                                  Dedicated computing resources. They are isolated by resource pools and can only be shared by queues in the same elastic resource pool. You can set scaling policies of different priorities for these queues to adjust compute resources according to queue workload in different periods of a day.
                                                                                                                                  
+
                                                                                                                                  Elastic Resource Pool
                                                                                                                                  An elastic resource pool consists of dedicated compute resources where the resources in different pools are completely isolated from each other. Within a single elastic resource pool, multiple queues can share the resources available in that pool. Additionally, you can configure policies based on the resource load of these queues to enable time-based elastic scaling to meet diverse business needs.
                                                                                                                                  
 
                                                                                                                                  
 
                                                                                                                                  DLI Storage Resource
                                                                                                                                  DLI storage resources are the internal storage capacities of the DLI service. They are utilized for storing databases and DLI tables, playing a crucial role in data import into DLI. These resources also indicate the volume of data that users have stored within DLI.
                                                                                                                                  
 
                                                                                                                                  
-
                                                                                                                                  Actual CUs, Used CUs, CU Range, and Specifications of an Elastic Resource Pool