You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Simon Willnauer (Jira)" <ji...@apache.org> on 2020/09/15 08:21:00 UTC
[jira] [Resolved] (LUCENE-9516) Remove DocConsumer and
IndexingChain from Lucene
[ https://issues.apache.org/jira/browse/LUCENE-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Willnauer resolved LUCENE-9516.
-------------------------------------
Fix Version/s: master (9.0)
Resolution: Fixed
> Remove DocConsumer and IndexingChain from Lucene
> ------------------------------------------------
>
> Key: LUCENE-9516
> URL: https://issues.apache.org/jira/browse/LUCENE-9516
> Project: Lucene - Core
> Issue Type: Wish
> Reporter: Simon Willnauer
> Priority: Major
> Fix For: master (9.0)
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Disclaimer: This is a breaking change!
> We allow today to replace the entire indexing chain which is a fundamental part of our software. I personally don't know if there are any users of this API. but given the complexity I personally don't think we should further support this. If you are willing to implement this entire thing yourself I really wonder if you are better off building lucene from the source. An option like this on IWC might make users look into it while I am convinced they shouldn't. It's too complex and nothing is made for reuse down there. I wonder what others think but from my perspective it's time to remove it in 9.0
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org