[
https://issues.apache.org/jira/browse/OAK-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451813#comment-13451813
]
Jukka Zitting commented on OAK-154:
-----------------------------------
bq. You mean the QueryIndexProvider.getQueryIndexes(), right?
Right.
bq. That is not going to be easy to pull off (OakDirectory also needs a
NodeState).
Is there some special reason why that method should be able to write to the
repository? If not, then it should be possible to abstract away the read-only
parts of OakDirectory needed by that method.
bq. Can we put it as a next TODO after the patch goes through?
Sure, no need for the code to be perfect at first go as long as we have rough
consensus on where and how it should evolve.
> Full text search index
> ----------------------
>
> Key: OAK-154
> URL: https://issues.apache.org/jira/browse/OAK-154
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Labels: lucene
> Attachments: OAK-154-enable-lucene.patch,
> OAK-154-optional-lucene.patch, oak-index.patch
>
>
> Oak should support full text search against content in the repository.
> As a default implementation of such a feature I'd like to add a simple
> Lucene-based full text index, somewhat similar to the search index we have in
> Jackrabbit 2.x.
--
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
