You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2022/06/16 06:31:24 UTC
[GitHub] [flink-table-store] JingsongLi opened a new pull request, #159: [FLINK-28088] Adjust table store document to catalog
JingsongLi opened a new pull request, #159:
URL: https://github.com/apache/flink-table-store/pull/159
After quite a bit of development, we needed to adjust the documentation, use the latest model, and tweak some details.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] LadyForest commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
LadyForest commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898753906
##########
docs/content/_index.md:
##########
@@ -24,16 +24,13 @@ under the License.
# Apache Flink Table Store
-Flink Table Store is a unified streaming and batch store for building dynamic
-tables on Apache Flink. It is designed to be the best connector to Flink as
-the storage for streaming warehouse. It uses a full Log-Structured Merge-Tree
-(LSM) structure for high speed and large amount of data update & query capability.
-
-Flink Table Store supports the following usage:
-- **Streaming Insert**: Write changelog streams, including CDC from database and streams.
-- **Batch Insert**: Write batch data as offline warehouse, including OVERWRITE support.
-- **Batch/OLAP Query**: Read snapshot of the storage, efficient querying of real-time data.
-- **Streaming Query**: Read changes of the storage, ensure exactly-once consistency.
+Flink Table Store is a unified storage to build dynamic tables for both streaming and
+batch processing in Flink, supporting high speed data ingestion and timely data query.
+Table Store offers the following core capabilities:
+- Support storage of large datasets and allows read / write in both batch and streaming manner.
Review Comment:
```suggestion
- Support storage of large datasets and allow read/write in both batch and streaming mode.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] LadyForest commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
LadyForest commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898836246
##########
docs/content/docs/development/query-table.md:
##########
@@ -58,51 +58,14 @@ Supported filter functions are:
- `in`
- starts with `like`
-## Streaming Real-time
+## Real-time Streaming Consumption
By default, data is only visible after the checkpoint, which means
that the streaming reading has transactional consistency.
-If you want the data to be immediately visible, you need to set the following options:
+If you want the data to be immediately visible, you need to set table option:
+`log.consistency` = `eventual`.
-<table class="table table-bordered">
- <thead>
- <tr>
- <th class="text-left" style="width: 20%">Table Option</th>
- <th class="text-center" style="width: 5%">Default</th>
- <th class="text-center" style="width: 60%">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td><h5>`log.system` = `kafka`</h5></td>
- <td>No</td>
- <td>You need to enable log system because the FileStore's continuous consumption only provides checkpoint-based visibility.</td>
- </tr>
- <tr>
- <td><h5>`log.consistency` = `eventual`</h5></td>
- <td>No</td>
- <td>This means that writes are visible without using LogSystem's transaction mechanism.</td>
- </tr>
- </tbody>
-</table>
-
-Note: All tables need to have the primary key defined because only then can the
-data be de-duplicated by the normalizing node of the downstream job.
-
-## Streaming Low Cost
-
-By default, for the table with the primary key, the records in the table store only
-contain `INSERT`, `UPDATE_AFTER`, and `DELETE`. The downstream consuming job will
-generate a normalized node, and it stores all processed key-value to produce the
-`UPDATE_BEFORE` message, which will bring extra overhead.
-
-If you want to remove downstream normalized node (It's costly) or see the all
-changes of this table, you can configure:
-- 'log.changelog-mode' = 'all'
-- 'log.consistency' = 'transactional' (default)
-
-The inserted query written to the table store must contain all message types with
-`UPDATE_BEFORE`, otherwise the planner will throw an exception. It means that Planner
-expects the inserted query to produce a real changelog, otherwise the data would
-be wrong.
+In this at-least-once mode, records are sent to downstream jobs ahead of time,
+which means that duplicate data may be sent at job failover, and you may need to
+manually de-duplicate data to achieve final consistency.
Review Comment:
```suggestion
Due to the tradeoff between data freshness and completeness, immediate data visibility is barely accomplished under exactly-once semantics. Nevertheless, users can relax the constraint to use at-least-once mode to achieve it. Note that records may be sent to downstream jobs ahead of the watermark (since no barrier alignment is required), which may lead to duplicate data during job failover. As a result, users may need to manually de-duplicate data to achieve final consistency.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] LadyForest commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
LadyForest commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898813837
##########
docs/content/docs/development/overview.md:
##########
@@ -26,9 +26,27 @@ under the License.
# Overview
-Flink Table Store is a unified streaming and batch store for building dynamic
-tables on Apache Flink. Flink Table Store serves as the storage engine behind
-Flink SQL Managed Table.
+Flink Table Store is a unified storage to build dynamic tables for both streaming and
+batch processing in Flink, supporting high speed data ingestion and timely data query.
+
+## Architecture
+
+<center>
+<img src="/img/architecture.png" width="100%"/>
+</center>
+
+As shown in the architecture above:
+
+* Users can use Flink to insert data into the Table Store, either by streaming the change log
+ captured from databases, or by loading the data in batches from the other stores like data warehouses.
Review Comment:
```suggestion
* **Consumption Mode** Table Store supports a versatile way to read/write data and perform OLAP queries.
- For reads, it supports consuming data <1> from historical snapshots (in batch mode), <2>from the latest offset (in continuous mode), or <3> reading incremental snapshots in a hybrid way.
- For writes, it supports streaming synchronization of the changelog of databases(CDC) or bulk load the tables from other data warehouses.
OLAP queries are supported either in streaming or batch mode.
* **Ecosystem** In addition to Apache Flink, Table Store also supports read/write by other computation engines like Apache Hive.
* **Internal** Under the hood, table Store uses a hybrid storage architecture with a lakehouse format to store historical data and a queue system to store incremental data. The former stores the columnar files on the filesystem/object-store and uses the LSM tree structure to support a large volume of data updates and high-performance queries. The latter uses Apache Kafka to capture data in real-time[1].
[1] https://kafka.apache.org/intro
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] JingsongLi commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
JingsongLi commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898857537
##########
docs/content/docs/development/create-table.md:
##########
@@ -26,6 +26,31 @@ under the License.
# Create Table
+## Catalog
+
+Table Store uses Catalog to manage all the databases and tables. You need to create a
+Table Store catalog and use it. Table Store catalog has a root directory, configured through `warehouse`.
+
+```sql
+CREATE CATALOG my_catalog WITH (
+ 'type'='table-store',
+ 'warehouse'='hdfs://nn:8020/warehouse/path'
+);
+
+USE CATALOG my_catalog;
+```
+
+Table Store catalog supports SQL DDL commands:
+- `CREATE TABLE ... PARTITIONED BY`
+- `DROP TABLE ...`
+- `ALTER TABLE ...`
+- `SHOW DATABASES`
+- `SHOW TABLES`
+
+The path of table in catalog is `${warehouse}/${database_name}.db/${table_name}`.
Review Comment:
This is in the catalog chapter.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] JingsongLi merged pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
JingsongLi merged PR #159:
URL: https://github.com/apache/flink-table-store/pull/159
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] LadyForest commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
LadyForest commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898771362
##########
docs/content/docs/development/create-table.md:
##########
@@ -26,6 +26,31 @@ under the License.
# Create Table
+## Catalog
+
+Table Store uses Catalog to manage all the databases and tables. You need to create a
+Table Store catalog and use it. Table Store catalog has a root directory, configured through `warehouse`.
+
+```sql
+CREATE CATALOG my_catalog WITH (
+ 'type'='table-store',
+ 'warehouse'='hdfs://nn:8020/warehouse/path'
+);
+
+USE CATALOG my_catalog;
+```
+
+Table Store catalog supports SQL DDL commands:
+- `CREATE TABLE ... PARTITIONED BY`
+- `DROP TABLE ...`
+- `ALTER TABLE ...`
+- `SHOW DATABASES`
+- `SHOW TABLES`
+
+The path of table in catalog is `${warehouse}/${database_name}.db/${table_name}`.
Review Comment:
```suggestion
This will create a directory under `${warehouse}/${database_name}.db/${table_name}`.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] LadyForest commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
LadyForest commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898752925
##########
docs/content/_index.md:
##########
@@ -24,16 +24,13 @@ under the License.
# Apache Flink Table Store
-Flink Table Store is a unified streaming and batch store for building dynamic
-tables on Apache Flink. It is designed to be the best connector to Flink as
-the storage for streaming warehouse. It uses a full Log-Structured Merge-Tree
-(LSM) structure for high speed and large amount of data update & query capability.
-
-Flink Table Store supports the following usage:
-- **Streaming Insert**: Write changelog streams, including CDC from database and streams.
-- **Batch Insert**: Write batch data as offline warehouse, including OVERWRITE support.
-- **Batch/OLAP Query**: Read snapshot of the storage, efficient querying of real-time data.
-- **Streaming Query**: Read changes of the storage, ensure exactly-once consistency.
+Flink Table Store is a unified storage to build dynamic tables for both streaming and
+batch processing in Flink, supporting high speed data ingestion and timely data query.
Review Comment:
```suggestion
batch processing in Flink, supporting high-speed data ingestion and timely data query.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] LadyForest commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
LadyForest commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898810490
##########
docs/content/docs/development/overview.md:
##########
@@ -26,9 +26,27 @@ under the License.
# Overview
-Flink Table Store is a unified streaming and batch store for building dynamic
-tables on Apache Flink. Flink Table Store serves as the storage engine behind
-Flink SQL Managed Table.
+Flink Table Store is a unified storage to build dynamic tables for both streaming and
+batch processing in Flink, supporting high speed data ingestion and timely data query.
+
+## Architecture
+
+<center>
+<img src="/img/architecture.png" width="100%"/>
+</center>
+
+As shown in the architecture above:
Review Comment:
I found this part is a little bit unclearly, so I reorganized it as follows.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] LadyForest commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
LadyForest commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898770845
##########
docs/content/docs/development/create-table.md:
##########
@@ -26,6 +26,31 @@ under the License.
# Create Table
+## Catalog
+
+Table Store uses Catalog to manage all the databases and tables. You need to create a
+Table Store catalog and use it. Table Store catalog has a root directory, configured through `warehouse`.
+
+```sql
+CREATE CATALOG my_catalog WITH (
+ 'type'='table-store',
+ 'warehouse'='hdfs://nn:8020/warehouse/path'
+);
+
+USE CATALOG my_catalog;
+```
+
+Table Store catalog supports SQL DDL commands:
+- `CREATE TABLE ... PARTITIONED BY`
+- `DROP TABLE ...`
+- `ALTER TABLE ...`
+- `SHOW DATABASES`
+- `SHOW TABLES`
+
+The path of table in catalog is `${warehouse}/${database_name}.db/${table_name}`.
Review Comment:
Suggest moving it right following the sql example
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] LadyForest commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
LadyForest commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898816161
##########
docs/content/docs/development/query-table.md:
##########
@@ -45,7 +45,7 @@ SELECT * FROM MyTable /*+ OPTIONS ('log.scan'='latest') */;
## Query Optimization
-It is highly recommended to take partition and primary key filters
+It is highly recommended taking partition and primary key filters
Review Comment:
```suggestion
It is highly recommended to specify partition and primary key filters
along with the query, which will speed up the data skipping of the query.
```
Nit: `It is recommended to do sth.`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] LadyForest commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
LadyForest commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898773824
##########
docs/content/docs/development/overview.md:
##########
@@ -26,9 +26,27 @@ under the License.
# Overview
-Flink Table Store is a unified streaming and batch store for building dynamic
-tables on Apache Flink. Flink Table Store serves as the storage engine behind
-Flink SQL Managed Table.
+Flink Table Store is a unified storage to build dynamic tables for both streaming and
+batch processing in Flink, supporting high speed data ingestion and timely data query.
Review Comment:
```suggestion
batch processing in Flink, supporting high-speed data ingestion and timely data query.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] LadyForest commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
LadyForest commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898817487
##########
docs/content/docs/development/query-table.md:
##########
@@ -58,51 +58,14 @@ Supported filter functions are:
- `in`
- starts with `like`
-## Streaming Real-time
+## Real-time Streaming Consumption
By default, data is only visible after the checkpoint, which means
that the streaming reading has transactional consistency.
-If you want the data to be immediately visible, you need to set the following options:
+If you want the data to be immediately visible, you need to set table option:
Review Comment:
```suggestion
Immediate data visibility is configured via
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] LadyForest commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
LadyForest commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898836246
##########
docs/content/docs/development/query-table.md:
##########
@@ -58,51 +58,14 @@ Supported filter functions are:
- `in`
- starts with `like`
-## Streaming Real-time
+## Real-time Streaming Consumption
By default, data is only visible after the checkpoint, which means
that the streaming reading has transactional consistency.
-If you want the data to be immediately visible, you need to set the following options:
+If you want the data to be immediately visible, you need to set table option:
+`log.consistency` = `eventual`.
-<table class="table table-bordered">
- <thead>
- <tr>
- <th class="text-left" style="width: 20%">Table Option</th>
- <th class="text-center" style="width: 5%">Default</th>
- <th class="text-center" style="width: 60%">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td><h5>`log.system` = `kafka`</h5></td>
- <td>No</td>
- <td>You need to enable log system because the FileStore's continuous consumption only provides checkpoint-based visibility.</td>
- </tr>
- <tr>
- <td><h5>`log.consistency` = `eventual`</h5></td>
- <td>No</td>
- <td>This means that writes are visible without using LogSystem's transaction mechanism.</td>
- </tr>
- </tbody>
-</table>
-
-Note: All tables need to have the primary key defined because only then can the
-data be de-duplicated by the normalizing node of the downstream job.
-
-## Streaming Low Cost
-
-By default, for the table with the primary key, the records in the table store only
-contain `INSERT`, `UPDATE_AFTER`, and `DELETE`. The downstream consuming job will
-generate a normalized node, and it stores all processed key-value to produce the
-`UPDATE_BEFORE` message, which will bring extra overhead.
-
-If you want to remove downstream normalized node (It's costly) or see the all
-changes of this table, you can configure:
-- 'log.changelog-mode' = 'all'
-- 'log.consistency' = 'transactional' (default)
-
-The inserted query written to the table store must contain all message types with
-`UPDATE_BEFORE`, otherwise the planner will throw an exception. It means that Planner
-expects the inserted query to produce a real changelog, otherwise the data would
-be wrong.
+In this at-least-once mode, records are sent to downstream jobs ahead of time,
+which means that duplicate data may be sent at job failover, and you may need to
+manually de-duplicate data to achieve final consistency.
Review Comment:
```suggestion
Due to the tradeoff between data freshness and completeness, immediate data visibility is barely accomplished under exactly-once semantics. Nevertheless, users can relax the constraint to use at-least-once mode to achieve it. Note that records may be sent to downstream jobs ahead (since no barrier alignment is required), which may lead to duplicate data during job failover. As a result, users may need to manually de-duplicate data to achieve final consistency.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] LadyForest commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
LadyForest commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898755770
##########
docs/content/_index.md:
##########
@@ -24,16 +24,13 @@ under the License.
# Apache Flink Table Store
-Flink Table Store is a unified streaming and batch store for building dynamic
-tables on Apache Flink. It is designed to be the best connector to Flink as
-the storage for streaming warehouse. It uses a full Log-Structured Merge-Tree
-(LSM) structure for high speed and large amount of data update & query capability.
-
-Flink Table Store supports the following usage:
-- **Streaming Insert**: Write changelog streams, including CDC from database and streams.
-- **Batch Insert**: Write batch data as offline warehouse, including OVERWRITE support.
-- **Batch/OLAP Query**: Read snapshot of the storage, efficient querying of real-time data.
-- **Streaming Query**: Read changes of the storage, ensure exactly-once consistency.
+Flink Table Store is a unified storage to build dynamic tables for both streaming and
+batch processing in Flink, supporting high speed data ingestion and timely data query.
+Table Store offers the following core capabilities:
+- Support storage of large datasets and allows read / write in both batch and streaming manner.
+- Support streaming queries with minimum latency down to milliseconds.
+- Support Batch/OLAP queries with minimum latency down to the second level.
+- Support incremental snapshots for stream consumption by default. So users don’t need to solve the problem of combining different stores by themselves.
Review Comment:
```suggestion
- Support incremental snapshots for stream consumption by default. So users do not need to combine different pipelines by themself.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] JingsongLi commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
JingsongLi commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898857537
##########
docs/content/docs/development/create-table.md:
##########
@@ -26,6 +26,31 @@ under the License.
# Create Table
+## Catalog
+
+Table Store uses Catalog to manage all the databases and tables. You need to create a
+Table Store catalog and use it. Table Store catalog has a root directory, configured through `warehouse`.
+
+```sql
+CREATE CATALOG my_catalog WITH (
+ 'type'='table-store',
+ 'warehouse'='hdfs://nn:8020/warehouse/path'
+);
+
+USE CATALOG my_catalog;
+```
+
+Table Store catalog supports SQL DDL commands:
+- `CREATE TABLE ... PARTITIONED BY`
+- `DROP TABLE ...`
+- `ALTER TABLE ...`
+- `SHOW DATABASES`
+- `SHOW TABLES`
+
+The path of table in catalog is `${warehouse}/${database_name}.db/${table_name}`.
Review Comment:
This is in the catalog chapter.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-table-store] LadyForest commented on a diff in pull request #159: [FLINK-28088] Adjust table store document to catalog
Posted by GitBox <gi...@apache.org>.
LadyForest commented on code in PR #159:
URL: https://github.com/apache/flink-table-store/pull/159#discussion_r898763868
##########
docs/content/docs/development/create-table.md:
##########
@@ -26,6 +26,31 @@ under the License.
# Create Table
+## Catalog
+
+Table Store uses Catalog to manage all the databases and tables. You need to create a
+Table Store catalog and use it. Table Store catalog has a root directory, configured through `warehouse`.
Review Comment:
```suggestion
Table Store uses its own Catalog to manage all the databases and tables. Users need to configure the type `table-store` and a root directory `warehouse` to use it.
```
##########
docs/content/docs/development/create-table.md:
##########
@@ -26,6 +26,31 @@ under the License.
# Create Table
+## Catalog
+
+Table Store uses Catalog to manage all the databases and tables. You need to create a
+Table Store catalog and use it. Table Store catalog has a root directory, configured through `warehouse`.
Review Comment:
```suggestion
Table Store uses its own catalog to manage all the databases and tables. Users need to configure the type `table-store` and a root directory `warehouse` to use it.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org