romseygeek opened a new issue, #16820:
URL: https://github.com/apache/lucene/issues/16820

   ### Description
   
   As part of doing a new major version we should also consider deprecating 
parts of the codebase that are unmaintained or block further development, to be 
removed in the unstable branch once we have forked for version 11.
   
   We had a discussion at Community over Code 2026 and came up with the 
following suggestions.  Let's discuss in this issue.
   
   ### Span Queries
   
   SpanQueries have some basically unfixable correctness bugs and in any case 
have been superseded by IntervalQueries.  We should deprecate them, and produce 
instructions on how to migrate to Intervals.
   
   ### ValueSource
   
   ValueSource provides per-document values via a random access API, which does 
not fit with the rest of lucene's iterator-based APIs and can be very trappy 
performance-wise.  We already have DoubleDocValues and LongDocValues to handle 
numeric values via iterators.  Let's deprecate ValueSource and see if we need 
to add any other iterator-based values to replace it.
   
   ### Highlighters
   
   We have four highlighters, and it is not at all obvious which one to pick 
for new users.  Let's deprecate the classic and fast-vector highlighters and 
push users towards the unified highlighter, or the matches highlighter 
components if they need something more bespoke.
   
   ### Query parsers
   
   We have seven (!) query parsers, most of which have not seen any updates for 
many years.  People who need complex parsers beyond what classic and simple 
offer are going to be rolling their own, or extending QueryParserBase from 
classic.  The XML query parser is mainly a source of security issues.  Let's 
deprecate xml, ext, complexPhrase, surround and flexible.


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