[
https://issues.apache.org/jira/browse/SOLR-12632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059907#comment-18059907
]
Eric Pugh commented on SOLR-12632:
----------------------------------
Hi all... In SOLR-18111 I'm proposing to remove the legacy field types.
We deprecated the fields in Solr 7 eight years ago, and I think it's time to
move forward. I'm proposing to remove the Trie support in Solr 11, which
gives us time for someone to step forward and propose a better solution.
Based on the history of comments, I get the feeling that if we don't try to
move forward in some meaningful fashion, then we'll be stuck with Status Quo
for forever. There ARE some good ideas proposed, but they don't seem to be
moving forward.
One thought I had if people think that Solr 11 is too imminent for an
improvement... What if we move the Trie and Legacy fields into their own
Github repo, similar to DIH?
The current testing and code around handling both Trie and Points is super
confusing and has all sorts of complications. Our messaging in the Ref Guide
is also suggesting "don't use tries, we are getting rid of them"...
We could move Trie and legacy off to it's own repo, and migrate the test that
are specific to it. Yes, we would have to do some new interfaces in Solr to
support referencing classes that aren't in our Solr code base.
> Completely remove Trie fields
> -----------------------------
>
> Key: SOLR-12632
> URL: https://issues.apache.org/jira/browse/SOLR-12632
> Project: Solr
> Issue Type: Task
> Reporter: Steven Rowe
> Priority: Major
> Labels: numeric-tries-to-points
>
> Trie fields were deprecated in Solr 7.0. We should remove them completely
> before we release Solr 8.0.
> Unresolved points-related issues:
> [https://jira.apache.org/jira/issues/?jql=project=SOLR+AND+labels=numeric-tries-to-points+AND+resolution=unresolved]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
