[
https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4935:
---
Fix Version/s: 0.11.0.0
> Consider disabling record level CRC checks for message format V2
>
[
https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4935:
---
Resolution: Fixed
Fix Version/s: (was: 0.11.0.0)
0.11.1.0
[
https://issues.apache.org/jira/browse/KAFKA-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023656#comment-16023656
]
Ismael Juma commented on KAFKA-5211:
This particular JIRA doesn't need a KIP because it's indeed just
[
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)
[
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
[
https://issues.apache.org/jira/browse/KAFKA-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5310:
---
Fix Version/s: 0.11.0.0
> reset ControllerContext during resignation
>
[
https://issues.apache.org/jira/browse/KAFKA-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5236:
---
Labels: regression (was: )
> Regression in on-disk log size when using Snappy compression with 0.8.2
[
https://issues.apache.org/jira/browse/KAFKA-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5236:
---
Fix Version/s: 0.11.0.0
> Regression in on-disk log size when using Snappy compression with 0.8.2 log
[
https://issues.apache.org/jira/browse/KAFKA-5291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017637#comment-16017637
]
Ismael Juma commented on KAFKA-5291:
cc [~cmccabe]
> AdminClient should not trigger auto creation of
[
https://issues.apache.org/jira/browse/KAFKA-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5294:
---
Fix Version/s: 0.11.0.0
> PlainSaslServerFactory should allow a null Map in getMechanismNames
>
[
https://issues.apache.org/jira/browse/KAFKA-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017505#comment-16017505
]
Ismael Juma commented on KAFKA-5294:
Thanks for the report. This is a simple fix, so we should do it.
[
https://issues.apache.org/jira/browse/KAFKA-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5294:
---
Priority: Major (was: Minor)
> PlainSaslServerFactory should allow a null Map in getMechanismNames
>
[
https://issues.apache.org/jira/browse/KAFKA-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5293:
---
Description:
The PR for KAFKA-3878 implemented KIP-144 with one exception: it automatically
enables
[
https://issues.apache.org/jira/browse/KAFKA-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5293:
---
Issue Type: Bug (was: Improvement)
> Do not apply exponential backoff if users have overridden
Ismael Juma created KAFKA-5293:
--
Summary: Do not apply exponential backoff if users have overridden
reconnect.backoff.ms
Key: KAFKA-5293
URL: https://issues.apache.org/jira/browse/KAFKA-5293
Project:
[
https://issues.apache.org/jira/browse/KAFKA-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3878:
---
Summary: Exponential backoff for broker reconnect attempts (KIP-144) (was:
Exponential backoff for
[
https://issues.apache.org/jira/browse/KAFKA-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3878:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request
Ismael Juma created KAFKA-5292:
--
Summary: Authorization tests for AdminClient
Key: KAFKA-5292
URL: https://issues.apache.org/jira/browse/KAFKA-5292
Project: Kafka
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/KAFKA-5291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5291:
---
Status: Patch Available (was: Open)
> AdminClient should not trigger auto creation of topics
>
Ismael Juma created KAFKA-5291:
--
Summary: AdminClient should not trigger auto creation of topics
Key: KAFKA-5291
URL: https://issues.apache.org/jira/browse/KAFKA-5291
Project: Kafka
Issue Type:
[
https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017122#comment-16017122
]
Ismael Juma edited comment on KAFKA-5289 at 5/19/17 9:33 AM:
-
[~xuzq_zander],
[
https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017122#comment-16017122
]
Ismael Juma commented on KAFKA-5289:
[~xuzq_zander], because we don't to delay the response while the
[
https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reassigned KAFKA-5289:
--
Assignee: Ismael Juma
> One StopReplicaRequest will caused two Responses
>
[
https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5289:
---
Fix Version/s: 0.11.0.0
Status: Patch Available (was: Open)
> One StopReplicaRequest will
[
https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017075#comment-16017075
]
Ismael Juma commented on KAFKA-5289:
Thanks for the report. Great catch. What kind of exceptions can
[
https://issues.apache.org/jira/browse/KAFKA-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4291:
---
Summary: TopicCommand --describe shows topics marked for deletion as
under-replicated and unavailable
[
https://issues.apache.org/jira/browse/KAFKA-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reassigned KAFKA-4291:
--
Assignee: Ismael Juma (was: Mickael Maison)
> TopicCommand --describe shows topics marked for
[
https://issues.apache.org/jira/browse/KAFKA-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4291:
---
Labels: kip (was: )
> TopicCommand --describe shows topics marked for deletion as under-replicated
[
https://issues.apache.org/jira/browse/KAFKA-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-4222.
Resolution: Fixed
Assignee: Damian Guy (was: Eno Thereska)
> Transient failure in
[
https://issues.apache.org/jira/browse/KAFKA-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5258:
---
Resolution: Fixed
Fix Version/s: 0.11.0.0
Status: Resolved (was: Patch Available)
[
https://issues.apache.org/jira/browse/KAFKA-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3267:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request
[
https://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reassigned KAFKA-3995:
--
Assignee: Jiangjie Qin (was: Mayuresh Gharat)
> Split the ProducerBatch and resend when
[
https://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3995:
---
Status: Patch Available (was: Reopened)
> Split the ProducerBatch and resend when received
[
https://issues.apache.org/jira/browse/KAFKA-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3266:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Implement KIP-140 RPCs and APIs
[
https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reassigned KAFKA-5275:
--
Assignee: Ismael Juma
> Review and potentially tweak AdminClient API for the initial release
[
https://issues.apache.org/jira/browse/KAFKA-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5276:
---
Summary: Support derived and prefixed configs in DescribeConfigs (KIP-133)
(was: Support derived and
[
https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015081#comment-16015081
]
Ismael Juma commented on KAFKA-5275:
Because the ACLs and Configs PRs were developed in parallel,
Ismael Juma created KAFKA-5276:
--
Summary: Support derived and prefixed configs in DescribeConfigs
Key: KAFKA-5276
URL: https://issues.apache.org/jira/browse/KAFKA-5276
Project: Kafka
Issue
Ismael Juma created KAFKA-5275:
--
Summary: Review and potentially tweak AdminClient API for the
initial release (KIP-117)
Key: KAFKA-5275
URL: https://issues.apache.org/jira/browse/KAFKA-5275
Project:
[
https://issues.apache.org/jira/browse/KAFKA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5274:
---
Summary: Review and improve AdminClient Javadoc for the first release
(KIP-117) (was: Review and
Ismael Juma created KAFKA-5274:
--
Summary: Review and improve AdminClient Javadoc for the first
release
Key: KAFKA-5274
URL: https://issues.apache.org/jira/browse/KAFKA-5274
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5274:
---
Summary: Review and improve AdminClient Javadoc for the first release
(KIP-133) (was: Review and
[
https://issues.apache.org/jira/browse/KAFKA-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-5272 started by Ismael Juma.
--
> Improve validation for Describe/Alter Configs (KIP-133)
>
Ismael Juma created KAFKA-5272:
--
Summary: Improve validation for Describe/Alter Configs (KIP-133)
Key: KAFKA-5272
URL: https://issues.apache.org/jira/browse/KAFKA-5272
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3267:
---
Summary: Describe/Alter Configs protocol, server and client (KIP-133)
(was: Describe/Alter Configs
[
https://issues.apache.org/jira/browse/KAFKA-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5255:
---
Fix Version/s: 0.11.1.0
> Auto generate request/response classes
>
[
https://issues.apache.org/jira/browse/KAFKA-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3267:
---
Status: Patch Available (was: In Progress)
> Describe/Alter Configs protocol and server side
[
https://issues.apache.org/jira/browse/KAFKA-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5250:
---
Priority: Critical (was: Major)
> handleFetchRequest should do down conversion after throttling
>
[
https://issues.apache.org/jira/browse/KAFKA-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013872#comment-16013872
]
Ismael Juma commented on KAFKA-5261:
Is this a bottleneck? We have an in-memory cache:
{code}
[
https://issues.apache.org/jira/browse/KAFKA-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16012645#comment-16012645
]
Ismael Juma commented on KAFKA-977:
---
[~junrao], should we reopen this then? I believe there was at least
[
https://issues.apache.org/jira/browse/KAFKA-5257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5257.
Resolution: Fixed
> CLONE - Change Default unclean.leader.election.enabled from True to False
>
[
https://issues.apache.org/jira/browse/KAFKA-5257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16012595#comment-16012595
]
Ismael Juma commented on KAFKA-5257:
The original JIRA for KIP-106 was KAFKA-4623, but it somehow got
Ismael Juma created KAFKA-5255:
--
Summary: Auto generate request/response classes
Key: KAFKA-5255
URL: https://issues.apache.org/jira/browse/KAFKA-5255
Project: Kafka
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/KAFKA-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-977.
---
Resolution: Fixed
Marking this as fixed since it seems to be the same as KIP-101/KAFKA-1211.
>
[
https://issues.apache.org/jira/browse/KAFKA-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-977:
--
Fix Version/s: 0.11.0.0
> Implement generation/term per leader to reconcile messages correctly
>
[
https://issues.apache.org/jira/browse/KAFKA-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5215.
Resolution: Fixed
Fix Version/s: 0.11.0.0
Issue resolved by pull request 3013
[
https://issues.apache.org/jira/browse/KAFKA-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5175.
Resolution: Fixed
Fix Version/s: 0.11.0.0
Issue resolved by pull request 3067
[
https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reassigned KAFKA-4623:
--
Assignee: Sharad (was: Ben Stopford)
> Change Default unclean.leader.election.enabled from
[
https://issues.apache.org/jira/browse/KAFKA-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16011449#comment-16011449
]
Ismael Juma commented on KAFKA-5175:
Another instance:
{code}
java.lang.AssertionError: failed to get
[
https://issues.apache.org/jira/browse/KAFKA-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5244.
Resolution: Fixed
Issue resolved by pull request 3059
[https://github.com/apache/kafka/pull/3059]
Ismael Juma created KAFKA-5250:
--
Summary: handleFetchRequest should do down conversion after
throttling
Key: KAFKA-5250
URL: https://issues.apache.org/jira/browse/KAFKA-5250
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010821#comment-16010821
]
Ismael Juma commented on KAFKA-5244:
If you think the change makes sense, I could create a separate PR
[
https://issues.apache.org/jira/browse/KAFKA-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010820#comment-16010820
]
Ismael Juma commented on KAFKA-5244:
Good find [~rsivaram]. Note that in
[
https://issues.apache.org/jira/browse/KAFKA-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010645#comment-16010645
]
Ismael Juma edited comment on KAFKA-5182 at 5/15/17 2:57 PM:
-
This is still
[
https://issues.apache.org/jira/browse/KAFKA-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reopened KAFKA-5182:
This is still happening:
{code}
java.util.concurrent.ExecutionException: java.lang.AssertionError:
[
https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5232:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request
[
https://issues.apache.org/jira/browse/KAFKA-4965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4965:
---
Fix Version/s: 0.10.2.2
> set internal.leave.group.on.close to false in KafkaStreams
>
[
https://issues.apache.org/jira/browse/KAFKA-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5118:
---
Fix Version/s: 0.10.2.2
> Improve message for Kafka failed startup with non-Kafka data in data.dirs
>
[
https://issues.apache.org/jira/browse/KAFKA-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5230:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Recommended values for Connect
Ismael Juma created KAFKA-5238:
--
Summary: BrokerTopicMetrics can be recreated after topic is deleted
Key: KAFKA-5238
URL: https://issues.apache.org/jira/browse/KAFKA-5238
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009863#comment-16009863
]
Ismael Juma commented on KAFKA-5236:
Thanks for the report. The root cause is that the block size for
[
https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reassigned KAFKA-5232:
--
Assignee: jaikiran pai
> Kafka broker fails to start if a topic containing dot in its name is
[
https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5232:
---
Priority: Critical (was: Major)
> Kafka broker fails to start if a topic containing dot in its name
[
https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5232:
---
Fix Version/s: 0.11.0.0
> Kafka broker fails to start if a topic containing dot in its name is marked
[
https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5232:
---
Fix Version/s: 0.10.2.2
> Kafka broker fails to start if a topic containing dot in its name is marked
[
https://issues.apache.org/jira/browse/KAFKA-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5180:
---
Resolution: Fixed
Fix Version/s: 0.11.0.0
Status: Resolved (was: Patch Available)
[
https://issues.apache.org/jira/browse/KAFKA-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4982:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request
[
https://issues.apache.org/jira/browse/KAFKA-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5227.
Resolution: Fixed
Fix Version/s: 0.11.0.0
Issue resolved by pull request 3037
[
https://issues.apache.org/jira/browse/KAFKA-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008535#comment-16008535
]
Ismael Juma commented on KAFKA-4982:
Thanks! Can you please send an update to the KIP thread as well?
[
https://issues.apache.org/jira/browse/KAFKA-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4982:
---
Summary: Add listener tag to socket-server-metrics.connection-... metrics
(KIP-136) (was: Add
[
https://issues.apache.org/jira/browse/KAFKA-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4982:
---
Status: Patch Available (was: Open)
> Add listener tag to socket-server-metrics.connection-...
[
https://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008023#comment-16008023
]
Ismael Juma commented on KAFKA-3995:
Can we update the title of the JIRA, please?
> Add a new
[
https://issues.apache.org/jira/browse/KAFKA-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5194:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request
[
https://issues.apache.org/jira/browse/KAFKA-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5173.
Resolution: Fixed
Assignee: Rajini Sivaram
We believe this was fixed by
[
https://issues.apache.org/jira/browse/KAFKA-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4343:
---
Fix Version/s: 0.11.0.0
> Connect REST API should expose whether each connector is a source or sink
>
[
https://issues.apache.org/jira/browse/KAFKA-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4343:
---
Status: Patch Available (was: Open)
> Connect REST API should expose whether each connector is a
[
https://issues.apache.org/jira/browse/KAFKA-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4343:
---
Labels: kip newbie++ (was: needs-kip newbie++)
> Connect REST API should expose whether each
[
https://issues.apache.org/jira/browse/KAFKA-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5182.
Resolution: Fixed
Fix Version/s: 0.11.0.0
Issue resolved by pull request 3014
[
https://issues.apache.org/jira/browse/KAFKA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4422:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request
[
https://issues.apache.org/jira/browse/KAFKA-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5194:
---
Status: Patch Available (was: Open)
> KIP-153: Include only client traffic in BytesOutPerSec metric
[
https://issues.apache.org/jira/browse/KAFKA-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5194:
---
Summary: KIP-153: Include only client traffic in BytesOutPerSec metric
(was: KIP-153 : Include only
[
https://issues.apache.org/jira/browse/KAFKA-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005578#comment-16005578
]
Ismael Juma commented on KAFKA-5213:
Good catch.
> IllegalStateException in ensureOpenForRecordAppend
[
https://issues.apache.org/jira/browse/KAFKA-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5213:
---
Priority: Critical (was: Major)
> IllegalStateException in ensureOpenForRecordAppend
>
[
https://issues.apache.org/jira/browse/KAFKA-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5213:
---
Fix Version/s: 0.11.0.0
> IllegalStateException in ensureOpenForRecordAppend
>
[
https://issues.apache.org/jira/browse/KAFKA-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004720#comment-16004720
]
Ismael Juma commented on KAFKA-4689:
[~enothereska], we filed a new issue for re-enabling. As
[
https://issues.apache.org/jira/browse/KAFKA-5184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004547#comment-16004547
]
Ismael Juma commented on KAFKA-5184:
The issue reported here seems like it can never happen. I added
[
https://issues.apache.org/jira/browse/KAFKA-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5208.
Resolution: Duplicate
Duplicate of KAFKA-5173.
> Transient failure:
>
[
https://issues.apache.org/jira/browse/KAFKA-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5176.
Resolution: Fixed
> AdminClient: add controller and clusterId methods to DescribeClusterResults
>
[
https://issues.apache.org/jira/browse/KAFKA-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5041:
---
Fix Version/s: (was: 0.11.0.0)
0.11.1.0
> Kafka TestKit library
>
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000574#comment-16000574
]
Ismael Juma commented on KAFKA-4669:
The issue is that if we can't retrieve the channel, then we
801 - 900 of 3684 matches
Mail list logo
