locationtech / locationtech/geomesa
Converters - separate out file-based vs stream-based processing
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Converters - separate out file-based vs stream-based processing
Some of our converters require random file access, so they can't handle input streams. Originally, this was just the ShpFile converter, and we handled it with kind of a hack to set the file in the evaluation context. But now we've added parquet as well, so we should probably separate out stream vs file based processing and type inference somehow.
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2634
Key: GEOMESA-2634
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Fri, 31 May 2019 14:07:48 -0400
Updated: Fri, 31 May 2019 14:07:48 -0400
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 reading the ShpFile converter and the parquet converter, then trace how file input is supplied through the evaluation context and how type inference is selected. Done means file-dependent and stream-capable converters have distinct processing and type-inference paths without the current evaluation-context workaround, while existing behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100