[
https://issues.apache.org/jira/browse/OAK-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237553#comment-14237553
]
Chetan Mehrotra commented on OAK-2177:
--------------------------------------
With above approach I hope we would meet most of the analyzer customisation
requirement. In my initial proposal I was aiming for OSGi based extension
point. Thinking more about it I realized that supporting it would be bit tricky
due to dynamic nature of OSGi and so would be bit complex to support.
For now I am more inclined to defer support for OSGi based extension point.
[~alex.parvulescu] [~teofili] [~mreutegg] [~tmueller] [~mmarth] Can you have a
look at above proposed appraoch and wether it would be ok to proceed with this
for now and defer the OSGi based approach to some later time (if we get any
such usecase)
> Configurable Analyzer in Lucene index
> -------------------------------------
>
> Key: OAK-2177
> URL: https://issues.apache.org/jira/browse/OAK-2177
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: oak-lucene
> Affects Versions: 1.1.0
> Reporter: Tommaso Teofili
> Assignee: Chetan Mehrotra
> Attachments: OAK-2177.patch
>
>
> Currently the _OakAnalyzer_ is used by default for each Lucene field,
> sometimes using a different analyzer is needed though.
> It should be possible to make that configurable to support things like:
> multiple languages, stopword filtering, synonyms expansion, stemming, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
