[
https://issues.apache.org/jira/browse/OAK-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068368#comment-15068368
]
Vikas Saurabh commented on OAK-3576:
------------------------------------
Fixed in trunk at [r1721424|http://svn.apache.org/r1721424] and
[r1721428|http://svn.apache.org/r1721428]. Have incorporated following changes
over latest patch:
* Dropped usage of defn.getVersion().isAtLeast(IndexFormatVersion.V2)) in
LuceneIndexEditor
* Added {{Nonnull}} and {{CheckForNull}} annotations in SPI as applicable
(preferred Nonnull)
Using new API in Tracker (OAK-3815) would be done later.
> Allow custom extension to augment indexed lucene documents
> ----------------------------------------------------------
>
> Key: OAK-3576
> URL: https://issues.apache.org/jira/browse/OAK-3576
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Fix For: 1.4
>
> Attachments: OAK-3576.jsedding.patch, OAK-3576.take2.patch,
> OAK-3576.wip.patch
>
>
> Following up on http://oak.markmail.org/thread/a53ahsgb3bowtwyq, we should
> have an extension point in oak to allow custom code to add fields to
> documents getting indexed in lucene. We'd also need to allow extension point
> to add extra query terms to utilize such augmented fields.
> (cc [~teofili], [~chetanm])
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
