Hi,
I have not seen any feedback on this KIP.
I'll wait a few more days and if I don't see anything, I'll start a
vote early next week.
Thanks
On Thu, Jan 28, 2021 at 10:43 AM Mickael Maison
wrote:
>
> Hi all,
>
> I would like to start a discussion on KIP-699:
> https://cwiki.apache.org/conflue
Thanks everyone for the votes.
This KIP is accepted with
+3 binding (Harsha, Mani, and Jun) votes, and
+4 non-binding (Kowshik, Ivan, Kamal, and Prateek) votes.
On Wed, 17 Feb 2021 at 22:38, Prateek Agarwal wrote:
>
> +1 (non-binding).
>
> On Wed, Feb 17, 2021 at 5:53 AM Jun Rao wrote:
>
Hi Levani,
Thank you for the KIP.
Really interesting!
Here my comments:
1. To be consistent with the other configs that involve standbys , I
would rename
standby.task.assignment.awareness -> standby.replicas.awareness
2. I would also rename the prefix
instance.tag -> client.tag
3. The foll
Ramil Israfilov created KAFKA-12336:
---
Summary: custom stream naming does not work while calling
stream[K, V](topicPattern: Pattern) API with named Consumed parameter
Key: KAFKA-12336
URL: https://issues.apache.
Ramil Israfilov created KAFKA-12337:
---
Summary: provide full scala api for operators naming
Key: KAFKA-12337
URL: https://issues.apache.org/jira/browse/KAFKA-12337
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-12303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Maison resolved KAFKA-12303.
Fix Version/s: 3.0.0
Resolution: Fixed
> Flatten SMT drops some fields when null va
[
https://issues.apache.org/jira/browse/KAFKA-10833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Maison resolved KAFKA-10833.
Fix Version/s: 2.8.0
Resolution: Fixed
> KIP-661: Expose task configurations in Con
dengziming created KAFKA-12338:
--
Summary: The code of MetadataRecordSerde duplicate with
MetadataParser
Key: KAFKA-12338
URL: https://issues.apache.org/jira/browse/KAFKA-12338
Project: Kafka
Is
Hello everyone,
* Sorry, I meant KIP-710.
Right now the MirrorMaker cluster is somewhat unreliable, and not
supporting running in a cluster properly. I'd say that fixing this would be
a nice addition.
Does anyone have some input on this?
Thanks in advance
Daniel
Dániel Urbán ezt írta (időpont:
Hi,
I'd like to volunteer to be the release manager for the next bugfix
release, 2.7.1.
I created the release plan on the wiki:
https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+2.7.1
Thanks
Hello!
Recently, we need to build a compilation and development environment for Kafka
2.7.0 source code. Now the source code can run successfully. However, when we
execute "gradle install" or "gradle build", we will report an error: @ nowarn
annotation does not suppress any warnings. The detai
Hello again, all.
This is a notice that we are now in Code Freeze for the 2.8 branch.
>From now until the release, only fixes for blockers should be merged to the
>release branch. Fixes for failing tests are allowed and encouraged.
>Documentation-only commits are also ok, in case you have forg
Thanks for volunteering Mickael. Are there any critical bugs in 2.7.0 so
far that motivated the release? There doesn't have to be, but I'd be
interested to know if there are.
Ismael
On Thu, Feb 18, 2021 at 7:58 AM Mickael Maison wrote:
> Hi,
>
> I'd like to volunteer to be the release manager f
Hi all,
I realized that the DISCUSS thread got very long, so I'll be posting
updates to this thread from now on.
Just a quick update to the KIP. As a part of
https://issues.apache.org/jira/browse/KAFKA-12332 and
https://github.com/apache/kafka/pull/10143, I'm proposing adding a new
error.
INCONSIST
Chia-Ping Tsai created KAFKA-12339:
--
Summary: Starting new connector cluster with new internal topics
is unstable due to UnknownTopicOrPartitionException
Key: KAFKA-12339
URL: https://issues.apache.org/jira/brows
Randall Hauch created KAFKA-12340:
-
Summary: Recent change to use SharedTopicAdmin results in
potential resource leak in deprecated backing store constructors
Key: KAFKA-12340
URL: https://issues.apache.org/jira/b
Cosmin Giurgiu created KAFKA-12341:
--
Summary: Duplicate javassist library found in broker classpath
Key: KAFKA-12341
URL: https://issues.apache.org/jira/browse/KAFKA-12341
Project: Kafka
Iss
You guys have done a great job enabling mixed client/broker compatibility since
the early days, before 0.10.x.x
Are there any plans to bring the matrix [1] up-to-date?
Even just adding "any broker > 1.0.0 - Java: any version" (if that's true)
would be helpful.
TIA
[1]: https://cwiki.apache.or
Jason Gustafson created KAFKA-12342:
---
Summary: Get rid of raft/meta log shim layer
Key: KAFKA-12342
URL: https://issues.apache.org/jira/browse/KAFKA-12342
Project: Kafka
Issue Type: Improve
Randall Hauch created KAFKA-12343:
-
Summary: Recent change to use SharedTopicAdmin in KakfkaBasedLog
fails with AK 0.10.x brokers
Key: KAFKA-12343
URL: https://issues.apache.org/jira/browse/KAFKA-12343
Leah Thomas created KAFKA-12344:
---
Summary: Support SlidingWindows in the Scala API
Key: KAFKA-12344
URL: https://issues.apache.org/jira/browse/KAFKA-12344
Project: Kafka
Issue Type: Improvement
Feel free to edit the wiki page directly.
On 2/18/21 11:19 AM, Gary Russell wrote:
> You guys have done a great job enabling mixed client/broker compatibility
> since the early days, before 0.10.x.x
>
> Are there any plans to bring the matrix [1] up-to-date?
>
> Even just adding "any broker > 1
[
https://issues.apache.org/jira/browse/KAFKA-12331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-12331.
-
Resolution: Fixed
> KafkaRaftClient should use the LEO when appending LeaderChangeMessag
[
https://issues.apache.org/jira/browse/KAFKA-12278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-12278.
-
Resolution: Fixed
> Keep api versions consistent with api scope
> --
[
https://issues.apache.org/jira/browse/KAFKA-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-12232.
-
Resolution: Duplicate
> Distinguish API scope by broker/controller
> ---
Alok Nikhil created KAFKA-12345:
---
Summary: KIP-500: AlterIsrManager crashes on broker idle-state
Key: KAFKA-12345
URL: https://issues.apache.org/jira/browse/KAFKA-12345
Project: Kafka
Issue Typ
Hello, please use gradlew, for example `./gradlew jar` `./gradlew idea`, or you
can use the gradle plugin of IDEA.
The `@ nowarn` warn seems to be related to different version of scala and jdk
which you can just ignore.
> On Feb 18, 2021, at 16:38, 韩可 mailto:han...@cvicse.com>>
> wrote:
>
> H
Yes, and also, you can check the readme in kafka github repo for more
details.
ref: https://github.com/apache/kafka/blob/trunk/README.md
Thanks.
Luke
On Fri, Feb 19, 2021 at 9:51 AM deng ziming
wrote:
> Hello, please use gradlew, for example `./gradlew jar` `./gradlew idea`,
> or you can use th
[
https://issues.apache.org/jira/browse/KAFKA-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-9524.
Fix Version/s: 2.8.0
Resolution: Fixed
> Default window retention does not consider
[
https://issues.apache.org/jira/browse/KAFKA-12258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-12258.
-
Resolution: Fixed
> Change the BatchAccumulator to split records into batches
>
Hi, Kafka.
Recently I noticed that splitting partition may cause message delivery loss
for consumers with auto.offset.reset=latest.
I described details in https://issues.apache.org/jira/browse/KAFKA-12261 .
Since delivery loss is undesired in most cases, I think this should be
described in Consu
Arindam Ray created KAFKA-12346:
---
Summary: punctuate is called at twice the duration passed as the
first argument to Processor.Schedule (with PunctuationType.WALL_CLOCK_TIME)
Key: KAFKA-12346
URL: https://issues.apa
Hi Okada san,
Yes, I agree the "latest" setting in this situation is not good, and we
should document it.
But I don't think we should change the default auto.offset.reset setting to
the earliest.
The auto.offset.reset setting starts before kafka V1.0, which means, there
are already a lot of users u
Thanks for your quick response.
Yeah, agree with that. (also replied on the issue)
2021年2月19日(金) 16:25 Luke Chen :
> Hi Okada san,
> Yes, I agree the "latest" setting in this situation is not good, and we
> should document it.
> But I don't think we should change the default auto.offset.reset set
34 matches
Mail list logo
