Thanks for the KIP.
I don't think I fully digested the proposal yet, but my first reaction
is: this is quite complicated. Frankly, I am worried about complexity
and usability.
Especially the option `safe_latest` is a "weird" one IMHO, and `nearest`
is even more complex.
The problem at
Thanks for the KIP. Overall a good addition.
I am actually not sure if we need to add a new class? From my
understanding, if there is exactly one abstract method, the interface is
still functional? Thus, we could add a new method to
`StreamsPartitioner` with a default implementation (that
Hi, Artem,
Thanks for the KIP.
Could you explain the partition level ProducerIdCount a bit more? Does that
reflect the number of PIDs ever produced to a partition since the broker is
started? Do we reduce the count after a PID expires?
Thanks,
Jun
On Wed, Jun 22, 2022 at 1:08 AM David Jacot
Hi Jorge,
Apologies for the long delay, had my own KIP-related work to focus on.
I think it's fine to include array accesses but it's not a blocker. I'm +1
either way. On that front though, I think the MaskField section might need
to be updated as it still mentions arrays and deep-scan?
Cheers,
Hi everyone,
I'd like to bump this vote thread. Currently it's missing 1 +1 binding vote
to pass (2 +1 binding, 1 +1 non-binding).
There has been additional discussions to consider array access and
deep-scan (similar to JsonPath) but hasn't been included as part of this
KIP.
The only minor
Hi there,
I have update the KIP to the previous state voted, including the
configuration change from `field.style` to `field.syntax.version`.
I'll bump the vote thread as well to see if there's agreement on adding
this feature to Connect.
Cheers,
Jorge.
On Wed, 15 Jun 2022 at 23:02, Jorge
bbejeck commented on PR #395:
URL: https://github.com/apache/kafka-site/pull/395#issuecomment-1169015004
Hi @Venom-git - I was about to merge this PR but it renders like this for me
