New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modernize LineFileDocs. #12929
Modernize LineFileDocs. #12929
Conversation
This replaces `StringField`/`SortedDocValuesField` with `KeywordField` and `IntPoint`/`NumericDocValuesField` with `IntField`.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @jpountz. I wonder if luceneutil's hard fork of this source file is also rusty in the same way?
@mikemccand luceneutil is better at remaining up-to-date with Lucene than Lucene itself :) mikemccand/luceneutil@76ff349 mikemccand/luceneutil@bb071f7 |
Ha! Wild :) Maybe we should unfork? Why does luceneutil need a hard fork here ... couldn't it just depend on Lucene's |
From a quick check, the luceneutil version has much more complexity around indexing facets, doc values, etc. It's not entirely obvious to me if sharing the code would help or hurt. |
This replaces `StringField`/`SortedDocValuesField` with `KeywordField` and `IntPoint`/`NumericDocValuesField` with `IntField`.
I was working on adding some new BWC tests for the parent field and it seems BWC index creation and testing is relying on some things that changed here. Just flagging this for now while I work on a fix. |
The changes on apache#12929 broke the generation code for BWC indices since they are expecting vertain fields created by LineDocFile. Yet, this change adds some sanity checks that run with unittest to ensure the bwc generatin is at least readable with the current version. Relates to apache#12929
This replaces
StringField
/SortedDocValuesField
withKeywordField
andIntPoint
/NumericDocValuesField
withIntField
.