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] Allow to specify a custom Pulsar producer #3894

Merged
merged 1 commit into from
Mar 25, 2019

Conversation

casidiablo
Copy link
Contributor

Motivation

It is paramount, in pretty much any non-trivial use-case, to control the settings of the Pulsar producer used by the Flink producer.

Modifications

Allowed users to pass a custom Pulsar producer instance.

Verifying this change

  • This change is already covered by Flink tests

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

  • Dependencies (does it add or upgrade a dependency): no
  • The public API: no
  • The schema: no
  • The default values of configurations: no
  • The wire protocol: no
  • The rest endpoints: no
  • The admin cli options: no
  • Anything that affects deployment: no

This is necessary in pretty much any non-trivial use-case. The ability
to control the settings of the Pulsar producer is paramount to
building real-life applications
@merlimat merlimat added the type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages label Mar 24, 2019
@merlimat merlimat added this to the 2.4.0 milestone Mar 24, 2019
Copy link
Contributor

@merlimat merlimat left a comment

Choose a reason for hiding this comment

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

👍

@sijie sijie merged commit 19fd91c into apache:master Mar 25, 2019
@casidiablo casidiablo deleted the allow-custom-flink-producer branch March 27, 2019 17:58
casidiablo added a commit to casidiablo/pulsar that referenced this pull request Apr 1, 2019
This is an improvement over apache#3894.

Because of how Flink instantiates functions, instead of passing a
custom `PulsarProducer` client we need to pass an object that is
serializable. The current implementation will default to always
call `createProducer()` because `producer` is `transient`, so it will
always be null when Flink creates new instances of the sink.
sijie pushed a commit that referenced this pull request Apr 2, 2019
This is an improvement over #3894.

Because of how Flink instantiates functions, instead of passing a
custom `PulsarProducer` client we need to pass an object that is
serializable. The current implementation will default to always
call `createProducer()` because `producer` is `transient`, so it will
always be null when Flink creates new instances of the sink.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants