Skip to content

MINIFICPP-2771 Use separate state managers in schedule and trigger threads#2157

Draft
lordgamez wants to merge 1 commit intoapache:mainfrom
lordgamez:MINIFICPP-2771
Draft

MINIFICPP-2771 Use separate state managers in schedule and trigger threads#2157
lordgamez wants to merge 1 commit intoapache:mainfrom
lordgamez:MINIFICPP-2771

Conversation

@lordgamez
Copy link
Copy Markdown
Contributor

https://issues.apache.org/jira/browse/MINIFICPP-2771


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.

Comment on lines +52 to 53
explicit ListingStateManager(gsl::not_null<core::StateManager*> state_manager)
: state_manager_(state_manager) {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

In parameters, I'd use references instead of not_null pointers, but in data members, I'd keep the not_null pointer, because members generally shouldn't be const.

Suggested change
explicit ListingStateManager(gsl::not_null<core::StateManager*> state_manager)
: state_manager_(state_manager) {
explicit ListingStateManager(core::StateManager& state_manager)
: state_manager_(&state_manager) {

Comment on lines +27 to +28
if (!state_manager_) {
return;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Shouldn't this be an error, like an exception?

Comment on lines +472 to 473
void S3Wrapper::initializeMultipartUploadStateStorage(gsl::not_null<core::StateManager*> state_manager) {
multipart_upload_storage_ = std::make_unique<MultipartUploadStateStorage>(state_manager);
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
void S3Wrapper::initializeMultipartUploadStateStorage(gsl::not_null<core::StateManager*> state_manager) {
multipart_upload_storage_ = std::make_unique<MultipartUploadStateStorage>(state_manager);
void S3Wrapper::initializeMultipartUploadStateStorage(core::StateManager& state_manager) {
multipart_upload_storage_ = std::make_unique<MultipartUploadStateStorage>(state_manager);

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.

2 participants