[
https://issues.apache.org/jira/browse/SOLR-13014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704753#comment-16704753
]
Jan Høydahl commented on SOLR-13014:
------------------------------------
We're running fine in production with the current patch, so will aim at
committing these GET -> POST changes next week.
> URI Too Long with large streaming expressions in SolrJ
> ------------------------------------------------------
>
> Key: SOLR-13014
> URL: https://issues.apache.org/jira/browse/SOLR-13014
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrJ, streaming expressions
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Fix For: master (8.0), 7.7
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For very large expressions (e.g. with a complex search string) we'll hit the
> max HTTP GET limit since SolrJ does not enforce POST for all expressions.
> This goes at least for {{FacetStream}}, {{StatsStream}} and
> {{TimeSeriesStream}}, and I'll link a Pull Request fixing these three.
> Here is an example of a stack trace when using TimeSeriesStream with a very
> large expression: [https://gist.github.com/ea626cf1ec579daaf253aeb805d1532c]
> The fix is simply to use {{new QueryRequest(parameters,
> SolrRequest.METHOD.POST);}} to explicitly force POST.
> See also solr-user thread
> [http://lucene.472066.n3.nabble.com/Streaming-Expressions-GET-vs-POST-td4415044.html]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
