locationtech / locationtech/geomesa
Reach-back Synthentic ID for Converter Datastore
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Reach-back Synthentic ID for Converter Datastore
The converter datastore wraps an existing filesystem structure on some filesystem and then provides access to it by running a configured converter over it at query time. There needs to be some reach-back ID similar to an existing GM project that hashes the path to the file and offset for the features to provide quick reach-back when clicking on a map or doing an ID= query
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-1906
Key: GEOMESA-1906
Type: Technical task
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Andrew Hulbert
Created: Fri, 7 Jul 2017 09:55:03 -0400
Updated: Fri, 7 Jul 2017 09:58:53 -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
No files or tests are identified. Start by locating the converter datastore and reviewing the referenced existing GM project's reach-back ID approach; determine how the source path and feature offset should support map clicks and ID= queries. Done means both lookup paths provide reliable reach-back IDs for converted features.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100