[VOTE] KIP-123: Allow per stream/table timestamp extractor

Dear community, I'd like to start the vote for KIP-123: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=68714788 Cheers, Jeyhun -- -Cheers Jeyhun

Re: [VOTE] KIP-123: Allow per stream/table timestamp extractor

Thanks for the KIP Jeyhun! +1 On Tue, 28 Feb 2017 at 08:59 Jeyhun Karimov wrote: > Dear community, > > I'd like to start the vote for KIP-123: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=68714788 > > > Cheers, > Jeyhun > -- > -Cheers > > Jeyhun >

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

+1 On Tue, 28 Feb 2017 at 04:32 Vahid S Hashemian wrote: > +1 on 0.11.0.0. > > Can we also include KIP-54 to the list? > The PR for this KIP is ready for review. > > Thanks. > --Vahid > > > > > > From: Ismael Juma > To: dev@kafka.apache.org > Date: 02/27/2017 07:47 PM > Subject:

Re: [DISCUSS] KIP-123: Allow per stream/table timestamp extractor

Hi Jeyhun, Thanks for the KIP, sorry I'm coming a bit late to the discussion. One thing I'd like to understand is whether we can avoid situations where the user is mixing different times (event time vs. wallclock time) in their processing inadvertently. Before this KIP, all the relevant topics

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Makes sense, thank you Dong. Eno > On 28 Feb 2017, at 01:51, Dong Lin wrote: > > Hi Jun, > > In addition to the Eno's reference of why rebuild time with RAID-5 is more > expensive, another concern is that RAID-5 will fail if more than one disk > fails. JBOD is still works with 1+ disk failure a

Re: [DISCUSS] KIP-123: Allow per stream/table timestamp extractor

Hi Eno, Thanks for feedback. I think you mean [1]. In this KIP we do not consider the situations you mentioned. So, either we can extend the KIP and solve mentioned issues or submit 2 PRs incrementally. [1] https://issues.apache.org/jira/browse/KAFKA-4785 Cheers, Jeyhun On Tue, Feb 28, 2017 a

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

Hi Vahid, Sure, I've added KIP-54. I thought I had done it, sorry for the oversight. Ismael On Tue, Feb 28, 2017 at 4:31 AM, Vahid S Hashemian < vahidhashem...@us.ibm.com> wrote: > +1 on 0.11.0.0. > > Can we also include KIP-54 to the list? > The PR for this KIP is ready for review. > > Thanks.

[jira] [Created] (KAFKA-4812) We are facing the same issue as SAMZA-590

Manjeer Srujan. Y created KAFKA-4812: Summary: We are facing the same issue as SAMZA-590 Key: KAFKA-4812 URL: https://issues.apache.org/jira/browse/KAFKA-4812 Project: Kafka Issue Type: B

Re: [DISCUSS] KIP-123: Allow per stream/table timestamp extractor

Hi Jeyhun, I mean something slightly different. In your motivation you say "joining multiple streams/tables that require different timestamp extraction methods". I wan to understand the scope of this. Is it allowed to have a stream that uses wallclock time join a stream that uses event time? (I

[jira] [Updated] (KAFKA-4812) We are facing the same issue as SAMZA-590 for kafka

[ https://issues.apache.org/jira/browse/KAFKA-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjeer Srujan. Y updated KAFKA-4812: - Summary: We are facing the same issue as SAMZA-590 for kafka (was: We are facing the same

[VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

Hi everyone, Since the few who responded in the discuss thread were in favour and there were no objections, I would like to initiate the voting process for KIP-119: Drop Support for Scala 2.10 in Kafka 0.11: https://cwiki.apache.org/confluence/display/KAFKA/KIP-119%3A+Drop+Support+for+Scala+2.10+

[jira] [Commented] (KAFKA-4812) We are facing the same issue as SAMZA-590 for kafka

[ https://issues.apache.org/jira/browse/KAFKA-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887779#comment-15887779 ] Manjeer Srujan. Y commented on KAFKA-4812: -- [~criccomini]: Seems like you have fi

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

This is definitely a major release, looks already quite exciting... I don't want to start a bike-shading argument, but a few people have told me in the past year that once exactly-once delivery lands, Kafka would likely bump to 1.0. I do like it, but don't feel strongly either way. Ofir Manor Co-

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

Hi Ofir, Thanks for the feedback. This will be the first release with exactly-once. I think we should give ourselves at least one stabilisation/polish/feedback cycle before we go for 1.0. :) Ismael On Tue, Feb 28, 2017 at 10:55 AM, Ofir Manor wrote: > This is definitely a major release, looks

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

Hi Jeff, I share your desire to streamline the experience and remove options that don't make sense to new users. I should, however, point out that we won't be able to remove the old consumers in 0.11.0.0 as they haven't been deprecated yet. Hopefully that will happen in 0.12.0.0/1.0.0. Ismael On

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

+1. Best, Dongjin -- Dongjin Lee Software developer in Line+. So interested in massive-scale machine learning. facebook: www.facebook.com/dongjin.lee.kr (http://www.facebook.com/dongjin.lee.kr) linkedin: kr.linkedin.com/in/dongjinleekr (http://

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

+1 2017-02-28 12:17 GMT+01:00 Dongjin Lee : > > > +1. > > > > Best, > > Dongjin > > > -- > > > > > Dongjin Lee > > > > > > Software developer in Line+. > > So interested in massive-scale machine learning. > > > > facebook: www.facebook.com/dongjin.lee.kr (http://www.facebook.com/ > dongjin.le

[GitHub] kafka pull request #2607: MINOR: Fix typo in javadoc of `flatMapValues`

GitHub user miguno opened a pull request: https://github.com/apache/kafka/pull/2607 MINOR: Fix typo in javadoc of `flatMapValues` You can merge this pull request into a Git repository by running: $ git pull https://github.com/miguno/kafka trunk-flatMapValues-docstring Alterna

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

Hi Becket, Comments inline. On Sat, Feb 25, 2017 at 10:33 PM, Becket Qin wrote: > > 1. Regarding the mutability. > > I think it would be a big convenience to have headers mutable during > certain stage in the message life cycle for the use cases you mentioned. I > agree there is a material benef

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

Ismael, Thank you for volunteering to manage the next release. +1 for 0.11.0.0 Regards, Rajini On Tue, Feb 28, 2017 at 11:02 AM, Ismael Juma wrote: > Hi Ofir, > > Thanks for the feedback. This will be the first release with exactly-once. > I think we should give ourselves at least one stabil

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

+1 (non-binding) On Tue, 28 Feb 2017 at 11:42, Molnár Bálint wrote: > +1 > > 2017-02-28 12:17 GMT+01:00 Dongjin Lee : > > > > > > > +1. > > > > > > > > Best, > > > > Dongjin > > > > > > -- > > > > > > > > > > Dongjin Lee > > > > > > > > > > > > Software developer in Line+. > > > > So interested

[jira] [Commented] (KAFKA-4779) Failure in kafka/tests/kafkatest/tests/core/security_rolling_upgrade_test.py

[ https://issues.apache.org/jira/browse/KAFKA-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887913#comment-15887913 ] Rajini Sivaram commented on KAFKA-4779: --- The new failure looks like a very different

[jira] [Commented] (KAFKA-4779) Failure in kafka/tests/kafkatest/tests/core/security_rolling_upgrade_test.py

[ https://issues.apache.org/jira/browse/KAFKA-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887934#comment-15887934 ] Ismael Juma commented on KAFKA-4779: Thanks [~rsivaram]! Hopefully this is the last is

Re: [VOTE] KIP-123: Allow per stream/table timestamp extractor

Thanks, Jeyhun! I observed that there is still on ongoing conversation in the DISCUSS thread, so perhaps this voting thread was started a bit too early? -Michael On Tue, Feb 28, 2017 at 10:35 AM, Damian Guy wrote: > Thanks for the KIP Jeyhun! > > +1 > > On Tue, 28 Feb 2017 at 08:59 Jeyhun K

[jira] [Commented] (KAFKA-3990) Kafka New Producer may raise an OutOfMemoryError

[ https://issues.apache.org/jira/browse/KAFKA-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887957#comment-15887957 ] Adrian McCague commented on KAFKA-3990: --- I have narrowed down my particular issues t

Re: [VOTE] KIP-123: Allow per stream/table timestamp extractor

That's ok, that was my fault for looking at this thread late. We can leave the vote thread as is and simultaneously answer any remaining questions on the discuss thread. Thanks Eno > On 28 Feb 2017, at 12:55, Michael Noll wrote: > > Thanks, Jeyhun! > > I observed that there is still on ongoin

[GitHub] kafka pull request #2608: KAFKA-4779: Request metadata in consumer if partit...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/2608 KAFKA-4779: Request metadata in consumer if partitions unavailable If leader node of one more more partitions in a consumer subscription are temporarily unavailable, request metadata refresh s

[jira] [Commented] (KAFKA-4779) Failure in kafka/tests/kafkatest/tests/core/security_rolling_upgrade_test.py

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

[jira] [Created] (KAFKA-4813) 2h6R1

Vamsi Jakkula created KAFKA-4813: Summary: 2h6R1 Key: KAFKA-4813 URL: https://issues.apache.org/jira/browse/KAFKA-4813 Project: Kafka Issue Type: Bug Reporter: Vamsi Jakkula Cre

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

Thanks Ismael, makes perfect sense :) Ofir Manor Co-Founder & CTO | Equalum Mobile: +972-54-7801286 | Email: ofir.ma...@equalum.io On Tue, Feb 28, 2017 at 1:02 PM, Ismael Juma wrote: > Hi Ofir, > > Thanks for the feedback. This will be the first release with exactly-once. > I think we should

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

Thanks Ismael, +1 for 0.11.0.0 2017-02-28 15:20 GMT+01:00 Ofir Manor : > Thanks Ismael, makes perfect sense :) > > Ofir Manor > > Co-Founder & CTO | Equalum > > Mobile: +972-54-7801286 | Email: ofir.ma...@equalum.io > > On Tue, Feb 28, 2017 at 1:02 PM, Ismael Juma wrote: > > > Hi Ofir, > > > > T

[jira] [Commented] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888126#comment-15888126 ] Federico Giraud commented on KAFKA-4669: We had the same issue with a Kafka 0.8.2.

[GitHub] kafka pull request #2609: KAFKA-4677: [Follow Up] add optimization to Sticky...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2609 KAFKA-4677: [Follow Up] add optimization to StickyTaskAssignor for rolling rebounce Detect when a rebalance has happened due to one or more existing nodes bouncing. Keep assignment of previous active

[jira] [Commented] (KAFKA-4677) Avoid unnecessary task movement across threads during rebalance

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

Re: [DISCUSS] KIP-123: Allow per stream/table timestamp extractor

Hi Eno, Thanks for clarification. I think it is by definition allowed. So if we want to join a stream that uses wallclock time with a stream that uses an event time, then we can assign the first one a timestamp extractor that returns system clock, and for the second stream we can assign timestamp

Like to contribute

Hi I have been using for a while now and would like to be a contributor. I am a core java developer. May I know which part of kafka is written in java? as it is also written in Scala.. Would you please help me pick up some jira and add me to contributor list? thanks Sunitha

[jira] [Commented] (KAFKA-4811) ReplicaFetchThread may fail to create due to existing metric

[ https://issues.apache.org/jira/browse/KAFKA-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888339#comment-15888339 ] Jun Rao commented on KAFKA-4811: [~huxi_2b], yes, we should check both host and port and r

[jira] [Created] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

Stevo Slavic created KAFKA-4814: --- Summary: ZookeeperLeaderElector not respecting zookeeper.set.acl Key: KAFKA-4814 URL: https://issues.apache.org/jira/browse/KAFKA-4814 Project: Kafka Issue Typ

[jira] [Updated] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

[ https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4814: --- Fix Version/s: 0.10.2.1 0.10.3.0 > ZookeeperLeaderElector not respecting zookeeper.

[jira] [Updated] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

[ https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4814: --- Labels: newbie (was: ) > ZookeeperLeaderElector not respecting zookeeper.set.acl > --

[jira] [Updated] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

[ https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4814: --- Priority: Major (was: Minor) > ZookeeperLeaderElector not respecting zookeeper.set.acl >

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

＋1 On Tue, Feb 28, 2017 at 4:28 AM, Tom Crayford wrote: > +1 (non-binding) > > On Tue, 28 Feb 2017 at 11:42, Molnár Bálint > wrote: > > > +1 > > > > 2017-02-28 12:17 GMT+01:00 Dongjin Lee : > > > > > > > > > > > +1. > > > > > > > > > > > > Best, > > > > > > Dongjin > > > > > > > > > -- > > > >

Re: [DISCUSS] KIP-123: Allow per stream/table timestamp extractor

Eno, I think this problem is out-of-scope and also present in the current setting. We cannot avoid that a custom timestamp extractor uses and if-else branch and returns different timestamps for different topic. That is possible even right now. Furthermore, the TimestampExtractor interface states:

Re: [VOTE] KIP-123: Allow per stream/table timestamp extractor

+1 Thanks a lot for the KIP! -Matthias On 2/28/17 1:35 AM, Damian Guy wrote: > Thanks for the KIP Jeyhun! > > +1 > > On Tue, 28 Feb 2017 at 08:59 Jeyhun Karimov wrote: > >> Dear community, >> >> I'd like to start the vote for KIP-123: >> https://cwiki.apache.org/confluence/pages/viewpage.ac

Re: Like to contribute

Sunitha, Kafka Connect and Kafka Stream are both written in Java. If you want to get started, look for Jira with label "beginner" or similar. Also have a look here: https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Code+Changes Let us know if you have further question. Welcome to t

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Hi, Dong, RAID6 is an improvement over RAID5 and can tolerate 2 disks failure. Eno's point is that the rebuild of RAID5/RAID6 requires reading more data compared with RAID10, which increases the probability of error during rebuild. This makes sense. In any case, do you think you could ask the SREs

Re: [VOTE] KIP-107: Add purgeDataBefore() API in AdminClient

Hi, Dong, Yes, this change makes sense to me. Thanks, Jun On Mon, Feb 27, 2017 at 8:26 PM, Dong Lin wrote: > Hi Jun and everyone, > > I would like to change the KIP in the following way. Currently, if any > replica if offline, the purge result for a partition will > be NotEnoughReplicasExcept

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

Hi, Ismael, Good point on compatibility. Hi, Mayuresh, Given that, it seems that it's better to just add the raw principal as a new field in Session for now and deprecate the KafkaPrincipal field in the future if needed? Thanks, Jun On Mon, Feb 27, 2017 at 5:05 PM, Ismael Juma wrote: > Brea

Re: [DISCUSS] KIP-124: Request rate quotas

I noticed that the throttle_time_ms added to all the message responses is in milliseconds. Does it make sense to express this in microseconds in case we start doing more fine-grained CPU throttling later on? An int32 should still be more than enough if using microseconds. best, Colin On Fri, F

[GitHub] kafka pull request #2610: MINOR: Make asJsonSchema() and asConnectSchema() m...

GitHub user C0urante opened a pull request: https://github.com/apache/kafka/pull/2610 MINOR: Make asJsonSchema() and asConnectSchema() methods public Want to use these methods in an external project. You can merge this pull request into a Git repository by running: $ git pull h

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

+1 (non-binding). Thanks, Ismael. cheers, Colin On Mon, Feb 27, 2017, at 19:47, Ismael Juma wrote: > Hi all, > > With 0.10.2.0 out of the way, I would like to volunteer to be the release > manager for our next time-based release. See https://cwiki.apache.org/c > onfluence/display/KAFKA/Time+Ba

Re: [VOTE] KIP-81: Bound Fetch memory usage in the consumer

Yes I agree, having a generic flag is more future proof. I'll update the KIP in the coming days. Thanks On Tue, Feb 28, 2017 at 5:08 AM, Jason Gustafson wrote: > Hey Mickael, > > The suggestion to add something to Node makes sense. I could imagine for > example adding a flag to indicate that the

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

Hi Jun/Ismael, Thanks for the comments. I agree. What I was thinking was, we get the KIP passed now and wait till major kafka version release. We can then make this change, but for now we can wait. Does that work? If there are concerns, we can make the addition of extra field of type Principal t

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

+1 Sounds good to me. Thanks, Ismael. -Bill On Tue, Feb 28, 2017 at 1:01 PM, Colin McCabe wrote: > +1 (non-binding). > > Thanks, Ismael. > > cheers, > Colin > > > On Mon, Feb 27, 2017, at 19:47, Ismael Juma wrote: > > Hi all, > > > > With 0.10.2.0 out of the way, I would like to volunteer to b

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

We have tested RAID 5/6 in the past (and recently) and found it to be lacking. So, as noted, rebuild takes more time than RAID 10 because all the disks need to be accessed to recalculate parity. In addition, there’s a significant performance loss just in normal operations. It’s been a while since I

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Hey Jun, Certainly, I have added Todd to reply to the thread. And I have updated the item to in the wiki. 50. The full statement is "Broker assumes a log directory to be good after it starts, and mark log directory as bad once there is IOException when broker attempts to access (i.e. read or writ

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Thanks Todd for the explanation. Eno > On 28 Feb 2017, at 18:15, Todd Palino wrote: > > We have tested RAID 5/6 in the past (and recently) and found it to be > lacking. So, as noted, rebuild takes more time than RAID 10 because all the > disks need to be accessed to recalculate parity. In additi

Re: KIP-122: Add a tool to Reset Consumer Group Offsets

Thanks Jorge for addressing my suggestions. Looks good to me. --Vahid From: Jorge Esteban Quilcate Otoya To: dev@kafka.apache.org Date: 02/27/2017 01:57 AM Subject:Re: KIP-122: Add a tool to Reset Consumer Group Offsets @Vahid: make sense to add "new lag" info IMO, I will up

Re: [VOTE] KIP-107: Add purgeDataBefore() API in AdminClient

Thanks Jun. I have updated the KIP to reflect this change. On Tue, Feb 28, 2017 at 9:44 AM, Jun Rao wrote: > Hi, Dong, > > Yes, this change makes sense to me. > > Thanks, > > Jun > > On Mon, Feb 27, 2017 at 8:26 PM, Dong Lin wrote: > > > Hi Jun and everyone, > > > > I would like to change the K

[GitHub] kafka pull request #2611: MINOR: improve MinTimestampTrackerTest and fix NPE...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2611 MINOR: improve MinTimestampTrackerTest and fix NPE when null element removed You can merge this pull request into a Git repository by running: $ git pull https://github.com/dguy/kafka testing Al

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

If we deprecate KafkaPrincipal, then the Authorizer interface will also need to change - i.e., deprecate the getAcls(KafkaPrincipal) method. On Tue, Feb 28, 2017 at 10:11 AM, Mayuresh Gharat < gharatmayures...@gmail.com> wrote: > Hi Jun/Ismael, > > Thanks for the comments. > > I agree. > What I w

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

+1 (non-binding) for 0.11.0 I do agree with Ismael's point that exactly-once should go through one release of stabilization before bumping the version to 1.0. Thanks, Apurva On Mon, Feb 27, 2017 at 7:47 PM, Ismael Juma wrote: > Hi all, > > With 0.10.2.0 out of the way, I would like to voluntee

[GitHub] kafka pull request #2610: MINOR: Make asJsonSchema() and asConnectSchema() m...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2610 --- 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

[GitHub] kafka pull request #2484: KAFKA-3959: Follow-up; move upgrade notes to 0.10....

Github user ewencp closed the pull request at: https://github.com/apache/kafka/pull/2484 --- 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-3959) __consumer_offsets wrong number of replicas at startup

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

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

See Changes: [me] MINOR: Make asJsonSchema() and asConnectSchema() methods public -- [...truncated 7.43 KB...]

[jira] [Commented] (KAFKA-4809) docker/run_tests.sh should set up /opt/kafka-dev to be the source directory

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

[GitHub] kafka pull request #2602: KAFKA-4809: docker/run_tests.sh should set up /opt...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2602 --- 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-4809) docker/run_tests.sh should set up /opt/kafka-dev to be the source directory

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

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

I will settle for any API really, but just wanted to point out that as it stands right now the API targets the most "advanced" (hence obscure and rare) use cases, at the expense of the simple and common ones. i'd suggest (as the minimal set): Header header(String key) - returns JUST ONE (the very

[jira] [Created] (KAFKA-4815) Idempotent/transactional Producer Checklist (KIP-98)

Jason Gustafson created KAFKA-4815: -- Summary: Idempotent/transactional Producer Checklist (KIP-98) Key: KAFKA-4815 URL: https://issues.apache.org/jira/browse/KAFKA-4815 Project: Kafka Issue

Re: Improve License Header Check

Just a reminder. This PR got merged today. -Matthias On 1/20/17 9:02 AM, Matthias J. Sax wrote: > Hi, > > I opened an PR to improve the check for file license header (the check > is currently quite weak and it's possible to have files with an invalid > header). > > https://github.com/apache/ka

[jira] [Created] (KAFKA-4816) Message format changes for idempotent/transactional producer

Jason Gustafson created KAFKA-4816: -- Summary: Message format changes for idempotent/transactional producer Key: KAFKA-4816 URL: https://issues.apache.org/jira/browse/KAFKA-4816 Project: Kafka

[jira] [Created] (KAFKA-4817) Basic idempotent producer implementation

Jason Gustafson created KAFKA-4817: -- Summary: Basic idempotent producer implementation Key: KAFKA-4817 URL: https://issues.apache.org/jira/browse/KAFKA-4817 Project: Kafka Issue Type: Sub-ta

[jira] [Commented] (KAFKA-4738) Remove generic type of class ClientState

[ https://issues.apache.org/jira/browse/KAFKA-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1561#comment-1561 ] Sharad commented on KAFKA-4738: --- Yes, its done. PR submitted: https://github.com/apache/kaf

[GitHub] kafka pull request #2487: Kafka-4722 : Add application.id to StreamThread na...

Github user sharad-develop closed the pull request at: https://github.com/apache/kafka/pull/2487 --- 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

[jira] [Created] (KAFKA-4818) Implement transactional producer

Jason Gustafson created KAFKA-4818: -- Summary: Implement transactional producer Key: KAFKA-4818 URL: https://issues.apache.org/jira/browse/KAFKA-4818 Project: Kafka Issue Type: Sub-task

[jira] [Updated] (KAFKA-4817) Implement idempotent producer

[ https://issues.apache.org/jira/browse/KAFKA-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4817: --- Summary: Implement idempotent producer (was: Basic idempotent producer implementation) > Imp

[jira] [Assigned] (KAFKA-4815) Idempotent/transactional Producer Checklist (KIP-98)

[ https://issues.apache.org/jira/browse/KAFKA-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-4815: -- Assignee: Matthias J. Sax (was: Jason Gustafson) > Idempotent/transactional Producer C

[jira] [Assigned] (KAFKA-4815) Idempotent/transactional Producer Checklist (KIP-98)

[ https://issues.apache.org/jira/browse/KAFKA-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-4815: -- Assignee: (was: Matthias J. Sax) > Idempotent/transactional Producer Checklist (KIP

[jira] [Assigned] (KAFKA-4815) Idempotent/transactional Producer Checklist (KIP-98)

[ https://issues.apache.org/jira/browse/KAFKA-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-4815: -- Assignee: Jason Gustafson > Idempotent/transactional Producer Checklist (KIP-98) >

[jira] [Updated] (KAFKA-4815) Idempotent/transactional Producer Checklist (KIP-98)

[ https://issues.apache.org/jira/browse/KAFKA-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4815: --- Labels: kip (was: ) > Idempotent/transactional Producer Checklist (KIP-98) >

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

See Changes: [me] KAFKA-4809: docker/run_tests.sh should set up /opt/kafka-dev to be the [me] MINOR: improve license header check by providing head file instead of -- Sta

[GitHub] kafka pull request #2487: Kafka-4722 : Add application.id to StreamThread na...

GitHub user sharad-develop reopened a pull request: https://github.com/apache/kafka/pull/2487 Kafka-4722 : Add application.id to StreamThread name Kafka-4722 : Add application.id to StreamThread name You can merge this pull request into a Git repository by running: $ git pull h

[jira] [Created] (KAFKA-4819) Expose states of active tasks to public API

Florian Hussonnois created KAFKA-4819: - Summary: Expose states of active tasks to public API Key: KAFKA-4819 URL: https://issues.apache.org/jira/browse/KAFKA-4819 Project: Kafka Issue Typ

[GitHub] kafka pull request #2303: MINOR: improve license header check by providing h...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2303 --- 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

[GitHub] kafka pull request #2607: MINOR: Fix typo in javadoc of `flatMapValues`

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2607 --- 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

[GitHub] kafka pull request #2590: KAFKA-4789: Added support to ProcessorTopologyTest...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2590 --- 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-4789) ProcessorTopologyTestDriver does not forward extracted timestamps to internal topics

[ https://issues.apache.org/jira/browse/KAFKA-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4789. -- Resolution: Fixed Fix Version/s: 0.10.3.0 Issue resolved by pull request 2590 [https://gi

[jira] [Commented] (KAFKA-4789) ProcessorTopologyTestDriver does not forward extracted timestamps to internal topics

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

[jira] [Assigned] (KAFKA-4789) ProcessorTopologyTestDriver does not forward extracted timestamps to internal topics

[ https://issues.apache.org/jira/browse/KAFKA-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-4789: Assignee: Hamidreza Afzali > ProcessorTopologyTestDriver does not forward extracted timesta

[jira] [Commented] (KAFKA-4789) ProcessorTopologyTestDriver does not forward extracted timestamps to internal topics

[ https://issues.apache.org/jira/browse/KAFKA-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888903#comment-15888903 ] Guozhang Wang commented on KAFKA-4789: -- Thanks [~hrafzali] for the patch! I have adde

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Hi, Dong, 52. What you suggested would work. However, I am thinking that it's probably simpler to just set isNewReplica at the replica level. That way, the LeaderAndIsrRequest can be created a bit simpler. When reading a LeaderAndIsrRequest in the controller log, it's easier to see which replicas

[GitHub] kafka pull request #2612: KAFKA-4819: Expose states for active tasks to publ...

GitHub user fhussonnois opened a pull request: https://github.com/apache/kafka/pull/2612 KAFKA-4819: Expose states for active tasks to public API Simple implementation of the feature : [KAFKA-4819](https://issues.apache.org/jira/browse/KAFKA-4819) KAFKA-4819 This PR ad

[jira] [Commented] (KAFKA-4819) Expose states of active tasks to public API

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

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

Hi, Joel, Good point on the getAcls() method. KafkaPrincipal is also tied to ACL, which is used in pretty much every method in Authorizer. Now, I am not sure if it's easy to deprecate KafkaPrincipal. Hi, Mayuresh, Given the above, it seems that the easiest thing is to add a new Principal field i

[DISCUSS] KIP-129: Kafka Streams Exactly-Once Semantics

Hi all, I have just created KIP-129 to leverage KIP-98 in Kafka Streams and provide exactly-once processing semantics: https://cwiki.apache.org/confluence/display/KAFKA/KIP-129%3A+Streams+Exactly-Once+Semantics This KIP enables Streams users to optionally turn on exactly-once processing semantic

[jira] [Commented] (KAFKA-4789) ProcessorTopologyTestDriver does not forward extracted timestamps to internal topics

[ https://issues.apache.org/jira/browse/KAFKA-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888941#comment-15888941 ] Hamidreza Afzali commented on KAFKA-4789: - Thanks! > ProcessorTopologyTestDriver

[jira] [Commented] (KAFKA-4738) Remove generic type of class ClientState

[ https://issues.apache.org/jira/browse/KAFKA-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888950#comment-15888950 ] Matthias J. Sax commented on KAFKA-4738: [~sharad.develop] Your PR shows 81 commit

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Hi Jun, Yeah there is tradeoff between controller's implementation complexity vs. wire-protocol complexity. I personally think it is more important to keep wire-protocol concise and only add information in wire-protocol if necessary. It seems fine to add a little bit complexity to controller's imp

  1   2   >