lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (SOLR-13014) URI Too Long with large streaming expressions in SolrJ
Date Mon, 10 Dec 2018 18:01:00 GMT

     [ https://issues.apache.org/jira/browse/SOLR-13014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jan Høydahl resolved SOLR-13014.
--------------------------------
    Resolution: Fixed

> 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: 20m
>  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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message