[jira] [Work started] (KAFKA-4831) Extract WindowedSerde to public APIs

[ https://issues.apache.org/jira/browse/KAFKA-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4831 started by Vitaly Pushkar. - > Extract WindowedSerde to public APIs > >

[jira] [Assigned] (KAFKA-4831) Extract WindowedSerde to public APIs

[ https://issues.apache.org/jira/browse/KAFKA-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Pushkar reassigned KAFKA-4831: - Assignee: Vitaly Pushkar > Extract WindowedSerde to public APIs > ---

[GitHub] kafka pull request #2809: CPKAFKA-465 : Exactly once transactional producer ...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/2809 CPKAFKA-465 : Exactly once transactional producer -- initial implementation The basic flow works: find coordinator, get pid, add partitions to transaction, commit/abort. Still to add: 1

[GitHub] kafka pull request #2809: CPKAFKA-465 : Exactly once transactional producer ...

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

[jira] [Assigned] (KAFKA-5011) Replica fetchers may need to down-convert messages during a selective message format upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-5011: --- Assignee: Jiangjie Qin > Replica fetchers may need to down-convert messages during a selectiv

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

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

[GitHub] kafka pull request #2804: MINOR: don't throw CommitFailedException during su...

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

[jira] [Comment Edited] (KAFKA-4837) Config validation in Connector plugins need to compare against both canonical and simple class names

[ https://issues.apache.org/jira/browse/KAFKA-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956298#comment-15956298 ] Felix edited comment on KAFKA-4837 at 4/5/17 4:49 AM: -- thanks for fix

[jira] [Commented] (KAFKA-4837) Config validation in Connector plugins need to compare against both canonical and simple class names

[ https://issues.apache.org/jira/browse/KAFKA-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956298#comment-15956298 ] Felix commented on KAFKA-4837: -- thanks for fixing this! It was already driving me nuts! > Co

Re: [DISCUSS] KIP-138: Change punctuate semantics

Hey guys, One thing I've always found super important for this kind of design work is to do a really good job of cataloging the landscape of use cases and how prevalent each one is. By that I mean not just listing lots of uses, but also grouping them into categories that functionally need the same

Re: [VOTE] KIP-120: Cleanup Kafka Streams builder API

+1 (binding) -Ewen On Thu, Mar 30, 2017 at 4:03 PM, Guozhang Wang wrote: > +1. > > > On Thu, Mar 30, 2017 at 1:18 AM, Damian Guy wrote: > > > Thanks Matthias. > > > > +1 > > > > On Thu, 23 Mar 2017 at 22:40 Matthias J. Sax > > wrote: > > > > > Hi, > > > > > > I would like to start the VOTE on

Re: [DISCUSS] KIP-138: Change punctuate semantics

Hi All, Thanks for the KIP. We were also in need of a mechanism to trigger punctuate in the absence of events. As I described in [ https://issues.apache.org/jira/browse/KAFKA-3514?focusedCommentId=15926036&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15926036 ],

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

See Changes: [me] KAFKA-4916: test streams with brokers failing -- [...truncated 341.75 KB...] kafka.server.DynamicConfigTest > shouldFailLeaderConfigsWithInvalidValues

[jira] [Commented] (KAFKA-4971) Why is there no difference between kafka benchmark tests on SSD and HDD?

[ https://issues.apache.org/jira/browse/KAFKA-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956205#comment-15956205 ] Dasol Kim commented on KAFKA-4971: -- It might be a silly question, If kafka uses the page

[jira] [Updated] (KAFKA-4916) Add streams tests with brokers failing

[ https://issues.apache.org/jira/browse/KAFKA-4916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4916: - Reviewer: Ewen Cheslack-Postava Status: Patch Available (was: Reopened) > A

[jira] [Reopened] (KAFKA-4916) Add streams tests with brokers failing

[ https://issues.apache.org/jira/browse/KAFKA-4916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reopened KAFKA-4916: -- Reopening since we've only got the trunk version committed and we want this as bloc

[jira] [Commented] (KAFKA-4916) Add streams tests with brokers failing

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

[GitHub] kafka pull request #2719: KAFKA-4916: test streams with brokers failing

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2719 --- 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-4916) Add streams tests with brokers failing

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

Build failed in Jenkins: kafka-0.10.2-jdk7 #120

See Changes: [me] MINOR: don't throw CommitFailedException during suspendTasksAndState [me] MINOR: improve MinTimestampTrackerTest and fix NPE when null element -- [...tr

Jenkins build is back to normal : kafka-trunk-jdk8 #1401

See

[jira] [Commented] (KAFKA-4730) Streams does not have an in-memory windowed store

[ https://issues.apache.org/jira/browse/KAFKA-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956097#comment-15956097 ] Nikki Thean commented on KAFKA-4730: Hi [~enothereska], I'm interested in this ticket.

Build failed in Jenkins: kafka-0.10.2-jdk7 #119

See Changes: [me] KAFKA-4837: Fix class name comparison in connector-plugins REST endpoint -- [...truncated 843.10 KB...] org.apache.kafka.connect.json.JsonConverterTest

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

See

[GitHub] kafka pull request #2743: KIP-101: Alter Replication Protocol to use Leader ...

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

[jira] [Updated] (KAFKA-4923) Add Exactly-Once Semantics to Streams

[ https://issues.apache.org/jira/browse/KAFKA-4923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4923: --- Summary: Add Exactly-Once Semantics to Streams (was: Add Exactly-Once Semantics) > Add Exact

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956038#comment-15956038 ] Joseph Aliase commented on KAFKA-4477: -- We have started seeing Open File Descriptor

[jira] [Commented] (KAFKA-5007) Kafka Replica Fetcher Thread- Resource Leak

[ https://issues.apache.org/jira/browse/KAFKA-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956036#comment-15956036 ] Joseph Aliase commented on KAFKA-5007: -- [~ijuma] Can you take look into this issue >

[GitHub] kafka pull request #2808: KIP-101: Alter Replication Protocol to use Leader ...

GitHub user benstopford opened a pull request: https://github.com/apache/kafka/pull/2808 KIP-101: Alter Replication Protocol to use Leader Epoch rather than High Watermark for Truncation This PR describes the addition of Partition Level Leader Epochs to messages in Kafka as a mecha

[GitHub] kafka pull request #2798: KAFKA-4837: Fix class name comparison in connector...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2798 --- 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-4837) Config validation in Connector plugins need to compare against both canonical and simple class names

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

[jira] [Updated] (KAFKA-4837) Config validation in Connector plugins need to compare against both canonical and simple class names

[ https://issues.apache.org/jira/browse/KAFKA-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4837: - Resolution: Fixed Fix Version/s: 0.11.0.0 Status: Resolved (was:

[jira] [Commented] (KAFKA-4810) SchemaBuilder should be more lax about checking that fields are unset if they are being set to the same value

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

[GitHub] kafka pull request #2806: KAFKA-4810: Kafka Connect SchemaBuilder unset fiel...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2806 --- 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-4810) SchemaBuilder should be more lax about checking that fields are unset if they are being set to the same value

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

[jira] [Commented] (KAFKA-5008) Kafka-Clients not OSGi ready

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

[GitHub] kafka pull request #2807: KAFKA-5008: Provide OSGi metadata for Kafka-Client...

GitHub user lostiniceland opened a pull request: https://github.com/apache/kafka/pull/2807 KAFKA-5008: Provide OSGi metadata for Kafka-Clients This change uses the bnd-gradle-plugin for the kafka-clients module in order to generate OSGi metadata. The bnd.bnd file is used by the

[jira] [Commented] (KAFKA-4222) Transient failure in QueryableStateIntegrationTest.queryOnRebalance

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

[GitHub] kafka pull request #2358: WIP -- DO NOT MERGE -- KAFKA-4222: Transient failu...

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

[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=15955739#comment-15955739 ] Matthias J. Sax commented on KAFKA-3455: [~nthean] "I have done exactly this" -> y

[jira] [Commented] (KAFKA-4810) SchemaBuilder should be more lax about checking that fields are unset if they are being set to the same value

[ https://issues.apache.org/jira/browse/KAFKA-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955732#comment-15955732 ] ASF GitHub Bot commented on KAFKA-4810: --- GitHub user vitaly-pushkar opened a pull re

[GitHub] kafka pull request #2806: KAFKA-4810: Kafka Connect SchemaBuilder unset fiel...

GitHub user vitaly-pushkar opened a pull request: https://github.com/apache/kafka/pull/2806 KAFKA-4810: Kafka Connect SchemaBuilder unset fields validation fix https://issues.apache.org/jira/browse/KAFKA-4810 > Currently SchemaBuilder is strict when checking that certain fi

[jira] [Commented] (KAFKA-4810) SchemaBuilder should be more lax about checking that fields are unset if they are being set to the same value

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

[GitHub] kafka pull request #2787: KAFKA-4810: Kafka Connect SchemaBuilder unset fiel...

Github user vitaly-pushkar closed the pull request at: https://github.com/apache/kafka/pull/2787 --- 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] [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=15955651#comment-15955651 ] Nikki Thean commented on KAFKA-3455: If it helps, as a user, I have done exactly this

Re: [DISCUSS] KIP-138: Change punctuate semantics

Yeah I like PuncutationType much better; I just threw Time out there more as a strawman than an actual suggestion ;) I still think it's worth considering what this buys us over an additional callback. I foresee a number of punctuate implementations following this pattern: public void punctuate(Pun

Re: [DISCUSS] KIP-138: Change punctuate semantics

Sounds promising to me too. I'll update the KIP with this as the primary proposal but leave the other alternatives there as under consideration for now. Cheers, Michal On 4 April 2017 at 19:10, Matthias J. Sax wrote: > That sounds promising. > > I am just wondering if `Time` is the best name.

[jira] [Commented] (KAFKA-5013) Fail the build when findbugs fails

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

[GitHub] kafka pull request #2805: KAFKA-5013. Fail the build when findbugs fails

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2805 KAFKA-5013. Fail the build when findbugs fails You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-5013 Alternatively you can r

[jira] [Commented] (KAFKA-5013) Fail the build when findbugs fails

[ https://issues.apache.org/jira/browse/KAFKA-5013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955602#comment-15955602 ] Colin P. McCabe commented on KAFKA-5013: For now, let's exclude tests. I'll post

[jira] [Created] (KAFKA-5013) Fail the build when findbugs fails

Colin P. McCabe created KAFKA-5013: -- Summary: Fail the build when findbugs fails Key: KAFKA-5013 URL: https://issues.apache.org/jira/browse/KAFKA-5013 Project: Kafka Issue Type: Bug

[jira] [Comment Edited] (KAFKA-5009) Globally Unique internal topic names when using Joins

[ https://issues.apache.org/jira/browse/KAFKA-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955544#comment-15955544 ] Matthias J. Sax edited comment on KAFKA-5009 at 4/4/17 6:16 PM:

[jira] [Commented] (KAFKA-5009) Globally Unique internal topic names when using Joins

[ https://issues.apache.org/jira/browse/KAFKA-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955544#comment-15955544 ] Matthias J. Sax commented on KAFKA-5009: All topics generated by Kafka Streams are

Re: [DISCUSS] KIP-138: Change punctuate semantics

That sounds promising. I am just wondering if `Time` is the best name. Maybe we want to add other non-time based punctuations at some point later. I would suggest enum PunctuationType { EVENT_TIME, SYSTEM_TIME, } or similar. Just to keep the door open -- it's easier to add new stuff if the n

[jira] [Updated] (KAFKA-5012) Refactor plugin discovery in Connect to offer a global index for plugins and transformations

[ https://issues.apache.org/jira/browse/KAFKA-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantine Karantasis updated KAFKA-5012: -- Description: Currently {{PluginDiscovery}} returns a list of plugins and a list

[jira] [Created] (KAFKA-5012) Refactor plugin discovery in Connect to offer a global index for plugins and transformations

Konstantine Karantasis created KAFKA-5012: - Summary: Refactor plugin discovery in Connect to offer a global index for plugins and transformations Key: KAFKA-5012 URL: https://issues.apache.org/jira/browse/

[jira] [Created] (KAFKA-5011) Replica fetchers may need to down-convert messages during a selective message format upgrade

Joel Koshy created KAFKA-5011: - Summary: Replica fetchers may need to down-convert messages during a selective message format upgrade Key: KAFKA-5011 URL: https://issues.apache.org/jira/browse/KAFKA-5011

Re: [VOTE] KIP-122: Add Reset Consumer Group Offsets tooling

Sorry for the delay Jorge. Responses inline. On Thu, Mar 23, 2017 at 5:56 PM, Jorge Esteban Quilcate Otoya < quilcate.jo...@gmail.com> wrote: > @Ismael, thanks for your feedback! > 1. Good point. I will add optional support for timezone as part of the > datetime input. But, when datetime is witho

[jira] [Commented] (KAFKA-4971) Why is there no difference between kafka benchmark tests on SSD and HDD?

[ https://issues.apache.org/jira/browse/KAFKA-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955260#comment-15955260 ] Michal Borowiecki commented on KAFKA-4971: -- I'd venture a guess that you are limi

[jira] [Commented] (KAFKA-4971) Why is there no difference between kafka benchmark tests on SSD and HDD?

[ https://issues.apache.org/jira/browse/KAFKA-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955219#comment-15955219 ] Dasol Kim commented on KAFKA-4971: -- I was experimenting with the kafka producer installed

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955113#comment-15955113 ] Ismael Juma commented on KAFKA-3174: We switched message format V2 to use CRC32C (see

[GitHub] kafka pull request #2804: MINOR: don't throw CommitFailedException during su...

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2804 MINOR: don't throw CommitFailedException during suspendTasksAndState Cherrypicked from trunk https://github.com/apache/kafka/pull/2535 You can merge this pull request into a Git repository by ru

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

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2803 MINOR: improve MinTimestampTrackerTest and fix NPE when null element Cherry picked from trunk fix https://github.com/apache/kafka/pull/2611 You can merge this pull request into a Git repository

[jira] [Updated] (KAFKA-5010) Log cleaner crashed with BufferOverflowException when writing to the writeBuffer

[ https://issues.apache.org/jira/browse/KAFKA-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5010: --- Labels: reliability (was: ) > Log cleaner crashed with BufferOverflowException when writing to the >

[jira] [Updated] (KAFKA-5010) Log cleaner crashed with BufferOverflowException when writing to the writeBuffer

[ https://issues.apache.org/jira/browse/KAFKA-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5010: --- Priority: Critical (was: Major) > Log cleaner crashed with BufferOverflowException when writing to th

[jira] [Updated] (KAFKA-5010) Log cleaner crashed with BufferOverflowException when writing to the writeBuffer

[ https://issues.apache.org/jira/browse/KAFKA-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5010: --- Fix Version/s: 0.11.0.0 > Log cleaner crashed with BufferOverflowException when writing to the > writ

Re: [DISCUSS] KIP-138: Change punctuate semantics

I agree that the framework providing and managing the notion of stream time is valuable and not something we would want to delegate to the tasks. I'm not entirely convinced that a separate callback (option C) is that messy (it could just be a default method with an empty implementation), but if we

[jira] [Resolved] (KAFKA-5009) Globally Unique internal topic names when using Joins

[ https://issues.apache.org/jira/browse/KAFKA-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Tranter resolved KAFKA-5009. - Resolution: Invalid This is only an issue when using Confluent Schema Registry related Serdes. >

[jira] [Commented] (KAFKA-3502) Build is killed during kafka streams tests due to `pure virtual method called` error

[ https://issues.apache.org/jira/browse/KAFKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955024#comment-15955024 ] Eno Thereska commented on KAFKA-3502: - Seeing this again. > Build is killed during ka

[jira] [Reopened] (KAFKA-3502) Build is killed during kafka streams tests due to `pure virtual method called` error

[ https://issues.apache.org/jira/browse/KAFKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reopened KAFKA-3502: - > Build is killed during kafka streams tests due to `pure virtual method > called` error > --

Re: log cleaner thread crashes with different log.cleaner.io.buffer.size

Filed a JIRA for this. https://issues.apache.org/jira/browse/KAFKA-5010 (also forwarded to the dev list.) On Tue, Apr 4, 2017 at 7:16 PM, Shuai Lin wrote: > After digging a bit into the source code of LogCleaner class, i realized > maybe i should not try to fix the crash by increasing the > log

[jira] [Created] (KAFKA-5010) Log cleaner crashed with BufferOverflowException when writing to the writeBuffer

Shuai Lin created KAFKA-5010: Summary: Log cleaner crashed with BufferOverflowException when writing to the writeBuffer Key: KAFKA-5010 URL: https://issues.apache.org/jira/browse/KAFKA-5010 Project: Kafka

Enable Kafka sink connector to insert data from topics to tables as and when sink is up

I have developed kafka-sink-connector (using confluent-oss-3.2.0-2.11, connect framework) for my data-store (Amppol ADS), which stores data from kafka topic to corresponding table in my store. Every thing is working as expected as long as kafka servers and ADS servers are up and running. Need a hel

Re: [VOTE] KIP-134: Delay initial consumer group rebalance

Hi Onur, Thanks for the update. I misunderstood what you said before. I believe what you are suggesting sounds ok, though i don't think it addresses the point Becket made earlier in the discussion thread. See below. Thanks, Damian 1.

[GitHub] kafka pull request #2802: MINOR: Log append validation improvements

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2802 MINOR: Log append validation improvements You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka validate-base-offset Alternatively you can

[jira] [Updated] (KAFKA-4913) creating a window store with one segment throws division by zero error

[ https://issues.apache.org/jira/browse/KAFKA-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4913: Priority: Blocker (was: Major) > creating a window store with one segment throws division by zero e

[jira] [Updated] (KAFKA-4916) Add streams tests with brokers failing

[ https://issues.apache.org/jira/browse/KAFKA-4916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4916: Issue Type: Bug (was: Improvement) > Add streams tests with brokers failing > -

[jira] [Created] (KAFKA-5009) Globally Unique internal topic names when using Joins

Mark Tranter created KAFKA-5009: --- Summary: Globally Unique internal topic names when using Joins Key: KAFKA-5009 URL: https://issues.apache.org/jira/browse/KAFKA-5009 Project: Kafka Issue Type

[jira] [Updated] (KAFKA-4943) SCRAM secret's should be better protected with Zookeeper ACLs

[ https://issues.apache.org/jira/browse/KAFKA-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4943: -- Status: Patch Available (was: Open) > SCRAM secret's should be better protected with Zookeeper

[jira] [Updated] (KAFKA-4943) SCRAM secret's should be better protected with Zookeeper ACLs

[ https://issues.apache.org/jira/browse/KAFKA-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4943: -- Affects Version/s: 0.10.2.0 Fix Version/s: 0.10.2.1 Component/s: security > SC

[GitHub] kafka pull request #2801: MINOR: Fix multiple org.apache.kafka.streams.Kafka...

GitHub user original-brownbear opened a pull request: https://github.com/apache/kafka/pull/2801 MINOR: Fix multiple org.apache.kafka.streams.KafkaStreams.StreamStateListener being instantiated There should only be a single `org.apache.kafka.streams.KafkaStreams.StreamStateListener`

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

See Changes: [me] KAFKA-4855: Struct SchemaBuilder should not allow duplicate fields -- [...truncated 342.63 KB...] kafka.integration.SaslPlaintextTopicMetadataTest > te

[jira] [Assigned] (KAFKA-3385) Need to log "Rejected connection" as WARNING message

[ https://issues.apache.org/jira/browse/KAFKA-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned KAFKA-3385: --- Assignee: (was: Andrea Cosentino) > Need to log "Rejected connection" as WARNING