jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tommaso Teofili (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4066) Suggestion dictionary don't update after suggestUpdateFrequencyMinutes unless something else causes index update
Date Mon, 29 Feb 2016 13:45:18 GMT

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

Tommaso Teofili commented on OAK-4066:
--------------------------------------

fine with me. Given there's always a bit of Oak commits (even not Lucene index related) happening
anyway in real life scenarios, that should be enough to avoid the problem with suggest index
not being updated for long times.

> Suggestion dictionary don't update after suggestUpdateFrequencyMinutes unless something
else causes index update
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: OAK-4066
>                 URL: https://issues.apache.org/jira/browse/OAK-4066
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: lucene
>    Affects Versions: 1.3.16
>            Reporter: Vikas Saurabh
>            Assignee: Vikas Saurabh
>            Priority: Blocker
>             Fix For: 1.3.17
>
>         Attachments: OAK-4066.patch
>
>
> Currently, suggestions building is tied at the end of indexing cycle. Along with that
we check if diff between currTime and lastSugguestionBuildTime is more than {{suggestUpdateFrequencyMinutes}}
before deciding to build suggestions or not.
> This allows for suggestions not getting updated if:
> * At T1 suggestions are built
> * At T2 an index update takes place but suggestions aren't rebuilt because not enough
time has passed since T1
> * Now at T3 (after sufficient time), changes at T2 won't show up for suggestions until
some other index change happens.
> We should probably see track about last changes in index (at T2) and use that too while
running indexing cycle at T3.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message