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

MINIFICPP-2294 Flow migration #1850

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

martinzink
Copy link
Member

-Removed deprecated "Send Body" and "Disable Peer Verification" properties from InvokeHTTP
-Removed deprecated "Message Key Field" property from PublishKafka
-Removed deprecated SSL related properties from PublishKafka and replaced them with a generated SSLContextService

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

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 MINIFICPP-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 main)?

  • Is your initial contribution a single, squashed commit?

For code 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?
  • If applicable, have you updated the NOTICE file?

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 GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.

@martinzink martinzink marked this pull request as ready for review August 2, 2024 10:03
extensions/librdkafka/PublishKafka.cpp Outdated Show resolved Hide resolved
extensions/librdkafka/migrators/PublishKafkaMigrator.cpp Outdated Show resolved Hide resolved
extensions/librdkafka/migrators/PublishKafkaMigrator.cpp Outdated Show resolved Hide resolved
extensions/librdkafka/migrators/PublishKafkaMigrator.cpp Outdated Show resolved Hide resolved
extensions/librdkafka/tests/PublishKafkaMigratorTests.cpp Outdated Show resolved Hide resolved
extensions/librdkafka/tests/PublishKafkaMigratorTests.cpp Outdated Show resolved Hide resolved
libminifi/include/core/flow/FlowMigrator.h Outdated Show resolved Hide resolved
libminifi/src/core/flow/StructuredConfiguration.cpp Outdated Show resolved Hide resolved
@szaszm
Copy link
Member

szaszm commented Nov 13, 2024

I would close this until we figure out how to do it in a C2-friendly way

@szaszm szaszm closed this Nov 13, 2024
@szaszm
Copy link
Member

szaszm commented Nov 13, 2024

my mistake, I misunderstood parts of the PR. Apparently migrations are unversioned, idempotent, so they run on all input flow definitions, regardless of whether that was meant to target older or newer minifi versions. This way it's not a problem if we don't know what minifi version is targeted by the C2 server.

I'm still not sure if an unversioned approach is the right one, but it's not inherently bad, like I thought an hour ago.

@szaszm szaszm reopened this Nov 13, 2024
Comment on lines 82 to 87
SECTION("Adaptive Yaml Configuration") {
core::flow::AdaptiveConfiguration adaptive_configuration(test_controller.getContext());
auto root_flow_definition = adaptive_configuration.getRootFromPayload(std::string{ORIGINAL_YAML});
REQUIRE(root_flow_definition);
serialized_flow_definition = adaptive_configuration.serialize(*root_flow_definition);
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need to test this in the scope of this feature? As far as I see the flow migration logic doesn't impact how the AdaptiveConfiguration recognizes the flow format, so testing the yml and json configuration separately should be enough.

Copy link
Member Author

Choose a reason for hiding this comment

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

Good point removed it in a8b7f94

  -Removed deprecated "Send Body" and "Disable Peer Verification" properties from InvokeHTTP
  -Removed deprecated "Message Key Field" property from PublishKafka
  -Removed deprecated SSL related properties from PublishKafka and replaced them with a generated SSLContextService
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants