locationtech / locationtech/geomesa
ArrowFeatureSource - implement canSort
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
ArrowFeatureSource - implement canSort
If the arrow files are already sorted and the requested sort field corresponds with the arrow file, we can handle the sorting ourselves. Otherwise, we can wrap in a sorting feature collection.
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-1817
Key: GEOMESA-1817
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Tue, 16 May 2017 14:52:26 -0400
Updated: Tue, 16 May 2017 14:52:26 -0400
Affects Version(s): 1.3.2
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 ArrowFeatureSource and reading how it currently handles requested sorting and the ordering of its Arrow files. Confirm the behavior with the existing query or sorting checks, if present; done means already-sorted compatible requests are handled by ArrowFeatureSource while other requests use a sorting feature collection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100