[Flink] Flink catalog fails on duplicate index columns

[platinumhamburg]

Search before asking

• I searched in the issues and found nothing similar.

Motivation

When multiple Fluss indexes use the same ordered column list, the Flink connector adds all of them to the Flink schema. Flink then rejects the table with:

Invalid index. There is a duplicated index composed of the same columns: [...]

Solution

Update the Flink 2.2 SchemaAdapter to keep only the first index for each ordered column list. Column order remains significant, so [a, b] and [b, a] are different indexes.

Anything else?

No response

Willingness to contribute

• I'm willing to submit a PR!