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-4759 Fixed a bug that left a hard-coded reference to _id in as t… #2401

Closed
wants to merge 1 commit into from

Conversation

MikeThomsen
Copy link
Contributor

@MikeThomsen MikeThomsen commented Jan 12, 2018

…he update key for MongoDB upserts.

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

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.

Copy link
Contributor

@mgaido91 mgaido91 left a comment

Choose a reason for hiding this comment

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

Thanks for updating the PR. I left 3 minor comments. Otherwise it LGTM.


for (String upsert : upserts) {
runner.setProperty(PutMongo.UPDATE_QUERY_KEY, updateKeyProps[index]);
for (int x = 0; x < 5; x++) {
Copy link
Contributor

Choose a reason for hiding this comment

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

What about using 2 instead of 5?

@Test
public void testNiFi_4759_Regressions() {
String[] upserts = new String[]{
"{\n" +
Copy link
Contributor

Choose a reason for hiding this comment

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

What about writing the JSON document on one line?

}
}

/*
Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: I'd remove this and the empty line above...

@MikeThomsen
Copy link
Contributor Author

@mgaido91 I think it's all done now.

@mgaido91
Copy link
Contributor

LGTM, thanks.

@mgaido91
Copy link
Contributor

@joewitt @pvillard31 maybe you can help reviewing this too, thanks.

@pvillard31
Copy link
Contributor

+1, LGTM, thanks for the PR @MikeThomsen and thanks for the review @mgaido91

@asfgit asfgit closed this in ca54186 Jan 17, 2018
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