locationtech / locationtech/geomesa
NiFi - 'existing' schema compatibility check should allow for fewer fields in the input
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
NiFi - 'existing' schema compatibility check should allow for fewer fields in the input
If your configured sft has fewer fields than the existing schema, the schema check will return 'incompatible' and the 'existing' config won't be considered. Ideally, we'd be able to distinguish between truly incompatible schemas and ones with just some non-critical fields missing
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-3072
Key: GEOMESA-3072
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Wed, 12 May 2021 13:11:05 -0400
Updated: Wed, 12 May 2021 13:11:05 -0400
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
The issue does not name files or tests. Start by locating the NiFi implementation of the 'existing' schema compatibility check and tracing how configured SFT fields are compared with the existing schema. Done means schemas with fewer non-critical input fields are accepted while truly incompatible schemas remain rejected, with coverage for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100