[
https://issues.apache.org/jira/browse/OAK-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171558#comment-15171558
]
Vikas Saurabh edited comment on OAK-4066 at 2/29/16 8:30 AM:
-------------------------------------------------------------
bq. We update dict but lastUpdated is still T1
-[~chetanm], lastUpdated for suggester build is different than that of index
build... so, I think duplicate build up won't be an issue.-
Got it... ok, would take care of this -- [~chetanm], would
{{:stats->lastUpdate}} be a reliable thing to use here?
bq. And yes some description on bug would be helpful to understand the severity
of this issue
Ack. I created the issue in haste and adding description went down as TODO :)
was (Author: catholicon):
bq. We update dict but lastUpdated is still T1
-[~chetanm], lastUpdated for suggester build is different than that of index
build... so, I think duplicate build up won't be an issue.-
Got it... ok, would take care of this.
bq. And yes some description on bug would be helpful to understand the severity
of this issue
Ack. I created the issue in haste and adding description went down as TODO :)
> 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)
