Re: Build problems in Eclipse dev environment setup

Hi Ismael, Thanks for your response. I agree this is not a Kafka issue, its about gradle and its eclipse plugin. I was able to resolve the compile errors in Eclipse by manually setting the Default output folder for core project to core/build/classes/main. I understand Eclipse is not the popu

Re: [DISCUSS] KIP-104: Granular Sensors for Streams

Thanks for updating the KIP to include the Metrics API that we are now exposing, very helpful! Looking at it, do we really want to expose it to users? The API seems to have grown organically (as an internal API) and doesn't look particularly user-friendly to me. Questions I have: 1. `metricName` a

[VOTE] KIP-108: Create Topic Policy

Hi all, As the discussion seems to have settled down, I would like to initiate the voting process for KIP-108: Create Topic Policy: https://cwiki.apache.org/confluence/display/KAFKA/KIP-108 %3A+Create+Topic+Policy The vote will run for a minimum of 72 hours. Thanks, Ismael

Re: [DISCUSS] KIP-104: Granular Sensors for Streams

Ismael, Based on the streams user demand for registering their sensors and metrics we decided to expose the metrics registry. I'm not a fan of replicating a ton of code and add yet another layer/interface that does the same thing that the existing Metrics class and I think the methods are prett

Re: [DISCUSS] KIP-104: Granular Sensors for Streams

I can see the point that all of a sudden exposing the internal Metrics class might be too big a bite to take in this KIP, since the Metrics class might have to be cleaned up further. I was perhaps naively assuming it's good since it has been reviewed when it was first introduced into Kafka. Furt

Re: [VOTE] KIP-104: Granular Sensors for Streams

+1 On Sat, Jan 7, 2017 at 1:06 PM, Matthias J. Sax wrote: > +1 > > On 1/6/17 4:48 PM, Sriram Subramanian wrote: > > +1 > > > > On Fri, Jan 6, 2017 at 4:41 PM, Eno Thereska > wrote: > > > >> I light of the recent discussion on KIP-104 I've made changes to the KIP > >> to explicitly list all APIs

[jira] [Updated] (KAFKA-4465) Create docker image and scripts for running tests locally

[ https://issues.apache.org/jira/browse/KAFKA-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4465: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved

[GitHub] kafka pull request #2197: KAFKA-4465: Create docker image and scripts for ru...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2197 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-4465) Create docker image and scripts for running tests locally

[ https://issues.apache.org/jira/browse/KAFKA-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15810267#comment-15810267 ] ASF GitHub Bot commented on KAFKA-4465: --- Github user asfgit closed the pull request

[GitHub] kafka pull request #2333: KAFKA-3452 Follow-up: Refactoring StateStore hiera...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/2333 KAFKA-3452 Follow-up: Refactoring StateStore hierarchies This is a refactoring follow-up of https://github.com/apache/kafka/pull/2166. You can merge this pull request into a Git repository by

[jira] [Commented] (KAFKA-3452) Support session windows

[ https://issues.apache.org/jira/browse/KAFKA-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15810319#comment-15810319 ] ASF GitHub Bot commented on KAFKA-3452: --- GitHub user guozhangwang opened a pull requ

Jenkins build is back to normal : kafka-trunk-jdk7 #1810

See

Build failed in Jenkins: kafka-trunk-jdk8 #1156

See Changes: [me] KAFKA-4465: Create docker image and scripts for running tests locally -- [...truncated 18062 lines...] org.apache.kafka.streams.KafkaStreamsTest > testCleanup STARTED org.apa

[jira] [Commented] (KAFKA-4558) throttling_test fails if the producer starts too fast.

[ https://issues.apache.org/jira/browse/KAFKA-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15810593#comment-15810593 ] Ewen Cheslack-Postava commented on KAFKA-4558: -- [~apurva] I couldn't remember

[jira] [Resolved] (KAFKA-4402) Kafka Producer's DefaultPartitioner is actually not round robin as said in the code comments "If no partition or key is present choose a partition in a round-robin fashi

[ https://issues.apache.org/jira/browse/KAFKA-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4402. -- Resolution: Fixed Fix Version/s: 0.10.2.0 Issue resolved by pull request

[GitHub] kafka pull request #2128: KAFKA-4402: make the KafkaProducer true round robi...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2128 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-4402) Kafka Producer's DefaultPartitioner is actually not round robin as said in the code comments "If no partition or key is present choose a partition in a round-robin fash

[ https://issues.apache.org/jira/browse/KAFKA-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15810616#comment-15810616 ] ASF GitHub Bot commented on KAFKA-4402: --- Github user asfgit closed the pull request

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

Hi, Jason, 100. Yes, AppId level security is mainly for protecting the shared transaction log. We could also include AppId in produce request (not in message format) so that we could protect writes at the AppId level. I agree that we need to support prefix matching on AppId for applications like s

[jira] [Created] (KAFKA-4608) RocksDBWindowStore.fetch() is inefficient for large ranges

Elias Levy created KAFKA-4608: - Summary: RocksDBWindowStore.fetch() is inefficient for large ranges Key: KAFKA-4608 URL: https://issues.apache.org/jira/browse/KAFKA-4608 Project: Kafka Issue Type

Build failed in Jenkins: kafka-trunk-jdk8 #1157

See Changes: [me] KAFKA-4402: make the KafkaProducer true round robin per topic -- [...truncated 31151 lines...] kafka.security.auth.SimpleAclAuthorizerTest > testLoadCache PASSED kafka.integra

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

It seems like no one needs any update on this KIP. If then, May I start the vote? Regards, Dongjin On Fri, Jan 6, 2017 at 11:40 AM, Dongjin Lee wrote: > Hi all, > > I've just posted a new KIP "KIP-110: Add Codec for ZStandard Compression" > for > discussion: > > https://cwiki.apache.org/conflue

[jira] [Assigned] (KAFKA-3745) Consider adding join key to ValueJoiner interface

[ https://issues.apache.org/jira/browse/KAFKA-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreepathi Prasanna reassigned KAFKA-3745: - Assignee: Sreepathi Prasanna > Consider adding join key to ValueJoiner interface