[
https://issues.apache.org/jira/browse/SOLR-9077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15626072#comment-15626072
]
Kevin Risden commented on SOLR-9077:
------------------------------------
Currently the matching logic is as follows:
- collection name case sensitive
- collection name case insensitive
- alias name case sensitive
This means that current behavior for TopicStream, FeatureSelectionStream, and
TextLogitStream would be unaffected and would just add the alias support. Are
there any known downsides to using aliases other than maybe complicating
things? It looks to me that slices are what is used for the checkpoints so that
would just work with aliases getting more slices.
I'll double check the tests for TopicStream, FeatureSelectionStream, and
TextLogitStream to make sure those are being tested with aliases.
One item that I might adjust with the tests is to make sure aliases are
pointing to multiple collections. Currently the alias only points to a single
collection.
> 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]
