@clickzetta/cz-cli-darwin-x64 0.5.16 → 0.5.17
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bin/cz-cli +0 -0
- package/bin/skills/lakehouse-doc-en/SKILL.md +6 -11
- package/bin/skills/lakehouse-doc-en/references/AIGateway.md +58 -13
- package/bin/skills/lakehouse-doc-en/references/Computation.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/DataSource_Amazon_DocumentDB.md +3 -1
- package/bin/skills/lakehouse-doc-en/references/Foreach.md +14 -14
- package/bin/skills/lakehouse-doc-en/references/JDBC-Driver.md +0 -1
- package/bin/skills/lakehouse-doc-en/references/LakehouseAI-overview.md +21 -8
- package/bin/skills/lakehouse-doc-en/references/LakehouseDataGPT-tour.md +4 -9
- package/bin/skills/lakehouse-doc-en/references/LakehouseStudio-tour.md +14 -19
- package/bin/skills/lakehouse-doc-en/references/Lakehouse_Zilliz_MakeDataReadyforBIandAI.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/Logstash.md +3 -3
- package/bin/skills/lakehouse-doc-en/references/Migrate_Spark_DataEngineeringBestPractices_Project_to_Lakehouse.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/Notebook.md +17 -17
- package/bin/skills/lakehouse-doc-en/references/RemoteFunction-as-udf.md +14 -14
- package/bin/skills/lakehouse-doc-en/references/SQL_External_Catalog_Guide.md +1 -9
- package/bin/skills/lakehouse-doc-en/references/SUMMARY.md +59 -29
- package/bin/skills/lakehouse-doc-en/references/WINDOWFUNCTION.md +99 -57
- package/bin/skills/lakehouse-doc-en/references/Zettapark_Data_Engineering_Demo.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/access-control-configuration.md +1 -8
- package/bin/skills/lakehouse-doc-en/references/aigw-2026-2-5-1.0.md +16 -0
- package/bin/skills/lakehouse-doc-en/references/aigw-2026-3-29-1.0.2.md +14 -0
- package/bin/skills/lakehouse-doc-en/references/aigw-2026-3-8-1.0.1.md +16 -0
- package/bin/skills/lakehouse-doc-en/references/aigw-2026-4-28-1.1.md +29 -0
- package/bin/skills/lakehouse-doc-en/references/aigw-2026-5-12-1.1.1.md +18 -0
- package/bin/skills/lakehouse-doc-en/references/aigw-2026-5-15-1.2.md +9 -0
- package/bin/skills/lakehouse-doc-en/references/aigw-2026-5-21-1.3.md +9 -0
- package/bin/skills/lakehouse-doc-en/references/aigw-2026-5-28-1.4.md +10 -0
- package/bin/skills/lakehouse-doc-en/references/aigw-2026-6-3-1.5.md +9 -0
- package/bin/skills/lakehouse-doc-en/references/alicloud-arn-externalid.md +0 -5
- package/bin/skills/lakehouse-doc-en/references/answer-accuracy-improve.md +120 -103
- package/bin/skills/lakehouse-doc-en/references/application-list.md +1 -3
- package/bin/skills/lakehouse-doc-en/references/approval-list.md +16 -17
- package/bin/skills/lakehouse-doc-en/references/batch-load-parquet-file-into-lakehouse.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/batch_sync.md +9 -9
- package/bin/skills/lakehouse-doc-en/references/batch_sync_Sop.md +2 -2
- package/bin/skills/lakehouse-doc-en/references/batchloadparquetfileintoLakehouse.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/bulkloadv1-python-sdk.md +3 -3
- package/bin/skills/lakehouse-doc-en/references/chart-auto-refresh-guide.md +12 -6
- package/bin/skills/lakehouse-doc-en/references/clickzetta-sample-data.md +3 -3
- package/bin/skills/lakehouse-doc-en/references/code_approval.md +1 -5
- package/bin/skills/lakehouse-doc-en/references/composite_task.md +31 -42
- package/bin/skills/lakehouse-doc-en/references/comprehensive_guide_to_ingesting_environment_and_data_generate.md +6 -9
- package/bin/skills/lakehouse-doc-en/references/comprehensive_guide_to_ingesting_javasdk_bulkload_realtime.md +4 -10
- package/bin/skills/lakehouse-doc-en/references/comprehensive_guide_to_ingesting_kafka_realtime_sync.md +1 -10
- package/bin/skills/lakehouse-doc-en/references/comprehensive_guide_to_ingesting_local_file_into_table_by_studio.md +0 -6
- package/bin/skills/lakehouse-doc-en/references/comprehensive_guide_to_ingesting_studio_batchload_public_network.md +0 -5
- package/bin/skills/lakehouse-doc-en/references/comprehensive_guide_to_ingesting_studio_python_node.md +2 -7
- package/bin/skills/lakehouse-doc-en/references/comprehensive_guide_to_ingesting_studio_realtime_cdc_public_network.md +13 -18
- package/bin/skills/lakehouse-doc-en/references/comprehensive_guide_to_ingesting_studio_sql_insert.md +0 -1
- package/bin/skills/lakehouse-doc-en/references/concepts.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/config-datasource.md +5 -7
- package/bin/skills/lakehouse-doc-en/references/connect-with-cli.md +116 -72
- package/bin/skills/lakehouse-doc-en/references/connect-with-cz-cli.md +151 -0
- package/bin/skills/lakehouse-doc-en/references/continue-job.md +9 -17
- package/bin/skills/lakehouse-doc-en/references/create-api-connection.md +315 -286
- package/bin/skills/lakehouse-doc-en/references/create-catalog-connection.md +1 -0
- package/bin/skills/lakehouse-doc-en/references/create-dynamic-table.md +4 -4
- package/bin/skills/lakehouse-doc-en/references/create-external-catalog.md +85 -22
- package/bin/skills/lakehouse-doc-en/references/create-table-ddl.md +45 -0
- package/bin/skills/lakehouse-doc-en/references/creating_alicloud_privatelinkendpoint.md +4 -6
- package/bin/skills/lakehouse-doc-en/references/creating_alicloud_privatelinkservice.md +4 -7
- package/bin/skills/lakehouse-doc-en/references/creating_tencentcloud_privatelinkendpoint.md +2 -7
- package/bin/skills/lakehouse-doc-en/references/creating_tencentcloud_privatelinkservice.md +1 -5
- package/bin/skills/lakehouse-doc-en/references/cz-cli-agent.md +15 -10
- package/bin/skills/lakehouse-doc-en/references/cz-cli-datasource.md +0 -8
- package/bin/skills/lakehouse-doc-en/references/cz-cli-sql.md +2 -45
- package/bin/skills/lakehouse-doc-en/references/cz-cli.md +53 -42
- package/bin/skills/lakehouse-doc-en/references/dashboard-version-management-guide.md +12 -4
- package/bin/skills/lakehouse-doc-en/references/data-integration-intro.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/data-integration.md +29 -27
- package/bin/skills/lakehouse-doc-en/references/data-load-summary.md +3 -3
- package/bin/skills/lakehouse-doc-en/references/data-quality.md +25 -25
- package/bin/skills/lakehouse-doc-en/references/data-sharing.md +31 -54
- package/bin/skills/lakehouse-doc-en/references/data-sources.md +45 -45
- package/bin/skills/lakehouse-doc-en/references/data_catalog.md +23 -25
- package/bin/skills/lakehouse-doc-en/references/data_privacy.md +5 -2
- package/bin/skills/lakehouse-doc-en/references/data_sharing_between_accounts_guide.md +0 -4
- package/bin/skills/lakehouse-doc-en/references/data_visualization.md +4 -15
- package/bin/skills/lakehouse-doc-en/references/dataagent.md +39 -7
- package/bin/skills/lakehouse-doc-en/references/databricks-delta-to-lakehouse-migration.md +168 -0
- package/bin/skills/lakehouse-doc-en/references/databricks-dlt-to-lakehouse-migration.md +331 -0
- package/bin/skills/lakehouse-doc-en/references/databricks-external-catalog-practice.md +367 -0
- package/bin/skills/lakehouse-doc-en/references/databricks-jobs-to-studio-migration.md +199 -0
- package/bin/skills/lakehouse-doc-en/references/databricks-notebook-to-studio-migration.md +350 -0
- package/bin/skills/lakehouse-doc-en/references/databricks-uc-governance-to-lakehouse-migration.md +327 -0
- package/bin/skills/lakehouse-doc-en/references/datagpt-model-config.md +34 -0
- package/bin/skills/lakehouse-doc-en/references/datagpt_data_source.md +50 -37
- package/bin/skills/lakehouse-doc-en/references/datagpt_introduction.md +55 -79
- package/bin/skills/lakehouse-doc-en/references/datagpt_quickstart.md +50 -64
- package/bin/skills/lakehouse-doc-en/references/datalake-acceleration.md +75 -2
- package/bin/skills/lakehouse-doc-en/references/dbt-databricks-to-clickzetta-migration.md +242 -0
- package/bin/skills/lakehouse-doc-en/references/dynamic-mask.md +30 -30
- package/bin/skills/lakehouse-doc-en/references/dynamic-table-bestpractice.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/dynamic-table-introduce.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/dynamic_table_summary.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/eco_integration/streamlit.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/eco_integration/superset.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/ecosystem-all.md +1 -3
- package/bin/skills/lakehouse-doc-en/references/ecosystem.md +145 -0
- package/bin/skills/lakehouse-doc-en/references/external-catalog-summary.md +33 -38
- package/bin/skills/lakehouse-doc-en/references/external-function-combo-practice.md +466 -0
- package/bin/skills/lakehouse-doc-en/references/f6fc6447ee.md +7 -9
- package/bin/skills/lakehouse-doc-en/references/federation-query.md +56 -6
- package/bin/skills/lakehouse-doc-en/references/finebi-mysql.md +2 -0
- package/bin/skills/lakehouse-doc-en/references/get-started-with-sample-data.md +10 -11
- package/bin/skills/lakehouse-doc-en/references/gitfolder.md +2 -3
- package/bin/skills/lakehouse-doc-en/references/grant-privileges.md +2 -0
- package/bin/skills/lakehouse-doc-en/references/iceberg-rest-catalog-databricks.md +166 -0
- package/bin/skills/lakehouse-doc-en/references/ide.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/if_else_task.md +59 -57
- package/bin/skills/lakehouse-doc-en/references/input_output.md +10 -7
- package/bin/skills/lakehouse-doc-en/references/jobprofile-bestpractices.md +60 -64
- package/bin/skills/lakehouse-doc-en/references/kafka-connection.md +0 -1
- package/bin/skills/lakehouse-doc-en/references/key-concepts.md +146 -117
- package/bin/skills/lakehouse-doc-en/references/lakehouse-ai-gateway-cz-cli.md +317 -0
- package/bin/skills/lakehouse-doc-en/references/lakehouse-ai-sql-analysis.md +345 -0
- package/bin/skills/lakehouse-doc-en/references/lakehouse-dqc-guide.md +300 -0
- package/bin/skills/lakehouse-doc-en/references/lakehouse-medallion-sql-dt-guide.md +543 -0
- package/bin/skills/lakehouse-doc-en/references/lakehouse-multi-cloud-acceleration.md +274 -0
- package/bin/skills/lakehouse-doc-en/references/lakehouse-multimodal-ai-pipeline.md +198 -0
- package/bin/skills/lakehouse-doc-en/references/lakehouse-quick-experience_guide.md +49 -52
- package/bin/skills/lakehouse-doc-en/references/lakehouse-volume-pipe-acceleration-guide.md +380 -0
- package/bin/skills/lakehouse-doc-en/references/langchain-plug-installation.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/management.md +4 -9
- package/bin/skills/lakehouse-doc-en/references/medallion-lakehouse-from-scratch.md +2 -1
- package/bin/skills/lakehouse-doc-en/references/metrics_answer_build.md +58 -21
- package/bin/skills/lakehouse-doc-en/references/migrate-spark-data-engineering-best-practices-to-lakehouse.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/mindsdb.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/monitoring_and_alerting.md +65 -60
- package/bin/skills/lakehouse-doc-en/references/monitoring_item_specification.md +33 -33
- package/bin/skills/lakehouse-doc-en/references/multitable_batch_sync.md +16 -16
- package/bin/skills/lakehouse-doc-en/references/multitable_realtime_sync.md +65 -72
- package/bin/skills/lakehouse-doc-en/references/multitable_realtime_sync_sop.md +54 -52
- package/bin/skills/lakehouse-doc-en/references/navicat-mysql.md +2 -0
- package/bin/skills/lakehouse-doc-en/references/om-dynamic-table.md +71 -66
- package/bin/skills/lakehouse-doc-en/references/om-vcluster.md +2 -0
- package/bin/skills/lakehouse-doc-en/references/open-api-create-session.md +79 -0
- package/bin/skills/lakehouse-doc-en/references/open-api-generate-auth-token.md +63 -0
- package/bin/skills/lakehouse-doc-en/references/open-api-overview.md +96 -0
- package/bin/skills/lakehouse-doc-en/references/open-api-quick-start.md +286 -0
- package/bin/skills/lakehouse-doc-en/references/open-api-response-guide.md +264 -0
- package/bin/skills/lakehouse-doc-en/references/open-api-safe-question-poll.md +201 -0
- package/bin/skills/lakehouse-doc-en/references/open-api-text2insight-query.md +99 -0
- package/bin/skills/lakehouse-doc-en/references/open-api-text2insight-stop.md +74 -0
- package/bin/skills/lakehouse-doc-en/references/overview.md +6 -7
- package/bin/skills/lakehouse-doc-en/references/permission-application.md +5 -5
- package/bin/skills/lakehouse-doc-en/references/pipe-introduction.md +1 -0
- package/bin/skills/lakehouse-doc-en/references/pipe-kafka-table-stream.md +72 -70
- package/bin/skills/lakehouse-doc-en/references/pipe-kafka.md +105 -110
- package/bin/skills/lakehouse-doc-en/references/pipe-overview.md +40 -40
- package/bin/skills/lakehouse-doc-en/references/pipe-storage-object.md +43 -48
- package/bin/skills/lakehouse-doc-en/references/pipe-summary.md +14 -4
- package/bin/skills/lakehouse-doc-en/references/pipe-syntax.md +58 -151
- package/bin/skills/lakehouse-doc-en/references/practice_python_task.md +4 -4
- package/bin/skills/lakehouse-doc-en/references/pricing-ai-gateway.md +181 -0
- package/bin/skills/lakehouse-doc-en/references/pricing-lakehouse.md +316 -0
- package/bin/skills/lakehouse-doc-en/references/pricing.md +44 -288
- package/bin/skills/lakehouse-doc-en/references/private-link-general.md +0 -2
- package/bin/skills/lakehouse-doc-en/references/pyspark-to-zettapark-migration-f1.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/python-igs.md +7 -3
- package/bin/skills/lakehouse-doc-en/references/python-sample-put-github-rt-events.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/python-task.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/python_reference/connector.md +3 -3
- package/bin/skills/lakehouse-doc-en/references/python_reference/connector_advanced.md +2 -2
- package/bin/skills/lakehouse-doc-en/references/python_reference/connector_examples.md +2 -2
- package/bin/skills/lakehouse-doc-en/references/python_sdk_guide.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/python_shell_datasource.md +11 -9
- package/bin/skills/lakehouse-doc-en/references/quick_start_batch_sync_data.md +9 -18
- package/bin/skills/lakehouse-doc-en/references/quick_start_bi_analysis.md +8 -25
- package/bin/skills/lakehouse-doc-en/references/quick_start_create_workspace.md +4 -6
- package/bin/skills/lakehouse-doc-en/references/quick_start_data_quality.md +8 -8
- package/bin/skills/lakehouse-doc-en/references/quick_start_etl.md +16 -20
- package/bin/skills/lakehouse-doc-en/references/quick_start_monitoring_and_alerting.md +10 -18
- package/bin/skills/lakehouse-doc-en/references/quick_start_sql_query.md +7 -10
- package/bin/skills/lakehouse-doc-en/references/quick_start_upload_data.md +5 -7
- package/bin/skills/lakehouse-doc-en/references/quick_start_user_management.md +8 -8
- package/bin/skills/lakehouse-doc-en/references/quick_start_workspace.md +0 -5
- package/bin/skills/lakehouse-doc-en/references/quick_start_workspace_user.md +8 -8
- package/bin/skills/lakehouse-doc-en/references/quickstart.md +69 -56
- package/bin/skills/lakehouse-doc-en/references/quickstart_datashare_between_companies.md +0 -5
- package/bin/skills/lakehouse-doc-en/references/quickstart_envirment_for_team.md +0 -24
- package/bin/skills/lakehouse-doc-en/references/realtime-pipeline-selection-guide.md +1 -2
- package/bin/skills/lakehouse-doc-en/references/realtime-sales-dashboard-with-dynamic-table.md +3 -3
- package/bin/skills/lakehouse-doc-en/references/realtime_sync.md +0 -1
- package/bin/skills/lakehouse-doc-en/references/release-note-2026-05-19.md +5 -3
- package/bin/skills/lakehouse-doc-en/references/revoke-privileges.md +3 -1
- package/bin/skills/lakehouse-doc-en/references/roles.md +2 -3
- package/bin/skills/lakehouse-doc-en/references/row-filter.md +165 -0
- package/bin/skills/lakehouse-doc-en/references/row_level_permission.md +30 -19
- package/bin/skills/lakehouse-doc-en/references/scheduled_task.md +28 -21
- package/bin/skills/lakehouse-doc-en/references/security_overview.md +99 -21
- package/bin/skills/lakehouse-doc-en/references/set-command.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/setup.md +13 -15
- package/bin/skills/lakehouse-doc-en/references/show-grants.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/snowflake-dynamic-tables-to-lakehouse.md +2 -2
- package/bin/skills/lakehouse-doc-en/references/spark-connector-summary.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/sql_functions/context_functions/current_vcluster.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/sso-configuration.md +2 -2
- package/bin/skills/lakehouse-doc-en/references/streaming_pipeline_with_dynamic_table.md +0 -1
- package/bin/skills/lakehouse-doc-en/references/studio-incremental-sync-practice.md +27 -23
- package/bin/skills/lakehouse-doc-en/references/studio-shell-task.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/supported-cloud-platforms.md +32 -0
- package/bin/skills/lakehouse-doc-en/references/table_rendering.md +18 -12
- package/bin/skills/lakehouse-doc-en/references/task-develop.md +89 -91
- package/bin/skills/lakehouse-doc-en/references/task_development.md +19 -17
- package/bin/skills/lakehouse-doc-en/references/task_group.md +16 -14
- package/bin/skills/lakehouse-doc-en/references/task_instance.md +21 -21
- package/bin/skills/lakehouse-doc-en/references/task_param.md +38 -35
- package/bin/skills/lakehouse-doc-en/references/task_param_reference.md +81 -79
- package/bin/skills/lakehouse-doc-en/references/task_scheduling_dependency.md +20 -21
- package/bin/skills/lakehouse-doc-en/references/tencentcloud_arn_and_externalid.md +1 -5
- package/bin/skills/lakehouse-doc-en/references/trial-account-quotas-and-limits.md +1 -3
- package/bin/skills/lakehouse-doc-en/references/tutorial_connect_to_lakehouse.md +69 -0
- package/bin/skills/lakehouse-doc-en/references/tutorials.md +4 -1
- package/bin/skills/lakehouse-doc-en/references/unique-key.md +167 -0
- package/bin/skills/lakehouse-doc-en/references/usageandbillingview.md +138 -0
- package/bin/skills/lakehouse-doc-en/references/use-dbt-dev.md +3 -3
- package/bin/skills/lakehouse-doc-en/references/use-java-sdk-realtime-uploaddata.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/use-java-sdk-upload-data-local.md +3 -3
- package/bin/skills/lakehouse-doc-en/references/use-models.md +128 -0
- package/bin/skills/lakehouse-doc-en/references/use-mysql-client.md +81 -81
- package/bin/skills/lakehouse-doc-en/references/use-python-sdk-upload-data.md +10 -12
- package/bin/skills/lakehouse-doc-en/references/user-identification.md +2 -3
- package/bin/skills/lakehouse-doc-en/references/user_permission_grand_guide.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/using-udf-in-dynamic-table.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/vc_cache.md +18 -22
- package/bin/skills/lakehouse-doc-en/references/vcluster_size_description.md +33 -31
- package/bin/skills/lakehouse-doc-en/references/virtual-cluster.md +43 -45
- package/bin/skills/lakehouse-doc-en/references/web-job-history.md +94 -108
- package/bin/skills/lakehouse-doc-en/references/web_search.md +16 -7
- package/bin/skills/lakehouse-doc-en/references/zettapark-data-engineering-demo.md +1 -1
- package/bin/skills/lakehouse-doc-en/references/zettapark-dataframe-guide.md +144 -70
- package/bin/skills/lakehouse-doc-en/references/zettapark-dynamic-table-guide.md +2 -2
- package/bin/skills/lakehouse-doc-en/references/zettapark-etl-guide.md +73 -33
- package/bin/skills/lakehouse-doc-en/references/zettapark-feature-engineering.md +2 -2
- package/bin/skills/lakehouse-doc-en/references/zettapark-functions-guide.md +75 -46
- package/bin/skills/lakehouse-doc-en/references/zettapark-quick-start.md +2 -2
- package/bin/skills/lakehouse-doc-en/references/zettapark-stream-guide.md +4 -4
- package/bin/skills/lakehouse-doc-en/references/zettapark-volume-guide.md +93 -29
- package/package.json +1 -1
- package/bin/skills/lakehouse-doc-en/references/CLAUDE.md +0 -606
- package/bin/skills/lakehouse-doc-en/references/modelprice.md +0 -155
package/bin/cz-cli
CHANGED
|
Binary file
|
|
@@ -1,16 +1,11 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: lakehouse-doc-en
|
|
3
|
-
description:
|
|
4
|
-
Singdata/Clickzetta Lakehouse official documentation knowledge base (English). Consult references/
|
|
5
|
-
when writing SQL or answering questions about query syntax, functions, data types, DDL/DML,
|
|
6
|
-
dynamic tables, permissions, vclusters, data lake, AI functions, external catalog federation queries,
|
|
7
|
-
and other Lakehouse topics.
|
|
8
|
-
Keywords: documentation, SQL syntax, functions, DDL, DML, data types, permissions, vcluster, reference
|
|
3
|
+
description: "Singdata Lakehouse official documentation knowledge base (English). Consult references/ when writing SQL or answering questions about query syntax, functions, data types, DDL/DML, dynamic tables, permissions, vclusters, data lake, AI functions, and other Lakehouse topics."
|
|
9
4
|
---
|
|
10
5
|
|
|
11
6
|
# lakehouse-doc-en
|
|
12
7
|
|
|
13
|
-
Singdata
|
|
8
|
+
Singdata Lakehouse official documentation (English). Locate docs by filename under `references/` based on the user's question.
|
|
14
9
|
|
|
15
10
|
## references/ layout
|
|
16
11
|
|
|
@@ -52,9 +47,9 @@ references/
|
|
|
52
47
|
|
|
53
48
|
## Document Index (llms.txt)
|
|
54
49
|
|
|
55
|
-
# Singdata
|
|
50
|
+
# Singdata Lakehouse Documentation (LLM Navigation)
|
|
56
51
|
|
|
57
|
-
> Singdata
|
|
52
|
+
> Singdata Lakehouse is a fully managed lakehouse architecture platform built from the ground up on cloud-native design principles. Through **storage-compute separation**, **Serverless elastic architecture**, **open storage formats**, and **AI-optimized tools**, it provides enterprises with a unified platform for data warehousing, data lakes, real-time processing, and BI reporting. [Free Trial](https://www.singdata.com)
|
|
58
53
|
|
|
59
54
|
|
|
60
55
|
## Quick Start
|
|
@@ -106,7 +101,7 @@ references/
|
|
|
106
101
|
|
|
107
102
|
## Practice Tutorials
|
|
108
103
|
|
|
109
|
-
- [Efficient Object and Data Organization Management](references/data_org.md):
|
|
104
|
+
- [Efficient Object and Data Organization Management](references/data_org.md):
|
|
110
105
|
- [Data Import and Export Practice](references/practice_data_import_and_export.md): An empty placeholder page with no substantive content.
|
|
111
106
|
- [Data Lake Acceleration](references/datalake-acceleration.md): Brief overview of in-place data lake acceleration, connecting directly to an existing Hive Metastore and object storage via External Schema to replace Spark/Hive ETL and Presto/Trino queries with Serverless compute.
|
|
112
107
|
- [Migration Guide](references/tutorial_migration.md): Migration guide hub mapping source systems (Databricks/PySpark, RDD, Spark SQL, Snowflake, Medallion) to recommended Lakehouse migration paths with links and path-selection advice.
|
|
@@ -114,7 +109,7 @@ references/
|
|
|
114
109
|
- [Building and Maintaining ELT Processes](references/ELT_practice.md): Placeholder page for ELT practice in Singdata Lakehouse; currently empty with no substantive content.
|
|
115
110
|
- [Optimize Computing Resources](references/optimizing-computing-resources.md): Placeholder page for optimizing computing resources in Singdata Lakehouse; currently empty with no substantive content.
|
|
116
111
|
- [Performance Experience](references/performence_test.md): Empty placeholder page intended for performance testing content; no substantive material is present beyond a content marker.
|
|
117
|
-
- [Modern Data Stack with Ecosystem Tools](references/modern-data-stack-with-ecosystem-tools.md):
|
|
112
|
+
- [Modern Data Stack with Ecosystem Tools](references/modern-data-stack-with-ecosystem-tools.md):
|
|
118
113
|
- [AI Application Development](references/ai_app_dev_practical.md): Brief landing page introducing practical guides for building AI-powered applications on Singdata Lakehouse.
|
|
119
114
|
- [Security Compliance Audit](references/security_compliance_audit_dir_guide.md): A brief section header introducing security and compliance audit topics.
|
|
120
115
|
- [Cost Management](references/cost_management.md): Stub page titled Cost Management for Singdata Lakehouse, intended to cover billing and cost control topics but currently without content.
|
|
@@ -1,26 +1,71 @@
|
|
|
1
1
|
# AI Gateway
|
|
2
2
|
|
|
3
|
-
Singdata AI Gateway is an enterprise-grade AI gateway service that provides unified multi-model API management, intelligent routing, BYOK model integration, and usage
|
|
3
|
+
Singdata AI Gateway is an enterprise-grade AI gateway service that provides unified multi-model API management, intelligent routing and scheduling, BYOK model integration, and usage analytics—helping enterprises simplify multi-vendor LLM integration with a single connection that can call all models.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+

|
|
6
6
|
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
|
7
|
+
## Access Methods
|
|
8
|
+
|
|
9
|
+
AI Gateway supports two access scenarios:
|
|
10
|
+
|
|
11
|
+
**Pre-configured clients (zero configuration, ready out of the box)**: The following clients have AI Gateway integration built in with no additional configuration required:
|
|
12
|
+
|
|
13
|
+
| Client | Purpose |
|
|
14
|
+
|--------|------|
|
|
15
|
+
| [Lakehouse SQL](AI_function_in_SQL.md) | Call `AI_COMPLETE()` / `AI_EMBEDDING()` directly in SQL |
|
|
16
|
+
| [Data Analytics Agent](datagpt_introduction.md) | Natural language conversational data analysis |
|
|
17
|
+
| [Data Engineering Agent](dataagent.md) | Natural language ETL development, task management, and ops diagnostics |
|
|
18
|
+
| [cz-cli](setup_cz_cli.md) | CLI command line / MCP tool interface |
|
|
19
|
+
| [Singclaw](https://www.singclaw.ai/) | Desktop intelligent agent that understands your business |
|
|
20
|
+
|
|
21
|
+
Using Lakehouse SQL as an example, simply call `AI_COMPLETE()` or `AI_EMBEDDING()` directly in SQL to use all enabled models:
|
|
22
|
+
|
|
23
|
+
```sql
|
|
24
|
+
-- Text generation, sentiment analysis, translation, summarization...
|
|
25
|
+
SELECT AI_COMPLETE('gw:qwen-max', CONCAT('Summarize in one sentence: ', content))
|
|
26
|
+
FROM articles;
|
|
27
|
+
|
|
28
|
+
-- Vectorization for semantic search and RAG
|
|
29
|
+
SELECT AI_EMBEDDING('gw:text-embedding-v3', text)
|
|
30
|
+
FROM documents;
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
**Custom Agent (one Endpoint + one API Key)**: Use the standard OpenAI SDK, replace `base_url` and `api_key`, no other code changes needed:
|
|
34
|
+
|
|
35
|
+
```python
|
|
36
|
+
from openai import OpenAI
|
|
37
|
+
|
|
38
|
+
client = OpenAI(
|
|
39
|
+
base_url="https://<your-instance>.singdata.com/ai-gateway/v1",
|
|
40
|
+
api_key="<your-api-key>",
|
|
41
|
+
)
|
|
42
|
+
response = client.chat.completions.create(
|
|
43
|
+
model="moonshotai/kimi-k2.6",
|
|
44
|
+
messages=[{"role": "user", "content": "hello"}],
|
|
45
|
+
)
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
## What I Want to Do
|
|
49
|
+
|
|
50
|
+
| Goal | Where to Go |
|
|
51
|
+
|------|--------|
|
|
52
|
+
| Understand AI Gateway features and positioning | [Product Introduction](Introduction.md) |
|
|
53
|
+
| Complete setup and call the first model in 10 minutes | [Quick Start](quickstart.md) |
|
|
54
|
+
| View supported models and pricing | [Model Pricing](pricing-ai-gateway.md) |
|
|
55
|
+
| Integrate your own third-party model (BYOK) | [Product Introduction → BYOK](Introduction.md) |
|
|
56
|
+
| Manage API Keys, set usage limits | [Product Introduction → API Key Management](Introduction.md) |
|
|
57
|
+
| Call LLMs in SQL for data analysis | [Call LLMs in SQL](lakehouse-ai-sql-analysis.md) |
|
|
58
|
+
| Analyze images in SQL | [Analyze Images in SQL](lakehouse-multimodal-ai-pipeline.md) |
|
|
14
59
|
|
|
15
60
|
## Core Capabilities at a Glance
|
|
16
61
|
|
|
17
|
-
**Unified access**:
|
|
62
|
+
**Unified access**: One API endpoint to call models from 20+ providers including Qwen, DeepSeek, GLM, Kimi, Doubao, GPT, Claude, Gemini, etc. 100% OpenAI interface compatible; existing code only needs endpoint and key replaced.
|
|
18
63
|
|
|
19
|
-
**Intelligent routing**: Automatically selects the optimal model by price, latency, and throughput, with automatic failover
|
|
64
|
+
**Intelligent routing**: Automatically selects the optimal model by price, latency, and throughput, with support for automatic failover and load balancing.
|
|
20
65
|
|
|
21
|
-
**BYOK**: Bring your own third-party API Key
|
|
66
|
+
**BYOK**: Bring your own third-party API Key; billing goes directly to the vendor account with no additional platform charges.
|
|
22
67
|
|
|
23
|
-
**Usage control**: Track token consumption by API Key, team,
|
|
68
|
+
**Usage control**: Track token consumption by API Key, team, and project dimensions, with support for limits and alerts, and real-time cost breakdown viewing.
|
|
24
69
|
|
|
25
70
|
## Quick Start
|
|
26
71
|
|
|
@@ -110,4 +110,6 @@ After completing all parameter configurations and passing the connection test, y
|
|
|
110
110
|
* Select this AWS DocumentDB data source in data synchronization tasks
|
|
111
111
|
* Configure specific collections and field mappings
|
|
112
112
|
* Set scheduling strategies and incremental update rules for data synchronization
|
|
113
|
-
* Execute data import or export operations
|
|
113
|
+
* Execute data import or export operations
|
|
114
|
+
|
|
115
|
+
^
|
|
@@ -4,15 +4,13 @@ This document introduces the composition and application logic of the For-each l
|
|
|
4
4
|
|
|
5
5
|
## How It Works
|
|
6
6
|
|
|
7
|
-

|
|
8
|
-
|
|
9
7
|
1. Special tasks that support output parameters: The For-each loop task must be bound to an upstream task that has output parameters. The system currently supports SQL, Python, and Shell task types for configuring **output parameters**.
|
|
10
8
|
2. LoopArray parameter: Configured on the For-each task, this is used to bind to upstream data. The upstream data results determine the number of loop iterations on the For-each task, as well as the specific values to be substituted within the For-each internal tasks.
|
|
11
9
|
3. Sub-task reference: If internal tasks of the For-each task need to reference upstream task values, they can obtain the values bound to the LoopArray from upstream via built-in parameters.
|
|
12
10
|
|
|
13
11
|
## Steps
|
|
14
12
|
|
|
15
|
-
**Prepare upstream data (configure a Python task)
|
|
13
|
+
**Prepare upstream data (configure a Python task**)
|
|
16
14
|
|
|
17
15
|
Create a new Python task and configure **output parameters** for it.
|
|
18
16
|
|
|
@@ -32,12 +30,11 @@ Click **Scheduling** -> **Loop Info** -> **Input Parameters**, and bind the Loop
|
|
|
32
30
|
>
|
|
33
31
|
> Dataset: `[1,'abc',2,'djg']`
|
|
34
32
|
|
|
35
|
-
|
|
33
|
+
^
|
|
36
34
|
|
|
37
35
|
The value of LoopArray is determined by binding to the output parameters of the upstream node. At the same time, selecting another task that has output parameters configured will automatically establish a dependency relationship between the two nodes.
|
|
38
36
|
|
|
39
37
|
2. Loop strategy
|
|
40
|
-

|
|
41
38
|
|
|
42
39
|
* Sequential: Runs in order according to the number of iterations.
|
|
43
40
|
* Parallel: Allows concurrent execution of internal For-each loops, improving task execution efficiency. In parallel mode, if any individual loop body fails, you can configure the **On Loop Failure** handling strategy to determine whether subsequent loops should be set to failed immediately or continue executing.
|
|
@@ -58,8 +55,8 @@ The value of LoopArray is determined by binding to the output parameters of the
|
|
|
58
55
|
|
|
59
56
|
Inside the For-each task, create a new SQL node.
|
|
60
57
|
|
|
61
|
-
After entering `${aa}` in the script area, configure this custom parameter in **
|
|
62
|
-
|
|
58
|
+
After entering `${aa}` in the script area, configure this custom parameter in \[**Parameters**]. During actual execution, parameter value substitution will take place.
|
|
59
|
+
|
|
63
60
|
|
|
64
61
|
## Temporary Run
|
|
65
62
|
|
|
@@ -69,22 +66,25 @@ For-each loops support entering LoopArray values for testing and verification du
|
|
|
69
66
|
|
|
70
67
|
> The upstream output dataset is `[1,2,3,4]`
|
|
71
68
|
|
|
72
|
-
| |
|
|
73
|
-
| ----------------------- |
|
|
74
|
-
| Parameter Name | Meaning
|
|
75
|
-
| dag\_foreach\_current() | Gets the data item currently being processed
|
|
69
|
+
| | | |
|
|
70
|
+
| ----------------------- | -------------------------------------------- | --------------------------------------- |
|
|
71
|
+
| Parameter Name | Meaning | Example |
|
|
72
|
+
| dag\_foreach\_current() | Gets the data item currently being processed | 4 iterations in total. \* 1st output: 1 |
|
|
73
|
+
|
|
76
74
|
* 2nd output: 2
|
|
77
75
|
* 3rd output: 3
|
|
78
76
|
* 4th output: 4 |
|
|
79
|
-
|
|
77
|
+
\| dag\_loopArray() | Gets the complete **result set** from the upstream assignment task | 4 iterations in total. \* 1st output: 1,2,3,4
|
|
80
78
|
* 2nd output: 1,2,3,4
|
|
81
79
|
* 3rd output: 1,2,3,4
|
|
82
80
|
* 4th output: 1,2,3,4 |
|
|
83
|
-
|
|
81
|
+
\| dag\_loopTimes() | Gets the current **iteration number**, starting from **1** | 4 iterations in total. \* 1st output: 1
|
|
84
82
|
* 2nd output: 2
|
|
85
83
|
* 3rd output: 3
|
|
86
84
|
* 4th output: 4 |
|
|
87
|
-
|
|
85
|
+
\| dag\_offset() | Gets the current loop **offset**, starting from **0**. | 4 iterations in total. \* 1st output: 0
|
|
88
86
|
* 2nd output: 1
|
|
89
87
|
* 3rd output: 2
|
|
90
88
|
* 4th output: 3 |
|
|
89
|
+
|
|
90
|
+
^
|
|
@@ -40,7 +40,6 @@ jdbc:clickzetta://<service_instance_name>.api.singdata.com/<workspace_name>?<con
|
|
|
40
40
|
|
|
41
41
|
* `<service_instance_name>`: Lakehouse service instance name. When a Lakehouse service instance is activated in a specified Region, the system will automatically assign an instance name. You can find the Lakehouse instance name on the Singdata product console page.
|
|
42
42
|
|
|
43
|
-

|
|
44
43
|
|
|
45
44
|
* `<workspace_name>`: Workspace name.
|
|
46
45
|
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# Lakehouse AI Features Overview
|
|
1
|
+
qqing# Lakehouse AI Features Overview
|
|
2
2
|
|
|
3
3
|
Singdata Lakehouse integrates AI capabilities natively into the data platform — you can call large language models, run vector search, and build RAG pipelines directly in SQL, without moving data to an external AI platform.
|
|
4
4
|
|
|
@@ -16,7 +16,8 @@ Singdata Lakehouse integrates AI capabilities natively into the data platform
|
|
|
16
16
|
| Call external HTTP services (cloud functions, vision APIs, custom models) | [External Function](remotefunction-intro.md) |
|
|
17
17
|
| Python data processing + AI inference with a PySpark-like interface | [Zettapark](zettapark-quick-start.md) |
|
|
18
18
|
| Encapsulate business semantics for BI tools and AI Agents | [Semantic View](semantic-view-overview.md) |
|
|
19
|
-
| Natural language conversational data analysis, zero-barrier data querying | [Data Analytics Agent (DataGPT)](
|
|
19
|
+
| Natural language conversational data analysis, zero-barrier data querying | [Data Analytics Agent (DataGPT)](datagpt_introduction.md) |
|
|
20
|
+
| Use natural language for ETL development, task management, operations diagnostics | [Data Engineering Agent](dataagent.md) |
|
|
20
21
|
| Let an AI Agent operate Lakehouse directly | [CZ-CLI](cz-cli.md) |
|
|
21
22
|
|
|
22
23
|
***
|
|
@@ -29,13 +30,10 @@ Singdata Lakehouse integrates AI capabilities natively into the data platform
|
|
|
29
30
|
|
|
30
31
|
```sql
|
|
31
32
|
-- Sentiment analysis on each user review
|
|
32
|
-
-- Replace endpoint:my_llm with the LLM endpoint name configured in your AI Gateway
|
|
33
33
|
SELECT
|
|
34
34
|
review_id,
|
|
35
35
|
review_text,
|
|
36
|
-
AI_COMPLETE('
|
|
37
|
-
'Classify the sentiment of the following review as "positive", "negative", or "neutral": '
|
|
38
|
-
|| review_text) AS sentiment
|
|
36
|
+
AI_COMPLETE('Classify the sentiment of the following review as "positive", "negative", or "neutral": ' || review_text) AS sentiment
|
|
39
37
|
FROM user_reviews;
|
|
40
38
|
```
|
|
41
39
|
|
|
@@ -49,10 +47,9 @@ Create vector indexes on tables to support approximate nearest neighbor (ANN) re
|
|
|
49
47
|
|
|
50
48
|
```sql
|
|
51
49
|
-- Semantic similarity search: find the 5 most relevant documents
|
|
52
|
-
-- Replace endpoint:my_embedding with the Embedding endpoint name configured in your AI Gateway
|
|
53
50
|
SELECT doc_id, content
|
|
54
51
|
FROM knowledge_base
|
|
55
|
-
ORDER BY cosine_distance(embedding,
|
|
52
|
+
ORDER BY cosine_distance(embedding, AI_EMBED('user question')) ASC
|
|
56
53
|
LIMIT 5;
|
|
57
54
|
```
|
|
58
55
|
|
|
@@ -84,6 +81,22 @@ A PySpark-like Python interface for running Python scripts on Lakehouse — suit
|
|
|
84
81
|
|
|
85
82
|
***
|
|
86
83
|
|
|
84
|
+
### Data Engineering Agent — Drive the Data Platform with Natural Language
|
|
85
|
+
|
|
86
|
+
An AI agent built on Lakehouse + Studio that uses natural language to complete ETL development, task management, daily operations, data source integration, and other tasks across the full data development lifecycle. No manual operation of the Studio interface required — just describe your requirements, and the Agent automatically breaks down tasks, calls tools, and executes.
|
|
87
|
+
|
|
88
|
+
Typical uses:
|
|
89
|
+
|
|
90
|
+
- **ETL development**: Describe your data warehouse layering design; automatically generate modeling specification documents and SQL code
|
|
91
|
+
- **Ad-hoc queries**: Ask questions in natural language; automatically generate and execute SQL, returning results directly
|
|
92
|
+
- **Daily operations**: Analyze failed tasks, locate root causes, quantify downstream impact, recommend fixes
|
|
93
|
+
- **Task management**: Create and configure Studio tasks, set scheduling and dependency relationships
|
|
94
|
+
- **Data source management**: Integrate and configure data sources, monitor sync status
|
|
95
|
+
|
|
96
|
+
→ [Data Engineering Agent Full Documentation](dataagent.md)
|
|
97
|
+
|
|
98
|
+
***
|
|
99
|
+
|
|
87
100
|
## Typical Scenarios
|
|
88
101
|
|
|
89
102
|
**RAG Knowledge Base Q&A**: Ingest documents → vectorize → build vector index → retrieve relevant chunks on user query → AI\_COMPLETE generates the answer
|
|
@@ -8,19 +8,16 @@ To learn more about DataGPT concepts and technical architecture, refer to [DataG
|
|
|
8
8
|
|
|
9
9
|
## Supported Data Sources
|
|
10
10
|
|
|
11
|
-
Lakehouse GPT can analyze data already stored in [Lakehouse tables](table.md). This means users can directly engage in conversational data analysis with Lakehouse GPT, extending Lakehouse's use cases from data engineering and SQL/Python-based analysis to interactive, visual data analysis experiences. This provides users with an easier way to explore data, allowing them to quickly obtain data results and corresponding SQL code through simple Q
|
|
11
|
+
Lakehouse GPT can analyze data already stored in [Lakehouse tables](table.md). This means users can directly engage in conversational data analysis with Lakehouse GPT, extending Lakehouse's use cases from data engineering and SQL/Python-based analysis to interactive, visual data analysis experiences. This provides users with an easier way to explore data, allowing them to quickly obtain data results and corresponding SQL code through simple Q\&A interactions.
|
|
12
12
|
|
|
13
13
|
Additionally, Lakehouse GPT supports directly loading files such as Excel, CSV, and PDF, with the loaded data stored in Lakehouse. This way, users no longer need to worry about Lakehouse-specific concepts (such as schemas, tables, or SQL), significantly lowering the barrier to entry for data analysis.
|
|
14
14
|
|
|
15
|
-

|
|
16
15
|
|
|
17
16
|
## Engage with DataGPT and Seamlessly Receive Comprehensive Data Analysis Results
|
|
18
17
|
|
|
19
|
-

|
|
20
18
|
|
|
21
19
|
We received a notification indicating that "**Results require verification**." Upon investigating the details, we found that the query involved "**Haidian District**." DataGPT is a data analysis tool powered by large language models (LLMs). It intelligently handled the multilingual nature of the data by interpreting "Haidian District" and associating it with the Chinese value "Haidian" in the table's district field. Since the table contains only Chinese district information, DataGPT's reasoning capabilities allowed it to recognize this correspondence and seamlessly align the data to produce accurate results. Nevertheless, the tool prompts users to verify the accuracy of the results.
|
|
22
20
|
|
|
23
|
-

|
|
24
21
|
|
|
25
22
|
This case clearly demonstrates the powerful capabilities of DataGPT, leveraging the strengths of large language models (LLMs) to overcome challenges commonly encountered by traditional business intelligence (BI) tools in data analysis. By harnessing the power of large language models (LLMs), DataGPT effectively addresses complex multilingual data issues, providing a solution that goes beyond the limitations of traditional BI tools, thereby elevating the entire analysis process.
|
|
26
23
|
|
|
@@ -34,23 +31,21 @@ Metric-based data analysis includes comparative analysis across different time p
|
|
|
34
31
|
|
|
35
32
|
Comparative analysis involves examining changes and trends over time, such as month-over-month, year-over-year, or quarter-over-quarter comparisons, to identify patterns, growth, or decline in performance metrics. This analysis is crucial for understanding progress and making strategic decisions.
|
|
36
33
|
|
|
37
|
-

|
|
38
34
|
|
|
39
35
|
### Multi-Dimensional Drill-Down
|
|
40
36
|
|
|
41
37
|
Multi-dimensional drill-down refers to the process of exploring data from multiple perspectives or dimensions. This may involve segmenting data by region, product line, customer group, or other relevant categories to gain deeper insights. Through drill-down, analysts can uncover the factors influencing overall metrics, enabling more targeted and information-driven decisions.
|
|
42
38
|
|
|
43
|
-

|
|
44
39
|
|
|
45
40
|
## Quick Start
|
|
46
41
|
|
|
47
42
|
* [DataGPT Quick Start](datagpt_quickstart.md): Quickly experience conversational analysis using **sample datasets**. We have prepared a well-configured dataset with complete table configurations and metric systems. You can start asking questions right away and quickly experience intelligent analysis features. Additionally, this sample can serve as a template to help you create analysis domains suited to your business scenarios.
|
|
48
|
-
|
|
43
|
+
|
|
49
44
|
|
|
50
45
|
* [DataGPT Data Source Management](config-datasource.md): Connect to Lakehouse instances in other regions.
|
|
51
46
|
|
|
52
47
|
* **Once your data is ready, you can start asking questions in natural language**.
|
|
53
|
-
|
|
48
|
+
|
|
54
49
|
|
|
55
50
|
## Configuration
|
|
56
51
|
|
|
@@ -59,6 +54,6 @@ Multi-dimensional drill-down refers to the process of exploring data from multip
|
|
|
59
54
|
|
|
60
55
|
## Data Privacy
|
|
61
56
|
|
|
62
|
-
* [DataGPT Data Privacy](data_privacy.md): Data privacy concerns during the Q
|
|
57
|
+
* [DataGPT Data Privacy](data_privacy.md): Data privacy concerns during the Q\&A process.
|
|
63
58
|
|
|
64
59
|
^
|
|
@@ -4,7 +4,7 @@ This document helps you quickly understand the core features offered by Lakehous
|
|
|
4
4
|
|
|
5
5
|
> You can use this document to quickly understand Studio's features. We also strongly recommend referring to the [Getting Started Guide](lakehouse-studio-101.md) series to get started quickly.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
|
|
8
8
|
|
|
9
9
|
^
|
|
10
10
|
|
|
@@ -53,11 +53,11 @@ Depending on the data source, data format, loading method, and processing type (
|
|
|
53
53
|
|
|
54
54
|
### Import Methods Overview
|
|
55
55
|
|
|
56
|
-
|
|
56
|
+
|
|
57
57
|
|
|
58
58
|
### Supported Data Sources
|
|
59
59
|
|
|
60
|
-
|
|
60
|
+
|
|
61
61
|
|
|
62
62
|
### Real-time Multi-Table Data Synchronization Tasks (CDC)
|
|
63
63
|
|
|
@@ -66,7 +66,7 @@ Depending on the data source, data format, loading method, and processing type (
|
|
|
66
66
|
* Submit and run the task, then start the task
|
|
67
67
|
* Task monitoring and maintenance (start, stop, offline)
|
|
68
68
|
|
|
69
|
-
|
|
69
|
+
|
|
70
70
|
|
|
71
71
|
For details, refer to the following documentation:
|
|
72
72
|
|
|
@@ -89,7 +89,7 @@ Worksheets provide a simple way to write SQL jobs (DML and DDL), view results, a
|
|
|
89
89
|
|
|
90
90
|
If you select Worksheets in the navigation menu, you will see the worksheet list and can select one to view and update worksheet content.
|
|
91
91
|
|
|
92
|
-
|
|
92
|
+
|
|
93
93
|
|
|
94
94
|
For details, refer to the following documentation:
|
|
95
95
|
|
|
@@ -102,13 +102,13 @@ For details, refer to the following documentation:
|
|
|
102
102
|
|
|
103
103
|
When running queries in Lakehouse Studio, you can choose to visualize the data profile of the results.
|
|
104
104
|
|
|
105
|
-
|
|
105
|
+
|
|
106
106
|
|
|
107
107
|
## Share Data
|
|
108
108
|
|
|
109
109
|
Achieve collaboration by sharing data with users of other Lakehouse accounts. When sharing data, you can use the automatic delivery (or auto-fulfillment) feature to easily provide data within the same cloud region. As a data consumer, you can access datasets shared with your account, gaining real-time data insights without setting up data pipelines or writing any code.
|
|
110
110
|
|
|
111
|
-
|
|
111
|
+
|
|
112
112
|
|
|
113
113
|
For details, refer to the following documentation:
|
|
114
114
|
|
|
@@ -120,7 +120,7 @@ For details, refer to the following documentation:
|
|
|
120
120
|
|
|
121
121
|
You can monitor and view query details, explore the performance of executed queries, monitor data loading status and errors, view task graphs, and debug and re-run as needed. You can also monitor the refresh status of dynamic tables and view various tags and security policies created for maintaining data governance.
|
|
122
122
|
|
|
123
|
-
|
|
123
|
+
|
|
124
124
|
|
|
125
125
|
For details, refer to the following documentation:
|
|
126
126
|
|
|
@@ -130,15 +130,15 @@ For details, refer to the following documentation:
|
|
|
130
130
|
|
|
131
131
|
The Operations Center provides management operations for tasks and instances. Workflow tasks managed by the Operations Center include manually triggered tasks, periodically scheduled tasks, and their corresponding instances, for centralized management.
|
|
132
132
|
|
|
133
|
-
|
|
133
|
+
|
|
134
134
|
|
|
135
135
|
Data backfilling involves supplementing historical or future data within a specific time period and writing it to the corresponding time partitions. If the code contains scheduling parameters, those parameters will be automatically filled with appropriate values based on the selected data backfill business time. Combined with business logic, this ensures that data for the corresponding time period is written to the specified partitions. The partition to write to and the code logic executed are determined by the task definitions in the code.
|
|
136
136
|
|
|
137
|
-
|
|
137
|
+
|
|
138
138
|
|
|
139
139
|
Monitoring functionality allows you to leverage built-in rules or custom configurations to keep a close watch on anomalies (such as task execution failures) and send alert notifications when needed.
|
|
140
140
|
|
|
141
|
-
|
|
141
|
+
|
|
142
142
|
|
|
143
143
|
For details, refer to the following documentation:
|
|
144
144
|
|
|
@@ -152,15 +152,15 @@ These pages help you understand Lakehouse data usage, manage virtual clusters, m
|
|
|
152
152
|
|
|
153
153
|
You can manage and monitor virtual clusters.
|
|
154
154
|
|
|
155
|
-
|
|
155
|
+
|
|
156
156
|
|
|
157
157
|
Access users and roles.
|
|
158
158
|
|
|
159
|
-
|
|
159
|
+
|
|
160
160
|
|
|
161
161
|
Perform cost management.
|
|
162
162
|
|
|
163
|
-
|
|
163
|
+
|
|
164
164
|
|
|
165
165
|
^
|
|
166
166
|
|
|
@@ -174,12 +174,7 @@ For details, refer to the following documentation:
|
|
|
174
174
|
* [Managing Service Instances](managing-instance.md)
|
|
175
175
|
* [User and Permission Management](authority-management.md)
|
|
176
176
|
|
|
177
|
-
## Related Videos
|
|
178
177
|
|
|
179
|
-
Achieve real-time data ingestion to real-time data analysis using Lakehouse Studio.
|
|
180
178
|
|
|
181
|
-
```[bilibili]
|
|
182
|
-
https://www.bilibili.com/video/BV1TfYYeEEYg/
|
|
183
|
-
```
|
|
184
179
|
|
|
185
180
|
^
|
|
@@ -45,7 +45,7 @@ hints['query_tag'] = 'test_conn_hints_zettapark'
|
|
|
45
45
|
connection_parameters = {
|
|
46
46
|
"username": "qiliang",
|
|
47
47
|
"password": "",
|
|
48
|
-
"service": "
|
|
48
|
+
"service": "api.clickzetta.com",
|
|
49
49
|
"instance": "",
|
|
50
50
|
"workspace": "ql_ws",
|
|
51
51
|
"schema": "wayfair_wans",
|
|
@@ -95,7 +95,7 @@ input {
|
|
|
95
95
|
|
|
96
96
|
output {
|
|
97
97
|
clickzetta {
|
|
98
|
-
jdbcUrl => "jdbc:clickzetta://9a310b9b.
|
|
98
|
+
jdbcUrl => "jdbc:clickzetta://9a310b9b.api.clickzetta.com/quick_start?schema=public&username=index_test&password=password&virtualCluster=YETING_TEST_AP"
|
|
99
99
|
username => "index_test"
|
|
100
100
|
password => "password"
|
|
101
101
|
schema => "public"
|
|
@@ -154,7 +154,7 @@ ruby {
|
|
|
154
154
|
output {
|
|
155
155
|
if "odd" in [tags] {
|
|
156
156
|
clickzetta {
|
|
157
|
-
jdbcUrl => "jdbc:clickzetta://9a310b9b.
|
|
157
|
+
jdbcUrl => "jdbc:clickzetta://9a310b9b.api.clickzetta.com/quick_start?schema=public&username=index_test&password=password&virtualCluster=YETING_TEST_AP"
|
|
158
158
|
username => "index_test"
|
|
159
159
|
password => "password"
|
|
160
160
|
schema => "public"
|
|
@@ -166,7 +166,7 @@ output {
|
|
|
166
166
|
}
|
|
167
167
|
} else {
|
|
168
168
|
clickzetta {
|
|
169
|
-
jdbcUrl => "jdbc:clickzetta://9a310b9b.
|
|
169
|
+
jdbcUrl => "jdbc:clickzetta://9a310b9b.api.clickzetta.com/quick_start?schema=public&username=index_test&password=password&virtualCluster=YETING_TEST_AP"
|
|
170
170
|
username => "index_test"
|
|
171
171
|
password => "password"
|
|
172
172
|
schema => "public"
|
|
@@ -185,7 +185,7 @@ Set the value for each parameter:
|
|
|
185
185
|
|
|
186
186
|
:-: 
|
|
187
187
|
|
|
188
|
-
For how to obtain parameter values, please refer to [this article](
|
|
188
|
+
For how to obtain parameter values, please refer to [this article](jdbc-driver.md).
|
|
189
189
|
|
|
190
190
|
^
|
|
191
191
|
|
|
@@ -8,7 +8,7 @@ Notebook is a web-based code editor that can be used for writing code and viewin
|
|
|
8
8
|
|
|
9
9
|
Click on the sidebar: Analysis -> New Notebook
|
|
10
10
|
|
|
11
|
-

|
|
12
12
|
|
|
13
13
|
A: Left sidebar Directory Tree and Data Tree
|
|
14
14
|
B: Notebook Function Operations Area
|
|
@@ -25,12 +25,12 @@ C: Notebook Cells
|
|
|
25
25
|
|
|
26
26
|
## Function Operations Area
|
|
27
27
|
|
|
28
|
-
| No. | Icon
|
|
29
|
-
|
|
|
30
|
-
| 1
|
|
31
|
-
| 2
|
|
32
|
-
| 3
|
|
33
|
-
| 4
|
|
28
|
+
| No. | Icon | Description |
|
|
29
|
+
| --- | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
30
|
+
| 1 |  | The global parameters of the current Notebook. If custom parameters are referenced below in the format `${custom_parameter}`, users need to input the parameter values here.Note: Parameters are global. If the same custom parameter name is referenced in different cells, it will be replaced with the same parameter value during execution. |
|
|
31
|
+
| 2 |  | Run All Cells or Stop Execution." The name of this button changes dynamically based on the notebook's status. After the user clicks "Run All", the cells will be executed sequentially in order. |
|
|
32
|
+
| 3 |  | Cluster information for executing SQL cells. |
|
|
33
|
+
| 4 |  | More Actions: Supports renaming, duplicating, and deleting the Notebook. |
|
|
34
34
|
|
|
35
35
|
^
|
|
36
36
|
|
|
@@ -63,16 +63,16 @@ Notebook contains two types of cell collections: Code cells and Markdown cells.
|
|
|
63
63
|
|
|
64
64
|
### Cell Operations
|
|
65
65
|
|
|
66
|
-
| No. | Icon
|
|
67
|
-
|
|
|
68
|
-
| 1
|
|
69
|
-
| 2
|
|
70
|
-
|
|
|
71
|
-
| 3
|
|
72
|
-
| 4
|
|
73
|
-
| 5
|
|
74
|
-
| 6
|
|
75
|
-
| 7
|
|
66
|
+
| No. | Icon | Description |
|
|
67
|
+
| --- | --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
68
|
+
| 1 |  | Cell Types.Different cell types support different languages. |
|
|
69
|
+
| 2 |  | Cell Name. When a user creates a new cell, the system automatically assigns a default cell name. Double-clicking this area allows the user to rename the cell.Notebook enables users to directly reference a cell's output values in Python scripts. This requires users to specify the exact name of the cell containing the output information for data positioning.Cell names only support English letters (both uppercase and lowercase), numbers, and underscores (\_). |
|
|
70
|
+
| | | |
|
|
71
|
+
| 3 |  | Expand/Collapse Cell Code and Display Results.When the code content in the current Notebook is too long, users can click the arrow on the left side to separately expand or collapse the code and result areas. |
|
|
72
|
+
| 4 |  | Moving Cells. The execution in a Notebook follows a strict sequential order. If users need to adjust the position of a cell, they can hover the mouse over the cell, select the move handle area, and then drag the cell up or down to reposition it. |
|
|
73
|
+
| 5 |  | Quickly Add Cells.When hovering over the area above or below the central region of the current cell, new cells can be quickly added above or below the current position. |
|
|
74
|
+
| 6 |  | Run cell. |
|
|
75
|
+
| 7 |  | More Cell Operations. Rename: Click to assign a new name to the cell.Clear Output: Clears the execution results of the current cell. If other cells depend on the output of this cell, their execution may fail. Delete: Deletes the cell. |
|
|
76
76
|
|
|
77
77
|
##
|
|
78
78
|
|