 CloudBeaver User Guide v.23.2Guide 23.2. Page 173 of 182. Note: This feature is available in edition only. Team Edition A Dataset is a query result set presented in the form of a data grid that analytical team members can effectively going deep into database mechanisms. Note: Dataset changes are immediately available to colleagues. If you delete or edit a in the web version of Dataset , it will immediately disappear in the desktop version. Dataset You can unfold your database connection in the , access the existing table, open it in the main Database Navigator view, and use the button at the bottom. Add Dataset Create using0 码力 | 182 页 | 15.64 MB | 1 年前3 CloudBeaver User Guide v.23.2Guide 23.2. Page 173 of 182. Note: This feature is available in edition only. Team Edition A Dataset is a query result set presented in the form of a data grid that analytical team members can effectively going deep into database mechanisms. Note: Dataset changes are immediately available to colleagues. If you delete or edit a in the web version of Dataset , it will immediately disappear in the desktop version. Dataset You can unfold your database connection in the , access the existing table, open it in the main Database Navigator view, and use the button at the bottom. Add Dataset Create using0 码力 | 182 页 | 15.64 MB | 1 年前3
 CloudBeaver User Guide v.23.3Grouping Panel Editing Datasets Note: This feature is available in edition only. Team Edition A Dataset is a query result set presented in the form of a data grid that analytical team members can effectively going deep into database mechanisms. Note: Dataset changes are immediately available to colleagues. If you delete or edit a in the web version of Dataset , it will immediately disappear in the desktop version. Dataset You can unfold your database connection in the , access the existing table, open it in the main Database Navigator view, and use the button at the bottom. Add Dataset Create using0 码力 | 252 页 | 21.86 MB | 1 年前3 CloudBeaver User Guide v.23.3Grouping Panel Editing Datasets Note: This feature is available in edition only. Team Edition A Dataset is a query result set presented in the form of a data grid that analytical team members can effectively going deep into database mechanisms. Note: Dataset changes are immediately available to colleagues. If you delete or edit a in the web version of Dataset , it will immediately disappear in the desktop version. Dataset You can unfold your database connection in the , access the existing table, open it in the main Database Navigator view, and use the button at the bottom. Add Dataset Create using0 码力 | 252 页 | 21.86 MB | 1 年前3
 Apache ShardingSphere 5.0.0-alpha Documentenv‐native.properties – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/dataset.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/schema.xml • test integration‐test‐cases.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/cases/SQL-TYPE/dataset/FEATURE-TYPE/*.xml • sql‐case – /sharding‐sql‐test/src/main/resources/sql/sharding/SQL-TYPE/*.xml rc/test/ resources/env/SQL-TYPE/dataset.xml. Developer can set up metadata and expected data to start the data initialization in dataset.xml. For example: <dataset> Apache ShardingSphere 5.0.0-alpha Documentenv‐native.properties – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/dataset.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/schema.xml • test integration‐test‐cases.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/cases/SQL-TYPE/dataset/FEATURE-TYPE/*.xml • sql‐case – /sharding‐sql‐test/src/main/resources/sql/sharding/SQL-TYPE/*.xml rc/test/ resources/env/SQL-TYPE/dataset.xml. Developer can set up metadata and expected data to start the data initialization in dataset.xml. For example: <dataset>- 0 码力 | 311 页 | 2.09 MB | 1 年前 3
 Apache ShardingSphere 中文文档 5.0.0-alphaexpected-data-file="${dataset_file_1}.xml" /> Apache ShardingSphere 中文文档 5.0.0-alphaexpected-data-file="${dataset_file_1}.xml" />- 3.10. 测试引擎 的查找规则是:1. 查找同级目录中 dataset\${SCENARIO_NAME}\ ${DATABASE_TYPE}\${dataset_file}.xml 文 件;2. 查 找 同 级 目 录 中 dataset\ ${SCENARIO_NAME}\${dataset_file}.xml 文 件;3. 查 找 同 级 目 录 中 dataset\ ${dataset_file}.xml 文件;4 文件;4. 都找不到则报错。 断言文件格式如下: <dataset> 0 码力 | 301 页 | 3.44 MB | 1 年前3
 Apache ShardingSphere 5.1.1 Documentenv‐native.properties – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/dataset.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/schema.xml • test integration‐test‐cases.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/cases/SQL-TYPE/dataset/FEATURE-TYPE/*.xml • sql‐case – /sharding‐sql‐test/src/main/resources/sql/sharding/SQL-TYPE/*.xml rc/test/ resources/env/SQL-TYPE/dataset.xml. Developer can set up metadata and expected data to start the data initialization in dataset.xml. For example: <dataset> Apache ShardingSphere 5.1.1 Documentenv‐native.properties – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/dataset.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/schema.xml • test integration‐test‐cases.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/cases/SQL-TYPE/dataset/FEATURE-TYPE/*.xml • sql‐case – /sharding‐sql‐test/src/main/resources/sql/sharding/SQL-TYPE/*.xml rc/test/ resources/env/SQL-TYPE/dataset.xml. Developer can set up metadata and expected data to start the data initialization in dataset.xml. For example: <dataset>- 0 码力 | 458 页 | 3.43 MB | 1 年前 3
 Apache ShardingSphere 5.1.2 Documentenv‐native.properties – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/dataset.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/schema.xml • test integration‐test‐cases.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/cases/SQL-TYPE/dataset/FEATURE-TYPE/*.xml • sql‐case – /sharding‐sql‐test/src/main/resources/sql/sharding/SQL-TYPE/*.xml rc/test/ resources/env/SQL-TYPE/dataset.xml. Developer can set up metadata and expected data to start the data initialization in dataset.xml. For example: <dataset> Apache ShardingSphere 5.1.2 Documentenv‐native.properties – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/dataset.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/schema.xml • test integration‐test‐cases.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/cases/SQL-TYPE/dataset/FEATURE-TYPE/*.xml • sql‐case – /sharding‐sql‐test/src/main/resources/sql/sharding/SQL-TYPE/*.xml rc/test/ resources/env/SQL-TYPE/dataset.xml. Developer can set up metadata and expected data to start the data initialization in dataset.xml. For example: <dataset>- 0 码力 | 503 页 | 3.66 MB | 1 年前 3
 SelectDB案例 从 ClickHouse 到 Apache DorisDWS 表中抽取字段。  加速层:在数仓中构建的大宽表导入到加速层中,Clickhouse 作为分析引擎, Elasticsearch 作为搜索/圈选引擎。  应用层:根据场景创建 DataSet,作为逻辑视图从大宽表选取所需的标签与指标,同 时可以二次定义衍生的标签与指标。 存在的问题:  数仓层:不支持部分列更新,当上游任一来源表产生延迟,均会造成大宽表延迟, 进而导致数据时效性下降。 应用层:DataSet 统一指向 Doris,Doris 支持外表查询,利用该特性可对 ES 引擎 直接查询。 架构 2.0 存在的问题:  DataSet 灵活度较高,数据分析师可对指标和标签自由组合和定义,但是不同的分 析师对同一数据的定义不尽相同、定义口径不一致,导致指标和标签缺乏统一管理, 4 这使得数据管理和使用的难度都变高。  Dataset 与物理位置绑定,应用层无法进行透明优化,如果 换为业务部门更容易理解的概念,目的是将标签 (tag)与指标(metric)变为“一等公民”,作为 数据定义与管理的基本对象。 引入语义层的优势有:  对于技术来说,应用层不再需要创建 DataSet,从语义层可直接获取特定内容对象 的标签集 (tagset)和指标集(metricset) 来发起查询。  对于数据分析师来说,可统一在语义层定义和创建衍生的指标和标签,解决了定义 口径不一致、管理和使用难度较高的问题。0 码力 | 12 页 | 1.55 MB | 1 年前3 SelectDB案例 从 ClickHouse 到 Apache DorisDWS 表中抽取字段。  加速层:在数仓中构建的大宽表导入到加速层中,Clickhouse 作为分析引擎, Elasticsearch 作为搜索/圈选引擎。  应用层:根据场景创建 DataSet,作为逻辑视图从大宽表选取所需的标签与指标,同 时可以二次定义衍生的标签与指标。 存在的问题:  数仓层:不支持部分列更新,当上游任一来源表产生延迟,均会造成大宽表延迟, 进而导致数据时效性下降。 应用层:DataSet 统一指向 Doris,Doris 支持外表查询,利用该特性可对 ES 引擎 直接查询。 架构 2.0 存在的问题:  DataSet 灵活度较高,数据分析师可对指标和标签自由组合和定义,但是不同的分 析师对同一数据的定义不尽相同、定义口径不一致,导致指标和标签缺乏统一管理, 4 这使得数据管理和使用的难度都变高。  Dataset 与物理位置绑定,应用层无法进行透明优化,如果 换为业务部门更容易理解的概念,目的是将标签 (tag)与指标(metric)变为“一等公民”,作为 数据定义与管理的基本对象。 引入语义层的优势有:  对于技术来说,应用层不再需要创建 DataSet,从语义层可直接获取特定内容对象 的标签集 (tagset)和指标集(metricset) 来发起查询。  对于数据分析师来说,可统一在语义层定义和创建衍生的指标和标签,解决了定义 口径不一致、管理和使用难度较高的问题。0 码力 | 12 页 | 1.55 MB | 1 年前3
 Apache ShardingSphere 5.4.1 Documentexpected-data-file="${dataset_file_1}.xml" /> Apache ShardingSphere 5.4.1 Documentexpected-data-file="${dataset_file_1}.xml" />- as follows: 1. Find the file dataset\ ${SCENARIO_NAME}\${DATABASE_TYPE}\${dataset_file}.xml in the same level directory; 2. Find the file dataset\${SCENARIO_NAME}\${dataset_file}.xml in the same level document 3. Find the file dataset\${dataset_file}.xml in the same level directory; 4. Report an error if none of them are found. The assertion file format is as follows: <dataset> 0 码力 | 572 页 | 3.73 MB | 1 年前3 Apache ShardingSphere 5.2.0 Documentexpected-data-file="${dataset_file_1}.xml" /> Apache ShardingSphere 5.2.0 Documentexpected-data-file="${dataset_file_1}.xml" />- the file dataset\ ${SCENARIO_NAME}\${DATABASE_TYPE}\${dataset_file}.xml in the same level directory; 2. 6.5. Integration Test 328 Apache ShardingSphere document, v5.2.0 Find the file dataset\${SCENA dataset\${SCENARIO_NAME}\${dataset_file}.xml in the same level directory; 3. Find the file dataset\${dataset_file}.xml in the same level directory; 4. Report an error if none of them are found. The assertion file 0 码力 | 483 页 | 4.27 MB | 1 年前3 Apache ShardingSphere 5.0.0 Documentenv‐native.properties – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/dataset.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/schema.xml • test integration‐test‐cases.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/cases/SQL-TYPE/dataset/FEATURE-TYPE/*.xml • sql‐case – /sharding‐sql‐test/src/main/resources/sql/sharding/SQL-TYPE/*.xml rc/test/ resources/env/SQL-TYPE/dataset.xml. Developer can set up metadata and expected data to start the data initialization in dataset.xml. For example: <dataset> Apache ShardingSphere 5.0.0 Documentenv‐native.properties – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/dataset.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/env/SQL-TYPE/schema.xml • test integration‐test‐cases.xml – /shardingsphere‐integration‐test‐suite/src/test/resources/cases/SQL-TYPE/dataset/FEATURE-TYPE/*.xml • sql‐case – /sharding‐sql‐test/src/main/resources/sql/sharding/SQL-TYPE/*.xml rc/test/ resources/env/SQL-TYPE/dataset.xml. Developer can set up metadata and expected data to start the data initialization in dataset.xml. For example: <dataset>- 0 码力 | 403 页 | 3.15 MB | 1 年前 3
共 82 条
- 1
- 2
- 3
- 4
- 5
- 6
- 9














