jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Sedding (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3576) Allow custom extension to augment indexed lucene documents
Date Wed, 04 Nov 2015 10:32:28 GMT

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

Julian Sedding commented on OAK-3576:
-------------------------------------

[~catholicon], thank you for your thoughts.

When developing a new SPI (or API), I think it is worthwhile putting in some extra effort
to avoid "maintenance and debugging nightmare". If doing this seems like "too much work",
maybe it would be a better idea to include support for your use-case directly in Oak.

I realise that you believe your use-case is not suited to be directly supported in Oak. Unfortunately
you did not share said use-case, which makes it impossible to come up with alternative suggestions
for a solution.

Could you please explain the use-case you are trying to accommodate? Thanks!

> 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
>         Attachments: 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)

Mime
View raw message