[FLINK-16124] YAML-ized Kinesis ingress / egresses #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up to #61, adding the YAML-ized Kinesis ingress / egresses.
Usage
Note: by default,
awsRegion,awsCredentials,startupPosition,maxOutstandingRecords, andclientConfigPropertiesdo not need to be specified.Changelog
Important changes are:
54cf5a2 Implement runtime classes / providers for the routable protobuf Kinesis ingress
001561f Binds the
AutoRoutableProtobufRouterfor the routable Kinesis ingress in theJsonModulead56622 Binds the new provider for the routable Kinesis ingress
ba46048 Implements runtime classes / providers for the generic Kinesis egress
094dc6c Binds the new provider for the generic Kinesis egress
All other commits are preliminary changes for the above.