You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2011/06/14 13:37:47 UTC
[jira] [Commented] (SOLR-1873) Commit Solr Cloud to trunk
[ https://issues.apache.org/jira/browse/SOLR-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049132#comment-13049132 ]
Noble Paul commented on SOLR-1873:
----------------------------------
How can we make the logic for identifying the shards pluggable? if I have a per user data stored in a given shard, the search should be performed only there. Is there an issue to track this or shall I open one?
> 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: 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, log4j-over-slf4j-1.5.5.jar, 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org