[
https://issues.apache.org/jira/browse/SOLR-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922564#action_12922564
]
Grant Ingersoll commented on SOLR-1873:
---------------------------------------
I don't understand why this puts all the check shards logic into the
QueryComponent. We have many paths that don't go through the QueryComponent
that could use this. Seems like we should either make a something like a
ShardsComponent, or abstract it up to the RequestHandlerBase, so that everyone
can take advantage of it if they want to.
> Commit Solr Cloud to trunk
> --------------------------
>
> Key: SOLR-1873
> URL: https://issues.apache.org/jira/browse/SOLR-1873
> Project: Solr
> Issue Type: New Feature
> Affects Versions: 1.4
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 4.0
>
> Attachments: log4j-over-slf4j-1.5.5.jar, SOLR-1873.patch,
> SOLR-1873.patch, SOLR-1873.patch, SOLR-1873.patch, SOLR-1873.patch,
> SOLR-1873.patch, SOLR-1873.patch, SOLR-1873.patch, SOLR-1873.patch,
> SOLR-1873.patch, SOLR-1873.patch, SOLR-1873.patch, SOLR-1873.patch,
> SOLR-1873.patch, TEST-org.apache.solr.cloud.ZkSolrClientTest.txt,
> zookeeper-3.2.2.jar, zookeeper-3.3.1.jar
>
>
> See http://wiki.apache.org/solr/SolrCloud
> This is a real hassle - I didn't merge up to trunk before all the svn
> scrambling, so integrating cloud is now a bit difficult. I'm running through
> and just preparing a commit by hand though (applying changes/handling
> conflicts a file at a time).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
