[ 
https://issues.apache.org/jira/browse/SOLR-9077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623346#comment-15623346
 ] 

Kevin Risden commented on SOLR-9077:
------------------------------------

Yea most of the changes are actually test variable changes (COLLECTION -> 
COLLECTIONORALIAS). Wasn't sure how else to make that change. The important 
section is confined to CloudSolrStream.getSlices(). The changes I'm concerned 
with are the FeaturesSectionStream, ParallelStream, TextLogitStream, and 
TopicStream. These all had getActiveSlices. Not sure the slices HAD to be for a 
specific collection. Now they should work with all slices from all collections 
in an alias.

Any easier way to view is here: 
https://github.com/apache/lucene-solr/commit/1e9a285d53ee1a57a0229c4eaf6666deb8f13c35

> Streaming expressions should support collection alias
> -----------------------------------------------------
>
>                 Key: SOLR-9077
>                 URL: https://issues.apache.org/jira/browse/SOLR-9077
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 5.5.1
>            Reporter: Suds
>            Priority: Minor
>         Attachments: SOLR-9077.patch, SOLR-9077.patch, SOLR-9077.patch, 
> SOLR-9077.patch
>
>
> Streaming expression in solr does not support collection alias
> when I tried to access collection alias I get null pointer exception 
> issue seems to be related to following code , clusterState.getActiveSlices 
> returns null 
>  Collection<Slice> slices = clusterState.getActiveSlices(this.collection);
>  for(Slice slice : slices) {
> }
> fix seems to fairly simple , clusterState.getActiveSlices can be made aware 
> of collection alias. I am not sure what will happen when we have large alias 
> which has hundred of slices.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to