[
https://issues.apache.org/jira/browse/SOLR-13999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992886#comment-16992886
]
Jason Gerlowski edited comment on SOLR-13999 at 12/10/19 9:31 PM:
------------------------------------------------------------------
The docs look good. I'm mostly just doing a little digging into any potential
limitations to using zkHost before I merge. From what I can tell the code uses
zkHost to create a SolrClient, and then that client is used for both the data
and "checkpoint" collections. So both of those collections have to be on the
same Solr cluster currently. Have you tested this out at all?
EDIT: That is how it works, I talked to the Joel about it briefly and tested it
out locally.
was (Author: gerlowskija):
The docs look good. I'm mostly just doing a little digging into any potential
limitations to using zkHost before I merge. From what I can tell the code uses
zkHost to create a SolrClient, and then that client is used for both the data
and "checkpoint" collections. So both of those collections have to be on the
same Solr cluster currently. Have you tested this out at all?
> Ref Guide is missing the ZKHost parameter for TopicStream
> ---------------------------------------------------------
>
> Key: SOLR-13999
> URL: https://issues.apache.org/jira/browse/SOLR-13999
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation, streaming expressions
> Affects Versions: 8.3
> Reporter: David Eric Pugh
> Assignee: Jason Gerlowski
> Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> During a discussion about if you can use Streaming expressions across
> seperate Solr clusters, noticed that the `search` expression supports passing
> in a ZK Host, but `topic` doesn't. However, investigating the code, you can
> pass in your own zk host to register a tpic on another Solr cluster. This is
> to fix the docs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
