[jira] [Updated] (KAFKA-4967) java.io.EOFException Error while committing offsets

[ https://issues.apache.org/jira/browse/KAFKA-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Upendra Yadav updated KAFKA-4967: - Description: kafka server and client : 0.10.0.1 And consumer and producer side using latest kafka

[jira] [Updated] (KAFKA-4967) java.io.EOFException Error while committing offsets

[ https://issues.apache.org/jira/browse/KAFKA-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Upendra Yadav updated KAFKA-4967: - Description: kafka server and client : 0.10.0.1 And consumer and producer side using latest kafka

[jira] [Created] (KAFKA-5047) NullPointerException while using GlobalKTable in KafkaStreams

Ivan Ursul created KAFKA-5047: - Summary: NullPointerException while using GlobalKTable in KafkaStreams Key: KAFKA-5047 URL: https://issues.apache.org/jira/browse/KAFKA-5047 Project: Kafka Issue

[jira] [Updated] (KAFKA-5047) NullPointerException while using GlobalKTable in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Ursul updated KAFKA-5047: -- Description: Main.java : https://gist.github.com/ivanursul/dcd4bb382c05843606a96417561b4b31 pom.xml : ht

[jira] [Updated] (KAFKA-5047) NullPointerException while using GlobalKTable in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Ursul updated KAFKA-5047: -- Description: Main.java : https://gist.github.com/ivanursul/dcd4bb382c05843606a96417561b4b31 pom.xml : ht

[jira] [Updated] (KAFKA-5047) NullPointerException while using GlobalKTable in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Ursul updated KAFKA-5047: -- Description: Main.java : https://gist.github.com/ivanursul/dcd4bb382c05843606a96417561b4b31 pom.xml : ht

[jira] [Updated] (KAFKA-5047) NullPointerException while using GlobalKTable in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Ursul updated KAFKA-5047: -- Description: Main.java : https://gist.github.com/ivanursul/dcd4bb382c05843606a96417561b4b31 pom.xml : ht

[jira] [Updated] (KAFKA-5047) NullPointerException while using GlobalKTable in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Ursul updated KAFKA-5047: -- Component/s: streams > NullPointerException while using GlobalKTable in KafkaStreams > -

[jira] [Updated] (KAFKA-5047) NullPointerException while using GlobalKTable in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Ursul updated KAFKA-5047: -- Priority: Trivial (was: Major) > NullPointerException while using GlobalKTable in KafkaStreams > --

[jira] [Updated] (KAFKA-5047) NullPointerException while using GlobalKTable in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Ursul updated KAFKA-5047: -- Description: Main.java : https://gist.github.com/ivanursul/dcd4bb382c05843606a96417561b4b31 pom.xml : ht

[jira] [Commented] (KAFKA-5044) max.in.flight.requests.per.connection > 1 is ineffective

[ https://issues.apache.org/jira/browse/KAFKA-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962709#comment-15962709 ] Rajini Sivaram commented on KAFKA-5044: --- [~twbecker] {{max.in.flight.requests.per.co

[jira] [Commented] (KAFKA-5044) max.in.flight.requests.per.connection > 1 is ineffective

[ https://issues.apache.org/jira/browse/KAFKA-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962713#comment-15962713 ] Ismael Juma commented on KAFKA-5044: Heh, I just wrote something similar in the PR. :)

Re: [VOTE] KIP-86: Configurable SASL callback handlers

+1 (non binding) many thanks Rajini ! -- Edoardo Comar IBM MessageHub eco...@uk.ibm.com IBM UK Ltd, Hursley Park, SO21 2JN IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Po

[GitHub] kafka pull request #2827: Fix KAFKA-5044.

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

[jira] [Commented] (KAFKA-5044) max.in.flight.requests.per.connection > 1 is ineffective

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

[jira] [Commented] (KAFKA-5044) max.in.flight.requests.per.connection > 1 is ineffective

[ https://issues.apache.org/jira/browse/KAFKA-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962742#comment-15962742 ] Tommy Becker commented on KAFKA-5044: - Thanks for the explanation; closing this issue.

[jira] [Resolved] (KAFKA-5044) max.in.flight.requests.per.connection > 1 is ineffective

[ https://issues.apache.org/jira/browse/KAFKA-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Becker resolved KAFKA-5044. - Resolution: Invalid > max.in.flight.requests.per.connection > 1 is ineffective > -

Re: [DISCUSS] KIP-138: Change punctuate semantics

Thanks Ewen. @Michal, @all, I have created a child page to start the Use Cases discussion [https://cwiki.apache.org/confluence/display/KAFKA/Punctuate+Use+Cases]. Please go through it and give your comments. @Tianji, Sorry for the delay. I am trying to make the patch public. -- Arun Mathew On

[jira] [Commented] (KAFKA-4982) Add listener tag to socket-server-metrics.connection-... metrics

[ https://issues.apache.org/jira/browse/KAFKA-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962765#comment-15962765 ] Edoardo Comar commented on KAFKA-4982: -- KIP is https://cwiki.apache.org/confluence/di

[jira] [Created] (KAFKA-5048) kafka brokers hangup when one of broker node in the cluster is killed and remaining nodes are not consuming the data.

Srinivas Yarra created KAFKA-5048: - Summary: kafka brokers hangup when one of broker node in the cluster is killed and remaining nodes are not consuming the data. Key: KAFKA-5048 URL: https://issues.apache.org/jir

[jira] [Updated] (KAFKA-5048) kafka brokers hangup when one of broker node in the cluster is killed and remaining nodes are not consuming the data.

[ https://issues.apache.org/jira/browse/KAFKA-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinivas Yarra updated KAFKA-5048: -- Environment: (was: Three Node cluster.) > kafka brokers hangup when one of broker node in th

[jira] [Commented] (KAFKA-5048) kafka brokers hangup when one of broker node in the cluster is killed and remaining nodes are not consuming the data.

[ https://issues.apache.org/jira/browse/KAFKA-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962809#comment-15962809 ] Srinivas Yarra commented on KAFKA-5048: --- I am using three node cluster. > kafka bro

[jira] [Comment Edited] (KAFKA-5048) kafka brokers hangup when one of broker node in the cluster is killed and remaining nodes are not consuming the data.

[ https://issues.apache.org/jira/browse/KAFKA-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962809#comment-15962809 ] Srinivas Yarra edited comment on KAFKA-5048 at 4/10/17 1:02 PM:

[jira] [Created] (KAFKA-5049) Chroot check should be done for each ZkUtils instance

Ismael Juma created KAFKA-5049: -- Summary: Chroot check should be done for each ZkUtils instance Key: KAFKA-5049 URL: https://issues.apache.org/jira/browse/KAFKA-5049 Project: Kafka Issue Type: B

[GitHub] kafka pull request #2831: MINOR: KAFKA-5036 (points 2, 5): Refactor caching ...

GitHub user benstopford opened a pull request: https://github.com/apache/kafka/pull/2831 MINOR: KAFKA-5036 (points 2, 5): Refactor caching of Latest Epoch This PR covers point (2) and point (5) from KAFKA-5036: 2. Currently, we update the leader epoch in epochCache after log appe

[jira] [Commented] (KAFKA-5036) Followups from KIP-101

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

[jira] [Commented] (KAFKA-5036) Followups from KIP-101

[ https://issues.apache.org/jira/browse/KAFKA-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962827#comment-15962827 ] Ben Stopford commented on KAFKA-5036: - Points 2, 5 are addressed in PR: https://github

[GitHub] kafka pull request #2832: KAFKA-5045: KTable cleanup [WiP]

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2832 KAFKA-5045: KTable cleanup [WiP] You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka KAFKA-5045-ktable Alternatively you can

[jira] [Commented] (KAFKA-5045) KTable materialization and improved semantics

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

[jira] [Updated] (KAFKA-5048) kafka brokers hang when one of broker node in the cluster is killed and remaining nodes are not consuming the data.

[ https://issues.apache.org/jira/browse/KAFKA-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinivas Yarra updated KAFKA-5048: -- Description: Kafka brokers hang when one of broker node killed in cluster and remaining broker

[jira] [Updated] (KAFKA-5048) kafka brokers hang when one of broker node killed in the cluster and remaining broker nodes are not consuming the data.

[ https://issues.apache.org/jira/browse/KAFKA-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinivas Yarra updated KAFKA-5048: -- Summary: kafka brokers hang when one of broker node killed in the cluster and remaining broker n

[GitHub] kafka pull request #2829: HOTFIX: Use a true sentinel for `UseDefaultAcls`

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2829 --- 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] [Created] (KAFKA-5050) Implement Plain Ldap Authentication

nihed mbarek created KAFKA-5050: --- Summary: Implement Plain Ldap Authentication Key: KAFKA-5050 URL: https://issues.apache.org/jira/browse/KAFKA-5050 Project: Kafka Issue Type: New Feature

[GitHub] kafka pull request #2833: KAFKA-5050 add ldap authentication support on Plai...

GitHub user nihed opened a pull request: https://github.com/apache/kafka/pull/2833 KAFKA-5050 add ldap authentication support on PlainSaslServer This feature will provide a way to add ldap authentication on PlainSaslServer. Our Jaas Server configuration will be : KafkaServ

[jira] [Updated] (KAFKA-5047) NullPointerException while using GlobalKTable in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5047: --- Priority: Major (was: Trivial) > NullPointerException while using GlobalKTable in KafkaStream

[jira] [Assigned] (KAFKA-5047) NullPointerException while using GlobalKTable in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-5047: - Assignee: Damian Guy > NullPointerException while using GlobalKTable in KafkaStreams > --

[jira] [Commented] (KAFKA-5047) NullPointerException while using GlobalKTable in KafkaStreams

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

[GitHub] kafka pull request #2834: KAFKA-5047: NullPointerException while using Globa...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2834 KAFKA-5047: NullPointerException while using GlobalKTable in KafkaStreams Skip null keys when initializing GlobalKTables. This is inline with what happens during normal processing. You can merge this

Re: [VOTE] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Ping Ismael. Thanks, Mayuresh On Thu, Apr 6, 2017 at 9:50 AM, Mayuresh Gharat wrote: > Hi Ismael, > > Are you suggesting to use the InvalidRecordException when the key is null? > > Thanks, > > Mayuresh > > On Thu, Apr 6, 2017 at 8:49 AM, Ismael Juma wrote: > >> Hi Mayuresh, >> >> I took a clo

How about releasing 9.0.2

Hi guys, I am monitoring jira milestone 0.9.0.2. All issues are fixed now so I have some questions: Will there be a 0.9.0.2? When will it be released? Is 0.10.X backwards compatible to 0.9 clients? Is there anything I need to care about when migrating? Best Regards Alexander

[jira] [Assigned] (KAFKA-4564) When the destination brokers are down or misconfigured in config, Streams should fail fast

[ https://issues.apache.org/jira/browse/KAFKA-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-4564: -- Assignee: Matthias J. Sax (was: Umesh Chaudhary) > When the destination brokers are do

[jira] [Work started] (KAFKA-4564) When the destination brokers are down or misconfigured in config, Streams should fail fast

[ https://issues.apache.org/jira/browse/KAFKA-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4564 started by Matthias J. Sax. -- > When the destination brokers are down or misconfigured in config, Streams

Re: [VOTE] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Hi Mayuresh, I was suggesting that we introduce a new error code for non retriable invalid record exceptions (not sure what's a good name). We would then change LogValidator and Log to use this new exception wherever it makes sense (errors that are not retriable). One of many such cases is https:/

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

See

[jira] [Updated] (KAFKA-5047) NullPointerException while using GlobalKTable in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5047: -- Status: Patch Available (was: Open) > NullPointerException while using GlobalKTable in KafkaStreams > -

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

See -- [...truncated 184.28 KB...] kafka.server.DynamicConfigTest > shouldFailLeaderConfigsWithInvalidValues STARTED kafka.server.DynamicConfigTest > shouldFailLeaderConfigsWithInvalid

[jira] [Commented] (KAFKA-5016) Consumer hang in poll method while rebalancing is in progress

[ https://issues.apache.org/jira/browse/KAFKA-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963299#comment-15963299 ] Vahid Hashemian commented on KAFKA-5016: [~ijuma] Sure, I'll take a look. [~domeni

[jira] [Updated] (KAFKA-5016) Consumer hang in poll method while rebalancing is in progress

[ https://issues.apache.org/jira/browse/KAFKA-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Domenico Di Giulio updated KAFKA-5016: -- I am currently out of the office, with limited access to my e-mail. I will be back at work o

[jira] [Assigned] (KAFKA-5016) Consumer hang in poll method while rebalancing is in progress

[ https://issues.apache.org/jira/browse/KAFKA-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-5016: -- Assignee: Vahid Hashemian > Consumer hang in poll method while rebalancing is in progre

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

See -- [...truncated 185.67 KB...] kafka.utils.timer.TimerTaskListTest > testAll STARTED kafka.utils.timer.TimerTaskListTest > testAll PASSED kafka.utils.CommandLineUtilsTest > testPar

Re: [VOTE] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Got it. We can probably extend the InvalidRecordException with a more specific exception this use case and make it first class for produce side OR we can add an error code for InvalidRecordException in the Errors class and make it first class. I am fine either ways. What do you prefer? Thanks, Ma

[jira] [Commented] (KAFKA-4950) ConcurrentModificationException when iterating over Kafka Metrics

[ https://issues.apache.org/jira/browse/KAFKA-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963308#comment-15963308 ] Vahid Hashemian commented on KAFKA-4950: [~ijuma] Yup, thanks! > ConcurrentModifi

[jira] [Commented] (KAFKA-3355) GetOffsetShell command doesn't work with SASL enabled Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963307#comment-15963307 ] Fred Ji commented on KAFKA-3355: Thanks for fixing this one! what version of kafka has thi

[jira] [Commented] (KAFKA-4419) Unable to GetOffset when the ACL of topic is defined

[ https://issues.apache.org/jira/browse/KAFKA-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963310#comment-15963310 ] Fred Ji commented on KAFKA-4419: [~rsivaram], what version of kafka has this fix in? > Un

[jira] [Comment Edited] (KAFKA-4419) Unable to GetOffset when the ACL of topic is defined

[ https://issues.apache.org/jira/browse/KAFKA-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963310#comment-15963310 ] Fred Ji edited comment on KAFKA-4419 at 4/10/17 6:35 PM: - [~rsivar

[jira] [Created] (KAFKA-5051) Avoid DNS reverse lookup in security-critical TLS code path

Rajini Sivaram created KAFKA-5051: - Summary: Avoid DNS reverse lookup in security-critical TLS code path Key: KAFKA-5051 URL: https://issues.apache.org/jira/browse/KAFKA-5051 Project: Kafka

[jira] [Comment Edited] (KAFKA-3355) GetOffsetShell command doesn't work with SASL enabled Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963307#comment-15963307 ] Fred Ji edited comment on KAFKA-3355 at 4/10/17 6:36 PM: - [~singha

[jira] [Updated] (KAFKA-5036) Followups from KIP-101

[ https://issues.apache.org/jira/browse/KAFKA-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-5036: Description: 1. It would be safer to hold onto the leader lock in Partition while serving an Offset

[jira] [Comment Edited] (KAFKA-5036) Followups from KIP-101

[ https://issues.apache.org/jira/browse/KAFKA-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962827#comment-15962827 ] Ben Stopford edited comment on KAFKA-5036 at 4/10/17 6:42 PM: --

[GitHub] kafka pull request #2835: KAFKA-5051: Avoid reverse DNS lookup to obtain hos...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/2835 KAFKA-5051: Avoid reverse DNS lookup to obtain hostname for TLS You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka KAFKA-

[jira] [Commented] (KAFKA-5051) Avoid DNS reverse lookup in security-critical TLS code path

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

[GitHub] kafka pull request #2836: MINOR: improve test stability for Streams broker-c...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2836 MINOR: improve test stability for Streams broker-compatibility test You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka minor-broker-comp-

[jira] [Assigned] (KAFKA-4950) ConcurrentModificationException when iterating over Kafka Metrics

[ https://issues.apache.org/jira/browse/KAFKA-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-4950: -- Assignee: Vahid Hashemian > ConcurrentModificationException when iterating over Kafka M

[jira] [Issue Comment Deleted] (KAFKA-5016) Consumer hang in poll method while rebalancing is in progress

[ https://issues.apache.org/jira/browse/KAFKA-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Domenico Di Giulio updated KAFKA-5016: -- Comment: was deleted (was: I am currently out of the office, with limited access to my e

[jira] [Created] (KAFKA-5052) We shouldn't pass the underlying exception to RetriableCommitFailedException when an async offset commit fails.

Apurva Mehta created KAFKA-5052: --- Summary: We shouldn't pass the underlying exception to RetriableCommitFailedException when an async offset commit fails. Key: KAFKA-5052 URL: https://issues.apache.org/jira/browse/K

[GitHub] kafka pull request #2837: KAFKA-4564: Add system test for pre-0.10 brokers

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2837 KAFKA-4564: Add system test for pre-0.10 brokers You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka kafka-4564-fail-fast-test-stream-com

[jira] [Commented] (KAFKA-4564) When the destination brokers are down or misconfigured in config, Streams should fail fast

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

[jira] [Created] (KAFKA-5053) Send Error messages along with FindCoordinatorResponse

Apurva Mehta created KAFKA-5053: --- Summary: Send Error messages along with FindCoordinatorResponse Key: KAFKA-5053 URL: https://issues.apache.org/jira/browse/KAFKA-5053 Project: Kafka Issue Type

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

Thanks for pushing this KIP Eno. The update give a very clear description about the scope, that is super helpful for the discussion! - To put it into my own words, the KIP focus is on enable to query all KTables. ** The ability to query a store is determined by providing a name for the store.

Re: [DISCUSS] KIP-138: Change punctuate semantics

Thanks for preparing this page! About terminology: You introduce the term "event time" -- but we should call this "stream time" -- "stream time" is whatever TimestampExtractor returns and this could be event time, ingestion time, or processing/wall-clock time. Does this make sense to you? -Ma

Re: [DISCUSS] KIP-138: Change punctuate semantics

Thanks Matthias. Sure, will correct it right away. On 11-Apr-2017 8:07 AM, "Matthias J. Sax" wrote: Thanks for preparing this page! About terminology: You introduce the term "event time" -- but we should call this "stream time" -- "stream time" is whatever TimestampExtractor returns and this c

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

Hi Matthias, > However, this still forces users, to provide a name for store that we > must materialize, even if users are not interested in querying the > stores. Thus, I would like to have overloads for all currently existing > methods having mandatory storeName paremeter, with overloads, that d

[jira] [Updated] (KAFKA-5052) We shouldn't pass the underlying exception to RetriableCommitFailedException when an async offset commit fails.

[ https://issues.apache.org/jira/browse/KAFKA-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5052: --- Description: This is a follow up to : https://issues.apache.org/jira/browse/KAFKA-3527 We currently w

[jira] [Updated] (KAFKA-5052) We shouldn't pass the underlying exception to RetriableCommitFailedException when an async offset commit fails.

[ https://issues.apache.org/jira/browse/KAFKA-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5052: --- Fix Version/s: 0.11.0.0 > We shouldn't pass the underlying exception to RetriableCommitFailedException

[jira] [Resolved] (KAFKA-5052) We shouldn't pass the underlying exception to RetriableCommitFailedException when an async offset commit fails.

[ https://issues.apache.org/jira/browse/KAFKA-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5052. Resolution: Fixed Issue resolved by pull request 2838 [https://github.com/apache/kafka/pull/2838] >

[GitHub] kafka pull request #2838: KAFKA-5052 : Don't send undelying exception to Ret...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2838 --- 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-5052) We shouldn't pass the underlying exception to RetriableCommitFailedException when an async offset commit fails.

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

[jira] [Commented] (KAFKA-5019) Exactly-once upgrade notes

[ https://issues.apache.org/jira/browse/KAFKA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963676#comment-15963676 ] Ismael Juma commented on KAFKA-5019: Include a note about KAFKA-5052. > Exactly-once

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

See

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

See Changes: [ismael] KAFKA-5052; Don't pass underlying internal exception to -- [...truncated 707.75 KB...] org.apache.kafka.common.utils.ChecksumsTest > testUpdateByteB

[jira] [Updated] (KAFKA-4967) java.io.EOFException Error while committing offsets

[ https://issues.apache.org/jira/browse/KAFKA-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Upendra Yadav updated KAFKA-4967: - Description: kafka server and client : 0.10.0.1 And consumer and producer side using latest kafka

Credentials for Confluence

Hi, I’d like to create a KIP on Confluence but according to Matthias Sax I need credentials. Can you please provide me some? Looking forward to redacting my first KIP :) Regards, Stephane