Hi Keith And thank you for driving this. I'm not sure if a monthly sync just for Lance is required, however I think it will be good to run a sync to discuss this, identify what we need in that aspect. feature gaps, what we need to add, etc. >From there, we could extract a roadmap for Lance, as we have for Iceberg.
Considering it's Easter holidays, I'm not sure that date will work, though. We can create a poll on Slack for those interested to see which dates/times work. Best, Giannis On Thu, Mar 26, 2026 at 2:35 PM Keith Lee <[email protected]> wrote: > Hi everyone, > > The Lance integration has come a long way with log table tiering shipped in > 0.8 (FIP-5) and array types, nested rows, and FixedSizeList for vector > search added since. Great work by everyone who contributed to getting it to > this point. > > As the integration matures, I think it could be helpful to have a recurring > community sync to keep momentum and provide the community a good picture > (roadmap) of where Fluss/Lance is at and where we are heading. > > Where things stand (as I understand it), there are a few open areas that > could benefit from broader discussion: > > - Primary key table support [1] > - Flink SQL read path: batch queries and union reads [2][3] > - Data type coverage: Map type [4] > - Documentation: Lance quickstart with vector search example [5] > - Native vector search > > What a sync could look like > - Review current state and in-flight work > - Align on priorities and surface blockers early > - Coordinate across the different workstreams (write path, read path, type > support, docs) > - Agree on cadence going forward > > I'm happy to drive the first sync (suggesting 10th April 8AM UTC), but > would also love to rotate facilitation if others are interested in taking > turns. If this sounds worthwhile or if you have suggestions on > format/cadence please reply to this thread. > > Best regards > Keith Lee > > [1] https://github.com/apache/fluss/issues/1160 > [2] https://github.com/apache/fluss/issues/2715 > [3] https://github.com/apache/fluss/issues/2751 > [4] https://github.com/apache/fluss/issues/2403 > [5] https://github.com/apache/fluss/issues/2716 >
