ColdL commented on PR #7240: URL: https://github.com/apache/paimon/pull/7240#issuecomment-3988887489
> > vector-field > > vector-field is for Flink & Spark engines without Vector Type. So I think it should be retained. @JingsongLi Got it! I'll make some adjustments following this approach. Specifically: 1. The `vectorStoreFieldNames` in DataEvolution mode writer can probably be removed, we no longer need to split based on specific column names; using `vectorStoreFileFormat` along with data types should be sufficient. 2. `SchemaValidation` and some other related locations should see corresponding simplifications. 3. The `vector-field` will be consumed by the engines. I will provide a new version shortly. Additionally, since `vector-field` only needs to be used by the engines, does it still need to be defined in CoreOptions? Would you recommend placing it somewhere else instead. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
