locationtech / locationtech/geomesa
Converters - .foreach processing instead of .map processing
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Converters - .foreach processing instead of .map processing
Provide a way to operate on a stream of parsed values (i.e. .foreach), instead of converting them to simple features (i.e. .map). This could be used for something like populating a distributed cache.
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2457
Key: GEOMESA-2457
Type: Story
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Wed, 7 Nov 2018 09:25:02 -0500
Updated: Wed, 7 Nov 2018 09:25:02 -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 source files, tests, or entry points are named. Start by locating the converter API and its existing .map processing, then determine how a .foreach operation should expose parsed values for uses such as a distributed cache. Done means the API supports that operation and its behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100