[jira] [Updated] (KAFKA-4850) RocksDb cannot use Bloom Filters

[ https://issues.apache.org/jira/browse/KAFKA-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated KAFKA-4850: -- Status: Patch Available (was: In Progress) > RocksDb cannot use Bloom Filters > ---

[jira] [Commented] (KAFKA-4850) RocksDb cannot use Bloom Filters

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

[GitHub] kafka pull request #3048: KAFKA-4850:RocksDb cannot use Bloom Filters

GitHub user bharatviswa504 opened a pull request: https://github.com/apache/kafka/pull/3048 KAFKA-4850:RocksDb cannot use Bloom Filters Added BloomFilter to speedup rocksdb lookup. You can merge this pull request into a Git repository by running: $ git pull https://github.com/b

[jira] [Updated] (KAFKA-4563) State transitions error PARTITIONS_REVOKED to NOT_RUNNING

[ https://issues.apache.org/jira/browse/KAFKA-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4563: - Issue Type: Sub-task (was: Bug) Parent: KAFKA-5156 > State transitions error PARTITIONS_R

[jira] [Updated] (KAFKA-5156) Options for handling exceptions in streams

[ https://issues.apache.org/jira/browse/KAFKA-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5156: - Labels: user-experience (was: ) > Options for handling exceptions in streams > --

[jira] [Updated] (KAFKA-5157) Options for handling corrupt data during deserialization

[ https://issues.apache.org/jira/browse/KAFKA-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5157: - Labels: user-experience (was: ) > Options for handling corrupt data during deserialization >

[jira] [Commented] (KAFKA-5228) Revisit Streams DSL JavaDocs

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

[GitHub] kafka pull request #3047: KAFKA-5228: Revisit Streams DSL JavaDocs

GitHub user jeyhunkarimov opened a pull request: https://github.com/apache/kafka/pull/3047 KAFKA-5228: Revisit Streams DSL JavaDocs You can merge this pull request into a Git repository by running: $ git pull https://github.com/jeyhunkarimov/kafka KAFKA-5228 Alternatively you

[GitHub] kafka pull request #3046: MINOR: Consolidate Topic classes

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3046 MINOR: Consolidate Topic classes During the 0.11.0.0 cycle, a Java version of the class was introduced so that Streams could use it. Given that it includes the bulk of the functionality of the

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

Jeyhun, I am not an expert on Lambdas. Can you elaborate a little bit? I cannot follow the explanation in the KIP to see what the problem is. For updating the KIP title I don't know -- guess it's up to you. Maybe a committer can comment on this? Further comments: - The KIP get a little hard t

Re: [DISCUSS] Modify / Remove "Unstable" annotations in Streams API

+1 for the overall proposal. Some comments: Currently, `Windowed#window()` returns type `Window` and I am wondering if we should improve type safety here and return the actual window type (ie, TimeWindow, SessionWindow, JoinWindow) etc. If this would be a useful improvement (frankly speaking, I

[GitHub] kafka pull request #3045: MINOR: Handle nulls in NonEmptyListValidator

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/3045 MINOR: Handle nulls in NonEmptyListValidator You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka minor-non-empty-list-validator-nulls

[jira] [Updated] (KAFKA-5230) Recommended values for Connect transformations contain the wrong class name

[ https://issues.apache.org/jira/browse/KAFKA-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-5230: - Reviewer: Gwen Shapira Status: Patch Available (was: Open) > Recommended va

[jira] [Commented] (KAFKA-5230) Recommended values for Connect transformations contain the wrong class name

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

[GitHub] kafka pull request #3044: KAFKA-5230: Fix conversion of Class configs to han...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/3044 KAFKA-5230: Fix conversion of Class configs to handle nested classes properly You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka kafk

[jira] [Updated] (KAFKA-5230) Recommended values for Connect transformations contain the wrong class name

[ https://issues.apache.org/jira/browse/KAFKA-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-5230: - Fix Version/s: 0.10.2.2 0.11.0.0 > Recommended values for Conne

[jira] [Assigned] (KAFKA-5230) Recommended values for Connect transformations contain the wrong class name

[ https://issues.apache.org/jira/browse/KAFKA-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-5230: Assignee: Ewen Cheslack-Postava > Recommended values for Connect transforma

[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=16009464#comment-16009464 ] ASF GitHub Bot commented on KAFKA-5167: --- Github user mjsax closed the pull request a

[GitHub] kafka pull request #3001: KAFKA-5167: fix unreleased state lock due to uncau...

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

[jira] [Commented] (KAFKA-5226) NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize

[ https://issues.apache.org/jira/browse/KAFKA-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009462#comment-16009462 ] Matthias J. Sax commented on KAFKA-5226: [~ian.springer] You are right -- I mixed

[jira] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009460#comment-16009460 ] Matthias J. Sax edited comment on KAFKA-5154 at 5/13/17 6:42 PM: ---

[jira] [Commented] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009460#comment-16009460 ] Matthias J. Sax commented on KAFKA-5154: [~Lukas Gemela] Thanks. This helps alread

[jira] [Commented] (KAFKA-5226) NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize

[ https://issues.apache.org/jira/browse/KAFKA-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009418#comment-16009418 ] Ian Springer commented on KAFKA-5226: - The key serde is not a custom serde. It's org.

[jira] [Commented] (KAFKA-3455) Connect custom processors with the streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009389#comment-16009389 ] Bobby Calderwood commented on KAFKA-3455: - The current Interface definitions for `

[jira] [Updated] (KAFKA-5233) Changes to punctuate semantics (KIP-138)

[ https://issues.apache.org/jira/browse/KAFKA-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Borowiecki updated KAFKA-5233: - Labels: kip (was: ) > Changes to punctuate semantics (KIP-138) >

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

Thank you all! This KIP passed the vote with 3 binding and 5 non-binding +1s: +1 (binding) from Guozhang Wang, Ismael Juma and Ewen Cheslack-Postava +1 (non-binding) from Matthias J. Sax, Bill Bejeck, Eno Thereska, Arun Mathew and Thomas Becker Created KAFKA-5233

[jira] [Commented] (KAFKA-3514) Stream timestamp computation needs some further thoughts

[ https://issues.apache.org/jira/browse/KAFKA-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009365#comment-16009365 ] Michal Borowiecki commented on KAFKA-3514: -- I've created KAFKA-5233 to track work

[jira] [Created] (KAFKA-5233) Changes to punctuate semantics (KIP-138)

Michal Borowiecki created KAFKA-5233: Summary: Changes to punctuate semantics (KIP-138) Key: KAFKA-5233 URL: https://issues.apache.org/jira/browse/KAFKA-5233 Project: Kafka Issue Type: Im

[jira] [Commented] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

[ https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009314#comment-16009314 ] jaikiran pai commented on KAFKA-5232: - One of the crude (but easy) way to reproduce th

[jira] [Commented] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

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

[jira] [Updated] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

[ https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-5232: Status: Patch Available (was: Open) I just submitted a PR which contains a fix and includes a testc

[GitHub] kafka pull request #3043: KAFKA-5232 Fix Log.parseTopicPartitionName to take...

GitHub user jaikiran opened a pull request: https://github.com/apache/kafka/pull/3043 KAFKA-5232 Fix Log.parseTopicPartitionName to take into account dot character in topic names of deleted topics The commit here contains a fix and testcase for the issue reported in https://issues.

[jira] [Updated] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

[ https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-5232: Description: We are using 0.10.2.0 (but this is reproducible even with 0.10.2.1 and latest upstream

[jira] [Created] (KAFKA-5232) Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime

jaikiran pai created KAFKA-5232: --- Summary: Kafka broker fails to start if a topic containing dot in its name is marked for delete but hasn't been deleted during previous uptime Key: KAFKA-5232 URL: https://issues.ap

[GitHub] kafka pull request #3042: MINOR: More informative assertion for flaky metric...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3042 MINOR: More informative assertion for flaky metrics test You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka more-informative-assertion-f

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

See Changes: [ismael] MINOR: Improve shutdown sequence [ismael] MINOR: Various small improvements to kafka.metrics.MetricsTest -- [...truncated 3.24 MB...] org.apache.ka

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

See Changes: [ismael] MINOR: Various small improvements to kafka.metrics.MetricsTest -- [...truncated 858.39 KB...] kafka.log.BrokerCompressionTest > testBrokerSideCompres

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

See Changes: [ismael] MINOR: Improve shutdown sequence -- [...truncated 860.87 KB...] kafka.server.LogOffsetTest > testEmptyLogsGetOffsets PASSED kafka.server.LogOffsetTe

[GitHub] kafka pull request #3034: MINOR: Various small improvements to kafka.metrics...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3034 --- 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 #3041: MINOR: Eliminate PID terminology from non test cod...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3041 MINOR: Eliminate PID terminology from non test code Producer id is used instead. Also refactored TransactionLog schema code to follow our naming convention and to have better structure. Y

[GitHub] kafka pull request #3030: MINOR: Improve shutdown sequence

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3030 --- 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 #3039: MINOR: Close ZooKeeper clients in tests

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