[
https://issues.apache.org/jira/browse/OAK-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-6210:
---------------------------------
Attachment: OAK-6210-v1.patch
[patch|^OAK-6210-v1.patch] for the same. Also the gitbranch [1].
This patch introduces following constructs
* Options - Class which is container of all possible options
* OptionsBean - Represents a set of options for e.g. RDBStoreOptions,
BlobStoreOptions
*Usage*
{code}
OptionParser parser = new OptionParser();
//Define custom options specific to current command
OptionSpec quiet = parser.accepts("quiet", "be less chatty");
Options opts = new Options();
{code}
[1]
https://github.com/chetanmeh/jackrabbit-oak/compare/trunk...chetanmeh:OAK-6210
> Provide a consistent and extensible way to handle oak-run options while
> creating NodeStore
> ------------------------------------------------------------------------------------------
>
> Key: OAK-6210
> URL: https://issues.apache.org/jira/browse/OAK-6210
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 1.8
>
> Attachments: OAK-6210-v1.patch
>
>
> Currently in oak-run commands are using different ways to interpret the
> command line arguments while constructing a NodeStore instance. For example
> see
> # Utils
> # NodeStoreOpener
> # Console command
> # Tika command etc etc
> This leads to following issues
> # Incomplete support for different BlobStore - Many command only support
> FileDataStore and not support other stores. Utils now has a generic method
> but its not used in all places
> # Not easy to modularise options and allow list of all options
> To simplify this and make it consistent we should
> # use a common and extensible way to handle command line options
> # construct NodeStore and BlobStore instance in a common way (wherever code
> deals with NodeStore API)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
