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-16557][docs] Document YAML-ized Kafka egresses / ingresses in … #63

Closed
wants to merge 3 commits into from

Conversation

sjwiesman
Copy link
Contributor

…Stateful Functions documentation

Copy link
Contributor

@tzulitai tzulitai left a comment

Choose a reason for hiding this comment

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

Looks good, thanks a lot for writing this up @sjwiesman.
Only found minor problems with indentation and typos, I'll address those when merging!

Comment on lines +66 to +67
ingresses:
- ingress:
Copy link
Contributor

Choose a reason for hiding this comment

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

Indentation seems a bit off here:

Suggested change
ingresses:
- ingress:
ingresses:
- ingress:

Comment on lines +135 to +136
egresses:
- egress:
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here: indentation

Comment on lines +82 to +83
topics:
- topic: messages-1
Copy link
Contributor

Choose a reason for hiding this comment

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

Indentation:

Suggested change
topics:
- topic: messages-1
topics:
- topic: messages-1


.. code-block:: none

KafkaEgressBuilder#withNoProducerSemantics();
Copy link
Contributor

Choose a reason for hiding this comment

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

This should be KafkaEgressBuilder#withAtLeastOnceSemantics

.. code-block:: yaml

deliverySemantic:
type: none
Copy link
Contributor

Choose a reason for hiding this comment

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

Should be type: at-least-once


The Kafka egress needs to know how to turn Java objects into binary data.
When using the Java pi, the Kafka egress needs to know how to turn Java objects into binary data.
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
When using the Java pi, the Kafka egress needs to know how to turn Java objects into binary data.
When using the Java api, the Kafka egress needs to know how to turn Java objects into binary data.

@tzulitai tzulitai closed this in b3a9ea1 Mar 22, 2020
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