[jira] [Resolved] (KAFKA-7164) Follower should truncate after every leader epoch change

[ https://issues.apache.org/jira/browse/KAFKA-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7164. Resolution: Fixed Fix Version/s: 2.1.0 2.0.1 1.

[jira] [Created] (KAFKA-7279) partitionsFor implicitly creates topic for the existent topic

huxihx created KAFKA-7279: - Summary: partitionsFor implicitly creates topic for the existent topic Key: KAFKA-7279 URL: https://issues.apache.org/jira/browse/KAFKA-7279 Project: Kafka Issue Type: Bu

Re: [DISCUSS] KIP-349 Priorities for Source Topics

Ah, sorry, yes it does. On Sun, Aug 12, 2018 at 2:58 PM wrote: > Does this clarify ? > -- > Nick > > On Aug 9, 2018, at 7:44 PM, n...@afshartous.com wrote: > > Since there are questions I changed the heading from VOTE to DISCUSS > > On Aug 8, 2018, at 9:09 PM, Matt Farmer wrote: > > s it

Re: [DISCUSS] KIP-110: Add Codec for ZStandard Compression (Updated)

Colin and Jason, Thanks for your opinions. In summarizing, the Pros and Cons of bumping fetch API version are: Cons: - The Broker can't know whether a given message batch is compressed with zstd or not. - Need some additional logic for the topic explicitly configured to use zstd. Pros: - The b

Jenkins build is back to normal : kafka-2.0-jdk8 #114

See

Jenkins build is back to normal : kafka-trunk-jdk10 #395

See

Re: [DISCUSS] KIP-349 Priorities for Source Topics

Does this clarify ? -- Nick > On Aug 9, 2018, at 7:44 PM, n...@afshartous.com wrote: > > Since there are questions I changed the heading from VOTE to DISCUSS > >> On Aug 8, 2018, at 9:09 PM, Matt Farmer mailto:m...@frmr.me>> >> wrote: >> >> s it worth spelling out explicitly what the b

[jira] [Resolved] (KAFKA-7261) Request and response total metrics record bytes instead of request count

[ https://issues.apache.org/jira/browse/KAFKA-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-7261. --- Resolution: Fixed Reviewer: Jun Rao Fix Version/s: 2.1.0 2.

Re: [VOTE] KIP-349 Priorities for Source Topics

Both use-case: Command queue for a streams job and work-queue in general seem reasonable. Thank you for explaining. On Sun, Aug 12, 2018 at 6:34 AM, Matt Farmer wrote: > The work-queue use case is mostly how I see this being used, yes. > > In the most generic sense I can see its use in a situati

[jira] [Resolved] (KAFKA-7255) Timing issue in SimpleAclAuthorizer with concurrent create/update

[ https://issues.apache.org/jira/browse/KAFKA-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-7255. --- Resolution: Fixed > Timing issue in SimpleAclAuthorizer with concurrent create/update > -

Re: [VOTE] KIP-349 Priorities for Source Topics

In thinking on it, another solution for this is another consumer external to the stream - but then we run into timing issues and complexity with using a state store as the storage of record. :/ On Sun, Aug 12, 2018 at 9:34 AM Matt Farmer wrote: > The work-queue use case is mostly how I see this b

Re: [VOTE] KIP-349 Priorities for Source Topics

The work-queue use case is mostly how I see this being used, yes. In the most generic sense I can see its use in a situation where the business dictates that we have to guarantee quality of service for some set of low number of messages while there's some high number of messages being processed fr