rmuir commented on PR #15584:
URL: https://github.com/apache/lucene/pull/15584#issuecomment-3762542040

   high-level though, the idea is a good one to indicate custom term 
frequencies in the FieldInfo.
   
   I wouldn't try to do it as an "attribute" though, I think 
`IndexOptions.DOCS_AND_CUSTOM_FREQS` or something would make more sense. By 
being in that enum, it prevents a bunch of nonsensical possibilities (e.g. 
custom freqs but no freqs, custom freqs with positions, etc) And prevents 
incompatible segments from being merged (with the custom freqs on and off)
   
   I feel like after that, remaining concerns are in scoring system and 
pruning. Needs lots of testing to make sure they behave reasonably


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to