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 0EEC1DE8E for ; Sat, 15 Sep 2012 18:34:10 +0000 (UTC) Received: (qmail 66726 invoked by uid 500); 15 Sep 2012 18:34:08 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 66675 invoked by uid 500); 15 Sep 2012 18:34:08 -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 66667 invoked by uid 99); 15 Sep 2012 18:34:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Sep 2012 18:34:08 +0000 Date: Sun, 16 Sep 2012 05:34:08 +1100 (NCT) From: "Noble Paul (JIRA)" To: dev@lucene.apache.org Message-ID: <1593621168.84581.1347734048677.JavaMail.jiratomcat@arcas> In-Reply-To: <176709306.6153.1308125267048.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (SOLR-2592) Pluggable shard lookup mechanism for SolrCloud 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-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456462#comment-13456462 ] Noble Paul commented on SOLR-2592: ---------------------------------- Why should we have a composite id ? Why not we just configure the shard.key as a different field from the uniqueKey and pass the value of the field (shard.key.val) for add/delete? > Pluggable shard lookup mechanism for SolrCloud > ---------------------------------------------- > > Key: SOLR-2592 > URL: https://issues.apache.org/jira/browse/SOLR-2592 > Project: Solr > Issue Type: New Feature > Components: SolrCloud > Affects Versions: 4.0-ALPHA > Reporter: Noble Paul > Assignee: Mark Miller > Attachments: dbq_fix.patch, pluggable_sharding.patch, pluggable_sharding_V2.patch, SOLR-2592.patch, SOLR-2592_r1373086.patch, SOLR-2592_r1384367.patch, SOLR-2592_rev_2.patch, SOLR_2592_solr_4_0_0_BETA_ShardPartitioner.patch > > > If the data in a cloud can be partitioned on some criteria (say range, hash, attribute value etc) It will be easy to narrow down the search to a smaller subset of shards and in effect can achieve more efficient search. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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