Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NIFI-4559: Add non-zero status relationship to ExecuteStreamCommand #2246

Closed
wants to merge 2 commits into from

Conversation

mattyb149
Copy link
Contributor

Sorry about the whitespace changes, I must have slightly different (but still compliant) formatting settings in my IDE.

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced
    in the commit message?

  • Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

  • Has your PR been rebased against the latest commit within the target branch (typically master)?

  • Is your initial contribution a single, squashed commit?

For code changes:

  • Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
  • Have you written or updated unit tests to verify your changes?
  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
  • If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
  • If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
  • If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

  • Have you ensured that format looks appropriate for the output in which it is rendered?

Note:

Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@@ -222,6 +231,16 @@ public ValidationResult validate(String subject, String input, ValidationContext
.defaultValue(";")
.build();

static final PropertyDescriptor PENALIZE_NONZERO_STATUS = new PropertyDescriptor.Builder()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if this is necessary? The processor doesn't currently penalize anything. I think it may make sense to always penalize when sending to the new relationship and the user has the ability to just set Penalty Duration to "0 sec" if they don't want to penalize.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. That property is only to retain current behavior. If they leave the defaults, then once they upgrade, their "failed" flow files will now start to be penalized. That may be acceptable since the user will need to route or terminate that new relationship anyway, so I could add to the doc that flow files routed to that relationship will be penalized, which should imply that they might need to change the Penalty Duration setting?

Copy link
Contributor

@MikeThomsen MikeThomsen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked out the branch and it ran as intended against a simple python script that used sys.exit(1)

+1

@MikeThomsen
Copy link
Contributor

@mattyb149 As mentioned, I tried this out and got it to work. So I see no reason it cannot be merged.

@mattyb149
Copy link
Contributor Author

@MikeThomsen Thank you for your review! I think I tested it fairly well also, so with your +1 I can merge this in.

@asfgit asfgit closed this in 3b15ed8 Nov 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants