Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

Hi, Apurva, Thanks for the update. My replies are inlined below. On Wed, Jan 25, 2017 at 5:15 PM, Apurva Mehta wrote: > Hi Jun, > > Thanks again for the comments. More responses follow: > > > > 101. Compatibility during upgrade: Suppose that the brokers are upgraded > to > > the new version, bu

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

Hi, Jason, Thanks for the reply. They sound good to me. Jun On Fri, Jan 27, 2017 at 4:42 PM, Jason Gustafson wrote: > A few more responses: > > > > 101. Compatibility during upgrade: Suppose that the brokers are upgraded > to > > the new version, but the broker message format is still the old

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

Hello Jun, Thanks for the comments!! Some responses below: *> 100. Security: **We could also include AppId in produce request..* On brokers only PIDs are maintained and they are unaware of the AppIds, so I think it would be costly to prevent writes on the AppId level. On the other hand, having s

Rewind Kafka Stream consumer offset by timestamp

Hi everyone, I was wondering if its possible to rewind consumers offset in Kafka Stream using timestamp as with `offsetsForTimes(Map timestampsToSearch)` in KafkaConsumer. I know its possible to go back to `earliest` offset in topic or `latest`, but would be useful to go back using timestamp as w

[GitHub] kafka pull request #2463: 4706

GitHub user sharad-develop opened a pull request: https://github.com/apache/kafka/pull/2463 4706 4706 - Unify StreamsKafkaClient instances You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/kafka 0.10.2 Alternatively you can

Re: Rewind Kafka Stream consumer offset by timestamp

Hi Jorge, This is currently not possible, but it is likely to be considered for discussion. One challenge is that, if you have multiple topics, it is difficult to rewind them all back to a consistent point in time. KIP-95, currently under discussion, is handling the slightly different issue, of

[GitHub] kafka pull request #2462: MINOR: JavaDoc markup cleanup

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2462 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

Thanks Apurva - replies inline. On 2017年01月27日 15:19, Apurva Mehta wrote: Eugen, moving your email to the main thread so that it doesn't get split. The `transaction.app.id` is a prerequisite for using transactional APIs. And only messages wrapped inside transactions will enjoy idempotent guaran

Re: Rewind Kafka Stream consumer offset by timestamp

You can always built you own little tool similar to StreamsResetter.java to get this done. Ie, you set the committed offset "manually" based on timestamps before you start your application. But as Eno mentioned, you need to think carefully about what a consistent reset point would be because you c

Jenkins build is back to normal : kafka-trunk-jdk8 #1233

See

[GitHub] kafka pull request #2464: KAFKA-4662: adding test coverage for addSource met...

GitHub user bbejeck opened a pull request: https://github.com/apache/kafka/pull/2464 KAFKA-4662: adding test coverage for addSource methods with AutoOffse… …tReset You can merge this pull request into a Git repository by running: $ git pull https://github.com/bbejeck/kafka

Re: [DISCUSS] KIP-114: KTable materialization and improved semantics

Thinking loud here about the API options (materialize v.s. overloaded functions) and its impact on IQ: 1. The first issue of the current DSL is that, there is inconsistency upon whether / how KTables should be materialized: a) in many cases the library HAS TO materialize KTables no matter wha