[
https://issues.apache.org/jira/browse/SOLR-13459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-13459.
---------------------------------
Resolution: Fixed
Resolved by SOLR-14672
> Streaming Expressions experience a hard coded timeout
> -----------------------------------------------------
>
> Key: SOLR-13459
> URL: https://issues.apache.org/jira/browse/SOLR-13459
> Project: Solr
> Issue Type: Sub-task
> Components: streaming expressions
> Reporter: Gus Heck
> Priority: Major
>
> SolrClientBuilder has the capability to configure a timeout, but the usage in
> SolrStream accepts the hard-coded default:
> {code:java}
> /**
> * Opens the stream to a single Solr instance.
> **/
> public void open() throws IOException {
> if(cache == null) {
> client = new HttpSolrClient.Builder(baseUrl).build();
> } else {
> client = cache.getHttpSolrClient(baseUrl);
> }
> {code}
> While it might also be possible to specify the timeout in the expression,
> that also sounds like something that bloats the high level expression with
> low level concerns, so this ticket proposes to have SolrStream set a timeout
> on the builder which it will get from the StreamContext. When instantiated by
> the stream handler, the stream context in turn will set this based on a
> default timeout for inter-node communication defined in solr.xml.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
