Return-Path: Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: (qmail 65349 invoked from network); 19 Oct 2010 14:15:53 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 19 Oct 2010 14:15:53 -0000 Received: (qmail 35433 invoked by uid 500); 19 Oct 2010 14:15:52 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 35061 invoked by uid 500); 19 Oct 2010 14:15:50 -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 35054 invoked by uid 99); 19 Oct 2010 14:15:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Oct 2010 14:15:49 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Oct 2010 14:15:49 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o9JEFSGJ000971 for ; Tue, 19 Oct 2010 14:15:28 GMT Message-ID: <9602103.46431287497728114.JavaMail.jira@thor> Date: Tue, 19 Oct 2010 10:15:28 -0400 (EDT) From: "Grant Ingersoll (JIRA)" To: dev@lucene.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=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-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org