[
https://issues.apache.org/jira/browse/KAFKA-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-7369.
Resolution: Fixed
Fix Version/s: 2.1.0
2.0.1
> Retry when possibl
Do you want to raise a KIP and explain the motivation behind it ?
Please ignore if you’re doing that already.
Thanks ,
On Sat, 1 Sep 2018 at 00:15, Robert Yokota (JIRA) wrote:
> Robert Yokota created KAFKA-7370:
>
>
> Summary: Enhance FileConfi
Robert Yokota created KAFKA-7370:
Summary: Enhance FileConfigProvider to read a directory
Key: KAFKA-7370
URL: https://issues.apache.org/jira/browse/KAFKA-7370
Project: Kafka
Issue Type: Impr
Jason Gustafson created KAFKA-7369:
--
Summary: Retry when possible in AdminClient.listConsumerGroups
Key: KAFKA-7369
URL: https://issues.apache.org/jira/browse/KAFKA-7369
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-7287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-7287.
Resolution: Fixed
Fix Version/s: 2.1.0
2.0.1
1.1.2
Also merged
John Roesler created KAFKA-7368:
---
Summary: Support joining Windowed KTables
Key: KAFKA-7368
URL: https://issues.apache.org/jira/browse/KAFKA-7368
Project: Kafka
Issue Type: Improvement
John Roesler created KAFKA-7367:
---
Summary: Verify that Streams never creates RocksDB stores unless
they are needed
Key: KAFKA-7367
URL: https://issues.apache.org/jira/browse/KAFKA-7367
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Roesler resolved KAFKA-4988.
-
Resolution: Won't Fix
I think this issue is out of our hands.
If you think there is something fo
[
https://issues.apache.org/jira/browse/KAFKA-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Roesler resolved KAFKA-6033.
-
Resolution: Won't Fix
This is unfortunately out of our hands.
If you think I'm wrong about this,
@Guozhang Wang Could you review this again when you have time? Thanks! -Yishun
On Wed, Aug 29, 2018 at 11:57 AM Yishun Guan wrote:
>
> Hi, because I have made some significant changes on this design, so I
> want to reopen the discussion on this KIP:
> https://cwiki.apache.org/confluence/x/CgZPBQ
>
Yeah, let's go ahead and do that to minimize confusion and to stick to the
formal process.
Sorry for the run-around.
Thanks,
-John
On Fri, Aug 31, 2018 at 11:27 AM Joan Goyeau wrote:
> Ah ok I didn't know we need multiple binding vote.
> Should I send again a new email with the updated KIP-366
Hi Nikolay,
You can start a PR any time, but we cannot per it (and probably won't do
serious reviews) until after the KIP is voted and approved.
Sometimes people start a PR during discussion just to help provide more
context, but it's not required (and can also be distracting because the KIP
disc
Jun Rao created KAFKA-7366:
--
Summary: topic level segment.bytes and segment.ms not taking
effect immediately
Key: KAFKA-7366
URL: https://issues.apache.org/jira/browse/KAFKA-7366
Project: Kafka
Iss
Ah ok I didn't know we need multiple binding vote.
Should I send again a new email with the updated KIP-366 title?
Thanks
On Wed, 29 Aug 2018 at 21:14 John Roesler wrote:
> Hey Joan,
>
> It looks like you've updated the KIP to "Accepted", but I only count one
> binding vote (Guozhang). Ted, Att
Hi Nickolay,
Thanks for the clarification.
-Bill
On Fri, Aug 31, 2018 at 11:59 AM Nikolay Izhikov
wrote:
> Hello, John.
>
> This is my first KIP, so, please, help me with kafka development process.
>
> Should I start to work on PR now? Or should I wait for a "+1" from
> commiters?
>
> В Пт, 31
Hello, John.
This is my first KIP, so, please, help me with kafka development process.
Should I start to work on PR now? Or should I wait for a "+1" from commiters?
В Пт, 31/08/2018 в 10:33 -0500, John Roesler пишет:
> I see. I guess that once we are in the PR-reviewing phase, we'll be in a
> be
Hi Seweryn,
It's a little hard to say. For one thing, extra threads have some overhead
of their own, but I agree with you that the bulk of the extra memory would
come from the extra throughput you're able to drive through the application.
I haven't done any analysis of this before, so just reason
I see. I guess that once we are in the PR-reviewing phase, we'll be in a
better position to see what else can/should be done, and we can talk about
follow-on work at that time.
Thanks for the clarification,
-John
On Fri, Aug 31, 2018 at 1:19 AM Nikolay Izhikov wrote:
> Hello, Bill
>
> > In the
Is using /opt/confluent-4.1.1/bin/kafka-run-class kafka.tools.DumpLogSegments
kafka.tools.DumpLogSegments –files --print-data-log, correct way
to verify that the kafka logs are compressed, if using compression.type=snappy?
I have set my compression.type: snappy in my property file for kafka str
I just updated the draft implementation[^1], rebasing against the latest
trunk and implementing error routine (i.e., Error code 74 for
UnsupportedCompressionTypeException.) Since we decided to disallow all
fetch request below version 2.1.0 for the topics specifying ZStandard, I
added an error logic
Hi all,
I have updated the KIP based on the suggestions received so far, please
take a look at the new version:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-363%3A+Allow+performance+tools+to+print+final+results+to+output+file
Best,
- Attila
On Fri, Aug 24, 2018 at 3:52 PM Attila Sasvári
Yes I’m more than happy to change it to a more appropriate name.
The issue with RoundRobinPatitoner is that the DefaultPartitioner already
has a Round-Robin associated to it. But if community doesn’t mind the name,
I don’t either.
Thanks for reading the KIP btw.
Regards,
On Fri, 31 Aug 2018 at
Kashyap Ivaturi created KAFKA-7365:
--
Summary: max.poll.records setting in Kafka Consumer is not working
Key: KAFKA-7365
URL: https://issues.apache.org/jira/browse/KAFKA-7365
Project: Kafka
I
23 matches
Mail list logo
