-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for shards in SOLR #620
Comments
This one is really interesting. Will it be up to the user to correctly create the status core with the same number of shards as the |
yes. we should set it to a reasonable default value (10?) but then it is up to the user to manage it |
Hasn't that been done in #1240? Is there more in that branch that hasn't been merged? If so, would you mind creating a PR from that branch? Thanks! |
Hi @mvolikas - sorry about the delayed response, I have just returned from holidays
yes please, that would be great |
* #620 update spout to fetch from the corresponding shard * #620 add Solr scripts * #620 fix tests to operate in cloud mode * #620 fix code format * #620 add Solr spout test * #620 add license * #620 improve the Solr related scripts * #620 add solr archetype, update readmes * #620 minor fixes * #620 do not set the 'shard' query parameter when we have a single shard * #620 fix archetype includes, improve scripts and configuration files * #620 fix java topologies * #620 add 'injection.flux' topology * #620 bring in change from #1390 * #620 update sample flux topologies and readme * #620 minor comments and readme changes
Just like it's done in ES, we could route the documents in the statusupdaterbolt based on the host / name or IP and in the spouts check that the number of instances is equal to the # of shards and filter the queries per shard accordingly.
At the moment, we can have only one instance of a spout.
The text was updated successfully, but these errors were encountered: