You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2015/12/27 19:01:49 UTC
[jira] [Created] (SOLR-8467) CloudSolrStream should take a
SolrParams object rather than a Map to allow more complex
Solr queries to be specified
Erick Erickson created SOLR-8467:
------------------------------------
Summary: CloudSolrStream should take a SolrParams object rather than a Map<String, String> to allow more complex Solr queries to be specified
Key: SOLR-8467
URL: https://issues.apache.org/jira/browse/SOLR-8467
Project: Solr
Issue Type: Improvement
Reporter: Erick Erickson
Assignee: Erick Erickson
Currently, it's impossible to, say, specify multiple "fq" clauses when using Streaming Aggregation due to the fact that the c'tors take a Map of params.
Opening to discuss whether we should
1> deprecate the current c'tor
and/or
2> add a c'tor that takes a SolrParams object instead.
and/or
3> ???
I don't see a clean way to go from a Map<String, String> to a (Modifiable)SolrParams, so existing code would need a significant change. I hacked together a PoC, just to see if I could make CloudSolrStream take a ModifiableSolrParams object instead and it passes tests, but it's so bad that I'm not going to even post it. There's _got_ to be a better way to do this, but at least it's possible....
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org