locationtech / locationtech/geomesa
Support Writing multiple formats
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Support Writing multiple formats
currently only parquet can be written we need mapreduce output formats for other formats. plus autogenerated bindings stored in metadata....so if i want to ingest some random data and store it as TSV for example it should automatically make a converter to transform it at read time and store that as metadata.
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-1911
Key: GEOMESA-1911
Type: Technical task
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Andrew Hulbert
Created: Fri, 7 Jul 2017 10:06:26 -0400
Updated: Fri, 7 Jul 2017 10:06:26 -0400
Parent: GEOMESA-1905
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
The issue names no files, tests, or entry points. Start by locating the existing Parquet writer and MapReduce output-format handling, then trace how autogenerated bindings are stored in metadata. Done should include support for additional output formats such as TSV and metadata that enables conversion at read time.
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
- 25/100