locationtech / locationtech/geomesa
Optimize json serialization when json-schema is used
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Optimize json serialization when json-schema is used
For json values that conform to the schema, we don't need to store paths in our serialized data. Non-conforming values would be serialized separately using existing methods. We could store [conforming values][non-conforming values] in the serialized value
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-1451
Key: GEOMESA-1451
Type: Story
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Thu, 29 Sep 2016 10:27:29 -0400
Updated: Mon, 2 Oct 2017 09:42:38 -0400
Affects Version(s): 1.3.0
Related Issues:
- Blocks (is depended on by): GEOMESA-1450
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, tests, or entry points are named in the issue. First locate the JSON serialization and json-schema handling, then determine how conforming and non-conforming values are represented. Done means conforming values serialize without paths while non-conforming values continue using the existing methods, with measurements or tests demonstrating the optimization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- data, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100