Tommaso Teofili
Tommaso Teofili
I did an experiment for this a while ago, the behavior for some reason is not exactly the same (expected) as the fw one. I can dig into this.
Participation confirmed 👍
closes #130
I had initially opened a [Lucene PR](https://github.com/apache/lucene/pull/13367) to add this information in `SegmentInfo`, but that same information is present in `FieldInfo` and hence I've closed it and opened this PR...
one thing we could do is start by adding information from Lucene `SegmentInfo#codec` within ES `Engine` class to expose which kinds of underlying data structures are used within each segments...
another option is to enable tracking vector formats in `AbstractKnnVectorQuery#explain` so that the `Explanation` also contains per-doc vector format. This would help in situations were mappings have been updated (e.g....
in addition to the per-field `KnnVectorFormat` information recorded on the ES side (from mappings), Lucene can provide proper per-segment, per-field `KnnVectorFormat` (read from the segments), see [PR](https://github.com/apache/lucene/pull/13367). update: this [PR](https://github.com/elastic/elasticsearch/pull/108658)...
if / when we are ok with the changes, relevant documentation bits should be added, so that we set the correct expectations (e.g. updating `index_options` ≠ reindexing)
@elasticmachine update branch