Return-Path: Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: (qmail 4272 invoked from network); 21 Mar 2011 15:14:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 Mar 2011 15:14:44 -0000 Received: (qmail 94341 invoked by uid 500); 21 Mar 2011 15:14:43 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 94260 invoked by uid 500); 21 Mar 2011 15:14:43 -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 94253 invoked by uid 99); 21 Mar 2011 15:14:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Mar 2011 15:14:43 +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; Mon, 21 Mar 2011 15:14:42 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 31405402DED for ; Mon, 21 Mar 2011 15:14:06 +0000 (UTC) Date: Mon, 21 Mar 2011 15:14:06 +0000 (UTC) From: "Mark Harwood (JIRA)" To: dev@lucene.apache.org Message-ID: <490830770.766.1300720446198.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (LUCENE-2454) Nested Document query support 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/LUCENE-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009163#comment-13009163 ] Mark Harwood commented on LUCENE-2454: -------------------------------------- Lucene does not dictate a schema and so using this approach to index design/querying is not a problem with base Lucene. Solr, however does introduce a schema and much more that assumes a "flat" model. In the opening chapters of the "Solr 1.4 Enterprise Search Server" book the authors take the time to discuss the modelling limitations of this flat model and acknowledge this as an issue. The impact of adopting "nested" documents in Solr at this stage would be very large. There may be ways you can overcome some of your issues without requiring nested documents (using phrase/span queries or combining tokens from multiple fields in Solr) but in my experience these are often poor alternatives if richer structures are important. Cheers Mark > Nested Document query support > ----------------------------- > > Key: LUCENE-2454 > URL: https://issues.apache.org/jira/browse/LUCENE-2454 > Project: Lucene - Java > Issue Type: New Feature > Components: Search > Affects Versions: 3.0.2 > Reporter: Mark Harwood > Assignee: Mark Harwood > Priority: Minor > Attachments: LuceneNestedDocumentSupport.zip > > > A facility for querying nested documents in a Lucene index as outlined in http://www.slideshare.net/MarkHarwood/proposal-for-nested-document-support-in-lucene -- 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