[jira] [Resolved] (KAFKA-5120) Several controller metrics block if controller lock is held by another thread

[ https://issues.apache.org/jira/browse/KAFKA-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman resolved KAFKA-5120. - Resolution: Fixed KAFKA-5028 has been checked in so this should no longer be an issue. > Several

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

See

[jira] [Resolved] (KAFKA-3107) Error when trying to shut down auto balancing scheduler of controller

[ https://issues.apache.org/jira/browse/KAFKA-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman resolved KAFKA-3107. - Resolution: Fixed This problem should no longer exist after KAFKA-5028. > Error when trying to

[jira] [Updated] (KAFKA-4667) KIP-154: Connect should create internal topics

[ https://issues.apache.org/jira/browse/KAFKA-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4667: - Summary: KIP-154: Connect should create internal topics (was: Connect should

[jira] [Updated] (KAFKA-4783) KIP-128: Blackbox or pass through converter or ByteArrayConverter for connect

[ https://issues.apache.org/jira/browse/KAFKA-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4783: - Summary: KIP-128: Blackbox or pass through converter or ByteArrayConverter for

[jira] [Updated] (KAFKA-3487) KIP-146: Support per-connector/per-task classloaders in Connect

[ https://issues.apache.org/jira/browse/KAFKA-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3487: - Summary: KIP-146: Support per-connector/per-task classloaders in Connect (was:

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

[ https://issues.apache.org/jira/browse/KAFKA-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4343: - Summary: KIP-151: Connect REST API should expose whether each connector is a

[jira] [Updated] (KAFKA-3959) KIP-115: __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3959: - Summary: KIP-115: __consumer_offsets wrong number of replicas at startup (was:

[jira] [Commented] (KAFKA-5078) PartitionRecords.fetchRecords(...) should defer exception to the next call if iterator has already moved across any valid record

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

[GitHub] kafka pull request #2864: KAFKA-5078; PartitionRecords.fetchRecords(...) sho...

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

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

See

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

See Changes: [me] KAFKA-4343: Expose Connector type in REST API (KIP-151) -- [...truncated 850.11 KB...] kafka.tools.ConsoleConsumerTest >

[jira] [Work started] (KAFKA-5192) Range Scan for Windowed State Stores

[ https://issues.apache.org/jira/browse/KAFKA-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5192 started by Xavier Léauté. > Range Scan for Windowed State Stores > >

[jira] [Assigned] (KAFKA-5192) Range Scan for Windowed State Stores

[ https://issues.apache.org/jira/browse/KAFKA-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté reassigned KAFKA-5192: Assignee: Xavier Léauté > Range Scan for Windowed State Stores >

[jira] [Resolved] (KAFKA-5173) SASL tests failing with Could not find a 'KafkaServer' or 'sasl_plaintext.KafkaServer' entry in the JAAS configuration

[ https://issues.apache.org/jira/browse/KAFKA-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5173. Resolution: Fixed Assignee: Rajini Sivaram We believe this was fixed by

[jira] [Updated] (KAFKA-3487) Support per-connector/per-task classloaders in Connect

[ https://issues.apache.org/jira/browse/KAFKA-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3487: - Assignee: Konstantine Karantasis (was: Liquan Pei) Reviewer: Ewen

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

[ https://issues.apache.org/jira/browse/KAFKA-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4343: - Resolution: Fixed Reviewer: Ewen Cheslack-Postava Status: Resolved

[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=16007470#comment-16007470 ] ASF GitHub Bot commented on KAFKA-4343: --- Github user asfgit closed the pull request at:

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

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

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

Michal, you have enough votes, would you like to close the vote? Ismael On Thu, May 11, 2017 at 4:49 PM, Ewen Cheslack-Postava wrote: > +1 (binding) > > -Ewen > > On Thu, May 11, 2017 at 7:12 AM, Ismael Juma wrote: > > > Thanks for the KIP, Michal.

Re: [VOTE] KIP-133: List and Alter Configs Admin APIs (second attempt)

Thanks for all who provided feedback and voted. The vote passed with 5 binding +1s (Sriram, Guozhang, Jason, Jun, Ismael) and 3 non-binding +1s (Colin, Robert, James). Ismael On Fri, May 12, 2017 at 1:54 AM, Jun Rao wrote: > Hi, Ismael, > > Thanks for the update KIP. +1 > >

Re: [VOTE] KIP-133: List and Alter Configs Admin APIs (second attempt)

Hi, Ismael, Thanks for the update KIP. +1 Jun On Thu, May 11, 2017 at 4:13 PM, Ismael Juma wrote: > Thanks for the feedback Jun. > > 1. This is a good point. After thinking about it, I concluded that quotas > should be handled via separate APIs, so I moved it to future

[GitHub] kafka pull request #3029: fix reference to SchemaBuilder call

GitHub user smferguson opened a pull request: https://github.com/apache/kafka/pull/3029 fix reference to SchemaBuilder call You can merge this pull request into a Git repository by running: $ git pull https://github.com/smferguson/kafka schemabuilder_doc Alternatively you

[jira] [Commented] (KAFKA-3487) Support per-connector/per-task classloaders in Connect

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

[GitHub] kafka pull request #3028: KAFKA-3487: Support classloading isolation in Conn...

GitHub user kkonstantine opened a pull request: https://github.com/apache/kafka/pull/3028 KAFKA-3487: Support classloading isolation in Connect. You can merge this pull request into a Git repository by running: $ git pull https://github.com/kkonstantine/kafka

[GitHub] kafka pull request #3027: [WIP] KIP-155 KAFKA-5192 WindowStore range scan

GitHub user xvrl opened a pull request: https://github.com/apache/kafka/pull/3027 [WIP] KIP-155 KAFKA-5192 WindowStore range scan Note: this implementation based on the initial version of the kip, and does not reflect the latest changes that have yet to be agreed on. @dguy

Re: [VOTE] KIP-151: Expose Connector type in REST API (first attempt :)

here we are, only 72hrs later and we have reached agreement. +4 binding from Guozhang, Ismael, Ram, and Ewen. +2 non binding from Bharat and Konstantine. thanks everyone who voted/commented. dan On Wed, May 10, 2017 at 11:38 AM, Guozhang Wang wrote: > +1 > > On Wed, May

Re: [VOTE] KIP-133: List and Alter Configs Admin APIs (second attempt)

Thanks for the feedback Jun. 1. This is a good point. After thinking about it, I concluded that quotas should be handled via separate APIs, so I moved it to future work. I quote the reasoning from the KIP: "Support for reading and updating client, user and replication quotas. We initially

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

See Changes: [rajinisivaram] MINOR: JoinGroupRequest V0 invalid rebalance timeout -- [...truncated 846.85 KB...] kafka.api.SslConsumerTest > testSimpleConsumption PASSED

[jira] [Commented] (KAFKA-5217) Improve Streams internal exception handling

[ https://issues.apache.org/jira/browse/KAFKA-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007159#comment-16007159 ] Matthias J. Sax commented on KAFKA-5217: Sure. Done. > Improve Streams internal exception

[jira] [Updated] (KAFKA-5217) Improve Streams internal exception handling

[ https://issues.apache.org/jira/browse/KAFKA-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5217: --- Issue Type: Sub-task (was: Bug) Parent: KAFKA-5156 > Improve Streams internal

[jira] [Created] (KAFKA-5220) Application Reset Tool does not work with SASL

Matthias J. Sax created KAFKA-5220: -- Summary: Application Reset Tool does not work with SASL Key: KAFKA-5220 URL: https://issues.apache.org/jira/browse/KAFKA-5220 Project: Kafka Issue Type:

Re: [VOTE] KIP-146: Isolation of dependencies and classes in Kafka Connect (restarted voting thread)

A little after 72h have passed I'm happy to announce that this KIP has been accepted. Additionally, since all votes were submitted within the KIP deadline for KIPs targeting the 0.11.0.0 release, I intend to publish an implementation for review, targeting the forthcoming Apache Kafka release.

[GitHub] kafka pull request #2936: MINOR: JoinGroupRequest V0 invalid rebalance timeo...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2936 --- 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] [Commented] (KAFKA-5173) SASL tests failing with Could not find a 'KafkaServer' or 'sasl_plaintext.KafkaServer' entry in the JAAS configuration

[ https://issues.apache.org/jira/browse/KAFKA-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007029#comment-16007029 ] ASF GitHub Bot commented on KAFKA-5173: --- Github user rajinisivaram closed the pull request at:

[GitHub] kafka pull request #2985: KAFKA-5173: Log jaas.config if broker fails to sta...

Github user rajinisivaram closed the pull request at: https://github.com/apache/kafka/pull/2985 --- 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-5217) Improve Streams internal exception handling

[ https://issues.apache.org/jira/browse/KAFKA-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007013#comment-16007013 ] Eno Thereska commented on KAFKA-5217: - Do you want this as a subtask of

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

[ https://issues.apache.org/jira/browse/KAFKA-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-5156: --- Assignee: (was: Eno Thereska) > Options for handling exceptions in streams >

[jira] [Work started] (KAFKA-5217) Improve Streams internal exception handling

[ https://issues.apache.org/jira/browse/KAFKA-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5217 started by Matthias J. Sax. -- > Improve Streams internal exception handling >

Re: [VOTE] KIP-155 Add range scan for windowed state stores

Thanks Michal, you are correct. I can see your point now, and I can get behind returning Windowed as well for windowed stores. It might make sense to revisit the single key iterator in the future and do the same for consistency, but I'd rather not break backwards compatibility unless we have a

[GitHub] kafka pull request #3026: KAFKA-5713: Shutdown brokers in tests

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/3026 KAFKA-5713: Shutdown brokers in tests Add broker shutdown for `LeaderEpochIntegrationTest`. Move broker shutdown in other tests to `tearDown` to ensure brokers are shutdown even if tests

Re: [DISCUSS] KIP-143: Controller Health Metrics

Hi Ismael, Yes, a follow up KIP after the controller code settles down sounds good. Thanks, Jiangjie (Becket) Qin On Wed, May 10, 2017 at 6:11 PM, Ismael Juma wrote: > Thanks Jun. Discussed this offline with Onur and Jun and I believe there's > agreement so updated the

[jira] [Commented] (KAFKA-5072) Kafka topics should allow custom metadata configs within some config namespace

[ https://issues.apache.org/jira/browse/KAFKA-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006738#comment-16006738 ] Soumabrata Chakraborty commented on KAFKA-5072: --- Hi [~ijuma], [~benstopford], [~mjsax], I

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

See

Surprising behaviour with a Kafka 8 Producer writing to a Kafka 10 Cluster

Hi, I've noticed something a bit surprising (to me at least) when a Kafka 8 producer writes to a Kafka 10 Cluster where the messages are subsequently processed by a Kafka Connect sink. The messages are Avro encoded (a suitable Avro key/value converter is specified via worker.properties

Re: [VOTE] KIP-154 Add Kafka Connect configuration properties for creating internal topics

Randall is out atm and given the KIP deadline and 72h passed w/ only +1s, I'm going to close this vote out. The KIP passes: 4 binding +1s 5 non-binding +1s 0 -1s Thanks everyone for voting! -Ewen On Thu, May 11, 2017 at 7:03 AM, Ismael Juma wrote: > Thanks for the KIP,

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

+1 (binding) -Ewen On Thu, May 11, 2017 at 7:12 AM, Ismael Juma wrote: > Thanks for the KIP, Michal. +1(binding) from me. > > Ismael > > On Sat, May 6, 2017 at 6:18 PM, Michal Borowiecki < > michal.borowie...@openbet.com> wrote: > >> Hi all, >> >> Given I'm not seeing any

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

See

0.11.0.0 KIP Freeze Update

Hi all, As you hopefully know, the KIP freeze for 0.11.0.0 was yesterday. Since this is the first release with a KIP freeze and a number of people from the community were in the Kafka Summit NY for a few days this week, I have included added KIPs that have enough votes to pass (even if the 72

[jira] [Updated] (KAFKA-5218) New Short serializer, deserializer, serde

[ https://issues.apache.org/jira/browse/KAFKA-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Molina updated KAFKA-5218: External issue URL: (was: https://github.com/apache/kafka/pull/3017) > New Short serializer,

[jira] [Updated] (KAFKA-5218) New Short serializer, deserializer, serde

[ https://issues.apache.org/jira/browse/KAFKA-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Molina updated KAFKA-5218: External issue URL: https://github.com/apache/kafka/pull/3017 > New Short serializer, deserializer,

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

[ https://issues.apache.org/jira/browse/KAFKA-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4343: --- Fix Version/s: 0.11.0.0 > Connect REST API should expose whether each connector is a source or sink >

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

[ https://issues.apache.org/jira/browse/KAFKA-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4343: --- Status: Patch Available (was: Open) > Connect REST API should expose whether each connector is a

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

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

[jira] [Commented] (KAFKA-4750) KeyValueIterator returns null values

[ https://issues.apache.org/jira/browse/KAFKA-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006486#comment-16006486 ] Dmitry Minkovsky commented on KAFKA-4750: - Affects 0.10.2.1 also > KeyValueIterator returns null

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

Thanks for the KIP, Michal. +1(binding) from me. Ismael On Sat, May 6, 2017 at 6:18 PM, Michal Borowiecki < michal.borowie...@openbet.com> wrote: > Hi all, > > Given I'm not seeing any contentious issues remaining on the discussion > thread, I'd like to initiate the vote for: > > KIP-138:

Re: [VOTE] KIP-154 Add Kafka Connect configuration properties for creating internal topics

Thanks for the KIP, Randall. +1 (binding) from me. On Mon, May 8, 2017 at 8:51 PM, Randall Hauch wrote: > Hi, everyone. > > Given the simple and non-controversial nature of the KIP, I would like to > start the voting process for KIP-154: Add Kafka Connect configuration >

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

Hi, Thanks for your comments. I think we cannot extend the two interfaces if we want to keep lambdas. I updated the KIP [1]. Maybe I should change the title, because now we are not limiting the KIP to only ValueMapper, ValueTransformer and ValueJoiner. Please feel free to comment. [1]

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

See Changes: [ismael] KAFKA-5182; Close txn coordinator threads during broker shutdown -- [...truncated 850.73 KB...] kafka.utils.CommandLineUtilsTest > testParseEmptyArg

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

See Changes: [ismael] KAFKA-5182; Close txn coordinator threads during broker shutdown -- [...truncated 849.37 KB...] kafka.log.ProducerStateManagerTest >

[GitHub] kafka pull request #3022: HOTFIX: change compression codec in TransactionSta...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3022 --- 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] [Resolved] (KAFKA-5182) Transient failure: RequestQuotaTest.testResponseThrottleTime

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

[GitHub] kafka pull request #3014: KAFKA-5182: Close txn coordinator threads during b...

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

Re: [DISCUSS] KIP-133: List and Alter Configs Admin APIs

Hey Colin, I added Config#get(String) to the KIP. Ismael On Mon, May 8, 2017 at 6:47 PM, Colin McCabe wrote: > > Good idea. Should we add a Config#get(String) that can get the value of > a specific ConfigEntry? >

[jira] [Commented] (KAFKA-4881) Add internal leave.group.on.close config to consumer

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

[GitHub] kafka pull request #3025: KAFKA-4881: add internal.leave.group.config to con...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3025 KAFKA-4881: add internal.leave.group.config to consumer Backport from https://github.com/apache/kafka/pull/2650 You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-4317) RocksDB checkpoint files lost on kill -9

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

[GitHub] kafka pull request #3024: KAFKA-4317: Checkpoint state stores on commit inte...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3024 KAFKA-4317: Checkpoint state stores on commit interval This is a backport of https://github.com/apache/kafka/pull/2471 You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-4317) RocksDB checkpoint files lost on kill -9

[ https://issues.apache.org/jira/browse/KAFKA-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006289#comment-16006289 ] ASF GitHub Bot commented on KAFKA-4317: --- Github user dguy closed the pull request at:

[jira] [Commented] (KAFKA-4317) RocksDB checkpoint files lost on kill -9

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

[GitHub] kafka pull request #3023: KAFKA-4317: Checkpoint StateStores on commit inter...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3023 KAFKA-4317: Checkpoint StateStores on commit interval This is a backport of: https://github.com/apache/kafka/pull/2471 from trunk You can merge this pull request into a Git repository by running:

[GitHub] kafka pull request #3023: KAFKA-4317: Checkpoint StateStores on commit inter...

Github user dguy closed the pull request at: https://github.com/apache/kafka/pull/3023 --- 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] [Work started] (KAFKA-4603) the argument of shell in doc wrong and command parsed error

[ https://issues.apache.org/jira/browse/KAFKA-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4603 started by Xin. -- > the argument of shell in doc wrong and command parsed error >

Re: [DISCUSS] Modify / Remove "Unstable" annotations in Streams API

Sounds reasonable. Thanks, Eno > On May 11, 2017, at 7:39 AM, Ismael Juma wrote: > > Thanks for the proposal Guozhang. This sounds good to me. > > Ismael > > On Thu, May 11, 2017 at 6:02 AM, Guozhang Wang wrote: > >> Hello folks, >> >> As we are

[GitHub] kafka pull request #3022: HOTFIX: change compression codec in TransactionSta...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3022 HOTFIX: change compression codec in TransactionStateManager to UncompressedCodec Change the compression code used for the transaction log to UncompressedCoded as it fails during creation when the

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

See

[jira] [Created] (KAFKA-5219) Move transaction expiration logic and scheduling to the Transaction Manager

Damian Guy created KAFKA-5219: - Summary: Move transaction expiration logic and scheduling to the Transaction Manager Key: KAFKA-5219 URL: https://issues.apache.org/jira/browse/KAFKA-5219 Project: Kafka

[jira] [Assigned] (KAFKA-5129) TransactionCoordinator - Add ACL check for each request

[ https://issues.apache.org/jira/browse/KAFKA-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-5129: - Assignee: Damian Guy > TransactionCoordinator - Add ACL check for each request >

[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: Priority: Blocker (was: Major) > KeyValueStore.put may throw exception unrelated to the current

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

[ https://issues.apache.org/jira/browse/KAFKA-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5156 started by Eno Thereska. --- > Options for handling exceptions in streams >

[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: Status: Patch Available (was: In Progress) > KeyValueStore.put may throw exception unrelated to

[jira] [Work started] (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 ] Work on KAFKA-5006 started by Eno Thereska. --- > KeyValueStore.put may throw exception unrelated to the current put attempt >

[GitHub] kafka pull request #3021: KAFKA-5006: change exception path

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/3021 KAFKA-5006: change exception path This should be backported to 0.10.2 as well. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (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:comment-tabpanel=16006136#comment-16006136 ] ASF GitHub Bot commented on KAFKA-5006: --- GitHub user enothereska opened a pull request:

provide rc.d scripts

Would be nice to add autostart scripts to be used by the various distributions. Preferably not only Kafka but the confluent platform services (schema registry, rest proxy) as well.

[GitHub] kafka pull request #3020: [WIP] Test PR builder for Scala 2.10 runs if targe...

Github user ijuma closed the pull request at: https://github.com/apache/kafka/pull/3020 --- 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 #3019: [WIP] Test that Scala PR builder for 2.10 doesn't ...

Github user ijuma closed the pull request at: https://github.com/apache/kafka/pull/3019 --- 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 #3019: [WIP] Test that Scala PR builder for 2.10 doesn't ...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3019 [WIP] Test that Scala PR builder for 2.10 doesn't trigger You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka test-scala-2.10-disabled

Re: [VOTE] KIP-155 Add range scan for windowed state stores

Also, wrt In the case of the window store, the "key" of the single-key iterator is the actual timestamp of the underlying entry, not just range of the window, so if we were to wrap the result key a window we wouldn't be getting back the equivalent of the single key iterator. I believe the

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

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

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

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

[ https://issues.apache.org/jira/browse/KAFKA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4422: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

Re: [VOTE] KIP-155 Add range scan for windowed state stores

Well, another concern, apart from potential confusion, is that you won't be able to peek the actual next key, just the timestamp. So the tradeoff is between having consistency in return types versus consistency in having the ability to know the next key without moving the iterator. To me the

Re: [DISCUSS] Modify / Remove "Unstable" annotations in Streams API

Thanks for the proposal Guozhang. This sounds good to me. Ismael On Thu, May 11, 2017 at 6:02 AM, Guozhang Wang wrote: > Hello folks, > > As we are approaching the feature freeze deadline of 0.11.0.0, one thing I > realized is that currently the Streams public APIs are

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

See Changes: [jason] KAFKA-5213; Mark a MemoryRecordsBuilder as full as soon as the append -- [...truncated 3.57 MB...] kafka.server.ReplicaFetcherThreadTest >

Re: [VOTE] KIP-155 Add range scan for windowed state stores

+1 Thanks Eno > On 10 May 2017, at 20:25, Michal Borowiecki > wrote: > > Apologies, I missed the discussion (or lack thereof) about the return type of: > > WindowStoreIterator> fetch(K from, K to, long timeFrom, long > timeTo) > > >