[jira] [Commented] (KAFKA-4335) FileStreamSource Connector not working for large files (~ 1GB)

[ https://issues.apache.org/jira/browse/KAFKA-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604522#comment-15604522 ] Rahul Shukla commented on KAFKA-4335: - Yes I got this exception on producer console

[jira] [Resolved] (KAFKA-4337) Create topic in multiple zookeepers with Kafka AdminUtils.CreateTopic JAVA API in Kafka 0.9.0.1 gives Error (Topic gets created in only one of the specified zookeeper)

[ https://issues.apache.org/jira/browse/KAFKA-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4337. Resolution: Not A Bug > Create topic in multiple zookeepers with Kafka AdminUtils.CreateTopic JAVA

[GitHub] kafka pull request #2062: Expose name of processor on KStream

GitHub user thijsc opened a pull request: https://github.com/apache/kafka/pull/2062 Expose name of processor on KStream When connecting a processor on a KStream to downstream processors or sinks you need to know the generated name of the processor. This change exposes that name in

Re: [DISCUSS] KIP-80: Kafka REST Server

Good point Ismael :D On Mon, Oct 24, 2016 at 11:07 PM, Ismael Juma wrote: > If we want to start a vote on this, I suggest starting a [VOTE] thread > instead of mentioning it in the middle of a very long [DISCUSS] thread. :) > > Ismael > > On Mon, Oct 24, 2016 at 9:46 PM, Ben Davison > wrote: >

[DISCUSS] Deprecating the old consumers in trunk

Hi all, In 0.10.1.0, we removed the beta label from the new Java consumer documentation and updated the various tools so that they can use the new consumer without having to pass the `--new-consumer` flag (more specifically the new consumer is used if `bootstrap-server` is set). More details of th

[jira] [Commented] (KAFKA-3317) too many open files between kafka borkers or may between borker and clients

[ https://issues.apache.org/jira/browse/KAFKA-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604883#comment-15604883 ] fengkaibin commented on KAFKA-3317: --- I met this problem too，and my kafka version is 0.8.

[GitHub] kafka pull request #1646: The order of the parameters of zkSessionTimeOutMs ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1646 --- 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-4339) Failing ConsumerGroupCommand System Tests

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

[GitHub] kafka pull request #2061: KAFKA-4339: Update system tests to accommodate the...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2061 --- 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] [Resolved] (KAFKA-4339) Failing ConsumerGroupCommand System Tests

[ https://issues.apache.org/jira/browse/KAFKA-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4339. Resolution: Fixed Issue resolved by pull request 2061 [https://github.com/apache/kafka/pull/2061] >

handleFetchRequest throw exception

Hi all, I use Kafka 0.9.0.0, and we have a cluster with 6 nodes, when I restart a broker，we find there are many logs as below， [2016-10-24 15:29:00,914] ERROR [KafkaApi-2141642] error when handling request Name: FetchRequest; Version: 1; CorrelationId: 4928; ClientId: ReplicaFetcherThre

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

See Changes: [ismael] Parameters zkSessionTimeOutMs and zkConnectionTimeoutMs are reversed in -- [...truncated 3887 lines...] kafka.api.AuthorizerIntegrationTest > testAuthorizationWithTopicNot

[jira] [Updated] (KAFKA-4297) Cannot Stop Kafka with Shell Script

[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mabin Jeong updated KAFKA-4297: --- Fix Version/s: (was: 0.10.0.1) > Cannot Stop Kafka with Shell Script > ---

[jira] [Commented] (KAFKA-4301) Include some SSL/TLS logging to avoid need need for javax debug util every time an issue arises

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

[GitHub] kafka pull request #2027: KAFKA-4301: Add more trace for SSL handshake

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2027 --- 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] [Resolved] (KAFKA-4301) Include some SSL/TLS logging to avoid need need for javax debug util every time an issue arises

[ https://issues.apache.org/jira/browse/KAFKA-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4301. Resolution: Fixed Fix Version/s: 0.10.2.0 Issue resolved by pull request 2027 [https://github

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

See Changes: [ismael] KAFKA-4339; Update system tests to accommodate the new consumer group [ismael] KAFKA-4301; Add more trace for SSL handshake -- [...truncated 1151 lines...] kafka.api.UserC

Build failed in Jenkins: kafka-trunk-jdk7 #1655

See Changes: [ismael] Parameters zkSessionTimeOutMs and zkConnectionTimeoutMs are reversed in -- [...truncated 14353 lines...] org.apache.kafka.streams.state.internals.MergedSortedCacheKeyValueS

Build failed in Jenkins: kafka-trunk-jdk7 #1656

See Changes: [ismael] KAFKA-4339; Update system tests to accommodate the new consumer group [ismael] KAFKA-4301; Add more trace for SSL handshake -- [...truncated 2330 lines...] kafka.api.Autho

[jira] [Commented] (KAFKA-3536) ReplicaFetcherThread should not log errors when leadership changes

[ https://issues.apache.org/jira/browse/KAFKA-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605691#comment-15605691 ] Guozhang Wang commented on KAFKA-3536: -- This issue is observed in 0.9.0 as well, copy

[jira] [Updated] (KAFKA-4341) KIP-87 - Add Compaction Tombstone Flag

[ https://issues.apache.org/jira/browse/KAFKA-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Andre Pearce (IG) updated KAFKA-4341: - Summary: KIP-87 - Add Compaction Tombstone Flag (was: KIP-82 - Add Compac

[jira] [Created] (KAFKA-4341) KIP-82 - Add Compaction Tombstone Flag

Michael Andre Pearce (IG) created KAFKA-4341: Summary: KIP-82 - Add Compaction Tombstone Flag Key: KAFKA-4341 URL: https://issues.apache.org/jira/browse/KAFKA-4341 Project: Kafka

Re: [VOTE] KIP-47 - Add timestamp-based log deletion policy

Bill, That's a good question. I am thinking of the following approach for implementing trim(): (1) client issues metadata request to the broker to determine the leader of topic/partitions and groups topic/partitions by the leader broker; (2) client sends a TrimRequest to each broker with partition

[DISCUSS] KIP-87 - Add Compaction Tombstone Flag

Hi All, I would like to discuss the following KIP proposal: https://cwiki.apache.org/confluence/display/KAFKA/KIP-87+-+Add+Compaction+Tombstone+Flag This is off the back of the discussion on KIP-82 / KIP meeting where it was agreed to separate this issue and feature. See: http://mail-archives.a

[jira] [Updated] (KAFKA-4161) Decouple flush and offset commits

[ https://issues.apache.org/jira/browse/KAFKA-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4161: - Assignee: Shikhar Bhushan (was: Ewen Cheslack-Postava) > Decouple flush and offse

Re: [DISCUSS] KIP-87 - Add Compaction Tombstone Flag

Hi Michael, With the version bumps for Produce and Fetch requests, do you really need to bump MagicByte too? Regards, Magnus 2016-10-25 18:09 GMT+02:00 Michael Pearce : > Hi All, > > I would like to discuss the following KIP proposal: > https://cwiki.apache.org/confluence/display/KAFKA/KIP- >

Re: [DISCUSS] KIP-87 - Add Compaction Tombstone Flag

Hi Magnus, I was wondering if I even needed to change those also, as technically we’re just making use of a non used attribute bit, but im not 100% that it be always false currently. If someone can say 100% it will already be set false with current and historic bit wise masking techniques used

[jira] [Created] (KAFKA-4342) Kafka-connect- support tinyint values

Sagar Rao created KAFKA-4342: Summary: Kafka-connect- support tinyint values Key: KAFKA-4342 URL: https://issues.apache.org/jira/browse/KAFKA-4342 Project: Kafka Issue Type: Bug Repor

Re: [DISCUSS] KIP-87 - Add Compaction Tombstone Flag

It is safe to assume that a previously undefined attributes bit will be unset in protocol requests from existing clients, if not, such a client is already violating the protocol and needs to be fixed. So I dont see a need for a MagicByte bump, both broker and client has the information it needs to

[jira] [Created] (KAFKA-4343) Connect REST API should expose whether each connector is a source or sink

Ewen Cheslack-Postava created KAFKA-4343: Summary: Connect REST API should expose whether each connector is a source or sink Key: KAFKA-4343 URL: https://issues.apache.org/jira/browse/KAFKA-4343

[jira] [Updated] (KAFKA-4343) Connect REST API should expose whether each connector is a source or sink

[ https://issues.apache.org/jira/browse/KAFKA-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4343: - Labels: needs-kip (was: ) > Connect REST API should expose whether each connector

Re: [DISCUSS] KIP-87 - Add Compaction Tombstone Flag

I think you probably require a MagicByte bump if you expect correct behavior of the system as a whole. >From a client perspective you want to make sure that when you deliver a message that the broker supports the feature you're expecting (compaction). So, depending on the behavior of the broker o

Re: [DISCUSS] KIP-87 - Add Compaction Tombstone Flag

If we can be sure as per Magnus mentions then I'd actually prefer not to be bumping the magic bit, as we take the default as false as such no behaviour change. I had included the magic bit and api changes only because of uncertainty how true that by default the flags should be false. The less

[jira] [Created] (KAFKA-4344) Exception when accessing partition, offset and timestamp in processor class

saiprasad mishra created KAFKA-4344: --- Summary: Exception when accessing partition, offset and timestamp in processor class Key: KAFKA-4344 URL: https://issues.apache.org/jira/browse/KAFKA-4344 Proje

[jira] [Commented] (KAFKA-3455) Connect custom processors with the streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606491#comment-15606491 ] Guozhang Wang commented on KAFKA-3455: -- [~jonathan.bender] I'm looking at this JIRA a

[VOTE] Add REST Server to Apache Kafka

Hi All, We are proposing to have a REST Server as part of Apache Kafka to provide producer/consumer/admin APIs. We Strongly believe having REST server functionality with Apache Kafka will help a lot of users. Here is the KIP that Mani Kumar wrote https://cwiki.apache.org/confluence/disp

[jira] [Commented] (KAFKA-4217) KStream.transform equivalent of flatMap

[ https://issues.apache.org/jira/browse/KAFKA-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606502#comment-15606502 ] Guozhang Wang commented on KAFKA-4217: -- For now a suggested workaround would be {{str

[jira] [Created] (KAFKA-4345) Run decktape test for each pull request

Raghav Kumar Gautam created KAFKA-4345: -- Summary: Run decktape test for each pull request Key: KAFKA-4345 URL: https://issues.apache.org/jira/browse/KAFKA-4345 Project: Kafka Issue Type:

[jira] [Assigned] (KAFKA-4345) Run decktape test for each pull request

[ https://issues.apache.org/jira/browse/KAFKA-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghav Kumar Gautam reassigned KAFKA-4345: -- Assignee: Raghav Kumar Gautam > Run decktape test for each pull request > -

Re: [DISCUSS] KIP-68 Add a consumed log retention before log retention

One of the main reasons for retaining messages on the broker after consumption is to support replay. A common reason for replay is to fix and application error. So, it seems that it's a bit hard to delete log segments just based on the committed offsets that the broker knows. An alternative approac

Re: [VOTE] Add REST Server to Apache Kafka

-1 I think the REST server for Kafka that already exists is quite good and getting contributions. Moving this into the core project doesn't solve a problem that I see. -Jay On Tue, Oct 25, 2016 at 2:16 PM, Harsha Chintalapani wrote: > Hi All, >We are proposing to have a REST Server

[jira] [Commented] (KAFKA-1466) Kafka server is hung after throwing "Attempt to swap the new high watermark file with the old one failed"

[ https://issues.apache.org/jira/browse/KAFKA-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606600#comment-15606600 ] Arup Malakar commented on KAFKA-1466: - I think we may have found the cause for this is

[jira] [Resolved] (KAFKA-4342) Kafka-connect- support tinyint values

[ https://issues.apache.org/jira/browse/KAFKA-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shikhar Bhushan resolved KAFKA-4342. Resolution: Not A Problem The Connect schema type {{Schema.Type.INT8}} accurately maps to a

Re: [DISCUSS] KIP-68 Add a consumed log retention before log retention

+1 - I was thinking the exact same thing. On Tue, Oct 25, 2016 at 2:52 PM, Jun Rao wrote: > One of the main reasons for retaining messages on the broker after > consumption is to support replay. A common reason for replay is to fix and > application error. So, it seems that it's a bit hard to de

[jira] [Created] (KAFKA-4346) Add foreachValue method to KStream

Xavier Léauté created KAFKA-4346: Summary: Add foreachValue method to KStream Key: KAFKA-4346 URL: https://issues.apache.org/jira/browse/KAFKA-4346 Project: Kafka Issue Type: Improvement

[GitHub] kafka pull request #2063: KAFKA-4346: Add foreachValue method to KStream

GitHub user xvrl opened a pull request: https://github.com/apache/kafka/pull/2063 KAFKA-4346: Add foreachValue method to KStream enables syntactic sugar using method references You can merge this pull request into a Git repository by running: $ git pull https://github.com/xvrl/

[jira] [Commented] (KAFKA-4346) Add foreachValue method to KStream

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

Re: [VOTE] Add REST Server to Apache Kafka

+1. On Tue, Oct 25, 2016 at 2:58 PM, Jay Kreps wrote: > -1 > > I think the REST server for Kafka that already exists is quite good and > getting contributions. Moving this into the core project doesn't solve a > problem that I see. > > -Jay > > On Tue, Oct 25, 2016 at 2:16 PM, Harsha Chintalapan

Re: [DISCUSS] Deprecating the old consumers in trunk

I am in favor of the deprecation in 0.10.2.0, and generally speaking I'd propose we make up a timeline guidance for removing deprecated clients / protocols. I remember we talked about this and someone proposed three major releases (i.e. a year based on our current timeline release plan), which sou

Re: [VOTE] Add REST Server to Apache Kafka

+1. This is an http access to core Kafka. This is very much needed as part of Apache Kafka under ASF governance model. This would be great for the community instead of duplicated and splintered efforts that may spring up. Get Outlook for iOS

Re: [VOTE] Add REST Server to Apache Kafka

-1 for all the reasons that have been described before. This does not need to be part of the core project. On Tue, Oct 25, 2016 at 3:25 PM, Suresh Srinivas wrote: > +1. > > This is an http access to core Kafka. This is very much needed as part of > Apache Kafka under ASF governance model. This

[jira] [Commented] (KAFKA-4344) Exception when accessing partition, offset and timestamp in processor class

[ https://issues.apache.org/jira/browse/KAFKA-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606680#comment-15606680 ] Guozhang Wang commented on KAFKA-4344: -- [~saimishra] I created a similar topology of

[GitHub] kafka pull request #2064: KAFKA-4345: Run decktape test for each pull reques...

GitHub user raghavgautam opened a pull request: https://github.com/apache/kafka/pull/2064 KAFKA-4345: Run decktape test for each pull request As of now the ducktape tests that we have for kafka are not run for pull request. We can run these test using travis-ci. Here is a sample run

[jira] [Commented] (KAFKA-4345) Run decktape test for each pull request

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

Re: [VOTE] Add REST Server to Apache Kafka

-1 As an end-user, while I like the idea in theory, in practice I don't think it's a good idea just yet. Certainly, it'd be useful, enabling things like https://github.com/Landoop/kafka-topics-ui to work without needing anything outside of Kafka core. But there are already enough things in the e

Re: [DISCUSS] KIP-84: Support SASL/SCRAM mechanisms

Hi, Rajini, Thanks for the proposal. Looks good overall and seems quite useful (e.g. for supporting delegation tokens). A few comments/questions below. 1. For the ZK data format change, should we use the same convention as in KIP-55 to use encoded user name (i.e., /config/users/)? 2. For tooling

Re: [VOTE] Add REST Server to Apache Kafka

I am not able to link the whole thread on REST server discussion thread from dev list properly. But if you go here http://mail-archives.apache.org/mod_mbox/kafka-dev/201610.mbox/thread look for subject "[DISCUSS] KIP-80: Kafka REST Server" Thanks, Harsha On Tue, Oct 25, 2016 at 4:13 PM Ali Akhta

Re: [VOTE] Add REST Server to Apache Kafka

+ 1 On Tue, Oct 25, 2016 at 10:16 PM, Harsha Chintalapani wrote: > Hi All, >We are proposing to have a REST Server as part of Apache Kafka > to provide producer/consumer/admin APIs. We Strongly believe having > REST server functionality with Apache Kafka will help a lot of users. >

Re: [VOTE] Add REST Server to Apache Kafka

+1 Thanks, Jun On Tue, Oct 25, 2016 at 2:16 PM, Harsha Chintalapani wrote: > Hi All, >We are proposing to have a REST Server as part of Apache Kafka > to provide producer/consumer/admin APIs. We Strongly believe having > REST server functionality with Apache Kafka will help a lot

Re: [VOTE] Add REST Server to Apache Kafka

Sorry a typo. -1 instead. Thanks, Jun On Tue, Oct 25, 2016 at 4:24 PM, Jun Rao wrote: > +1 > > Thanks, > > Jun > > On Tue, Oct 25, 2016 at 2:16 PM, Harsha Chintalapani > wrote: > >> Hi All, >>We are proposing to have a REST Server as part of Apache Kafka >> to provide producer/co

Re: [VOTE] Add REST Server to Apache Kafka

-1 I think it's good to avoid adding non-essential items to the Apache Kafka project so that it can continue evolving at a fast pace. Since a REST server can be naturally implemented as an external project, I believe the disadvantages of including it outweigh the advantages. Ismael On Tue, Oct 2

Re: [VOTE] Add REST Server to Apache Kafka

+1 In my personal experience Kafka REST server is one of essential parts on building a reliable real-time pipeline. It's okay to keep the code reasonably separated from the core, but would appreciate to see some official supports for the REST servers from the Kafka community. Regards, Haohui On

KafkaProducer.java topics() call?

Hey all, I sent this to the users list by mistake. This one's better suited... Bit of curiosity that came out of the background to this thread: http://search-hadoop.com/m/Kafka/uyzND1lLYXb136UfJ1?subj= programmatic+way+to+check+for+topic+existence+ I noticed that KafkaConsumer.java has the abili

Re: [VOTE] Add REST Server to Apache Kafka

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 - -1 Kafka offers a protocol clients can implement, and REST server is only one of many clients. If we include REST, we need to include any other client, too, which seems not to be reasonable to me. - -Matthias On 10/25/16 5:29 PM, Haohui Mai wrot

Re: [VOTE] Add REST Server to Apache Kafka

-1 Let me make an observation and then state my reasons. First, I am a little surprised to see this vote thread as I think it is a bit premature. As a community, we've consistently invested in good communication. If there are differing opinions on a DISCUSS thread, we generally gather the communi

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607070#comment-15607070 ] Kamal Chandraprakash commented on KAFKA-4340: - Jiangjie Qin, I would like to

Re: [DISCUSS] KIP-86: Configurable SASL callback handlers

Hi, Rajini, Thanks for the proposal. One quick question. The KIP says "SaslClientCallbackHandler will be modified to obtain Subject using *Subject.getSubject(AccessController.getContext())* to avoid the current per-connection state." Since subject is going to be different for different connection

Re: [DISCUSS] KIP-68 Add a consumed log retention before log retention

The trim() interface would be useful in general. And I agree with Guozhang that conceptually letting the application to decide when to delete the messages is more intuitive and flexible. That said, I am not sure if putting coordination on the application side is the best option. At a high level, t

Re: [VOTE] Add REST Server to Apache Kafka

Neha, As I stated in my earlier email . This is an interest check vote thread and , not a KIP vote thread, to gather input from users mailing list if there is any interest for REST server to be part of Kafka. Also, this has been noted in the discuss thread that we should make a interest vo

Re: [VOTE] Add REST Server to Apache Kafka

Neha, As I stated in my earlier email, this is an interest check vote thread and, not a KIP vote thread, to gather input from users mailing list if there is any interest for REST server to be part of Kafka. Also, this has been noted in the discuss thread that we should make an interest vot

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607162#comment-15607162 ] Jiangjie Qin commented on KAFKA-4340: - [~Kamal C] I have actually already started work

[jira] [Updated] (KAFKA-2200) kafkaProducer.send() should not call callback.onCompletion()

[ https://issues.apache.org/jira/browse/KAFKA-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-2200: Affects Version/s: 0.10.1.0 Fix Version/s: 0.10.2.0 Component/s: clients > kafkaPr

Re: [DISCUSS] KIP-80: Kafka REST Server

Sorry that I've stayed quiet on this for a bit. My reason for doing so is well summed up by Jason's notes. First, I do want to say thanks for referencing the Confluent REST Proxy in the proposal! It makes me proud that it's being used as an important reference point. Second, Nacho, I want to say

Re: [VOTE] Add REST Server to Apache Kafka

Perhaps in the future we can use a [POLL] or similar? This confused a lot of folks because they thought a VOTE was being called on KIP-80 when it wasn't. (Even if we say shame on them for not reading the body in full, the title caught me as well.) -Ewen On Tue, Oct 25, 2016 at 7:11 PM, Harsha Chi

Re: [DISCUSS] KIP-82 - Add Record Headers

Hi All, In case you hadn't noticed re the compaction issue for non-null values i have created a separate KIP-87, if you could all contribute to its discussion would be much appreciated. https://cwiki.apache.org/confluence/display/KAFKA/KIP-87+-+Add+Compaction+Tombstone+Flag Secondly, focussing

Re: [VOTE] Add REST Server to Apache Kafka

Harsha -- Thanks for clarifying but I had noticed that and still gave those suggestions. Calling a VOTE thread on a discussion when there are varied viewpoints is never something this community has resorted to. The optics of it force binary decision making when in reality there are several tradeof

[GitHub] kafka pull request #2065: KAFKA-4302: Simplify KTableSource

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2065 KAFKA-4302: Simplify KTableSource KTableSource is always materialized since IQ: - removed flag KTableSource#materialized - removed MaterializedKTableSourceProcessor You can merge this pull

[jira] [Commented] (KAFKA-4302) Simplify KTableSource

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

[jira] [Updated] (KAFKA-4302) Simplify KTableSource

[ https://issues.apache.org/jira/browse/KAFKA-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4302: --- Status: Patch Available (was: In Progress) > Simplify KTableSource > - >

Re: [DISCUSS] KIP-80: Kafka REST Server

I find it a bit hard to just discuss "whether or not we should add a REST proxy into Apache Kafka repo" without discussing about "what should be included in the Apache Kafka repo", which, as people mentioned, was a grey-area and deserves ongoing discussions. So I would like to first throw my though

Re: [DISCUSS] KIP-68 Add a consumed log retention before log retention

Hello Becket, I am not 100 percent sure I get your points, reading the first half of the paragraph I thought we were on the same page that "the committed offsets and the offsets the applications ( most likely the consumers) would like to tell the brokers to trim to, could be totally different", bu