Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Tue, 7 Mar 2017 09:08:33 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.13048572.1488817903000.17447.1488877713100@Atlassian.JIRA>
In-Reply-To: <JIRA.13048572.1488817903000@Atlassian.JIRA>
References: <JIRA.13048572.1488817903000@Atlassian.JIRA> <JIRA.13048572.1488817903693@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CAMEL-10952) Kinesis Firehose support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 07 Mar 2017 09:08:36 -0000


    [ https://issues.apache.org/jira/browse/CAMEL-10952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899004#comment-15899004 ] 

Claus Ibsen commented on CAMEL-10952:
-------------------------------------

And in the producer you likely need to do something about the put result to be able to let the Camel user access that and know if the result was okay or not, or access the result if needed or something.

But keep hacking on the code.

> Kinesis Firehose support
> ------------------------
>
>                 Key: CAMEL-10952
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10952
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-aws
>            Reporter: Tony Tiger
>            Priority: Minor
>             Fix For: Future
>
>
> Kinesis Firehose is a separate API and SDK that has minor differences from that of vanilla flavoured Kinesis. The biggest difference is that Firehose is a "produce-only" Endpoint and can't really be a consumer as data from Firehose is eventually persisted into S3.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)