[ 
https://issues.apache.org/jira/browse/SOLR-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035499#comment-17035499
 ] 

Houston Putman commented on SOLR-14013:
---------------------------------------

[~noble.paul], at the very least I think we should backport this to 7_7. If we 
want to leave the latest release of 7 in a state with a significant 
regression/bug in it, then we are basically asking people to either:
 * Know that 7.6 is the last stable release of solr for people wanting to use 
multiValued fields in a sharded collection
 * Upgrade to Solr 8.4

In my opinion, neither of those are good options. Because users are always 
going to go with the most up to date version of Solr that works for their 
index, and upgrading to new major versions is a very tough process for a lot of 
people.

This isn't a bug that existed throughout the entirety of Solr 7, it was 
introduced in the last minor release. A lot of people are very comfortable with 
Solr 7, and trust it. People also trust that the last minor/patch version of 
something is going to be the most stable version. We should make sure that the 
latest release of our second to last major version (7) is stable and maintains 
that trust that users have in it and Solr in general.

It is very little work to backport this, and also probably not a whole lot of 
work to do another patch or minor release (7.8 or 7.7.3). And with that work we 
will be providing a significantly better user experience for our community. 

> javabin performance regressions
> -------------------------------
>
>                 Key: SOLR-14013
>                 URL: https://issues.apache.org/jira/browse/SOLR-14013
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 7.7
>            Reporter: Yonik Seeley
>            Assignee: Yonik Seeley
>            Priority: Blocker
>             Fix For: 8.4
>
>         Attachments: SOLR-14013.patch, SOLR-14013.patch, TestQuerySpeed.java, 
> test.json
>
>
> As noted by [~rrockenbaugh] in SOLR-13963, javabin also recently became 
> orders of magnitude slower in certain cases since v7.7.  The cases identified 
> so far include large numbers of values in a field.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to