Hi Ashish,
Table API has many restrictions. Even if the source schema has been changed
in a compatible manner from the database's perspective, the added column
should not be used in the downstream operators, e.g. join. In case schema
evolution is required in your business, you might want to consid
Hi, Ashish
As Timo said, the community currently doesn't have plan to support schema
evolution in Table API,
Best,
Ron
Timo Walther 于2023年8月15日周二 23:29写道：
> Hi Ashish,
>
> sorry for the late reply. There are currently no concrete plans to
> support schema evolution in Table API. Until recently
Hi Ashish,
sorry for the late reply. There are currently no concrete plans to
support schema evolution in Table API. Until recently, Flink version
evolution was the biggest topic. In the near future we can rediscuss
query and state evolution in more detail.
Personally, I think we will need e
Bumping the thread.
On Fri, Aug 4, 2023 at 12:51 PM Ashish Khatkar wrote:
> Hi all,
>
> We are using flink-1.17.0 table API and RocksDB as backend to provide a
> service to our users to run sql queries. The tables are created using the
> avro schema and when the schema is changed in a compatible
Hi all,
We are using flink-1.17.0 table API and RocksDB as backend to provide a
service to our users to run sql queries. The tables are created using the
avro schema and when the schema is changed in a compatible manner i.e
adding a field with default, we are unable to recover the job from the
sav
