[
https://issues.apache.org/jira/browse/LUCENE-8267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448771#comment-16448771
]
Dawid Weiss commented on LUCENE-8267:
-------------------------------------
bq. I get the maintenance aspect but we need community input on such decisions
to ascertain real-world use.
I think filing a JIRA issue is kind of soliciting feedback, don't you think? I
agree with Simon and Robert that there are classes that, while useful, are not
at the forefront of what a broad "Lucene API" is... We should have the liberty
to adjust or remove such things. I scanned the code of both Lucene and Solr and
there were no references (other than in tests) to those classes, so it's not
just "Lucene land".
Also, given the size and diversity of the Lucene/Solr user community I'm fairly
confident there will always be somebody who finds something very useful, no
matter what you'd like to change or remove. Hell, I use a lot of internal
Lucene infrastructure in my own projects and sometimes I miss things that go
away myself... (and frequently I just grab the latest source of something and
copy it over to maintain in my own source tree, that's part of the beauty of
open source).
> Remove memory codecs from the codebase
> --------------------------------------
>
> Key: LUCENE-8267
> URL: https://issues.apache.org/jira/browse/LUCENE-8267
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Dawid Weiss
> Priority: Major
>
> Memory codecs (MemoryPostings*, MemoryDocValues*) are part of random
> selection of codecs for tests and cause occasional OOMs when a test with huge
> data is selected. We don't use those memory codecs anywhere outside of tests,
> it has been suggested to just remove them to avoid maintenance costs and OOMs
> in tests. [1]
> [1] https://apache.markmail.org/thread/mj53os2ekyldsoy3
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
