[ https://issues.apache.org/jira/browse/JCR-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044758#comment-13044758 ]
Alex Parvulescu commented on JCR-2980: -------------------------------------- I removed 2.2.7 as it is better to wait a bit and make sure that this time there are no more surprises :) It will be included in 2.2.8. > 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