locationtech / locationtech/geomesa
Explore what happens with GT functions and parquet
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Explore what happens with GT functions and parquet
See what happens when you apply a UDF to the datastore? see FilterConverter too.
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-1938
Key: GEOMESA-1938
Type: Technical task
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Andrew Hulbert
Created: Mon, 17 Jul 2017 22:26:56 -0400
Updated: Mon, 17 Jul 2017 22:26:56 -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
Start by locating the GeoMesa datastore handling for parquet and the GT function and FilterConverter entry points. Exercise UDF and filter cases against parquet-backed data, documenting what happens and where behavior is unsupported or inconsistent. Done means the observed behavior and any required follow-up are clearly recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100