Hi, Rex
> , won't that therefore change the key used to reference the state in RockDB
> and in a checkpoint for the associated table?
> How might this effect state storage and checkpointing?
> Will the pk that was renamed remain a key for state or is some other
> mechanism used to form a key?
Yes, I think Flink still can infer the primary key from renamed pk column, the
state and checkpoint does not effect by the rename action.
BTW, Flink uses primary key in some optimizations, but Flink does not check
the primary key integrity because Flink does not own data like DB.
So user should ensure the unique key integrity when define a primary key, but
It’s unusual the data from Kafka is unique as I know,
this may lead unexpected result.
Best,
Leonard
>
> tableEnv.executeSql("""
> CREATE TABLE topic_users (
> id BIGINT,
> deleted_at BIGINT,
> PRIMARY KEY (id) NOT ENFORCED
> ) WITH (
> ...
> )
> """)
> val usersNotDeletedTable =
> tableEnv
> .from("topic_users")
> .select($"*")
> // Will PK automatically change to "users_user_id"?
> .renameColumns($"id".as("users_user_id"))
> .filter($"deleted_at".isNull)
>
> val membershipsNotDeletedTable =
> membershipsTable // This table also has "id" PK
> .join(
> usersNotDeletedTable,
> $"user_id" === $"users_user_id"
> )
> .dropColumns($"users_user_id")
>
> Thanks!
>
> --
> Rex Fenley | Software Engineer - Mobile and Backend
>
> Remind.com <https://www.remind.com/> | BLOG <http://blog.remind.com/> |
> FOLLOW US <https://twitter.com/remindhq> | LIKE US
> <https://www.facebook.com/remindhq>
