jpountz commented on pull request #11: URL: https://github.com/apache/lucene/pull/11#issuecomment-813948862
> I'm also curious if we plan to enforce value consistency in a follow-up? It would be great if we could enforce value consistency too. It feels more challenging because `IndexingChain`, where these checks are performed, only knows about the encoded representation of the data. For instance if you index a `LongPoint`, `IndexingChain` doesn't see a `long` but a `byte[8]`. So we'd need to hardcode expectations in `IndexingChain` about how the `byte[]` encoding of terms/points is expected to match the `long` encoding of numeric doc values for instance, which I don't feel great about. I believe that a better way of doing it would be to introduce a notion of schema in Lucene, so that you would be passing values to Lucene directly, and Lucene would take care of putting the right (encoded) data into the right data structures, but this would also be a much larger change. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
