[
https://issues.apache.org/jira/browse/SOLR-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991041#comment-16991041
]
Yonik Seeley commented on SOLR-14013:
-------------------------------------
Please don't commit that huge JSON file... a doc matching that can be created
with a few lines of java in the test.
I'm not sure the test belongs as a unit test anyway as it's more of a
performance benchmark, but I don't care much either way as long as it's quick
to run.
In general, what I think should be done is:
- the auto-convert changes should be removed (in SolrDocument, SolrInputField,
MaskCharSeqSolrDocument)
- if there are parts of the code base that can't handle CharSequence, then
disable reading Strings as CharSequence and look at if those other pieces of
code can be fixed to handle CharSequence.
> javabin performance regressions
> -------------------------------
>
> Key: SOLR-14013
> URL: https://issues.apache.org/jira/browse/SOLR-14013
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.7
> Reporter: Yonik Seeley
> Assignee: Yonik Seeley
> Priority: Major
> Attachments: 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: [email protected]
For additional commands, e-mail: [email protected]
