jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-2980) Nodes that have properties marked for async extraction should be available for querying
Date Wed, 01 Jun 2011 17:17:47 GMT

    [ https://issues.apache.org/jira/browse/JCR-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042299#comment-13042299
] 

Jukka Zitting commented on JCR-2980:
------------------------------------

Actually I just encountered this problem also on Jackrabbit trunk:

testInitialIndex(org.apache.jackrabbit.core.query.lucene.IndexingQueueTest)  Time elapsed:
0.626 sec  <<< FAILURE!
junit.framework.AssertionFailedError: expected:<110> but was:<107>
        at junit.framework.Assert.fail(Assert.java:47)
        at junit.framework.Assert.failNotEquals(Assert.java:282)
        at junit.framework.Assert.assertEquals(Assert.java:64)
        at junit.framework.Assert.assertEquals(Assert.java:136)
        at junit.framework.Assert.assertEquals(Assert.java:142)
        at org.apache.jackrabbit.core.query.lucene.IndexingQueueTest.testInitialIndex(IndexingQueueTest.java:127)


> 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

Mime
View raw message