You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2011/05/27 16:52:47 UTC

[jira] [Resolved] (JCR-2980) Nodes that have properties marked for async extraction should be available for querying

     [ https://issues.apache.org/jira/browse/JCR-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Parvulescu resolved JCR-2980.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3.0
                   2.2.7
         Assignee: Alex Parvulescu

fixed on trunk in rev 1128325
fixed on branch 2.2 in rev 1128329

> 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.2.7, 2.3.0
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>             Fix For: 2.2.7, 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