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

See Changes: [ismael] MINOR: Move a few methods from the `ZKUtils` class to the companion [cshapi] MINOR: Update Kafka configuration documentation to use kafka-configs.… [cshapi] KAFKA-4052: Allow passing properties file to

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

See Changes: [ismael] MINOR: Move a few methods from the `ZKUtils` class to the companion -- [...truncated 12257 lines...] org.apache.kafka.streams.processor.internals.MinTimestampTrackerTest >

[jira] [Commented] (KAFKA-1650) Mirror Maker could lose data on unclean shutdown.

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

[GitHub] kafka pull request #1654: MINOR: Update MirrorMaker docs to remove multiple ...

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

[GitHub] kafka pull request #1706: MINOR: doc changes for QueueTimeMs JMX metrics.

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1706 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Resolved] (KAFKA-3742) Can't run connect-distributed.sh with -daemon flag

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

[jira] [Commented] (KAFKA-3742) Can't run connect-distributed.sh with -daemon flag

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

[GitHub] kafka pull request #1717: KAFKA-3742: (FIX) Can't run bin/connect-*.sh with ...

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

[GitHub] kafka pull request #1789: MINOR: Improve log message in `ReplicaManager.beco...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1789 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-4070) Implement a useful Struct.toString()

[ https://issues.apache.org/jira/browse/KAFKA-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-4070: Assignee: Shikhar Bhushan > Implement a useful Struct.toString() >

[jira] [Commented] (KAFKA-4070) Implement a useful Struct.toString()

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

[GitHub] kafka pull request #1790: KAFKA-4070: implement Connect Struct.toString()

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1790 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Resolved] (KAFKA-4070) Implement a useful Struct.toString()

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

[jira] [Commented] (KAFKA-4052) Allow passing properties file to ProducerPerformance

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

[GitHub] kafka pull request #1749: KAFKA-4052: Allow passing properties file to Produ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1749 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-4052) Allow passing properties file to ProducerPerformance

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

[GitHub] kafka pull request #1772: MINOR: Update Kafka configuration documentation to...

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

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

See Changes: [ismael] HOTFIX: disabled application-reset-tool integration test [ismael] HOTFIX: Fix verbose logging in ControllerChannelManager.brokerReady -- [...truncated 12215 lines...]

[GitHub] kafka pull request #1775: MINOR: Move a few methods from the `ZKUtils` class...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1775 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-4089) KafkaProducer raises Batch Expired exception

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

[GitHub] kafka pull request #1791: KAFKA-4089: KafkaProducer expires batch when metad...

GitHub user sutambe opened a pull request: https://github.com/apache/kafka/pull/1791 KAFKA-4089: KafkaProducer expires batch when metadata is stale You can merge this pull request into a Git repository by running: $ git pull https://github.com/sutambe/kafka batch-expired

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

See

[jira] [Updated] (KAFKA-4089) KafkaProducer raises Batch Expired exception

[ https://issues.apache.org/jira/browse/KAFKA-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumant Tambe updated KAFKA-4089: Description: The basic idea of batch expiration is that we don't expire batches when producer

[jira] [Updated] (KAFKA-4089) KafkaProducer raises Batch Expired exception

[ https://issues.apache.org/jira/browse/KAFKA-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumant Tambe updated KAFKA-4089: Description: The basic idea of batch expiration is that we don't expire batches when producer

[jira] [Updated] (KAFKA-4089) KafkaProducer raises Batch Expired exception

[ https://issues.apache.org/jira/browse/KAFKA-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumant Tambe updated KAFKA-4089: Description: The basic idea of batch expiration is that we don't expire batches when producer

[jira] [Updated] (KAFKA-4089) KafkaProducer raises Batch Expired exception

[ https://issues.apache.org/jira/browse/KAFKA-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumant Tambe updated KAFKA-4089: Description: The basic idea of batch expiration is that we don't expire batches when producer

[jira] [Commented] (KAFKA-4070) Implement a useful Struct.toString()

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

[GitHub] kafka pull request #1790: KAFKA-4070: implement Connect Struct.toString()

GitHub user shikhar opened a pull request: https://github.com/apache/kafka/pull/1790 KAFKA-4070: implement Connect Struct.toString() You can merge this pull request into a Git repository by running: $ git pull https://github.com/shikhar/kafka add-struct-tostring

[GitHub] kafka pull request #1786: HOTFIX: Fix verbose logging in ControllerChannelMa...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1786 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-4089) KafkaProducer raises Batch Expired exception

[ https://issues.apache.org/jira/browse/KAFKA-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumant Tambe updated KAFKA-4089: Description: The batch expiration logic ({{RecordAccumualator.abortExpiredBatches}}) ejects

[jira] [Assigned] (KAFKA-4089) KafkaProducer raises Batch Expired exception

[ https://issues.apache.org/jira/browse/KAFKA-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin reassigned KAFKA-4089: --- Assignee: Dong Lin > KafkaProducer raises Batch Expired exception >

[jira] [Created] (KAFKA-4089) KafkaProducer raises Batch Expired exception

Sumant Tambe created KAFKA-4089: --- Summary: KafkaProducer raises Batch Expired exception Key: KAFKA-4089 URL: https://issues.apache.org/jira/browse/KAFKA-4089 Project: Kafka Issue Type: Bug

[GitHub] kafka pull request #1789: MINOR: Improve log message in `ReplicaManager.beco...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1789 MINOR: Improve log message in `ReplicaManager.becomeLeaderOrFollower` You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka

[GitHub] kafka pull request #1785: HOTFIX: disabled application-reset-tool integratio...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1785 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-4088) Add regression check for KAFKA-4073

[ https://issues.apache.org/jira/browse/KAFKA-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437963#comment-15437963 ] Jun Rao commented on KAFKA-4088: It may be possible to cover this in a unit test.

[jira] [Commented] (KAFKA-4088) Add regression check for KAFKA-4073

[ https://issues.apache.org/jira/browse/KAFKA-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437930#comment-15437930 ] Ismael Juma commented on KAFKA-4088: Thanks for filing this. I think what we should do is basically

[jira] [Created] (KAFKA-4088) Add regression check for KAFKA-4073

Geoff Anderson created KAFKA-4088: - Summary: Add regression check for KAFKA-4073 Key: KAFKA-4088 URL: https://issues.apache.org/jira/browse/KAFKA-4088 Project: Kafka Issue Type: Test

[jira] [Commented] (KAFKA-3008) Connect should parallelize task start/stop

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

[GitHub] kafka pull request #1788: KAFKA-3008: Parallel start and stop of connectors ...

GitHub user kkonstantine opened a pull request: https://github.com/apache/kafka/pull/1788 KAFKA-3008: Parallel start and stop of connectors and tasks in Connect You can merge this pull request into a Git repository by running: $ git pull https://github.com/kkonstantine/kafka

Re: [DISCUSS] KIP-76: Enable getting password from executable rather than passing as plaintext in config files

I guess this should be KIP-77 ? KIP-76 is "Improve Kafka Streams Join Semantics" See http://search-hadoop.com/m/uyzND19SmQJ1yfCQ42/v=plain -Matthias On 08/25/2016 10:13 PM, Ashish Singh wrote: > Hey Gwen, > > You’re right that if someone can alter the executable then they can do > things in

[jira] [Work started] (KAFKA-3940) Log should check the return value of dir.mkdirs()

[ https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3940 started by Ishita Mandhan. - > Log should check the return value of dir.mkdirs() >

[GitHub] kafka pull request #1787: KAFKA-3940 Log should check the return value of di...

GitHub user imandhan opened a pull request: https://github.com/apache/kafka/pull/1787 KAFKA-3940 Log should check the return value of dir.mkdirs() You can merge this pull request into a Git repository by running: $ git pull https://github.com/imandhan/kafka KAFKA-3940

[jira] [Commented] (KAFKA-3940) Log should check the return value of dir.mkdirs()

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

Re: [DISCUSS] Remove beta label from the new Java consumer

I'm +1 also. I feel a lot more confident about this with all of the system testing we now have in place (including the tests covering Streams and Connect). -Jason On Thu, Aug 25, 2016 at 9:57 AM, Gwen Shapira wrote: > Makes sense :) > > On Thu, Aug 25, 2016 at 9:40 AM, Neha

Re: [DISCUSS] Time-based releases for Apache Kafka

I happily agree that Kafka is a solid and the community is great :) But I think there is a gap in perception here. For me, LTS means that someone is actively taking care of a release - actively backporting critical fixes (security, stability, data loss, corruption, hangs etc) from trunk to that

[GitHub] kafka pull request #1786: HOTFIX: Fix verbose logging in ControllerChannelMa...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1786 HOTFIX: Fix verbose logging in ControllerChannelManager.brokerReady You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka

Re: [DISCUSS] KIP-76: Enable getting password from executable rather than passing as plaintext in config files

Hey Gwen, You’re right that if someone can alter the executable then they can do things in the context of the thing running the script, like kafka. But if you were kafka admin user (or root), you could also do lots of things to lots of other different files owned by the user, so it’s not really

[jira] [Commented] (KAFKA-3940) Log should check the return value of dir.mkdirs()

[ https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437515#comment-15437515 ] ASF GitHub Bot commented on KAFKA-3940: --- Github user imandhan closed the pull request at:

[GitHub] kafka pull request #1748: KAFKA-3940 Log should check the return value of di...

Github user imandhan closed the pull request at: https://github.com/apache/kafka/pull/1748 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-4087) DefaultParitioner Implementation Issue

[ https://issues.apache.org/jira/browse/KAFKA-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated KAFKA-4087: -- Affects Version/s: 0.10.0.1 > DefaultParitioner Implementation Issue >

[jira] [Updated] (KAFKA-4087) DefaultParitioner Implementation Issue

[ https://issues.apache.org/jira/browse/KAFKA-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated KAFKA-4087: -- Description: In DefaultPartitioner implementation, when key is null if

[jira] [Created] (KAFKA-4087) DefaultParitioner Implementation Issue

Bharat Viswanadham created KAFKA-4087: - Summary: DefaultParitioner Implementation Issue Key: KAFKA-4087 URL: https://issues.apache.org/jira/browse/KAFKA-4087 Project: Kafka Issue Type:

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

See Changes: [junrao] KAFKA-4015; Change cleanup.policy config to accept a list of valid -- [...truncated 1 lines...]

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

See Changes: [junrao] KAFKA-4015; Change cleanup.policy config to accept a list of valid -- [...truncated 6875 lines...] kafka.api.AuthorizerIntegrationTest >

[jira] [Commented] (KAFKA-3083) a soft failure in controller may leave a topic partition in an inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437288#comment-15437288 ] Mayuresh Gharat commented on KAFKA-3083: [~fpj] do we have an umbrella jira where this issue is

RE: [DISCUSS] Time-based releases for Apache Kafka

I agree that the Kafka community has managed to maintain a very high quality level, so I'm not concerned about the quality of non-LTS releases. If the principle is that every release is supported for 2 years, that would be good. I suppose that if the burden of having that many in-support

[GitHub] kafka-site pull request #18: Implementation: Clean-up invalid HTML

GitHub user epeay opened a pull request: https://github.com/apache/kafka-site/pull/18 Implementation: Clean-up invalid HTML Small typo I found in `implementation.html` You can merge this pull request into a Git repository by running: $ git pull

Re: [DISCUSS] Remove beta label from the new Java consumer

Makes sense :) On Thu, Aug 25, 2016 at 9:40 AM, Neha Narkhede wrote: > Yeah, I'm supportive of this. > > On Thu, Aug 25, 2016 at 9:26 AM Ismael Juma wrote: > >> Hi Gwen, >> >> We have a few recent stories of people using Connect and Streams in >>

Re: [DISCUSS] Time-based releases for Apache Kafka

I prefer Ismael's suggestion for supporting 2-years (6 releases) rather than have designated LTS releases. The LTS model seems to work well when some releases are high quality (LTS) and the rest are a bit more questionable. It is great for companies like Redhat, where they have to invest less to

RE: [DISCUSS] Time-based releases for Apache Kafka

The proposal sounds pretty good, but the main thing currently missing is a proper long-term support release. Having 3 releases a year sounds OK, but if they're all equivalent and bugfix releases are produced for the most recent 2 or 3 releases, anyone wanting to run on an "in support" release

[GitHub] kafka pull request #1785: HOTFIX: disabled application-reset-tool integratio...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/1785 HOTFIX: disabled application-reset-tool integration test You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka disableTest Alternatively

Re: [DISCUSS] Remove beta label from the new Java consumer

Yeah, I'm supportive of this. On Thu, Aug 25, 2016 at 9:26 AM Ismael Juma wrote: > Hi Gwen, > > We have a few recent stories of people using Connect and Streams in > production. That means the new Java Consumer too. :) > > Ismael > > On Thu, Aug 25, 2016 at 5:09 PM, Gwen

Re: [DISCUSS] Remove beta label from the new Java consumer

Hi Gwen, We have a few recent stories of people using Connect and Streams in production. That means the new Java Consumer too. :) Ismael On Thu, Aug 25, 2016 at 5:09 PM, Gwen Shapira wrote: > Originally, we suggested keeping the beta label until we know someone >

Re: [DISCUSS] Remove beta label from the new Java consumer

Originally, we suggested keeping the beta label until we know someone successfully uses the new consumer in production. We can consider the recent KIPs enough, but IMO it will be better if someone with production deployment hanging out on our mailing list will confirm good experience with the new

Re: [DISCUSS] KIP-76: Enable getting password from executable rather than passing as plaintext in config files

Hi Ashish, I appreciate the need to integrate our authentication with other systems that store passwords. I am not sure that doing so by running a binary is the best solution. First, it does not add security: As you said, a file is just "sitting there" the same way an executable is just "sitting

Re: [VOTE] KIP-63: Unify store and downstream caching in streams

+1 On 08/25/2016 04:22 PM, Damian Guy wrote: > +1 > > On Thu, 25 Aug 2016 at 11:57 Eno Thereska wrote: > >> Hi folks, >> >> We'd like to start the vote for KIP-63. At this point the Wiki addresses >> all previous questions and we believe the PoC is feature-complete. >>

[jira] [Resolved] (KAFKA-4015) Change cleanup.policy config to accept a list of valid policies

[ https://issues.apache.org/jira/browse/KAFKA-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-4015. Resolution: Fixed Issue resolved by pull request 1742 [https://github.com/apache/kafka/pull/1742] > Change

[jira] [Commented] (KAFKA-4015) Change cleanup.policy config to accept a list of valid policies

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

[GitHub] kafka pull request #1742: KAFKA-4015: Change cleanup.policy config to accept...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1742 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-955) After a leader change, messages sent with ack=0 are lost

[ https://issues.apache.org/jira/browse/KAFKA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436999#comment-15436999 ] Mazhar Shaikh commented on KAFKA-955: - Hi All, affected version & fixed version is same, just want to

Re: [VOTE] KIP-63: Unify store and downstream caching in streams

+1 On Thu, 25 Aug 2016 at 11:57 Eno Thereska wrote: > Hi folks, > > We'd like to start the vote for KIP-63. At this point the Wiki addresses > all previous questions and we believe the PoC is feature-complete. > > Thanks > Eno >

Re: [DISCUSS] Time-based releases for Apache Kafka

Regarding bug fixes, you may want to consider to have an LTS release once a year - designating it for longer-term support / better for the masses. If you like that - then fix bugs in trunk, backport important ones to latest release + the last two LTS releases. Even if you don't - if a downstream

[VOTE] KIP-63: Unify store and downstream caching in streams

Hi folks, We'd like to start the vote for KIP-63. At this point the Wiki addresses all previous questions and we believe the PoC is feature-complete. Thanks Eno

[jira] [Commented] (KAFKA-3172) Consumer threads stay in 'Watiting' status and are blocked at consumer poll method

[ https://issues.apache.org/jira/browse/KAFKA-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436624#comment-15436624 ] Oleg Gorobets commented on KAFKA-3172: -- Looks like JDK bug:

[jira] [Commented] (KAFKA-4065) Property missing in ProcuderConfig.java - KafkaProducer API 0.9.0.0

[ https://issues.apache.org/jira/browse/KAFKA-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436585#comment-15436585 ] Manikumar Reddy commented on KAFKA-4065: Agree, currently new producer don't support

[jira] [Commented] (KAFKA-4074) Deleting a topic can make it unavailable even if delete.topic.enable is false

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

[GitHub] kafka pull request #1784: KAFKA-4074: Deleting a topic can make it unavailab...

GitHub user omkreddy opened a pull request: https://github.com/apache/kafka/pull/1784 KAFKA-4074: Deleting a topic can make it unavailable even if delete.topic.enable is false You can merge this pull request into a Git repository by running: $ git pull

Re: [DISCUSS] Time-based releases for Apache Kafka

Thanks for putting this together Gwen. I think it sounds reasonable and instead of trying to optimise every aspect of it ahead of time (which is hard, subjective and time-consuming), I am happy to try what is being proposed and tweak based on experience. One thing we should pay particular

[jira] [Updated] (KAFKA-3777) Extract the existing LRU cache out of RocksDBStore

[ https://issues.apache.org/jira/browse/KAFKA-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3777: Assignee: Damian Guy (was: Eno Thereska) > Extract the existing LRU cache out of RocksDBStore >

[jira] [Resolved] (KAFKA-3961) broker sends malformed response when switching from no compression to snappy/gzip

[ https://issues.apache.org/jira/browse/KAFKA-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dieter Plaetinck resolved KAFKA-3961. - Resolution: Invalid This is most likely due to an issue with the sarama client library ,