[SOLR-13459] Streaming Expressions experience a hard coded timeout

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: streaming expressions
• Assignee: Unassigned
• Reporter: Gus Heck
• Created: 09/May/19 19:25
• Updated: 24/Jul/20 13:19

Description

SolrClientBuilder has the capability to configure a timeout, but the usage in SolrStream accepts the hard-coded default:

  /**
  * 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);
    }
 

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.

Issue Links

• relates to: SOLR-13457 Managing Timeout values in Solr
• relates to: SOLR-14672 Make timeouts configurable for the Streaming Expression SolrClientCache