locationtech / locationtech/geomesa
NiFi - improve warning checks for schema changes
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
NiFi - improve warning checks for schema changes
Currently the processors tend to incorrectly warn about schema changes. Figure out the root cause and fix it so that warnings are more accurate.
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-3127
Key: GEOMESA-3127
Type: Improvement
Priority: Major
Status: To Do
Resolution: Fixed
Assignee: Emilio Lahr-Vivaz
Reporter: Emilio Lahr-Vivaz
Created: Fri, 3 Sep 2021 08:31:15 -0400
Updated: Fri, 3 Sep 2021 10:51:05 -0400
Resolved: Fri, 3 Sep 2021 10:36:17 -0400
Fix Version(s): 3.2.1
Comments:
557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Fri, 3 Sep 2021 10:51:05 -0400):
going to leave this open for better fixes. In 3.2.1 we’ve turned down the logging level as a mitigation.
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 named. Start by locating the NiFi processors that perform schema-change warning checks, reproduce an incorrect warning, and trace its root cause. Done means warnings accurately reflect schema changes, with regression coverage for the reported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100