[jira] [Created] (KAFKA-4024) First metadata update always take retry.backoff.ms milliseconds to complete

Yuto Kawamura created KAFKA-4024: Summary: First metadata update always take retry.backoff.ms milliseconds to complete Key: KAFKA-4024 URL: https://issues.apache.org/jira/browse/KAFKA-4024 Project: Ka

[jira] [Commented] (KAFKA-4024) First metadata update always take retry.backoff.ms milliseconds to complete

[ https://issues.apache.org/jira/browse/KAFKA-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410560#comment-15410560 ] Yuto Kawamura commented on KAFKA-4024: -- I guess this problem is fairly easy to fix, j

[GitHub] kafka pull request #1707: KAFKA-4024 KafkaProducer should not initialize met...

GitHub user kawamuray opened a pull request: https://github.com/apache/kafka/pull/1707 KAFKA-4024 KafkaProducer should not initialize metadata with current timestamp Issue: https://issues.apache.org/jira/browse/KAFKA-4024 Solves the problem that the first metadata update of

[jira] [Commented] (KAFKA-4024) First metadata update always take retry.backoff.ms milliseconds to complete

[ https://issues.apache.org/jira/browse/KAFKA-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410563#comment-15410563 ] ASF GitHub Bot commented on KAFKA-4024: --- GitHub user kawamuray opened a pull request

[jira] [Updated] (KAFKA-4024) First metadata update always take retry.backoff.ms milliseconds to complete

[ https://issues.apache.org/jira/browse/KAFKA-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuto Kawamura updated KAFKA-4024: - Status: Patch Available (was: Open) > First metadata update always take retry.backoff.ms millisec

[jira] [Commented] (KAFKA-4024) First metadata update always take retry.backoff.ms milliseconds to complete

[ https://issues.apache.org/jira/browse/KAFKA-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410571#comment-15410571 ] Yuto Kawamura commented on KAFKA-4024: -- Submitted a patch. It actually leads a side e

[jira] [Commented] (KAFKA-4024) First metadata update always take retry.backoff.ms milliseconds to complete

[ https://issues.apache.org/jira/browse/KAFKA-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410572#comment-15410572 ] Yuto Kawamura commented on KAFKA-4024: -- [~ijuma] or [~hachikuji] PTAL. > First metad

[jira] [Commented] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410682#comment-15410682 ] Flavio Junqueira commented on KAFKA-1211: - [~junrao] I get (2), but (1) might need

[jira] [Commented] (KAFKA-4014) Use Collections.singletonList instead of Arrays.asList for single arguments

[ https://issues.apache.org/jira/browse/KAFKA-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410686#comment-15410686 ] ASF GitHub Bot commented on KAFKA-4014: --- Github user rekhajoshm closed the pull requ

[GitHub] kafka pull request #1697: KAFKA-4014; Using Collections.singletonList instea...

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

[jira] [Commented] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410693#comment-15410693 ] Flavio Junqueira commented on KAFKA-1211: - [~junrao] I was reading point (a) in yo

[GitHub] kafka pull request #1527: KAFKA-3809: Auto-generate documentation for topic-...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1527 --- 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] [Updated] (KAFKA-3809) Auto-generate documentation for topic-level configuration

[ https://issues.apache.org/jira/browse/KAFKA-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3809: - Resolution: Fixed Fix Version/s: 0.10.1.0 Status: Resolved (was:

[jira] [Commented] (KAFKA-3809) Auto-generate documentation for topic-level configuration

[ https://issues.apache.org/jira/browse/KAFKA-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410784#comment-15410784 ] ASF GitHub Bot commented on KAFKA-3809: --- Github user asfgit closed the pull request

[jira] [Created] (KAFKA-4025) build fails on windows due to rat target output encoding

radai rosenblatt created KAFKA-4025: --- Summary: build fails on windows due to rat target output encoding Key: KAFKA-4025 URL: https://issues.apache.org/jira/browse/KAFKA-4025 Project: Kafka

[jira] [Updated] (KAFKA-4025) build fails on windows due to rat target output encoding

[ https://issues.apache.org/jira/browse/KAFKA-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] radai rosenblatt updated KAFKA-4025: Environment: windows 7, either regular command prompt or git bash (was: windows 7, wither r

[jira] [Updated] (KAFKA-4025) build fails on windows due to rat target output encoding

[ https://issues.apache.org/jira/browse/KAFKA-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] radai rosenblatt updated KAFKA-4025: Attachment: windows build debug output.txt debug output for running the rat task on windows

[GitHub] kafka pull request #1708: KAFKA-4025 - make sure file.encoding system proper...

GitHub user radai-rosenblatt opened a pull request: https://github.com/apache/kafka/pull/1708 KAFKA-4025 - make sure file.encoding system property is set to UTF-8 when invoking the rat task reset back to previous value after. You can merge this pull request into a Git repository by

[jira] [Commented] (KAFKA-4025) build fails on windows due to rat target output encoding

[ https://issues.apache.org/jira/browse/KAFKA-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410798#comment-15410798 ] ASF GitHub Bot commented on KAFKA-4025: --- GitHub user radai-rosenblatt opened a pull

Build failed in Jenkins: kafka-trunk-jdk8 #802

See Changes: [me] KAFKA-3809: Auto-generate documentation for topic-level configuration -- [...truncated 3393 lines...] kafka.api.AuthorizerIntegrationTest > testProduceWithTopicWrite STARTED k

Jenkins build is back to normal : kafka-trunk-jdk7 #1464

See

[jira] [Resolved] (KAFKA-4002) task.open() should be invoked in case that 0 partitions is assigned to task.

[ https://issues.apache.org/jira/browse/KAFKA-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4002. -- Resolution: Fixed Fix Version/s: (was: 0.11.0.0) 0.

[jira] [Commented] (KAFKA-4002) task.open() should be invoked in case that 0 partitions is assigned to task.

[ https://issues.apache.org/jira/browse/KAFKA-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410819#comment-15410819 ] ASF GitHub Bot commented on KAFKA-4002: --- Github user asfgit closed the pull request

[GitHub] kafka pull request #1686: KAFKA-4002: task.open() should be invoked in case ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1686 --- 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-2932) Adjust importance level of Kafka Connect configs

[ https://issues.apache.org/jira/browse/KAFKA-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-2932. -- Resolution: Fixed Fix Version/s: 0.10.1.0 Issue resolved by pull request

[GitHub] kafka pull request #1653: KAFKA-2932: Adjust importance level of Kafka Conne...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1653 --- 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] [Commented] (KAFKA-2932) Adjust importance level of Kafka Connect configs

[ https://issues.apache.org/jira/browse/KAFKA-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410828#comment-15410828 ] ASF GitHub Bot commented on KAFKA-2932: --- Github user asfgit closed the pull request

Build failed in Jenkins: kafka-trunk-jdk7 #1465

See Changes: [me] KAFKA-4002: task.open() should be invoked in case that 0 partitions is -- [...truncated 3362 lines...] kafka.message.ByteBufferMessageSetTest > testValidBytesWithCompression S

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

See