[
https://issues.apache.org/jira/browse/STORM-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465337#comment-16465337
]
Aniket Alhat commented on STORM-2974:
-------------------------------------
[~Srdo] thanks for the reply, actually my concern is not only about connecting
to 0.11 Kafka with old consumer but making use of Kerberos/SASL_PLAINTEXT to
consume the messages. I'll definitely try to test it out with some simple
topology but I wasn't sure if storm-kafka client even allows to configure the
spout/topology with these new secure parameters. If you tried this in the past
please do let me know if you have any ideas. I'm also contacting the Kafka
mailing list and found a similar issue.
I might be wrong but I think the difference between opaque and transactional
spout is that, transactional guarantees that when batch is re-emitted each
batch will have exactly the same tuples which were present in the failed batch
while opaque doesn't guarantee that they will be part of the same batch, of
course we can have exactly once semantics with them as well but that will
require adding more state in the operation database. Again quoting from the
Storm Trident
[documents|https://storm.apache.org/releases/1.0.6/Trident-state.html].
> Add a transactional non-opaque spout to storm-kafka-client
> ----------------------------------------------------------
>
> Key: STORM-2974
> URL: https://issues.apache.org/jira/browse/STORM-2974
> Project: Apache Storm
> Issue Type: Sub-task
> Components: storm-kafka-client
> Affects Versions: 2.0.0
> Reporter: Stig Rohde Døssing
> Assignee: Stig Rohde Døssing
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)