locationtech / locationtech/geomesa
Kudu - support separate config for scan.ranges.target
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Kudu - support separate config for scan.ranges.target
Kudu works better with a smaller number of ranges - if you were using Kudu along with another data store, you would only be able to configure the range target globally. Add some per data store (or sft?) config for geomesa.scan.ranges.target
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2548
Key: GEOMESA-2548
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Tue, 5 Feb 2019 09:26:51 -0500
Updated: Tue, 5 Feb 2019 09:26:51 -0500
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the geomesa.scan.ranges.target configuration and the scan range handling for data stores. Define how the setting can be supplied separately per data store or SFT, then verify that each store uses its own target without changing the global behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100