thswlsqls opened a new issue, #9968: URL: https://github.com/apache/paimon/issues/9968
**Search before asking** - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. **Paimon version** master @ 1d368b4a5 **Compute Engine** Engine-agnostic (core read path); surfaces in Spark and Flink queries **Minimal reproduce step** 1. Create a table with `embedding ARRAY<FLOAT>` as in `paimon-eslib/README.md` (no es-index table properties). 2. Build the index as the README shows: `CALL sys.create_global_index(..., index_type => 'es-index', options => 'global-index.es-index.fields.embedding.dimension=768,...')`. 3. Run `vector_search`, `full_text_search`, or a `WHERE` on a companion column. Every query fails with `IllegalArgumentException: Vector field 'embedding' requires a positive dimension; ARRAY<FLOAT> has no fixed dimension in its data type.` Cause: `ESIndexGlobalIndexer` parses `ESIndexOptions` in its constructor (`ESIndexGlobalIndexer.java:51`), but the read paths (`AbstractDataEvolutionVectorRead`, `DataEvolutionFullTextRead`, `DataEvolutionGlobalIndexScanner`) create the indexer from the table options only, and the procedure `options` are never persisted. `ESIndexGlobalIndexReader` needs those options only for legacy offset-only metadata; v2 metadata persists the field configuration. **What doesn't meet your expectations?** An es-index whose metadata persists the field configuration should be readable regardless of the current table options, like the `paimon-vector` indexes. Build-time validation belongs to the writer path. **Anything else?** N/A **Are you willing to submit a PR?** - [x] I'm willing to submit a PR! -- 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]
