[jira] [Created] (KAFKA-5153) KAFKA Cluster : 0.10.2.0 : Servers Getting disconnected : Service Impacting

Arpan created KAFKA-5153: Summary: KAFKA Cluster : 0.10.2.0 : Servers Getting disconnected : Service Impacting Key: KAFKA-5153 URL: https://issues.apache.org/jira/browse/KAFKA-5153 Project: Kafka Is

[jira] [Updated] (KAFKA-5153) KAFKA Cluster : 0.10.2.0 : Servers Getting disconnected : Service Impacting

[ https://issues.apache.org/jira/browse/KAFKA-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpan updated KAFKA-5153: - Affects Version/s: 0.10.2.0 > KAFKA Cluster : 0.10.2.0 : Servers Getting disconnected : Service Impacting > --

[jira] [Created] (KAFKA-5154) Kafka Streams throws NPE during rebalance

Lukas Gemela created KAFKA-5154: --- Summary: Kafka Streams throws NPE during rebalance Key: KAFKA-5154 URL: https://issues.apache.org/jira/browse/KAFKA-5154 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP 141 - ProducerRecordBuilder Interface

Hi Matthias, Deprecating widely used APIs is a big deal. Build warnings are a nuisance and can potentially break the build for those who have a zero-warnings policy (which is good practice). It creates a bunch of busy work for our users and various resources like books, blog posts, etc. become out

[jira] [Created] (KAFKA-5155) Messages can be deleted prematurely when some producers use timestamps and some not

Petr Plavjaník created KAFKA-5155: - Summary: Messages can be deleted prematurely when some producers use timestamps and some not Key: KAFKA-5155 URL: https://issues.apache.org/jira/browse/KAFKA-5155 P

[jira] [Updated] (KAFKA-4307) Inconsistent parameters between console producer and consumer

[ https://issues.apache.org/jira/browse/KAFKA-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balint Molnar updated KAFKA-4307: - Status: Patch Available (was: In Progress) > Inconsistent parameters between console producer and

[jira] [Updated] (KAFKA-4703) Test with two SASL_SSL listeners with different JAAS contexts

[ https://issues.apache.org/jira/browse/KAFKA-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balint Molnar updated KAFKA-4703: - Status: Patch Available (was: In Progress) > Test with two SASL_SSL listeners with different JAAS

[jira] [Updated] (KAFKA-5127) Replace pattern matching with foreach where the case None is unused

[ https://issues.apache.org/jira/browse/KAFKA-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balint Molnar updated KAFKA-5127: - Status: Patch Available (was: In Progress) > Replace pattern matching with foreach where the case

[VOTE] KIP-137: Enhance TopicCommand --describe to show topics marked for deletion

Hi, I'd like to start the vote on KIP-137: https://cwiki.apache.org/confluence/display/KAFKA/KIP-137%3A+Enhance+TopicCommand+--describe+to+show+topics+marked+for+deletion Thanks,

Re: [VOTE] KIP-137: Enhance TopicCommand --describe to show topics marked for deletion

Thanks for the KIP, +1 (binding). Ismael On Tue, May 2, 2017 at 11:43 AM, Mickael Maison wrote: > Hi, > > I'd like to start the vote on KIP-137: > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 137%3A+Enhance+TopicCommand+--describe+to+show+topics+marked+for+deletion > > Thanks, >

[GitHub] kafka pull request #2924: change connection refused message from level DEBUG...

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

[GitHub] kafka pull request #2954: MINOR: Fix error logged if not enough alive broker...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2954 MINOR: Fix error logged if not enough alive brokers for transactions state topic You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka fix

[GitHub] kafka pull request #2955: Replace KeyValuePrinter and KStreamForeach with KS...

GitHub user jedichien opened a pull request: https://github.com/apache/kafka/pull/2955 Replace KeyValuePrinter and KStreamForeach with KStreamPeek I remove `KeyValuePrinter` and `KStreamForeach` two class, then implements them by `KStreamPeek`. So, now `KStreamPeek` can do `KeyV

[jira] [Commented] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992704#comment-15992704 ] james chien commented on KAFKA-4772: my new PR is here https://github.com/apache/kafka

[GitHub] kafka pull request #2952: MINOR: fix some c/p error that was causing describ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2952 --- 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-4422) Drop support for Scala 2.10

[ https://issues.apache.org/jira/browse/KAFKA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992774#comment-15992774 ] Ismael Juma commented on KAFKA-4422: For 0.11.0.0, we will remove support for Scala 2.

Re: Request to add to the contributor list

Hello, Wondering if you were able to look into it? Thanks, Amit Daga On Sun, Apr 30, 2017 at 1:29 PM, Amit Daga wrote: > Hello Team, > > Hope you are doing well. > > My name is Amit Daga. This is to request you to add me to the contributor > list. Also if KAFKA-4996 issue is still not assigned

[jira] [Updated] (KAFKA-5155) Messages can be deleted prematurely when some producers use timestamps and some not

[ https://issues.apache.org/jira/browse/KAFKA-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Plavjaník updated KAFKA-5155: -- Description: Some messages can be deleted prematurely and never read in following scenario. A p

[jira] [Created] (KAFKA-5156) Options for handling exceptions in streams

Eno Thereska created KAFKA-5156: --- Summary: Options for handling exceptions in streams Key: KAFKA-5156 URL: https://issues.apache.org/jira/browse/KAFKA-5156 Project: Kafka Issue Type: Task

[jira] [Created] (KAFKA-5157) Options for handling corrupt data during deserialization

Eno Thereska created KAFKA-5157: --- Summary: Options for handling corrupt data during deserialization Key: KAFKA-5157 URL: https://issues.apache.org/jira/browse/KAFKA-5157 Project: Kafka Issue Ty

[jira] [Updated] (KAFKA-5006) KeyValueStore.put may throw exception unrelated to the current put attempt

[ https://issues.apache.org/jira/browse/KAFKA-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-5006: Issue Type: Sub-task (was: Bug) Parent: KAFKA-5156 > KeyValueStore.put may throw exception

[GitHub] kafka pull request #2956: KAFKA-4422: Drop support for Scala 2.10

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2956 KAFKA-4422: Drop support for Scala 2.10 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-4422-drop-support-scala-2.10 Alternativ

[jira] [Commented] (KAFKA-4422) Drop support for Scala 2.10

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

[jira] [Updated] (KAFKA-4422) Drop support for Scala 2.10

[ https://issues.apache.org/jira/browse/KAFKA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4422: --- Status: Patch Available (was: Open) > Drop support for Scala 2.10 > --- > >

[jira] [Created] (KAFKA-5158) Options for handling exceptions during processing

Eno Thereska created KAFKA-5158: --- Summary: Options for handling exceptions during processing Key: KAFKA-5158 URL: https://issues.apache.org/jira/browse/KAFKA-5158 Project: Kafka Issue Type: Sub

[jira] [Updated] (KAFKA-4743) Add a tool to Reset Consumer Group Offsets

[ https://issues.apache.org/jira/browse/KAFKA-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4743: --- Status: Patch Available (was: Open) > Add a tool to Reset Consumer Group Offsets > --

[jira] [Assigned] (KAFKA-4743) Add a tool to Reset Consumer Group Offsets

[ https://issues.apache.org/jira/browse/KAFKA-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4743: -- Assignee: Jorge Quilcate > Add a tool to Reset Consumer Group Offsets > ---

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Hi Jeyhun, This approach would change ValueMapper (...etc) to be classes, rather than interfaces, which is also a backwards incompatible change. An alternative approach that would be backwards compatible would be to define new interfaces, and provide overrides where those interfaces are used. Un

[GitHub] kafka pull request #2957: KAFKA-5132: abort long running transactions

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2957 KAFKA-5132: abort long running transactions Abort any ongoing transactions that haven't been touched for longer than the transaction timeout You can merge this pull request into a Git repository by ru

[jira] [Commented] (KAFKA-5132) Abort long running transactions

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

[jira] [Updated] (KAFKA-4743) Add a tool to Reset Consumer Group Offsets

[ https://issues.apache.org/jira/browse/KAFKA-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4743: --- Fix Version/s: 0.11.0.0 > Add a tool to Reset Consumer Group Offsets > ---

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

See

[DISCUSS] KIP-148: Add a connect timeout for client

Hi all, Currently in our test environment, we found that after one of the broker node crash (reboot or os crash), the client may still be connecting to the crash node to send metadata request or other request, and it needs several minutes to be aware that the connection is timeout then try anot

[jira] [Updated] (KAFKA-5132) Abort long running transactions

[ https://issues.apache.org/jira/browse/KAFKA-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5132: -- Status: Patch Available (was: Open) > Abort long running transactions > ---

Re: [VOTE] KIP-137: Enhance TopicCommand --describe to show topics marked for deletion

+1 (non-binding) Thanks Mickael. --Vahid From: Ismael Juma To: dev@kafka.apache.org Date: 05/02/2017 03:46 AM Subject:Re: [VOTE] KIP-137: Enhance TopicCommand --describe to show topics marked for deletion Sent by:isma...@gmail.com Thanks for the KIP, +1 (binding).

[jira] [Updated] (KAFKA-5131) WriteTxnMarkers and complete commit/abort on partition immigration

[ https://issues.apache.org/jira/browse/KAFKA-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5131: -- Status: Patch Available (was: Open) > WriteTxnMarkers and complete commit/abort on partition immigratio

[GitHub] kafka pull request #2625: KAFKA-4623: Change default unclean.leader.election...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2625 --- 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] [Assigned] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4623: -- Assignee: Ismael Juma (was: Sharad) > Change Default unclean.leader.election.enabled from True

[jira] [Commented] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

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

[jira] [Assigned] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4623: -- Assignee: Sharad (was: Ismael Juma) > Change Default unclean.leader.election.enabled from True

[jira] [Updated] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4623: --- Issue Type: Improvement (was: Bug) > Change Default unclean.leader.election.enabled from True to Fals

[jira] [Assigned] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford reassigned KAFKA-4623: --- Assignee: Ben Stopford (was: Sharad) > Change Default unclean.leader.election.enabled from T

[jira] [Commented] (KAFKA-5153) KAFKA Cluster : 0.10.2.0 : Servers Getting disconnected : Service Impacting

[ https://issues.apache.org/jira/browse/KAFKA-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993116#comment-15993116 ] Arpan commented on KAFKA-5153: -- Yes KAFKA-4477 was fixed by KAFKFA-3994 in 0.10.1.1 but stil

[jira] [Assigned] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4623: -- Assignee: Sharad (was: Ben Stopford) > Change Default unclean.leader.election.enabled from Tru

[jira] [Assigned] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford reassigned KAFKA-4623: --- Assignee: Ben Stopford (was: Sharad) > Change Default unclean.leader.election.enabled from T

[jira] [Updated] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-4623: Issue Type: Task (was: Improvement) > Change Default unclean.leader.election.enabled from True to F

[jira] [Updated] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-4623: Issue Type: Improvement (was: New Feature) > Change Default unclean.leader.election.enabled from Tr

[jira] [Updated] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-4623: Issue Type: New Feature (was: Task) > Change Default unclean.leader.election.enabled from True to F

[jira] [Commented] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993120#comment-15993120 ] Ismael Juma commented on KAFKA-4623: Not sure why, but it seems like this issue cannot

[jira] [Updated] (KAFKA-5107) remove preferred replica election state from ControllerContext

[ https://issues.apache.org/jira/browse/KAFKA-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-5107: --- Resolution: Fixed Fix Version/s: 0.11.0.0 Status: Resolved (was: Patch Available) Issue res

[GitHub] kafka pull request #2927: KAFKA-5107: remove preferred replica election stat...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2927 --- 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-5107) remove preferred replica election state from ControllerContext

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

[jira] [Created] (KAFKA-5159) Update Kafka documentation to mention AdminClient

Ismael Juma created KAFKA-5159: -- Summary: Update Kafka documentation to mention AdminClient Key: KAFKA-5159 URL: https://issues.apache.org/jira/browse/KAFKA-5159 Project: Kafka Issue Type: Impro

[jira] [Commented] (KAFKA-4857) Improve Client handling

[ https://issues.apache.org/jira/browse/KAFKA-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993127#comment-15993127 ] Ismael Juma commented on KAFKA-4857: There are 2 changes here. One is to use AdminClie

[jira] [Commented] (KAFKA-4955) Add network handler thread utilization to request quota calculation

[ https://issues.apache.org/jira/browse/KAFKA-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993165#comment-15993165 ] Jun Rao commented on KAFKA-4955: [~rsivaram], now that KAFKA-4954 is committed, should we

RE: Kafka Connect and Partitions

Hi Gwen/Randall, I think I've finally understood, more or less, how partitioning relates to SourceRecords. Because I was using the SourceRecord constructor that doesn't provide values for key and key schema, the key is null. The DefaultPartioner appears to map null to a constant value rather

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

See Changes: [ismael] KAFKA-4623; Default unclean.leader.election.enabled to false (KIP-106) -- [...truncated 844.92 KB...] kafka.integration.SaslPlaintextTopicMetadataTes

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

See Changes: [ismael] KAFKA-4623; Default unclean.leader.election.enabled to false (KIP-106) -- [...truncated 1.52 MB...] kafka.admin.ConfigCommandTest > shouldDeleteBrok

Re: [DISCUSS] KIP-145: Classloading Isolation in Connect

Thank you for your vote Colin! Unfortunately the discussion thread had to move because of a KIP-number collision. Here's a link to the active discussion thread: https://www.mail-archive.com/dev@kafka.apache.org/msg71453.html Apologies for the inconvenience. Konstantine On Mon, May 1, 2017 at 1

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

See Changes: [junrao] KAFKA-5107; remove preferred replica election state from -- [...truncated 842.45 KB...] kafka.integration.SaslPlaintextTopicMetadataTest > testAutoC

Re: [DISCUSS] KIP 145 - Expose Record Headers in Kafka Connect

A couple of thoughts: First, agreed that we definitely want to expose header functionality. Thank you Mike for starting the conversation! Even if Connect doesn't do anything special with it, there's value in being able to access/set headers. On motivation -- I think there are much broader use cas

[jira] [Updated] (KAFKA-3266) Implement KIP-140 RPCs and APIs for creating, altering, and listing ACLs

[ https://issues.apache.org/jira/browse/KAFKA-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-3266: --- Summary: Implement KIP-140 RPCs and APIs for creating, altering, and listing ACLs (was: Imple

[jira] [Commented] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993408#comment-15993408 ] Matthias J. Sax commented on KAFKA-5154: Thanks for reporting this [~Lukas Gemela]

[jira] [Commented] (KAFKA-1313) Support adding replicas to existing topic partitions via kafka-topics tool without manually setting broker assignments

[ https://issues.apache.org/jira/browse/KAFKA-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993414#comment-15993414 ] Steven Schlansker commented on KAFKA-1313: -- I started using Kafka Streams recentl

[jira] [Created] (KAFKA-5160) KIP-98 : broker side handling for the TxnOffsetCommitRequest

Apurva Mehta created KAFKA-5160: --- Summary: KIP-98 : broker side handling for the TxnOffsetCommitRequest Key: KAFKA-5160 URL: https://issues.apache.org/jira/browse/KAFKA-5160 Project: Kafka Iss

Re: [DISCUSS] KIP-146: Classloading Isolation in Connect

Thanks for the KIP. A few responses inline, followed by additional comments. On Mon, May 1, 2017 at 9:50 PM, Konstantine Karantasis < konstant...@confluent.io> wrote: > Gwen, Randall thank you for your very insightful observations. I'm glad you > find this first draft to be an adequate platform

[jira] [Updated] (KAFKA-4955) Add network handler thread utilization to request quota calculation

[ https://issues.apache.org/jira/browse/KAFKA-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4955: -- Resolution: Fixed Status: Resolved (was: Patch Available) [~junrao] Yes, thank you. T

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993467#comment-15993467 ] Michael Noll commented on KAFKA-1194: - [~guozhang]: Do you happen to know the latest s

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

See

[jira] [Created] (KAFKA-5161) reassign-partitions to check if broker of ID exists in cluster

Lawrence Weikum created KAFKA-5161: -- Summary: reassign-partitions to check if broker of ID exists in cluster Key: KAFKA-5161 URL: https://issues.apache.org/jira/browse/KAFKA-5161 Project: Kafka

Re: [DISCUSS] KIP-136: Add Listener name and Security Protocol name to SelectorMetrics tags

Edoardo, Are you planning to do this only in the broker? Listener names only exist at the broker level. Also, clients only have a single security protocol, so maybe we should do this for brokers only. In that case, the compatibility impact is also lower because more users rely on the Yammer metric

[jira] [Created] (KAFKA-5162) Add a reference to AdminClient to docs/api.html

Colin P. McCabe created KAFKA-5162: -- Summary: Add a reference to AdminClient to docs/api.html Key: KAFKA-5162 URL: https://issues.apache.org/jira/browse/KAFKA-5162 Project: Kafka Issue Type:

[GitHub] kafka pull request #2958: KAFKA-5162: Add a reference to AdminClient to docs...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2958 KAFKA-5162: Add a reference to AdminClient to docs/api.html You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-5162 Alternativ

[jira] [Commented] (KAFKA-5162) Add a reference to AdminClient to docs/api.html

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

[jira] [Commented] (KAFKA-5162) Add a reference to AdminClient to docs/api.html

[ https://issues.apache.org/jira/browse/KAFKA-5162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993566#comment-15993566 ] Colin P. McCabe commented on KAFKA-5162: https://github.com/apache/kafka/pull/2958

[jira] [Work started] (KAFKA-5162) Add a reference to AdminClient to docs/api.html

[ https://issues.apache.org/jira/browse/KAFKA-5162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5162 started by Colin P. McCabe. -- > Add a reference to AdminClient to docs/api.html > -

[jira] [Commented] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993594#comment-15993594 ] Guozhang Wang commented on KAFKA-5154: -- I think I saw a similar issue a days ago and

Re: [DISCUSS] KIP 145 - Expose Record Headers in Kafka Connect

Hi Ewan, So on the point of JMS the predefined/standardised JMS and JMSX headers have predefined types. So these can be serialised/deserialised accordingly. Custom jms headers agreed could be a bit more difficult but on the 80/20 rule I would agree mostly they're string values and as anyhow you

Re: Kafka Connect and Partitions

Hi, David. Excellent. I'm glad that you've solved the puzzle. Best regards, Randall On Tue, May 2, 2017 at 9:18 AM, wrote: > Hi Gwen/Randall, > > I think I've finally understood, more or less, how partitioning relates to > SourceRecords. > > Because I was using the SourceRecord constructor tha

Re: [DISCUSS] KIP-136: Add Listener name and Security Protocol name to SelectorMetrics tags

Hi, Edo, Thanks for the proposal. It looks good to me. Jun On Thu, Mar 30, 2017 at 8:51 AM, Edoardo Comar wrote: > Hi all, > > We created KIP-136: Add Listener name and Security Protocol name to > SelectorMetrics tags > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 136%3A+Add+List

[jira] [Assigned] (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 ] dan norwood reassigned KAFKA-4343: -- Assignee: dan norwood > Connect REST API should expose whether each connector is a source or si

[jira] [Created] (KAFKA-5163) Support replicas movement between log directories (KIP-113)

Dong Lin created KAFKA-5163: --- Summary: Support replicas movement between log directories (KIP-113) Key: KAFKA-5163 URL: https://issues.apache.org/jira/browse/KAFKA-5163 Project: Kafka Issue Type:

[GitHub] kafka pull request #2959: Created convenience method to create ZkUtils

GitHub user bbaugher opened a pull request: https://github.com/apache/kafka/pull/2959 Created convenience method to create ZkUtils You can merge this pull request into a Git repository by running: $ git pull https://github.com/bbaugher/kafka zkutils Alternatively you can revi

[GitHub] kafka pull request #2960: KAFKA-4343: Expose Connector type in REST API

GitHub user norwood opened a pull request: https://github.com/apache/kafka/pull/2960 KAFKA-4343: Expose Connector type in REST API https://cwiki.apache.org/confluence/display/KAFKA/KIP-151+Expose+Connector+type+in+REST+API You can merge this pull request into a Git repository by ru

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15993709#comment-15993709 ] ASF GitHub Bot commented on KAFKA-4343: --- GitHub user norwood opened a pull request:

[DISCUSS] KIP 151 - Expose Connector type in REST API

hello. in an attempt to make the connect rest endpoints more useful i'd like to add the Connector type (Sink/Source) in our rest endpoints to make them more self descriptive. KIP here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-151+Expose+Connector+type+in+REST+API initial pr: https://

[jira] [Created] (KAFKA-5164) SetSchemaMetadata does not replace the schemas in structs correctly

Ewen Cheslack-Postava created KAFKA-5164: Summary: SetSchemaMetadata does not replace the schemas in structs correctly Key: KAFKA-5164 URL: https://issues.apache.org/jira/browse/KAFKA-5164 Pro

Re: [DISCUSS] KIP 151 - Expose Connector type in REST API

Both the proposal and PR look good to me. -Ewen On Tue, May 2, 2017 at 1:48 PM, dan wrote: > hello. > > in an attempt to make the connect rest endpoints more useful i'd like to > add the Connector type (Sink/Source) in our rest endpoints to make them > more self descriptive. > > KIP here: > htt

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

Hi all, As I looked deeper into the details of the impact of this change, it became apparent to me that it may better to postpone it to a future release. Reasons follow: 1. Once we move to Java 8, there will be a ripple effect in all projects that depend on the Kafka clients jar. Given where we a

[GitHub] kafka pull request #2961: MINOR: Serialize the real isolationLevel in FetchR...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/2961 MINOR: Serialize the real isolationLevel in FetchRequest You can merge this pull request into a Git repository by running: $ git pull https://github.com/apurvam/kafka MINOR-serialize-isolatio

[jira] [Commented] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela commented on KAFKA-5154: - Hi, we have a kafka streams app consuming from

[jira] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela edited comment on KAFKA-5154 at 5/2/17 10:27 PM: --

[jira] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela edited comment on KAFKA-5154 at 5/2/17 10:33 PM: --

[jira] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela edited comment on KAFKA-5154 at 5/2/17 10:33 PM: --

[jira] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela edited comment on KAFKA-5154 at 5/2/17 10:34 PM: --

[jira] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela edited comment on KAFKA-5154 at 5/2/17 10:35 PM: --

[jira] [Commented] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993933#comment-15993933 ] Matthias J. Sax commented on KAFKA-5154: Thanks for the details. We will investiga

[jira] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela edited comment on KAFKA-5154 at 5/2/17 10:56 PM: --

[jira] [Comment Edited] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993902#comment-15993902 ] Lukas Gemela edited comment on KAFKA-5154 at 5/2/17 11:10 PM: --

[GitHub] kafka pull request #2926: KAFKA-5131: WriteTxnMarkers and complete commit/ab...

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

  1   2   >