Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AC0746296 for ; Tue, 14 Jun 2011 11:38:10 +0000 (UTC) Received: (qmail 61154 invoked by uid 500); 14 Jun 2011 11:38:09 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 61078 invoked by uid 500); 14 Jun 2011 11:38:09 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 61071 invoked by uid 99); 14 Jun 2011 11:38:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jun 2011 11:38:09 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jun 2011 11:38:07 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 9774041540F for ; Tue, 14 Jun 2011 11:37:47 +0000 (UTC) Date: Tue, 14 Jun 2011 11:37:47 +0000 (UTC) From: "Noble Paul (JIRA)" To: dev@lucene.apache.org Message-ID: <1427492918.2405.1308051467591.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (SOLR-1873) Commit Solr Cloud to trunk MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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