Re: Kafka Connect: To much restarting with a SourceConnector with dynamic set of tasks

Thanks a lot for responding, Randall! See my comments below. Regards, Per Steffensen On 22/05/17 22:36, Randall Hauch wrote: You're not doing anything wrong, but I suspect you're requesting task reconfiguration more frequently than was originally envisioned, which means that the current implem

Re: Can I get a review for a PR for KAFKA-5191?

James, I left some comments on https://github.com/apache/kafka/pull/2993#pullrequestreview-39934457 Guozhang On Tue, May 23, 2017 at 2:28 PM, James Cheng wrote: > Hi, > > Can I get a review of pull request https://github.com/apache/ > kafka/pull/2993, for JIRA https://issues.apache.org/jira/br

[jira] [Updated] (KAFKA-5273) KafkaConsumer.committed() should get latest committed offsets from the server

[ https://issues.apache.org/jira/browse/KAFKA-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5273: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[jira] [Commented] (KAFKA-5273) KafkaConsumer.committed() should get latest committed offsets from the server

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

[GitHub] kafka pull request #3119: KAFKA-5273: Make KafkaConsumer.committed query the...

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

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

See Changes: [me] KAFKA-5081: Force jackson-annotations to a single version matching -- [...truncated 893.75 KB...] kafka.security.auth.SimpleAclAuthorizerTest > testAclM

Re: [Vote] KIP-150 - Kafka-Streams Cogroup

I don't think we should wait for entries from each stream, since that might limit the usefulness of the cogroup operator. There are instances where it can be useful to compute something based on data from one or more stream, without having to wait for all the streams to produce something for the gr

[jira] [Resolved] (KAFKA-4970) Add a 'ProducerIdResource' to enable authorization for generating producer ids

[ https://issues.apache.org/jira/browse/KAFKA-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta resolved KAFKA-4970. - Resolution: Fixed This has already been addressed in other work. > Add a 'ProducerIdResource' to

[jira] [Updated] (KAFKA-5147) KafkaProducer's TransactionManager needs a review on synchronization

[ https://issues.apache.org/jira/browse/KAFKA-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5147: Status: Patch Available (was: In Progress) > KafkaProducer's TransactionManager needs a review on s

[jira] [Work started] (KAFKA-5281) System tests for KIP-98 / transactions

[ https://issues.apache.org/jira/browse/KAFKA-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5281 started by Apurva Mehta. --- > System tests for KIP-98 / transactions > -- >

[jira] [Commented] (KAFKA-5147) KafkaProducer's TransactionManager needs a review on synchronization

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

[GitHub] kafka pull request #3132: KAFKA-5147: Add missing synchronization to Transac...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3132 KAFKA-5147: Add missing synchronization to TransactionManager The basic idea is that exactly three collections, ie. `pendingRequests`, `newPartitionsToBeAddedToTransaction`, and `partitionsInTransac

[jira] [Resolved] (KAFKA-5081) two versions of jackson-annotations-xxx.jar in distribution tgz

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

[jira] [Assigned] (KAFKA-5081) two versions of jackson-annotations-xxx.jar in distribution tgz

[ https://issues.apache.org/jira/browse/KAFKA-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-5081: Assignee: Ewen Cheslack-Postava > two versions of jackson-annotations-xxx.j

[jira] [Commented] (KAFKA-5081) two versions of jackson-annotations-xxx.jar in distribution tgz

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

[GitHub] kafka pull request #3116: KAFKA-5081: force version for 'jackson-annotations...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3116 --- 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-148: Add a connect timeout for client

I think using a single config to cover end-to-end latency with connecting and request round-trip may not be best appropriate since 1) some request may need much more time than others since they are parked (fetch request with long polling, join group request etc) or throttled, and 2) some requests a

[GitHub] kafka pull request #3131: 0.11.0

GitHub user linxiaobai opened a pull request: https://github.com/apache/kafka/pull/3131 0.11.0 ``` [2017-05-24 09:39:34,637] ERROR [ReplicaFetcherThread-0-175], Error for partition [__consumer_offsets,15] to broker 175:org.apache.kafka.common.errors.UnknownTopicOrPartitionExcep

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

Another question that came to me is on "window alignment": from the KIP it seems you are allowing users to specify a (potentially different) window spec in each co-grouped input stream. So if these window specs are different how should we "align" them with different input streams? I think it is mor

Re: [Vote] KIP-150 - Kafka-Streams Cogroup

The proposal LGTM, +1 One question I have is about when to send the record to the resulted KTable changelog. For example in your code snippet in the wiki page, before you see the end result of 1L, Customer[ cart:{Item[no:01], Item[no:03], Item[no:04]},

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

Thanks for the proposal Kyle, this is a quite common use case to support such multi-way table join (i.e. N source tables with N aggregate func) with a single store and N+1 serdes, I have seen lots of people using the low-level PAPI to achieve this goal. On Fri, May 19, 2017 at 10:04 AM, Kyle Wink

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

See Changes: [ismael] KAFKA-5135; Controller Health Metrics (KIP-143) -- [...truncated 891.05 KB...] kafka.coordinator.transaction.TransactionCoordinatorTest > shouldRes

[jira] [Assigned] (KAFKA-5281) System tests for KIP-98 / transactions

[ https://issues.apache.org/jira/browse/KAFKA-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5281: --- Assignee: Apurva Mehta > System tests for KIP-98 / transactions > ---

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

[ https://issues.apache.org/jira/browse/KAFKA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5019: --- Assignee: Jason Gustafson > Exactly-once upgrade notes > -- > >

[jira] [Updated] (KAFKA-5202) Handle topic deletion for ongoing transactions

[ https://issues.apache.org/jira/browse/KAFKA-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5202: Status: Patch Available (was: Open) > Handle topic deletion for ongoing transactions >

[jira] [Commented] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022127#comment-16022127 ] Apurva Mehta commented on KAFKA-5032: - [~ijuma] [~hachikuji] : I am a bit confused abo

[jira] [Updated] (KAFKA-5318) Streams state may be misleading

[ https://issues.apache.org/jira/browse/KAFKA-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joao updated KAFKA-5318: Description: I rely on "org.apache.kafka.streams.KafkaStreams#state" to know if my current stream instance is prope

[jira] [Created] (KAFKA-5318) Streams state may be misleading

Joao created KAFKA-5318: --- Summary: Streams state may be misleading Key: KAFKA-5318 URL: https://issues.apache.org/jira/browse/KAFKA-5318 Project: Kafka Issue Type: Bug Components: streams

[jira] [Created] (KAFKA-5317) Update KIP-98 to reflect changes during implementation.

Apurva Mehta created KAFKA-5317: --- Summary: Update KIP-98 to reflect changes during implementation. Key: KAFKA-5317 URL: https://issues.apache.org/jira/browse/KAFKA-5317 Project: Kafka Issue Typ

[jira] [Commented] (KAFKA-5135) Controller Health Metrics (KIP-143)

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

[GitHub] kafka pull request #2983: KAFKA-5135: Controller Health Metrics (KIP-143)

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2983 --- 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-5093) Load only batch header when rebuilding producer ID map

[ https://issues.apache.org/jira/browse/KAFKA-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5093: Labels: exactly-once (was: ) > Load only batch header when rebuilding producer ID map > ---

[jira] [Updated] (KAFKA-5135) Controller Health Metrics (KIP-143)

[ https://issues.apache.org/jira/browse/KAFKA-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5135: --- Resolution: Fixed Fix Version/s: 0.11.1.0 Status: Resolved (was: Patch Available) I

[jira] [Updated] (KAFKA-5093) Load only batch header when rebuilding producer ID map

[ https://issues.apache.org/jira/browse/KAFKA-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5093: Priority: Blocker (was: Critical) > Load only batch header when rebuilding producer ID map > --

[jira] [Commented] (KAFKA-5031) Additional validation in validateMessagesAndAssignOffsets

[ https://issues.apache.org/jira/browse/KAFKA-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022092#comment-16022092 ] Apurva Mehta commented on KAFKA-5031: - [~gosubpl] for the record counts at least, we s

[jira] [Commented] (KAFKA-5202) Handle topic deletion for ongoing transactions

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

[GitHub] kafka pull request #3130: KAFKA-5202: Handle topic deletion while trying to ...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/3130 KAFKA-5202: Handle topic deletion while trying to send txn markers Here is the sketch of this proposal: 1. When handling `addPartition` request, the coordinator will check if all its c

[jira] [Commented] (KAFKA-5310) reset ControllerContext during resignation

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

[jira] [Updated] (KAFKA-5024) Old clients don't support message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5024: Labels: documentation exactly-once (was: ) > Old clients don't support message format V2 >

[jira] [Updated] (KAFKA-5021) Update Message Delivery Semantics section to take into account KIP-98

[ https://issues.apache.org/jira/browse/KAFKA-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5021: Labels: documentation exactly-once (was: ) > Update Message Delivery Semantics section to take into

[GitHub] kafka pull request #3122: KAFKA-5310: reset ControllerContext during resigna...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3122 --- 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-5310) reset ControllerContext during resignation

[ https://issues.apache.org/jira/browse/KAFKA-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-5310: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 3122 [https:

[jira] [Updated] (KAFKA-5020) Update protocol documentation to mention message format v2

[ https://issues.apache.org/jira/browse/KAFKA-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5020: Labels: documentation exactly-once (was: docuentation exactly-once) > Update protocol documentation

[jira] [Updated] (KAFKA-5020) Update protocol documentation to mention message format v2

[ https://issues.apache.org/jira/browse/KAFKA-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5020: Labels: docuentation exactly-once (was: ) > Update protocol documentation to mention message format

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

[ https://issues.apache.org/jira/browse/KAFKA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5019: Labels: documentation exactly-once (was: exactly-once) > Exactly-once upgrade notes > -

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

[ https://issues.apache.org/jira/browse/KAFKA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5019: Labels: exactly-once (was: ) > Exactly-once upgrade notes > -- > >

[jira] [Work started] (KAFKA-5147) KafkaProducer's TransactionManager needs a review on synchronization

[ https://issues.apache.org/jira/browse/KAFKA-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5147 started by Apurva Mehta. --- > KafkaProducer's TransactionManager needs a review on synchronization > --

[jira] [Resolved] (KAFKA-5010) Log cleaner crashed with BufferOverflowException when writing to the writeBuffer

[ https://issues.apache.org/jira/browse/KAFKA-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5010. Resolution: Duplicate Fix Version/s: (was: 0.11.0.0) Marking this as a duplicate of KAFKA

[jira] [Updated] (KAFKA-5316) Log cleaning can increase message size and cause cleaner to crash with buffer overflow

[ https://issues.apache.org/jira/browse/KAFKA-5316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5316: --- Description: We have observed in practice that it is possible for a compressed record set to

[jira] [Created] (KAFKA-5316) Log cleaning can increase message size and cause cleaner to crash with buffer overflow

Jason Gustafson created KAFKA-5316: -- Summary: Log cleaning can increase message size and cause cleaner to crash with buffer overflow Key: KAFKA-5316 URL: https://issues.apache.org/jira/browse/KAFKA-5316

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

See Changes: [wangguoz] KAFKA-5280: Protect txn metadata map with read-write lock -- [...truncated 2.89 MB...] kafka.admin.ReassignPartitionsCommandTest > shouldRemoveThr

Re: [DISCUSS] KIP-148: Add a connect timeout for client

Another note-- it would be really nice if timeouts were end-to-end, rather than being set for particular phases of an RP From a user point of view, a 30 second timeout should mean that the call either succeeds or fails after 30 seconds, regardless of how much time is spent looking for metadata, co

[jira] [Commented] (KAFKA-5167) streams task gets stuck after re-balance due to LockException

[ https://issues.apache.org/jira/browse/KAFKA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021932#comment-16021932 ] Matthias J. Sax commented on KAFKA-5167: I see your point -- we are working on bet

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

See

Can I get a review for a PR for KAFKA-5191?

Hi, Can I get a review of pull request https://github.com/apache/kafka/pull/2993, for JIRA https://issues.apache.org/jira/browse/KAFKA-5191 ? I'm trying to get it into the 0.11.0.0 release. I think tomorrow is the last day to get it merged in? Thanks, -James

[jira] [Comment Edited] (KAFKA-5167) streams task gets stuck after re-balance due to LockException

[ https://issues.apache.org/jira/browse/KAFKA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021879#comment-16021879 ] Joao edited comment on KAFKA-5167 at 5/23/17 9:20 PM: -- [~mjsax] thank

[jira] [Commented] (KAFKA-5167) streams task gets stuck after re-balance due to LockException

[ https://issues.apache.org/jira/browse/KAFKA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021879#comment-16021879 ] Joao commented on KAFKA-5167: - [~mjsax] thanks for the clarification regarding the max poll in

[jira] [Commented] (KAFKA-5167) streams task gets stuck after re-balance due to LockException

[ https://issues.apache.org/jira/browse/KAFKA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021868#comment-16021868 ] Matthias J. Sax commented on KAFKA-5167: [~JoaoPeixoto] If I read the log you shar

[jira] [Commented] (KAFKA-5280) Protect concurrent access to the cached transaction status

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

[GitHub] kafka pull request #3082: KAFKA-5280: Protect txn metadata map with read-wri...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3082 --- 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-5280) Protect concurrent access to the cached transaction status

[ https://issues.apache.org/jira/browse/KAFKA-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5280: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[jira] [Commented] (KAFKA-5167) streams task gets stuck after re-balance due to LockException

[ https://issues.apache.org/jira/browse/KAFKA-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021786#comment-16021786 ] Joao commented on KAFKA-5167: - I just came across this very same exception, logs below, howeve

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

See Changes: [wangguoz] MINOR: improve EmbeddedKafkaCluster test utility for deleting topics -- [...truncated 887.44 KB...] kafka.producer.ProducerTest > testUpdateBrokerP

Re: [DISCUSS] KIP-148: Add a connect timeout for client

In the AdminClient, we allow setting per-call timeouts. The global timeout is just a default. It seems like that is really what we should do in the producer and consumer as well, rather than having a lot of special cases for timeouts in connecting vs. other call states. Then join requests could

Jenkins build is back to normal : kafka-0.11.0-jdk7 #19

See

Re: [DISCUSS] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

Ah, yes, I see you a highlighted part that should've made this clear to me the first read. :-) Much clearer now! By the way, enjoyed your Debezium talk in NYC. Looking forward to this Kafka Connect change; it will allow me to remove a post-deployment tool that I hacked together for the purpose o

[jira] [Commented] (KAFKA-1955) Explore disk-based buffering in new Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021683#comment-16021683 ] Brandon Bradley commented on KAFKA-1955: I've implemented a barebones malloc/free

[jira] [Updated] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhisek Saikia updated KAFKA-5296: -- Affects Version/s: 0.10.2.0 > Unable to write to some partitions of newly created topic in 10.2

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

See

[jira] [Assigned] (KAFKA-5311) Support ExtendedDeserializer in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-5311: Assignee: Dale Peakall > Support ExtendedDeserializer in Kafka Streams > --

[GitHub] kafka pull request #3104: MINOR: improve EmbeddedKafkaCluster test utility f...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3104 --- 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] [Comment Edited] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021577#comment-16021577 ] Abhisek Saikia edited comment on KAFKA-5296 at 5/23/17 6:46 PM:

Build failed in Jenkins: kafka-0.11.0-jdk7 #18

See Changes: [wangguoz] MINOR: remove TransactionCoordinatorIntegrationTest [jason] MINOR: Log transaction metadata state transitions plus a few cleanups -- [...truncated

[jira] [Comment Edited] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021577#comment-16021577 ] Abhisek Saikia edited comment on KAFKA-5296 at 5/23/17 6:45 PM:

[jira] [Commented] (KAFKA-5311) Support ExtendedDeserializer in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021584#comment-16021584 ] Matthias J. Sax commented on KAFKA-5311: [~guozhang] Can you add [~dale.peakall] t

[jira] [Updated] (KAFKA-5311) Support ExtendedDeserializer in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5311: --- Status: Patch Available (was: Open) > Support ExtendedDeserializer in Kafka Streams > ---

[jira] [Commented] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021577#comment-16021577 ] Abhisek Saikia commented on KAFKA-5296: --- Any new topic creation is running into issu

[jira] [Assigned] (KAFKA-5315) Streams exception w/ partially processed record corrupts state store

[ https://issues.apache.org/jira/browse/KAFKA-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-5315: -- Assignee: Matthias J. Sax > Streams exception w/ partially processed record corrupts st

[jira] [Commented] (KAFKA-5282) Transactions integration test: Use factory methods to keep track of open producers and consumers and close them all on tearDown

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

[GitHub] kafka pull request #3129: KAFKA-5282: Use a factory method to create produce...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/3129 KAFKA-5282: Use a factory method to create producers and consumers an d close them in tearDown You can merge this pull request into a Git repository by running: $ git pull https://gith

[jira] [Work started] (KAFKA-5314) Improve exception handling for state stores

[ https://issues.apache.org/jira/browse/KAFKA-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5314 started by Eno Thereska. --- > Improve exception handling for state stores > ---

[jira] [Commented] (KAFKA-5253) KStreamTestDriver must handle streams created with patterns

[ https://issues.apache.org/jira/browse/KAFKA-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021520#comment-16021520 ] Matthias J. Sax commented on KAFKA-5253: As you can see from the code {{KStreamTes

Re: [DISCUSS] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

Thanks for the quick feedback, Mathieu. Yes, the first configuration rule whose regex matches will be applied, and no other rules will be used. I've updated the KIP to try to make this more clear, but let me know if it's still not clear. Best regards, Randall On Tue, May 23, 2017 at 10:07 AM, Ma

[jira] [Work started] (KAFKA-5282) Transactions integration test: Use factory methods to keep track of open producers and consumers and close them all on tearDown

[ https://issues.apache.org/jira/browse/KAFKA-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5282 started by Vahid Hashemian. -- > Transactions integration test: Use factory methods to keep track of open >

[GitHub] kafka pull request #3081: MINOR: Log transaction metadata state transitions ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3081 --- 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 #3128: MINOR: remove TransactionCoordinatorIntegrationTes...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3128 --- 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: Pull-Requests not worked on

I agree with this. As a new contributor, it was a bit demoralizing to look at all the open PR's and wonder whether when I sent a patch it would just be left to sit in the ether. In other projects I'm involved with, more typically the maintainers go through periodically and close old PR's that will

[jira] [Commented] (KAFKA-5247) Consumer GroupCoordinator should continue to materialize committed offsets in offset order even for transactional offset commits

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

[GitHub] kafka pull request #3108: KAFKA-5247: Materialize committed offsets in offse...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3108 --- 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-5247) Consumer GroupCoordinator should continue to materialize committed offsets in offset order even for transactional offset commits

[ https://issues.apache.org/jira/browse/KAFKA-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5247: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull requ

Re: Re: Re: [DISCUSS] KIP-148: Add a connect timeout for client

Hi David, The only issue with yet another config is that nearly everyone will just leave it at the default value and it is hard to configure. But that is just my personal opinion. If you need the flexibility, then I don't have any objection to another config option. The specific scenario describe

Re:Re: Re: [DISCUSS] KIP-148: Add a connect timeout for client

Hi Rajini If we only use the request.timeout for the connect and process request, it is not flexible for some cases, for example we need the connecting phase to a short time(5s), and the request for a longer time(40s). Why not add a connect timeout to handler these different cases. Thanks, Da

[GitHub] kafka pull request #3128: MINOR: remove TransactionCoordinatorIntegrationTes...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3128 MINOR: remove TransactionCoordinatorIntegrationTest `TransactionCoordinatorIntegrationTest` is not covering anything that isn't already covered by the more complete `TransactionsTest` You can merge th

Re: [DISCUSS] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

Hi Randall, Awesome, very much looking forward to this. It isn't 100% clear from the KIP how multiple config-based rules would be applied; it looks like the first configuration rule whose regex matches the topic name will be used, and no other rules will be applied. Is that correct? (I wasn't s

[jira] [Commented] (KAFKA-5308) TC should handle UNSUPPORTED_FOR_MESSAGE_FORMAT in WriteTxnMarker response

[ https://issues.apache.org/jira/browse/KAFKA-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021295#comment-16021295 ] Damian Guy commented on KAFKA-5308: --- [~hachikuji] i think this may not be possible once

Re: KTable aggregate corruption on poorly timed exception

Hi Matthias, I've filed KAFKA-5315 (https://issues.apache.org/jira/browse/KAFKA-5315). Thanks, Mathieu On Fri, May 19, 2017 at 3:07 PM, Matthias J. Sax wrote: > Hi Mathieu, > > Thanks for reporting this! > > This is definitely a bug and it must get fixed for at-last-once > processing, too. Ex

[jira] [Created] (KAFKA-5315) Streams exception w/ partially processed record corrupts state store

Mathieu Fenniak created KAFKA-5315: -- Summary: Streams exception w/ partially processed record corrupts state store Key: KAFKA-5315 URL: https://issues.apache.org/jira/browse/KAFKA-5315 Project: Kafka

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

Hi Jeyhun, I understand your argument about "Rich" in RichFunctions. Perhaps I'm just being too puritan here, but let me ask this anyway: What is it that makes something a function? To me a function is something that takes zero or more arguments and possibly returns a value and while it may

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

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

[GitHub] kafka pull request #3127: Add sleep between empty polls to avoid burning CPU

GitHub user felixgborrego opened a pull request: https://github.com/apache/kafka/pull/3127 Add sleep between empty polls to avoid burning CPU Workaround for https://issues.apache.org/jira/browse/KAFKA-3159 You can merge this pull request into a Git repository by running: $ git

  1   2   >