locationtech / locationtech/geomesa
Arrow - support separate client/server batch size
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Arrow - support separate client/server batch size
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2566
Key: GEOMESA-2566
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Wed, 20 Feb 2019 11:14:07 -0500
Updated: Wed, 20 Feb 2019 11:14:07 -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
No files, tests, or entry points are identified in the issue. Start by locating the Arrow client and server batch-size handling and determine where the current shared setting is defined; done means client and server batch sizes can be configured separately with coverage for both paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- data, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100