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

See

[jira] [Commented] (KAFKA-4762) Consumer throwing RecordTooLargeException even when messages are not that large

[ https://issues.apache.org/jira/browse/KAFKA-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877674#comment-15877674 ] Huadong Liu commented on KAFKA-4762: [~huxi_2b] Thanks for your fast response! 9925056

[jira] [Comment Edited] (KAFKA-4762) Consumer throwing RecordTooLargeException even when messages are not that large

[ https://issues.apache.org/jira/browse/KAFKA-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877641#comment-15877641 ] huxi edited comment on KAFKA-4762 at 2/22/17 7:16 AM: -- [~huadongliu]

[jira] [Commented] (KAFKA-4762) Consumer throwing RecordTooLargeException even when messages are not that large

[ https://issues.apache.org/jira/browse/KAFKA-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877641#comment-15877641 ] huxi commented on KAFKA-4762: - [~huadongliu] The reason you saw `NoCompressionCodec` in the ou

[jira] [Commented] (KAFKA-4762) Consumer throwing RecordTooLargeException even when messages are not that large

[ https://issues.apache.org/jira/browse/KAFKA-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877616#comment-15877616 ] Huadong Liu commented on KAFKA-4762: Hi [~huxi_2b], you are right. The RecordTooLargeE

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

See Changes: [becket.qin] KAFKA-4757; NetworkClient should log request details at trace level when -- [...truncated 614.04 KB...] org.apache.kafka.common.record.MemoryRec

[jira] [Commented] (KAFKA-4569) Transient failure in org.apache.kafka.clients.consumer.KafkaConsumerTest.testWakeupWithFetchDataAvailable

[ https://issues.apache.org/jira/browse/KAFKA-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877598#comment-15877598 ] Armin Braun commented on KAFKA-4569: Just for future reference. Tried to debug a few i

[GitHub] kafka pull request #2582: MINOR: Fixed Non-Final Close Method + its Duplicat...

GitHub user original-brownbear opened a pull request: https://github.com/apache/kafka/pull/2582 MINOR: Fixed Non-Final Close Method + its Duplication Trivial but in my opinion it's well worth it making the `close` method `final` here and also deleting that duplication (especially si

[jira] [Resolved] (KAFKA-4757) Improve NetworkClient trace logging of request details

[ https://issues.apache.org/jira/browse/KAFKA-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-4757. - Resolution: Fixed > Improve NetworkClient trace logging of request details > -

[jira] [Updated] (KAFKA-4757) Improve NetworkClient trace logging of request details

[ https://issues.apache.org/jira/browse/KAFKA-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4757: Affects Version/s: 0.10.2.0 > Improve NetworkClient trace logging of request details > -

[jira] [Updated] (KAFKA-4757) Improve NetworkClient trace logging of request details

[ https://issues.apache.org/jira/browse/KAFKA-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4757: Fix Version/s: 0.10.3.0 > Improve NetworkClient trace logging of request details > -

[GitHub] kafka pull request #2563: Kafka 4757: NetworkClient should log request detai...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2563 --- 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-site pull request #45: Manual edits needed for 0.10.2 release

Github user guozhangwang closed the pull request at: https://github.com/apache/kafka-site/pull/45 --- 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 featur

[GitHub] kafka-site issue #45: Manual edits needed for 0.10.2 release

Github user guozhangwang commented on the issue: https://github.com/apache/kafka-site/pull/45 Merged. --- 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

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

Hi Jun, Thanks for the comments. I will mention in the KIP : how this change doesn't affect the default authorizer implementation. Regarding, Currently, we log the principal name in the request log in RequestChannel, which has the format of "principalType + SEPARATOR + name;". It would be good i

Re: [DISCUSS] KIP-126 - Allow KafkaProducer to batch based on uncompressed size

Apurva has a point that can be documented for this config. Overall, LGTM +1. Thanks, Mayuresh On Tue, Feb 21, 2017 at 6:41 PM, Becket Qin wrote: > Hi Apurva, > > Yes, it is true that the request size might be much smaller if the batching > is based on uncompressed size. I will let the users k

Re: [DISCUSS] KIP-126 - Allow KafkaProducer to batch based on uncompressed size

Hi Apurva, Yes, it is true that the request size might be much smaller if the batching is based on uncompressed size. I will let the users know about this. That said, in practice, this is probably fine. For example, at LinkedIn, our max message size is 1 MB, typically the compressed size would be

Re: [DISCUSS] KIP-82 - Add Record Headers

Hi Jason, Have converted the interface/api bullets into interface code snippets. Agreed implementation won’t take too long. We have early versions already. Maybe a week before you think about merging I would assume it would be more stabilised? I was thinking then we could fork from your conflue

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

It seems that it's simpler and more consistent to avoid optional keys and values. Not sure if it's worth squeezing every byte at the expense of additional complexity. Other than that, +1 from me. Also, since this is a large KIP, minor changes may arise as we start the implementation. It would be g

[jira] [Updated] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4144: --- Description: At the moment the timestamp extractor is configured via a {{StreamConfig}} value

[jira] [Updated] (KAFKA-4785) Records from internal repartitioning topics should always use RecordMetadataTimestampExtractor

[ https://issues.apache.org/jira/browse/KAFKA-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4785: --- Description: Users can specify what timestamp extractor should be used to decode the timestam

[jira] [Updated] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4144: --- Description: At the moment the timestamp extractor is configured via a {{StreamConfig}} value

Re: [DISCUSS] KIP-126 - Allow KafkaProducer to batch based on uncompressed size

Hi Becket, Thanks for the kip. I think one of the risks here is that when compression estimation is disabled, you could have much smaller batches than expected, and throughput could be hurt. It would be worth adding this to the documentation of this setting. Also, one of the rejected alternatives

[jira] [Updated] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4144: --- Description: At the moment the timestamp extractor is configured via a {{StreamConfig}} value

[jira] [Updated] (KAFKA-4785) Records from internal repartitioning topics should always use RecordMetadataTimestampExtractor

[ https://issues.apache.org/jira/browse/KAFKA-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4785: --- Description: Users can specify what timestamp extractor should be used to decode the timestam

[jira] [Created] (KAFKA-4785) Records from internal repartitioning topics should always use RecordMetadataTimestampExtractor

Matthias J. Sax created KAFKA-4785: -- Summary: Records from internal repartitioning topics should always use RecordMetadataTimestampExtractor Key: KAFKA-4785 URL: https://issues.apache.org/jira/browse/KAFKA-4785

[jira] [Updated] (KAFKA-2594) Add a key-value store that is a fixed-capacity in-memory LRU cache

[ https://issues.apache.org/jira/browse/KAFKA-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2594: --- Affects Version/s: 0.10.0.0 > Add a key-value store that is a fixed-capacity in-memory LRU cac

[jira] [Updated] (KAFKA-2649) Add support for custom partitioner in sink nodes

[ https://issues.apache.org/jira/browse/KAFKA-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2649: --- Affects Version/s: 0.10.0.0 > Add support for custom partitioner in sink nodes > -

[jira] [Updated] (KAFKA-2593) KeyValueStores should not require use of the context's default serializers and deserializers

[ https://issues.apache.org/jira/browse/KAFKA-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2593: --- Affects Version/s: 0.10.0.0 > KeyValueStores should not require use of the context's default s

[jira] [Updated] (KAFKA-2694) Make a task id be a composite id of a topic group id and a partition id

[ https://issues.apache.org/jira/browse/KAFKA-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2694: --- Affects Version/s: 0.10.0.0 > Make a task id be a composite id of a topic group id and a parti

[jira] [Updated] (KAFKA-3153) Serializer/Deserializer Registration and Type inference

[ https://issues.apache.org/jira/browse/KAFKA-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3153: --- Affects Version/s: 0.10.0.0 > Serializer/Deserializer Registration and Type inference > --

[jira] [Updated] (KAFKA-2706) Make state stores first class citizens in the processor DAG

[ https://issues.apache.org/jira/browse/KAFKA-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2706: --- Affects Version/s: 0.10.0.0 > Make state stores first class citizens in the processor DAG > --

[jira] [Updated] (KAFKA-2811) Add standby tasks

[ https://issues.apache.org/jira/browse/KAFKA-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2811: --- Affects Version/s: 0.10.0.0 > Add standby tasks > - > > Key: K

[jira] [Updated] (KAFKA-2902) StreamingConfig getConsumerConfiigs uses getRestoreConsumerConfigs instead of getBaseConsumerConfigs

[ https://issues.apache.org/jira/browse/KAFKA-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2902: --- Affects Version/s: 0.10.0.0 > StreamingConfig getConsumerConfiigs uses getRestoreConsumerConfi

[jira] [Updated] (KAFKA-2763) Reduce stream task migrations and initialization costs

[ https://issues.apache.org/jira/browse/KAFKA-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2763: --- Affects Version/s: 0.10.0.0 > Reduce stream task migrations and initialization costs > ---

[jira] [Updated] (KAFKA-2984) KTable should send old values along with new values to downstreams

[ https://issues.apache.org/jira/browse/KAFKA-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2984: --- Affects Version/s: 0.10.0.0 > KTable should send old values along with new values to downstrea

[jira] [Updated] (KAFKA-2727) initialize only the part of the topology relevant to the task

[ https://issues.apache.org/jira/browse/KAFKA-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2727: --- Affects Version/s: 0.10.0.0 > initialize only the part of the topology relevant to the task >

[jira] [Updated] (KAFKA-3060) Refactor MeteredXXStore

[ https://issues.apache.org/jira/browse/KAFKA-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3060: --- Affects Version/s: 0.10.0.0 > Refactor MeteredXXStore > --- > >

[jira] [Updated] (KAFKA-3016) Add KStream-KStream window joins

[ https://issues.apache.org/jira/browse/KAFKA-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3016: --- Affects Version/s: 0.10.0.0 > Add KStream-KStream window joins > -

[jira] [Updated] (KAFKA-2856) add KTable

[ https://issues.apache.org/jira/browse/KAFKA-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2856: --- Affects Version/s: 0.10.0.0 > add KTable > -- > > Key: KAFKA-2856 >

[jira] [Updated] (KAFKA-2872) Error starting KafkaStream caused by sink not being connected to parent source/processor nodes

[ https://issues.apache.org/jira/browse/KAFKA-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2872: --- Affects Version/s: 0.10.0.0 > Error starting KafkaStream caused by sink not being connected to

[jira] [Updated] (KAFKA-3278) clientId is not unique in producer/consumer registration leads to mbean warning

[ https://issues.apache.org/jira/browse/KAFKA-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3278: --- Affects Version/s: 0.10.0.0 > clientId is not unique in producer/consumer registration leads t

[jira] [Updated] (KAFKA-3195) Transient test failure in OffsetCheckpointTest.testReadWrite

[ https://issues.apache.org/jira/browse/KAFKA-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3195: --- Affects Version/s: 0.10.0.0 > Transient test failure in OffsetCheckpointTest.testReadWrite > -

[jira] [Updated] (KAFKA-3337) Extract selector as a separate groupBy operator for KTable aggregations

[ https://issues.apache.org/jira/browse/KAFKA-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3337: --- Affects Version/s: 0.10.0.0 > Extract selector as a separate groupBy operator for KTable aggre

[jira] [Updated] (KAFKA-3430) Allow users to set key in KTable.toStream() and KStream

[ https://issues.apache.org/jira/browse/KAFKA-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3430: --- Affects Version/s: 0.10.0.0 > Allow users to set key in KTable.toStream() and KStream > --

[jira] [Updated] (KAFKA-3338) Add print and writeAsText functions to the Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3338: --- Affects Version/s: 0.10.0.0 > Add print and writeAsText functions to the Streams DSL > ---

[jira] [Updated] (KAFKA-3439) Document possible exception thrown in public APIs

[ https://issues.apache.org/jira/browse/KAFKA-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3439: --- Affects Version/s: 0.10.0.0 > Document possible exception thrown in public APIs >

[jira] [Updated] (KAFKA-3519) Refactor Transformer templates to return the same strong-typed value.

[ https://issues.apache.org/jira/browse/KAFKA-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3519: --- Affects Version/s: 0.10.0.0 > Refactor Transformer templates to return the same strong-typed v

[jira] [Updated] (KAFKA-3477) Add customizable StreamPartition into #to functions of Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3477: --- Affects Version/s: 0.10.0.0 > Add customizable StreamPartition into #to functions of Streams D

[jira] [Updated] (KAFKA-3504) Changelog partition configured to enable log compaction

[ https://issues.apache.org/jira/browse/KAFKA-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3504: --- Affects Version/s: 0.10.0.0 > Changelog partition configured to enable log compaction > --

[jira] [Updated] (KAFKA-3512) Add a foreach() operator in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3512: --- Affects Version/s: 0.10.0.0 > Add a foreach() operator in Kafka Streams DSL >

[jira] [Updated] (KAFKA-3440) Add Javadoc for KTable (changelog stream) and KStream (record stream)

[ https://issues.apache.org/jira/browse/KAFKA-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3440: --- Affects Version/s: 0.10.0.0 > Add Javadoc for KTable (changelog stream) and KStream (record st

[jira] [Updated] (KAFKA-3505) Set curRecord in punctuate() functions

[ https://issues.apache.org/jira/browse/KAFKA-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3505: --- Affects Version/s: 0.10.0.0 > Set curRecord in punctuate() functions > ---

[jira] [Updated] (KAFKA-3499) byte[] should not be used as Map key nor Set member

[ https://issues.apache.org/jira/browse/KAFKA-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3499: --- Affects Version/s: 0.10.0.0 > byte[] should not be used as Map key nor Set member > --

[jira] [Updated] (KAFKA-3521) Better handling NPEs in Streams DSL implementation

[ https://issues.apache.org/jira/browse/KAFKA-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3521: --- Affects Version/s: 0.10.0.0 > Better handling NPEs in Streams DSL implementation > ---

[jira] [Updated] (KAFKA-3598) Improve JavaDoc of public API

[ https://issues.apache.org/jira/browse/KAFKA-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3598: --- Affects Version/s: 0.10.0.0 > Improve JavaDoc of public API > - >

[jira] [Updated] (KAFKA-3599) Move WindowStoreUtils to package "internals"

[ https://issues.apache.org/jira/browse/KAFKA-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3599: --- Affects Version/s: 0.10.0.0 > Move WindowStoreUtils to package "internals" > -

[jira] [Updated] (KAFKA-3658) Incorrect validation check on maintenance period with join window size

[ https://issues.apache.org/jira/browse/KAFKA-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3658: --- Affects Version/s: 0.10.0.0 > Incorrect validation check on maintenance period with join windo

[jira] [Updated] (KAFKA-3639) Configure default serdes passed via StreamsConfig

[ https://issues.apache.org/jira/browse/KAFKA-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3639: --- Affects Version/s: 0.10.0.0 > Configure default serdes passed via StreamsConfig >

[jira] [Updated] (KAFKA-3607) Close state stores explicitly in unit tests upon completing

[ https://issues.apache.org/jira/browse/KAFKA-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3607: --- Affects Version/s: 0.10.0.0 > Close state stores explicitly in unit tests upon completing > --

[jira] [Updated] (KAFKA-3523) Capture org.apache.kafka.clients.consumer.CommitFailedException in UncaughtExceptionHandler

[ https://issues.apache.org/jira/browse/KAFKA-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3523: --- Affects Version/s: 0.10.0.0 > Capture org.apache.kafka.clients.consumer.CommitFailedException

[jira] [Updated] (KAFKA-3629) KStreamImpl.to(...) throws NPE when the value SerDe is null

[ https://issues.apache.org/jira/browse/KAFKA-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3629: --- Affects Version/s: 0.10.0.0 > KStreamImpl.to(...) throws NPE when the value SerDe is null > --

[jira] [Updated] (KAFKA-3862) Kafka streams documentation: partition<->thread<->task assignment unclear

[ https://issues.apache.org/jira/browse/KAFKA-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3862: --- Affects Version/s: 0.10.0.0 > Kafka streams documentation: partition<->thread<->task assignmen

[jira] [Updated] (KAFKA-3619) State lock file handle leaks

[ https://issues.apache.org/jira/browse/KAFKA-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3619: --- Affects Version/s: 0.10.0.0 > State lock file handle leaks > > >

[jira] [Updated] (KAFKA-3612) Add initial set of integration tests

[ https://issues.apache.org/jira/browse/KAFKA-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3612: --- Affects Version/s: (was: 0.10.0.0) > Add initial set of integration tests > --

[jira] [Updated] (KAFKA-3612) Add initial set of integration tests

[ https://issues.apache.org/jira/browse/KAFKA-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3612: --- Affects Version/s: 0.10.0.0 > Add initial set of integration tests > -

[jira] [Updated] (KAFKA-3629) KStreamImpl.to(...) throws NPE when the value SerDe is null

[ https://issues.apache.org/jira/browse/KAFKA-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3629: --- Affects Version/s: (was: 0.10.0.0) > KStreamImpl.to(...) throws NPE when the value SerDe i

[jira] [Updated] (KAFKA-3619) State lock file handle leaks

[ https://issues.apache.org/jira/browse/KAFKA-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3619: --- Affects Version/s: (was: 0.10.0.0) > State lock file handle leaks > --

[jira] [Updated] (KAFKA-3862) Kafka streams documentation: partition<->thread<->task assignment unclear

[ https://issues.apache.org/jira/browse/KAFKA-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3862: --- Affects Version/s: (was: 0.10.0.0) > Kafka streams documentation: partition<->thread<->tas

[jira] [Updated] (KAFKA-3016) Add KStream-KStream window joins

[ https://issues.apache.org/jira/browse/KAFKA-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3016: --- Affects Version/s: (was: 0.9.0.1) 0.10.0.0 > Add KStream-KStream wi

[jira] [Updated] (KAFKA-2872) Error starting KafkaStream caused by sink not being connected to parent source/processor nodes

[ https://issues.apache.org/jira/browse/KAFKA-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2872: --- Affects Version/s: (was: 0.10.0.0) > Error starting KafkaStream caused by sink not being c

[jira] [Updated] (KAFKA-2727) initialize only the part of the topology relevant to the task

[ https://issues.apache.org/jira/browse/KAFKA-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2727: --- Affects Version/s: (was: 0.9.0.0) > initialize only the part of the topology relevant to t

[jira] [Updated] (KAFKA-2872) Error starting KafkaStream caused by sink not being connected to parent source/processor nodes

[ https://issues.apache.org/jira/browse/KAFKA-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2872: --- Affects Version/s: 0.10.0.0 > Error starting KafkaStream caused by sink not being connected to

[jira] [Updated] (KAFKA-2706) Make state stores first class citizens in the processor DAG

[ https://issues.apache.org/jira/browse/KAFKA-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2706: --- Affects Version/s: (was: 0.9.0.0) > Make state stores first class citizens in the processo

[jira] [Updated] (KAFKA-2984) KTable should send old values along with new values to downstreams

[ https://issues.apache.org/jira/browse/KAFKA-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2984: --- Affects Version/s: (was: 0.9.0.1) 0.10.0.0 > KTable should send old

[jira] [Updated] (KAFKA-2872) Error starting KafkaStream caused by sink not being connected to parent source/processor nodes

[ https://issues.apache.org/jira/browse/KAFKA-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2872: --- Affects Version/s: (was: 0.9.0.0) > Error starting KafkaStream caused by sink not being co

[jira] [Updated] (KAFKA-2763) Reduce stream task migrations and initialization costs

[ https://issues.apache.org/jira/browse/KAFKA-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2763: --- Affects Version/s: (was: 0.9.0.0) > Reduce stream task migrations and initialization costs

[jira] [Updated] (KAFKA-3016) Add KStream-KStream window joins

[ https://issues.apache.org/jira/browse/KAFKA-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3016: --- Affects Version/s: (was: 0.10.0.0) > Add KStream-KStream window joins > --

[jira] [Updated] (KAFKA-3278) clientId is not unique in producer/consumer registration leads to mbean warning

[ https://issues.apache.org/jira/browse/KAFKA-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3278: --- Affects Version/s: (was: 0.10.0.0) > clientId is not unique in producer/consumer registrat

[jira] [Updated] (KAFKA-3060) Refactor MeteredXXStore

[ https://issues.apache.org/jira/browse/KAFKA-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3060: --- Affects Version/s: (was: 0.10.0.0) > Refactor MeteredXXStore > --- > >

[jira] [Updated] (KAFKA-2984) KTable should send old values along with new values to downstreams

[ https://issues.apache.org/jira/browse/KAFKA-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-2984: --- Affects Version/s: (was: 0.10.0.0) > KTable should send old values along with new values t

[jira] [Updated] (KAFKA-3060) Refactor MeteredXXStore

[ https://issues.apache.org/jira/browse/KAFKA-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3060: --- Affects Version/s: (was: 0.9.0.1) 0.10.0.0 > Refactor MeteredXXStor

[jira] [Updated] (KAFKA-3278) clientId is not unique in producer/consumer registration leads to mbean warning

[ https://issues.apache.org/jira/browse/KAFKA-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3278: --- Affects Version/s: (was: 0.9.0.1) 0.10.0.0 > clientId is not unique

[jira] [Updated] (KAFKA-3395) prefix job id to internal topic names

[ https://issues.apache.org/jira/browse/KAFKA-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3395: --- Affects Version/s: (was: 0.9.0.1) 0.10.0.0 > prefix job id to inter

[jira] [Updated] (KAFKA-3537) Provide access to low-level Metrics in ProcessorContext

[ https://issues.apache.org/jira/browse/KAFKA-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3537: --- Affects Version/s: 0.10.0.0 0.10.0.1 0.10.1.0

[jira] [Updated] (KAFKA-3537) Provide access to low-level Metrics in ProcessorContext

[ https://issues.apache.org/jira/browse/KAFKA-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3537: --- Affects Version/s: (was: 0.9.0.1) > Provide access to low-level Metrics in ProcessorContex

[jira] [Updated] (KAFKA-3535) Add metrics ability for streams serde components

[ https://issues.apache.org/jira/browse/KAFKA-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3535: --- Affects Version/s: (was: 0.9.0.1) 0.10.0.0 0.

Re: [DISCUSS] KIP-82 - Add Record Headers

Hey Michael, Awesome. I have a minor request. The APIs are currently documented as a wiki list. Would you mind adding a code snippet instead? It's a bit easier to process. How will be best to manage this, as we will obviously build off your KIP’s > protocol changes, to avoid a merge hell, should

[jira] [Updated] (KAFKA-3534) Deserialize on demand when default time extractor used

[ https://issues.apache.org/jira/browse/KAFKA-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3534: --- Affects Version/s: (was: 0.9.0.1) 0.10.0.0 0.

Re: Kafka Connect / Access to OffsetStorageReader from SourceConnector

Hey Florian, It seems reasonable to me to let the connector track task progress through offsets. I recall there have been other use cases for communication between tasks and connectors (perhaps Ewen or someone else will jump in here and mention them), so I'm not sure if there if this could fall un

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

If the argument and objective within this KIP is to keep the overhead of the protocol as small as possible and remove redundancy, and every byte is being counted and the introduction of varInts, then it would make sense to use attributes to me. On 22/02/2017, 00:14, "Jason Gustafson" wrote:

Re: [DISCUSS] KIP-124: Request rate quotas

Hi, Rajini, Thanks for the proposal. The benefit of using the request processing time over the request rate is exactly what people have said. I will just expand that a bit. Consider the following case. The producer sends a produce request with a 10MB message but compressed to 100KB with gzip. The

[jira] [Updated] (KAFKA-2273) KIP-54: Add rebalance with a minimal number of reassignments to server-defined strategy list

[ https://issues.apache.org/jira/browse/KAFKA-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-2273: --- Summary: KIP-54: Add rebalance with a minimal number of reassignments to server-defined strate

[jira] [Updated] (KAFKA-2273) Kip-54: Add rebalance with a minimal number of reassignments to server-defined strategy list

[ https://issues.apache.org/jira/browse/KAFKA-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-2273: --- Summary: Kip-54: Add rebalance with a minimal number of reassignments to server-defined strate

[jira] [Updated] (KAFKA-2273) Add rebalance with a minimal number of reassignments to server-defined strategy list

[ https://issues.apache.org/jira/browse/KAFKA-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-2273: --- Status: Patch Available (was: In Progress) > Add rebalance with a minimal number of reassignm

[jira] [Updated] (KAFKA-2273) Add rebalance with a minimal number of reassignments to server-defined strategy list

[ https://issues.apache.org/jira/browse/KAFKA-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-2273: --- Labels: kip (was: kip newbie++ newbiee) > Add rebalance with a minimal number of reassignment

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

Done. I've left the key and value as optional since we may not have reached consensus on whether to use attributes or not. Perhaps we should just keep it simple and not do it? The benefit seems small. -Jason On Tue, Feb 21, 2017 at 4:05 PM, Michael Pearce wrote: > Ok, no worries, can you add it

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

Ok, no worries, can you add it back ValueLen on this KIP, and update the doc, then we can work from that ☺ Cheers Mike On 22/02/2017, 00:02, "Jason Gustafson" wrote: I feel it was a little odd to leave out the value length anyway, so I would rather add it back and put headers at the en

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

I feel it was a little odd to leave out the value length anyway, so I would rather add it back and put headers at the end. This is more consistent with the rest of the Kafka protocol. -Jason On Tue, Feb 21, 2017 at 3:58 PM, Michael Pearce wrote: > Or we keep as is (valuelen removed), and header

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

Or we keep as is (valuelen removed), and headers are added with headers length.. On 21/02/2017, 23:38, "Apurva Mehta" wrote: Right now, we don't need the value length: since it is the last item in the message, and we have the message length, we can deduce the value length. However, i

  1   2   >