From dev-return-31511-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org Wed Jun 1 15:35:29 2011 Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-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 756C36D87 for ; Wed, 1 Jun 2011 15:35:29 +0000 (UTC) Received: (qmail 61822 invoked by uid 500); 1 Jun 2011 15:35:28 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 61744 invoked by uid 500); 1 Jun 2011 15:35:28 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 61733 invoked by uid 99); 1 Jun 2011 15:35:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jun 2011 15:35:28 +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; Wed, 01 Jun 2011 15:35:27 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 7D04BEF7D7 for ; Wed, 1 Jun 2011 15:34:47 +0000 (UTC) Date: Wed, 1 Jun 2011 15:34:47 +0000 (UTC) From: "Jukka Zitting (JIRA)" To: dev@jackrabbit.apache.org Message-ID: <1117524415.59977.1306942487508.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <997904360.48795.1306506887457.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (JCR-2980) Nodes that have properties marked for async extraction should be available for querying 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/JCR-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042236#comment-13042236 ] Jukka Zitting commented on JCR-2980: ------------------------------------ Yep, I spent most of yesterday trying to understand the problem here and in the end had to just revert the change for now. We only upgraded to Lucene 3.0 in the trunk after 2.2 had already been branched (see JCR-2415), which is probably related to why the fix doesn't work the same in the 2.2 branch as it does in trunk. However, I'm still at loss at why this seemingly innocent change is causing trouble for 2.2. > Nodes that have properties marked for async extraction should be available for querying > --------------------------------------------------------------------------------------- > > Key: JCR-2980 > URL: https://issues.apache.org/jira/browse/JCR-2980 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: indexing > Affects Versions: 2.3.0 > Reporter: Alex Parvulescu > Assignee: Alex Parvulescu > Fix For: 2.3.0 > > > The problems only appears when dealing with nodes that have async extractors. In this case we return a lightweight copy of the node (without the property that will be processed in the background). > The copy algorithm ignores certain field types (that have been probably introduced during the Lucene 3 upgrade, not sure) such as SingletonTokenStream(s). > So the lightweight copy does not include all the existing properties, therefore the node will not appear in queries during the extraction time. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira