NIFI-14161: Fix QueryCassandra Processor Attribute Loss Issue #9637
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for pull request! Any commit that should land on NiFi 1.x should be via a PR against the branch https://github.com/apache/nifi/tree/support/nifi-1.x. However, I don't think the community is willing to invest additional time in making new releases for the 1.x branch. It is, of course, up to any committer/PMC member to decide if such a release should happen though and if, collectively, enough people are willing to go through the release process which is quite time consuming. |
pvillard31
changed the base branch from
support/nifi-1.28
to
support/nifi-1.x
pvillard31
changed the base branch from
support/nifi-1.x
to
support/nifi-1.28
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolved an issue in the QueryCassandra processor where attributes from the incoming FlowFile were occasionally lost in subsequent FlowFiles when the processor split the results due to a configured Fetch Size (e.g., 750). This fix ensures that all FlowFiles maintain the original attributes, even when multiple FlowFiles are generated from a single query result.