[
https://issues.apache.org/jira/browse/FLINK-8314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16308524#comment-16308524
]
Bowen Li commented on FLINK-8314:
---------------------------------
[~aljoscha] I believe this is unnecessary.
First, Firehose (FH) is just a wrapper with Kinesis inside, to better integrate
with AWS eg. S3. Second, users can create a FH and set Kinesis as source, and
Kinesis's data will automatically goes into FH. Based on the above two reasons,
I believe there's no need to create an extra FH connector and maintain it in
Flink.
> Add support for Kinesis Firehose
> --------------------------------
>
> Key: FLINK-8314
> URL: https://issues.apache.org/jira/browse/FLINK-8314
> Project: Flink
> Issue Type: New Feature
> Components: Kinesis Connector
> Reporter: Ivan Mushketyk
> Priority: Minor
>
> [Kinesis
> Firehose|https://docs.aws.amazon.com/firehose/latest/dev/what-is-this-service.html]
> is another product in Kinesis Family that allows zero-ops scalable stream
> for delivering streaming data to S3, RedShift, Elasticsearch, etc. It has a
> different
> [API|http://docs.aws.amazon.com/firehose/latest/APIReference/Welcome.html].
> I can contribute this myself, but I wonder if this feature makes sense to you.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
