LiebingYu commented on issue #1952:
URL: https://github.com/apache/fluss/issues/1952#issuecomment-3515523771
# Mapping Info
For database mapping, we can add `lakeDatabase` to simplify user's operation.
```java
public class DatabaseDescriptor {
private final @Nullable String lakeDatabase;
}
```
For per-table mapping, we can add a new table config to avoid introducing
excessive changes by modifying `TableDescriptor`.
```java
public static final ConfigOption<String> TABLE_DATALAKE_TABLE_NAME =
key("table.datalake.table-name")
.stringType()
.noDefaultValue()
.withDescription(
"The table name of the datalake table. "
+ "If not set, will be the same as Fluss
table.");
public static final ConfigOption<String> TABLE_DATALAKE_DATABASE_NAME =
key("table.datalake.database-name")
.stringType()
.noDefaultValue()
.withDescription(
"The database name of the datalake table. "
+ "If not set, will be the same as Fluss
database.");
```
During table creation:
+ If `table.datalake.database-name` is not set, overwrite by `lakeDatabase`.
# Tiering Service
For `lakeTieringHeartbeat` RPC call, we need to add an option
`lake_table_path`. Thus tiering service can directly use this infomation to map
the fluss table to lake table.
```protobuf
message PbLakeTieringTableInfo {
required int64 table_id = 1;
required PbTablePath table_path = 2;
required int64 tiering_epoch = 3;
option PbTablePath lake_table_path = 4;
}
```
# Flink Read
`table.datalake.database-name` and `table.datalake.table-name` will be
included in `TableInfo`.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
