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

[FLINK-17623][Connectors/Elasticsearch] Support user resource cleanup in Elasticsearch sink #12619

Closed
wants to merge 2 commits into from

Conversation

yun-wang
Copy link
Contributor

What is the purpose of the change

This pull request supports user resource cleanup in Elasticsearch sink.

Brief change log

  • Expose a default close method in ElasticsearchSinkFunction.

Verifying this change

This change added tests and can be verified as follows:

  • Added a unit test that both open() and close() methods are invoked in the Elasticsearch sink as expected.

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): (no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): (yes)
  • The serializers: (no)
  • The runtime per-record code paths (performance sensitive): (no)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
  • The S3 file system connector: (no)

Documentation

  • Does this pull request introduce a new feature? (yes)
  • If yes, how is the feature documented? (JavaDocs)

@flinkbot
Copy link
Collaborator

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Automated Checks

Last check on commit a73bb36 (Fri Jun 12 00:42:29 UTC 2020)

Warnings:

  • No documentation files were touched! Remember to keep the Flink docs up to date!

Mention the bot in a comment to re-run the automated checks.

Review Progress

  • ❓ 1. The [description] looks good.
  • ❓ 2. There is [consensus] that the contribution should go into to Flink.
  • ❓ 3. Needs [attention] from.
  • ❓ 4. The change fits into the overall [architecture].
  • ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.


The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands
The @flinkbot bot supports the following commands:

  • @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
  • @flinkbot approve all to approve all aspects
  • @flinkbot approve-until architecture to approve everything until architecture
  • @flinkbot attention @username1 [@username2 ..] to require somebody's attention
  • @flinkbot disapprove architecture to remove an approval you gave earlier

@flinkbot
Copy link
Collaborator

flinkbot commented Jun 12, 2020

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run travis re-run the last Travis build
  • @flinkbot run azure re-run the last Azure build

Copy link
Contributor

@KarmaGYZ KarmaGYZ 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 the PR, @yun-wang . I left two minor comments.

/**
* Tear-down method for the function. It is called when the sink closes.
*/
default void close () throws Exception {}
Copy link
Contributor

Choose a reason for hiding this comment

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

It's a bit weird that the open function does not allow to throw an exception. I admit it is out of the scope of this PR though.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I can update open to default void open() throws Exception {} real quick. It's a backward compatible change and should have no user impact.

Copy link
Contributor

Choose a reason for hiding this comment

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

Sounds good to me.

Comment on lines 420 to 429
ElasticsearchSinkFunction<String> sinkFunction = (ElasticsearchSinkFunction<String>) mock(ElasticsearchSinkFunction.class);
final DummyElasticsearchSink<String> sink = new DummyElasticsearchSink<>(
new HashMap<>(), sinkFunction, new DummyRetryFailureHandler());

sink.open(mock(Configuration.class));
sink.close();

verify(sinkFunction, times(1)).open();
verify(sinkFunction, times(1)).close();
verifyNoMoreInteractions(sinkFunction);
Copy link
Contributor

@KarmaGYZ KarmaGYZ Jun 12, 2020

Choose a reason for hiding this comment

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

The community tends to avoid mock if possible. In this case, I think we could add TestingElasticsearchSinkFunction or just an anonymous class.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure I can update the test.

Out of curiosity, any particular reason to avoid mock whenever possible? In this case adding a simple implementation class would serve the exact same purpose as the mock, only lengthier.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think this reflects how well our design adheres to the principles of dependency injection. If our design is good enough, we could directly use the constructor in the test.

final DummyElasticsearchSink<String> sink = new DummyElasticsearchSink<>(
new HashMap<>(), sinkFunction, new DummyRetryFailureHandler());

sink.open(mock(Configuration.class));
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
sink.open(mock(Configuration.class));
sink.open(new Configuration()));

@@ -586,6 +600,27 @@ public void process(String element, RuntimeContext ctx, RequestIndexer indexer)
}
}

private static class SimpleClosableSinkFunction<String> implements ElasticsearchSinkFunction<String> {
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe TestingClosableSinkFunction? Not quite sure about this.

Copy link
Contributor

@KarmaGYZ KarmaGYZ 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 addressing my comments, @yun-wang . It now LGTM. Just two minor comments you could take a look.

@KarmaGYZ
Copy link
Contributor

@wuchong Could you help to review and merge it?

Copy link
Member

@wuchong wuchong 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 the work @yun-wang and reviewing @KarmaGYZ .

LGTM.

@wuchong wuchong closed this in 57992c9 Jun 15, 2020
bigdata-ny pushed a commit to bigdata-ny/flink that referenced this pull request Jun 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants