[jira] [Created] (KAFKA-5537) Subscribe Earliest is not working as in 0.10.2.1

Michael Andre Pearce created KAFKA-5537: --- Summary: Subscribe Earliest is not working as in 0.10.2.1 Key: KAFKA-5537 URL: https://issues.apache.org/jira/browse/KAFKA-5537 Project: Kafka

[jira] [Created] (KAFKA-5536) Tools splitted between Java and Scala implementation

Paolo Patierno created KAFKA-5536: - Summary: Tools splitted between Java and Scala implementation Key: KAFKA-5536 URL: https://issues.apache.org/jira/browse/KAFKA-5536 Project: Kafka Issue Ty

Re: [DISCUSS] Streams DSL/StateStore Refactoring

Hi Guozhang, Thanks for the feedback On Thu, 29 Jun 2017 at 01:45 Guozhang Wang wrote: > I played the current proposal a bit with https://github.com/dguy/kafka/ > tree/dsl-experiment , > and here are my observations: > > 1. Personally I prefer

Re: [DISCUSS] Streams DSL/StateStore Refactoring

Hi Kyle, Thanks for your input. Really appreciated. On Thu, 29 Jun 2017 at 06:09 Kyle Winkelman wrote: > I like more of a builder pattern even though others have voiced against > it. The reason I like it is because it makes it clear to the user that a > call to KGroupedStream#count will return

Re: [DISCUSS] Streams DSL/StateStore Refactoring

> However, I don't understand your argument about putting aggregate() > after the withXX() -- all the calls to withXX() set optional parameters > for aggregate() and not for groupBy() -- but a groupBy().withXX() > indicates that the withXX() belongs to the groupBy(). IMHO, this might > be quite con

[jira] [Created] (KAFKA-5538) User-specified Producer/Consumer config doesn't effect with KafkaBackingStore(Config/Status/Offset)

Aegeaner created KAFKA-5538: --- Summary: User-specified Producer/Consumer config doesn't effect with KafkaBackingStore(Config/Status/Offset) Key: KAFKA-5538 URL: https://issues.apache.org/jira/browse/KAFKA-5538

Re: [DISCUSS] Streams DSL/StateStore Refactoring

I've updated the experimental code with a couple of ways of doing joins. One following the fluent approach and one following the builder approach. The 2 examples can be found here: https://github.com/dguy/kafka/blob/dsl-experiment/streams/src/test/java/org/apache/kafka/streams/kstream/internals/KSt

[GitHub] kafka pull request #3458: KAFKA-5538: User-specified Producer/Consumer confi...

GitHub user Aegeaner opened a pull request: https://github.com/apache/kafka/pull/3458 KAFKA-5538: User-specified Producer/Consumer config doesn't effect wi… For configuration of Kafka source and Kafka sink tasks, the same parameters can be used but need to be prefixed with consume

[GitHub] kafka pull request #3303: KAFKA-5402: Avoid creating quota related metrics i...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3303 --- 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

[jira] [Resolved] (KAFKA-5402) JmxReporter Fetch metrics for kafka.server should not be created when client quotas are not enabled

[ https://issues.apache.org/jira/browse/KAFKA-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-5402. --- Resolution: Fixed Fix Version/s: 0.11.1.0 Issue resolved by pull request 3303 [https://

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

See

RE: [DISCUSS] Streams DSL/StateStore Refactoring

Hi Damian, When trying to program in the fluent API that has been discussed most it feels difficult to know when you will actually get an object you can reuse. What if I make one KGroupedStream that I want to reuse, is it legal to reuse it or does this approach expect you to ca

Re: [DISCUSS] KIP-171: Extend Consumer Group Reset Offset for Stream Application

You're right, I was not considering Zookeeper dependency. I'm starting to like the idea to wrap `reset-offset` from `streams-application-reset`. I will wait a bit for more feedback and work on a draft with this changes. El mié., 28 jun. 2017 a las 0:20, Matthias J. Sax () escribió: > I agree,

Re: [DISCUSS] Streams DSL/StateStore Refactoring

Thanks Kyle. On Thu, 29 Jun 2017 at 15:11 Kyle Winkelman wrote: > Hi Damian, > > When trying to program in the fluent API that has been discussed most > it > feels difficult to know when you will actually get an object you can > reuse. > What if I make one KGroupedStream that I wa

[jira] [Created] (KAFKA-5539) Kafka Connect plugin.path is not used

Diego Montesinos created KAFKA-5539: --- Summary: Kafka Connect plugin.path is not used Key: KAFKA-5539 URL: https://issues.apache.org/jira/browse/KAFKA-5539 Project: Kafka Issue Type: Bug

[GitHub] kafka pull request #3459: KAFKA-3741: allow users to specify default topic c...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3459 KAFKA-3741: allow users to specify default topic configs for internal topics Allow users to specify default topic configs for streams internal topics by supplying properties from `TopicConfig` with a p

Re: [DISCUSS] KIP-171: Extend Consumer Group Reset Offset for Stream Application

Hi, Thanks for the KIP. What is not clear is how is this going to handle state stores? Right now the streams reset tool, resets everything and clears up the state stores. What are we going to do if we reset to a particular offset? If we clear the state then we've lost any previously aggregated val

[GitHub] kafka pull request #3446: MINOR: Improve TransactionIndex.sanityCheck() mess...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3446 --- 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-167: Add a restoreAll method to StateRestoreCallback

All, I've updated the KIP and I'd like to start a final round of discussion with an eye towards starting a vote soon, maybe on Monday. Thanks, Bill On Mon, Jun 26, 2017 at 7:26 PM, Guozhang Wang wrote: > Hmm... I'm not sure how this can achieve "closing the store before > restoration, re-open

Re: [DISCUSS] KIP-171: Extend Consumer Group Reset Offset for Stream Application

Damian, > resets everything and clears up >> the state stores. That's not correct. The reset tool does not touch local store. For this, we have `KafkaStreams#clenup` -- otherwise, you would need to run the tool in every machine you run an application instance. With regard to state, the tool only

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

Thanks for updating the KIP. I have one concern with regard to backward compatibility. You suggest to use RecrodContext as base interface for ProcessorContext. This will break compatibility. I think, we should just have two independent interfaces. Our own ProcessorContextImpl class would implemen

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

One more thing: I don't think `RichInitializer` does make sense. As we don't have any input record, there is also no context. We could of course provide the context of the record that triggers the init call, but this seems to be semantically questionable. Also, the context for this first record wi

[GitHub] kafka pull request #3389: KAFKA-5484: Refactor kafkatest docker support

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3389 --- 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

[jira] [Resolved] (KAFKA-5484) Refactor kafkatest docker support

[ https://issues.apache.org/jira/browse/KAFKA-5484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5484. -- Resolution: Fixed Fix Version/s: 0.11.0.1 0.10.2.2

[jira] [Created] (KAFKA-5540) Deprecate and remove internal converter configs

Ewen Cheslack-Postava created KAFKA-5540: Summary: Deprecate and remove internal converter configs Key: KAFKA-5540 URL: https://issues.apache.org/jira/browse/KAFKA-5540 Project: Kafka

[jira] [Created] (KAFKA-5541) Streams should not re-throw if suspending/closing task fails

Matthias J. Sax created KAFKA-5541: -- Summary: Streams should not re-throw if suspending/closing task fails Key: KAFKA-5541 URL: https://issues.apache.org/jira/browse/KAFKA-5541 Project: Kafka

[jira] [Resolved] (KAFKA-5299) MirrorMaker with New.consumer doesn't consume message from multiple topics whitelisted

[ https://issues.apache.org/jira/browse/KAFKA-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman resolved KAFKA-5299. Resolution: Cannot Reproduce > MirrorMaker with New.consumer doesn't consume message from multiple t

[GitHub] kafka pull request #3460: KAFKA-5534: `offsetForTimes` result should include...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/3460 KAFKA-5534: `offsetForTimes` result should include partitions with no offset For topics that support timestamp search, if no offset is found for a partition, the partition should still be inc

[jira] [Created] (KAFKA-5542) Improve Java doc for LeaderEpochFileCache.endOffsetFor()

Dong Lin created KAFKA-5542: --- Summary: Improve Java doc for LeaderEpochFileCache.endOffsetFor() Key: KAFKA-5542 URL: https://issues.apache.org/jira/browse/KAFKA-5542 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-5543) We don't remove the LastStableOffsetLag metric when a partition is moved away from a broker

Apurva Mehta created KAFKA-5543: --- Summary: We don't remove the LastStableOffsetLag metric when a partition is moved away from a broker Key: KAFKA-5543 URL: https://issues.apache.org/jira/browse/KAFKA-5543

[GitHub] kafka pull request #3461: MINOR: need to be backwards compatible with deprec...

GitHub user bbejeck opened a pull request: https://github.com/apache/kafka/pull/3461 MINOR: need to be backwards compatible with deprecated default config… …s until removed You can merge this pull request into a Git repository by running: $ git pull https://github.com/bbeje

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Hi Jeyhun, thanks for starting the VOTE thread. I did make one more pass over the KIP before casting my vote and I saw that the KIP still contains backward incompatible change introducing `ValueTransformerCommon`. I think, that for this case, it is not worth breaking compatibility. We should have

[GitHub] kafka pull request #3462: KAFKA-5543: Remove all partition metrics when a to...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3462 KAFKA-5543: Remove all partition metrics when a topic is deleted You can merge this pull request into a Git repository by running: $ git pull https://github.com/apurvam/kafka KAFKA-5543-remov

[jira] [Created] (KAFKA-5544) The LastStableOffsetLag metric should be removed when partition is deleted

Dong Lin created KAFKA-5544: --- Summary: The LastStableOffsetLag metric should be removed when partition is deleted Key: KAFKA-5544 URL: https://issues.apache.org/jira/browse/KAFKA-5544 Project: Kafka

[GitHub] kafka pull request #3463: KAFKA-5544; The LastStableOffsetLag metric should ...

GitHub user lindong28 opened a pull request: https://github.com/apache/kafka/pull/3463 KAFKA-5544; The LastStableOffsetLag metric should be removed when partition is deleted You can merge this pull request into a Git repository by running: $ git pull https://github.com/lindon

[jira] [Resolved] (KAFKA-5458) SASL handshake fails for METADATA requests

[ https://issues.apache.org/jira/browse/KAFKA-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Lad resolved KAFKA-5458. -- Resolution: Fixed actually there were multiple consumers created from code - each with different confi

[GitHub] kafka pull request #3464: MINOR: Enable a number of xlint scalac warnings

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3464 MINOR: Enable a number of xlint scalac warnings Update the code where possible to fix the warnings. The unused warning introduced in Scala 2.12 is quite handy and provides a reason to compile w

[GitHub] kafka pull request #3463: KAFKA-5544; The LastStableOffsetLag metric should ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3463 --- 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

[GitHub] kafka pull request #3457: MINOR: Rename baseTimestamp to firstTimestamp to c...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3457 --- 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

[jira] [Resolved] (KAFKA-5544) The LastStableOffsetLag metric should be removed when partition is deleted

[ https://issues.apache.org/jira/browse/KAFKA-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5544. Resolution: Fixed > The LastStableOffsetLag metric should be removed when partition is deleted > ---