[infinispan-issues] [JBoss JIRA] (ISPN-2206) Query returns nulls if cache entries were removed and transaction is still not commited

[Galder Zamarreño (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreño updated ISPN-2206:
-----------------------------------

       Fix Version/s: 5.2.0.ALPHA3
                      5.2.0.FINAL
    Git Pull Request: https://github.com/infinispan/infinispan/pull/1245  (was: https://github.com/infinispan/infinispan/pull/1245)

    
> Query returns nulls if cache entries were removed and transaction is still not commited
> ---------------------------------------------------------------------------------------
>
>                 Key: ISPN-2206
>                 URL: https://issues.jboss.org/browse/ISPN-2206
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Querying
>    Affects Versions: 5.2.0.ALPHA1
>            Reporter: Marko Lukša
>            Assignee: Sanne Grinovero
>             Fix For: 5.2.0.ALPHA3, 5.2.0.FINAL
>
>
> When using indexLocalOnly=true, the Lucene index is updated when the transaction is commited. 
> After removing an entry from the cache (and before commiting the transaction), queries will still match the entry, but since the entry is no longer in the cache, the list returned by the query will contain a null value.
> This forces clients to always check whether elements of the collection returned by queries are null. 
> IMO, Ispan-query should handle this and simply skip the entries that were matched in the index, but are no longer in the cache. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira