keith-turner commented on issue #2105:
URL: https://github.com/apache/accumulo/issues/2105#issuecomment-840673982
> I guess my issue is with the JSON in the first place.
I didn't easily settle on using json. However I saw it as an option between
the following
```
tserver.compaction.major.service.root.planner.opts.executors ..... |
[{'name':'small','maxSize':'32M','numThreads':1},{"name":"huge","numThreads":1}]
```
or the following
```
tserver.compaction.major.service.root.planner.opts.executors.e1.name=small
tserver.compaction.major.service.root.planner.opts.executors.e1.maxSize=32M
tserver.compaction.major.service.root.planner.opts.executors.e1.numThreads=1
tserver.compaction.major.service.root.planner.opts.executors.e2.name=huge
tserver.compaction.major.service.root.planner.opts.executors.e2.numThreads=1
```
and thought that json would be better than the exploded options. Also the
JSON is not intrinsic to Accumulo, its just something the default planner
plugin uses. One could write another planner that does not use json for its
options.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
