You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2016/07/29 08:17:20 UTC

[jira] [Commented] (OAK-4616) Record suggestor status in suggest-data node

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

Vikas Saurabh commented on OAK-4616:
------------------------------------

Yes, makes sense and looks good to me. Although, I'm trying to recall why did I make a separate node in the first place :-/.

> Record suggestor status in suggest-data node 
> ---------------------------------------------
>
>                 Key: OAK-4616
>                 URL: https://issues.apache.org/jira/browse/OAK-4616
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene
>            Reporter: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.6
>
>         Attachments: OAK-4616-v1.patch
>
>
> Currently the suggestor storage logic maintains a timestamp of when suggestor data was last updated in property {{lastUpdated}} in {{:suggesterStatus}} node. Actual suggest data is stored in a separate node {{:suggest-data}}.
> {noformat}
> /oak:index/lucene-suggest: { reindexCount = 1, name = lucene-suggest, compatVersion = 2, reindex = false, type = lucene, jcr:primaryType = oak:QueryIndexDefinition, :facet-config = { ... }, indexRules = { ... }, :data = { ... }, :status = { ... }, :suggest-data = { ... }, :suggesterStatus = { ... }}
> {noformat}
> It would be better if this property is stored in {{:suggest-data}}. This would simplify adding support for multiplexing as each dir node would be having complete info
> {noformat}
> + :oak:mount-foo-suggest-data
>    - lastUpdated
> + :suggest-data
>    - lastUpdated
> {noformat}



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