[OAK-6210] Provide a consistent and extensible way to handle oak-run options while creating NodeStore

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.0, 1.8.0
• Component/s: run
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 11/May/17 06:56
• Updated: 17/Oct/18 10:07
• Resolved: 23/May/17 09:48

Description

Currently in oak-run commands are using different ways to interpret the command line arguments while constructing a NodeStore instance. For example see

1. Utils
2. NodeStoreOpener
3. Console command
4. Tika command etc etc

This leads to following issues

1. 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
2. Not easy to modularise options and allow list of all options

To simplify this and make it consistent we should

1. use a common and extensible way to handle command line options
2. construct NodeStore and BlobStore instance in a common way (wherever code deals with NodeStore API)

Issue Links

• is related to: OAK-6312 Unify NodeStore/DataStore configurations
• is related to: OAK-6280 Expose whiteboard from NodeStoreFixture to provide access to NodeStore components
• relates to: OAK-6234 Update jopt-simple version to 5.0.3
• relates to: OAK-6257 Move the NodeStoreFixtureProvider support to oak-run-commons

Sub-Tasks

• Improve the help output from oak-run commands: Closed