locationtech / locationtech/geomesa
Add error-handling to validate future schema metadata
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Add error-handling to validate future schema metadata
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2543
Key: GEOMESA-2543
Type: Improvement
Priority: Major
Status: Done
Resolution: Fixed
Assignee: Emilio Lahr-Vivaz
Reporter: Emilio Lahr-Vivaz
Created: Mon, 4 Feb 2019 13:10:46 -0500
Updated: Mon, 11 Feb 2019 16:00:01 -0500
Resolved: Mon, 11 Feb 2019 16:00:01 -0500
Fix Version(s): 2.2.2, 2.1.3
Comments:
557058:48912df4-0004-4f90-9915-db26684ec006 (Mon, 11 Feb 2019 16:00:01 -0500):
2.1.x: https://github.com/locationtech/geomesa/commit/36de36c6183c27f760c5479c0dbc1bc314418b3d
2.2.x: https://github.com/locationtech/geomesa/commit/9f03d12c63a351fa49e396be31cc6e98cdca537d
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 2.1.x and 2.2.x commits linked in the issue, then trace the schema-metadata validation entry point they modify. Confirm how future metadata is handled and compare the behavior with the issue's requested error handling; the work is complete when validation reports errors appropriately for future schema metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100