Hello, As discussed on community sync yesterday on analysing where we are at the moment in terms of Lance format support. Here are my findings as part of working on Lance QuickStart documentation [1]. Lance lake tiering works in general, however there are some gaps that to be addressed to bring Lance format support in parity with Paimon / Iceberg.
- (Merged) Support for Arrow FixedSizeList to enable pylance native vector search [2] - (In progress) Support Flink SQL Union Read query against Lance table [3] - (Open) Support Flink SQL batch query against Lance table [4] - (Blocked) Primary Key table support - I believe this is still blocking on Lance format support for delete API [5] Finally there is also a gap in the ability of performing vector search on hot data / via union read. After discussion with Mehul, native vector indexing on hot data in Fluss would be a separate, bigger effort that we can evolve towards if there's demand for it. Appreciate feedback here from Cheng, Forward and anyone else with familiarity around this area as I have only started dipping my toes into Lance. *Additionally, if anyone wants to help contributing in this area, please reach out. * Best regards Keith Lee Reference [1] https://github.com/apache/fluss/pull/2716 [2] https://github.com/apache/fluss/issues/2706 [3] https://github.com/apache/fluss/issues/2715 [4] https://github.com/apache/fluss/issues/2751 [5] https://github.com/lance-format/lance/issues/3961
