locationtech / locationtech/geomesa
Support feature locking
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Support feature locking
Seems like at a minimum, our feature stores need to implement SimpleFeatureLocking, and our data stores need to implement getLockingManager. Locking is tied to transactions, so we may need to implement some aspects of transaction support.
Some background on locking: http://docs.geotools.org/latest/userguide/library/api/datastore.html
For semantics around calling it, see: https://github.com/geoserver/geoserver/blob/2.12.0/src/wfs/src/main/java/org/geoserver/wfs/LockFeature.java#L148
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2477
Key: GEOMESA-2477
Type: Story
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Tue, 27 Nov 2018 13:43:49 -0500
Updated: Tue, 27 Nov 2018 13:43:49 -0500
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 reviewing the feature-store and data-store implementations, then compare the SimpleFeatureLocking and getLockingManager APIs with the GeoServer LockFeature.java reference and the linked GeoTools locking documentation. Define the required transaction behavior and verify that each relevant store supports the locking semantics described by those references.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, scala
- Domain
- backend-api-design, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100