[
https://issues.apache.org/jira/browse/WAVE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458152#comment-13458152
]
Vicente J. Ruiz Jurado commented on WAVE-371:
---------------------------------------------
I did that two days ago, and again we have the same annoying problem. Non tech
people are not understanding the unread status because of the bug.
Thanks for the tip anyway.
> Search panel unread count are not updated correctly with lucene indexes
> -----------------------------------------------------------------------
>
> Key: WAVE-371
> URL: https://issues.apache.org/jira/browse/WAVE-371
> Project: Wave
> Issue Type: Bug
> Components: Server
> Reporter: Vicente J. Ruiz Jurado
> Priority: Minor
>
> Using lucene indexing sometimes we see a wave that have unread blips in the
> SearchPanel. Clicking in the digest opens the Wave, but this Wave in fact
> doesn't have any unread blip, so the digest show immediately the correct
> status (all read).
> In the next search, the digest of this wave shows again that have unread
> blips (incorrect).
> This seems that works correctly using in memory indexing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira