[jira] [Assigned] (OAK-7349) Tool to easily test an analyzer configuration

["Matt Ryan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OAK-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Ryan reassigned OAK-7349:
------------------------------

    Assignee: Vikas Saurabh  (was: Matt Ryan)

> Tool to easily test an analyzer configuration
> ---------------------------------------------
>
>                 Key: OAK-7349
>                 URL: https://issues.apache.org/jira/browse/OAK-7349
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene
>            Reporter: Vikas Saurabh
>            Assignee: Vikas Saurabh
>            Priority: Major
>
> Lucene index definitions allow the user to create custom analyer \[0]. The most common way to define one is to do it by composition \[1].
> This issue about creating some tool for users to play with analyzer configurations and see how that analyzer works for a given phrase (i.e. input <phrase, analyzer-config>, output <list of analyzed terms)
> A couple of ideas of where to solve this:
> * maybe a jmx that takes 2 text inputs <phrase> and <json for analyzer-config matching what one gives in index def> and outputs <list of analyzed terms>
> * maybe we can have dedicated oak-run console command - that can be more easily usable as we would have groovy as a language available to use to get inputs (especially for analyzer config)
> * some other page (say under http://oakutils.appspot.com/ ) - should be last resort though.
> \[0]: http://jackrabbit.apache.org/oak/docs/query/lucene.html#Analyzers
> \[1]: http://jackrabbit.apache.org/oak/docs/query/lucene.html#analyzer-composition



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)