[
https://issues.apache.org/jira/browse/WAVE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090720#comment-14090720
]
Yuri Zelikov commented on WAVE-371:
-----------------------------------
[~pablojan] I think you are right, but I also think this was intended - as for
now the indexer doesn't keep meta info about wave, the wave still has to be
loaded and the read blip count extracted from the supplement.
I encountered this problem when working on Frank's patch for Solr indexer. I
think this issue happens only when there are more than 1 participant in wave.
My guess is that the issue caused when read count is displayed for wrong user,
i.e. somehow UserDataWavelet of one user added to the wave view of another user
and then used to create the WaveSupplement.
> 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 was sent by Atlassian JIRA
(v6.2#6252)
