locationtech / locationtech/geomesa
Converters - recursive field dependency calculation is slow with 100s of dependent fields
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Converters - recursive field dependency calculation is slow with 100s of dependent fields
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2376
Key: GEOMESA-2376
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Thu, 16 Aug 2018 17:17:58 -0400
Updated: Thu, 13 Sep 2018 11:34:10 -0400
Comments:
557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Thu, 13 Sep 2018 09:18:46 -0400):
We need to verify that this is still a problem with the parboiled transformer parsing in 2.0. Andrew Hulbert can you take a look?
557058:3bdf14b8-308b-42a1-93b4-2ee86eacfbc7 (Thu, 13 Sep 2018 11:34:10 -0400):
yeah I'll try to find the code...I think Britt is out.
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 the converter's recursive field-dependency calculation and the parboiled transformer parsing in version 2.0. Reproduce the slowdown with hundreds of dependent fields, then verify that the calculation is acceptably faster without changing dependency results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100