[jira] [Commented] (KAFKA-2453) enable new consumer in EndToEndLatency

[ https://issues.apache.org/jira/browse/KAFKA-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725704#comment-14725704 ] Ben Stopford commented on KAFKA-2453: - [~junrao] changes made and system tests passing > enable new

[jira] [Created] (KAFKA-2498) need build steps/instruction while building apache kafka from source github branch 0.8.2

naresh gundu created KAFKA-2498: --- Summary: need build steps/instruction while building apache kafka from source github branch 0.8.2 Key: KAFKA-2498 URL: https://issues.apache.org/jira/browse/KAFKA-2498

Re: How can I start writing a Copycat connector?

I'd highly recommend keeping your connector in a separate repo and following the process Gwen suggested. That's how I'm working on connectors (and convertalizers, as Gwen likes to call them). Keep in mind that copycat-hdfs and copycat-jdbc haven't been updated to the Kafka Copycat code yet,

[jira] [Created] (KAFKA-2499) kafka-producer-perf-test should use something more realistic than empty byte arrays

Ben Stopford created KAFKA-2499: --- Summary: kafka-producer-perf-test should use something more realistic than empty byte arrays Key: KAFKA-2499 URL: https://issues.apache.org/jira/browse/KAFKA-2499

Re: ProducerPerformance.scala compressing Array of Zeros

You’re absolutely right. This should be fixed. I’ve made a note of this in https://issues.apache.org/jira/browse/KAFKA-2499 . If you’d like to submit a pull request for this that would be awesome :) Otherwise I’ll try and fit it into the

[jira] [Commented] (KAFKA-2499) kafka-producer-perf-test should use something more realistic than empty byte arrays

[ https://issues.apache.org/jira/browse/KAFKA-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726069#comment-14726069 ] Edward Ribeiro commented on KAFKA-2499: --- Hi [~benstopford], I have a tidy bit of previous experience

[jira] [Resolved] (KAFKA-2497) Logging

[ https://issues.apache.org/jira/browse/KAFKA-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-2497. -- Resolution: Fixed Assignee: Ewen Cheslack-Postava Added, thanks for the

[jira] [Commented] (KAFKA-2498) need build steps/instruction while building apache kafka from source github branch 0.8.2

[ https://issues.apache.org/jira/browse/KAFKA-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725882#comment-14725882 ] Edward Ribeiro commented on KAFKA-2498: --- Hi [~gundun], I am afraid you lost me here. If you are

[jira] [Resolved] (KAFKA-2496) New consumer from trunk doesn't work with 0.8.2.1 brokers

[ https://issues.apache.org/jira/browse/KAFKA-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-2496. -- Resolution: Invalid Assignee: Ewen Cheslack-Postava [~serejja] 2 points.

[jira] [Commented] (KAFKA-2486) New consumer performance

[ https://issues.apache.org/jira/browse/KAFKA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726063#comment-14726063 ] Jason Gustafson commented on KAFKA-2486: [~jkreps] I've been running the consumer performance

[jira] [Updated] (KAFKA-2000) Delete consumer offsets from kafka once the topic is deleted

[ https://issues.apache.org/jira/browse/KAFKA-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2000: --- Fix Version/s: 0.8.3 > Delete consumer offsets from kafka once the topic is deleted >

[jira] [Updated] (KAFKA-2460) Fix capitalization in SSL classes

[ https://issues.apache.org/jira/browse/KAFKA-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2460: --- Fix Version/s: (was: 0.8.3) > Fix capitalization in SSL classes > - > >

[jira] [Updated] (KAFKA-2295) Dynamically loaded classes (encoders, etc.) may not be found by Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2295: --- Fix Version/s: (was: 0.9.0) 0.8.3 > Dynamically loaded classes (encoders, etc.) may

[jira] [Updated] (KAFKA-2145) An option to add topic owners.

[ https://issues.apache.org/jira/browse/KAFKA-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2145: --- Fix Version/s: 0.8.3 > An option to add topic owners. > --- > >

[jira] [Commented] (KAFKA-2486) New consumer performance

[ https://issues.apache.org/jira/browse/KAFKA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726085#comment-14726085 ] Ben Stopford commented on KAFKA-2486: - [~hachikuji] [~jkreps] I'd add that the new consumer handles

[jira] [Updated] (KAFKA-2064) Replace ConsumerMetadataRequest and Response with org.apache.kafka.common.requests objects

[ https://issues.apache.org/jira/browse/KAFKA-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2064: Fix Version/s: (was: 0.8.3) > Replace ConsumerMetadataRequest and Response with >

[jira] [Updated] (KAFKA-2066) Replace FetchRequest / FetchResponse with their org.apache.kafka.common.requests equivalents

[ https://issues.apache.org/jira/browse/KAFKA-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2066: Fix Version/s: (was: 0.8.3) > Replace FetchRequest / FetchResponse with their >

[jira] [Updated] (KAFKA-1763) validate_index_log in system tests runs remotely but uses local paths

[ https://issues.apache.org/jira/browse/KAFKA-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1763: Fix Version/s: (was: 0.8.3) > validate_index_log in system tests runs remotely but uses local

[jira] [Updated] (KAFKA-2068) Replace OffsetCommit Request/Response with org.apache.kafka.common.requests equivalent

[ https://issues.apache.org/jira/browse/KAFKA-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2068: --- Fix Version/s: (was: 0.8.3) > Replace OffsetCommit Request/Response with

[jira] [Updated] (KAFKA-2067) Add LeaderAndISR request/response to org.apache.kafka.common.requests and replace usage in core module

[ https://issues.apache.org/jira/browse/KAFKA-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2067: --- Fix Version/s: (was: 0.8.3) > Add LeaderAndISR request/response to org.apache.kafka.common.requests and

Re: Review Request 36858: Patch for KAFKA-2120

> On Sept. 1, 2015, 1:02 a.m., Jun Rao wrote: > > clients/src/main/java/org/apache/kafka/clients/NetworkClient.java, lines > > 362-367 > > > > > > We need to think through this logic a bit more. The patch here > >

[GitHub] kafka pull request: Fixing KAFKA-2309

GitHub user auradkar opened a pull request: https://github.com/apache/kafka/pull/185 Fixing KAFKA-2309 Currently, a LeaderAndIsrRequest does not mark the isrShrinkRate if the received ISR is smaller than the existing ISR. This can happen if one of the replicas is shut down. You

[jira] [Commented] (KAFKA-2309) ISR shrink rate not updated on LeaderAndIsr request with shrunk ISR

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

[jira] [Updated] (KAFKA-2136) Client side protocol changes to return quota delays

[ https://issues.apache.org/jira/browse/KAFKA-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2136: --- Fix Version/s: 0.8.3 > Client side protocol changes to return quota delays >

[jira] [Updated] (KAFKA-2311) Consumer's ensureNotClosed method not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2311: --- Fix Version/s: 0.8.3 > Consumer's ensureNotClosed method not thread safe >

[jira] [Commented] (KAFKA-2496) New consumer from trunk doesn't work with 0.8.2.1 brokers

[ https://issues.apache.org/jira/browse/KAFKA-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726448#comment-14726448 ] Jay Kreps commented on KAFKA-2496: -- The first response is expected. The group management feature didn't

[jira] [Updated] (KAFKA-2419) Allow certain Sensors to be garbage collected after inactivity

[ https://issues.apache.org/jira/browse/KAFKA-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2419: --- Fix Version/s: 0.8.3 > Allow certain Sensors to be garbage collected after inactivity >

[jira] [Updated] (KAFKA-2338) Warn users if they change max.message.bytes that they also need to update broker and consumer settings

[ https://issues.apache.org/jira/browse/KAFKA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2338: Fix Version/s: (was: 0.8.3) > Warn users if they change max.message.bytes that they also need

[jira] [Updated] (KAFKA-2229) Phase 1: Requests and KafkaApis

[ https://issues.apache.org/jira/browse/KAFKA-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2229: Fix Version/s: (was: 0.8.3) > Phase 1: Requests and KafkaApis > ---

[jira] [Updated] (KAFKA-2303) Fix for KAFKA-2235 LogCleaner offset map overflow causes another compaction failures

[ https://issues.apache.org/jira/browse/KAFKA-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2303: Fix Version/s: (was: 0.8.3) > Fix for KAFKA-2235 LogCleaner offset map overflow causes another

[jira] [Updated] (KAFKA-1933) Fine-grained locking in log append

[ https://issues.apache.org/jira/browse/KAFKA-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1933: --- Fix Version/s: (was: 0.8.3) > Fine-grained locking in log append > -- > >

Re: ProducerPerformance.scala compressing Array of Zeros

I kind of think letting the ProducerPerformance send uncompressed bytes is not a bad idea. The reason being is that when you send compressed bytes, it is not easy to determine how much data are you actually send. Arguably sending uncompressed bytes does not take compression cost into performance

[jira] [Updated] (KAFKA-2470) kafka-producer-perf-test.sh can't configure all to request-num-acks

[ https://issues.apache.org/jira/browse/KAFKA-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2470: Fix Version/s: (was: 0.8.3) > kafka-producer-perf-test.sh can't configure all to

[jira] [Updated] (KAFKA-2146) adding partition did not find the correct startIndex

[ https://issues.apache.org/jira/browse/KAFKA-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2146: Fix Version/s: (was: 0.8.3) > adding partition did not find the correct startIndex >

[jira] [Updated] (KAFKA-1887) controller error message on shutting the last broker

[ https://issues.apache.org/jira/browse/KAFKA-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1887: --- Fix Version/s: (was: 0.8.3) > controller error message on shutting the last broker >

Re: Review Request 34492: Patch for KAFKA-2210

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34492/ --- (Updated Sept. 1, 2015, 10:36 p.m.) Review request for kafka. Bugs:

[jira] [Updated] (KAFKA-2454) Dead lock between delete log segment and shutting down.

[ https://issues.apache.org/jira/browse/KAFKA-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2454: --- Fix Version/s: 0.8.3 > Dead lock between delete log segment and shutting down. >

[jira] [Updated] (KAFKA-2499) kafka-producer-perf-test should use something more realistic than empty byte arrays

[ https://issues.apache.org/jira/browse/KAFKA-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-2499: Assignee: Edward Ribeiro > kafka-producer-perf-test should use something more realistic than empty

[jira] [Commented] (KAFKA-2499) kafka-producer-perf-test should use something more realistic than empty byte arrays

[ https://issues.apache.org/jira/browse/KAFKA-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726134#comment-14726134 ] Edward Ribeiro commented on KAFKA-2499: --- okay, thanks! > kafka-producer-perf-test should use

[jira] [Commented] (KAFKA-1977) Make logEndOffset available in the Zookeeper consumer

[ https://issues.apache.org/jira/browse/KAFKA-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726173#comment-14726173 ] Will Funnell commented on KAFKA-1977: - [~hachikuji] Created a ticket here:

[jira] [Updated] (KAFKA-2070) Replace OffsetRequest/response with ListOffsetRequest/response from org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2070: Fix Version/s: (was: 0.8.3) > Replace OffsetRequest/response with ListOffsetRequest/response

[jira] [Updated] (KAFKA-2385) zookeeper-shell does not work

[ https://issues.apache.org/jira/browse/KAFKA-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2385: --- Fix Version/s: (was: 0.8.3) > zookeeper-shell does not work > - > >

[jira] [Commented] (KAFKA-2421) Upgrade LZ4 to version 1.3 to avoid crashing with IBM Java 7

[ https://issues.apache.org/jira/browse/KAFKA-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726385#comment-14726385 ] Jun Rao commented on KAFKA-2421: The patch no longer applies. Could you rebase? > Upgrade LZ4 to version

[jira] [Updated] (KAFKA-2499) kafka-producer-perf-test should use something more realistic than empty byte arrays

[ https://issues.apache.org/jira/browse/KAFKA-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-2499: Labels: newbie (was: ) > kafka-producer-perf-test should use something more realistic than empty

[jira] [Created] (KAFKA-2500) Make logEndOffset available in the 0.8.3 Consumer

Will Funnell created KAFKA-2500: --- Summary: Make logEndOffset available in the 0.8.3 Consumer Key: KAFKA-2500 URL: https://issues.apache.org/jira/browse/KAFKA-2500 Project: Kafka Issue Type:

Re: [DISCUSS] Client-side Assignment for New Consumer

Sorry about the format... It seems apache mail list does not suppor table. Please refer to the following sheet. https://docs.google.com/spreadsheets/d/1eKlQC1Ty74qVrIDH9vk7S6hEs_eJAyOufFUZaIU-k28/edit?usp=sharing Thanks, Jiangjie (Becket) Qin On Tue, Sep 1, 2015 at 1:01 PM, Aditya Auradkar

[jira] [Updated] (KAFKA-2375) Implement elasticsearch Copycat sink connector

[ https://issues.apache.org/jira/browse/KAFKA-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2375: Fix Version/s: (was: 0.8.3) > Implement elasticsearch Copycat sink connector >

[jira] [Updated] (KAFKA-438) Code cleanup in MessageTest

[ https://issues.apache.org/jira/browse/KAFKA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-438: --- Fix Version/s: (was: 0.8.3) > Code cleanup in MessageTest > --- > >

[jira] [Updated] (KAFKA-1755) Improve error handling in log cleaner

[ https://issues.apache.org/jira/browse/KAFKA-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1755: Fix Version/s: (was: 0.8.3) > Improve error handling in log cleaner >

[jira] [Updated] (KAFKA-1566) Kafka environment configuration (kafka-env.sh)

[ https://issues.apache.org/jira/browse/KAFKA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1566: Fix Version/s: (was: 0.8.3) > Kafka environment configuration (kafka-env.sh) >

[jira] [Updated] (KAFKA-1927) Replace requests in kafka.api with requests in org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1927: Fix Version/s: (was: 0.8.3) > Replace requests in kafka.api with requests in >

[jira] [Commented] (KAFKA-2500) Make logEndOffset available in the 0.8.3 Consumer

[ https://issues.apache.org/jira/browse/KAFKA-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726238#comment-14726238 ] Gwen Shapira commented on KAFKA-2500: - [~hachikuji], do you want to take a look at this one? > Make

[jira] [Commented] (KAFKA-2472) Fix kafka ssl configs to not throw warnings

[ https://issues.apache.org/jira/browse/KAFKA-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726338#comment-14726338 ] Jun Rao commented on KAFKA-2472: The original intention is to warn people of mis-spelled config names.

[jira] [Updated] (KAFKA-2309) ISR shrink rate not updated on LeaderAndIsr request with shrunk ISR

[ https://issues.apache.org/jira/browse/KAFKA-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2309: --- Fix Version/s: (was: 0.8.3) > ISR shrink rate not updated on LeaderAndIsr request with shrunk ISR >

[jira] [Updated] (KAFKA-1898) compatibility testing framework

[ https://issues.apache.org/jira/browse/KAFKA-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1898: Fix Version/s: (was: 0.8.3) > compatibility testing framework >

[jira] [Updated] (KAFKA-2442) QuotasTest should not fail when cpu is busy

[ https://issues.apache.org/jira/browse/KAFKA-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2442: Fix Version/s: (was: 0.8.3) > QuotasTest should not fail when cpu is busy >

[jira] [Updated] (KAFKA-2120) Add a request timeout to NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2120: Fix Version/s: (was: 0.8.3) > Add a request timeout to NetworkClient >

[jira] [Updated] (KAFKA-2073) Replace TopicMetadata request/response with o.a.k.requests.metadata

[ https://issues.apache.org/jira/browse/KAFKA-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2073: Fix Version/s: (was: 0.8.3) > Replace TopicMetadata request/response with

Re: Review Request 36858: Patch for KAFKA-2120

> On Sept. 1, 2015, 1:02 a.m., Jun Rao wrote: > > clients/src/main/java/org/apache/kafka/clients/NetworkClient.java, lines > > 362-367 > > > > > > We need to think through this logic a bit more. The patch here > >

[jira] [Updated] (KAFKA-2072) Add StopReplica request/response to o.a.k.common.requests and replace the usage in core module

[ https://issues.apache.org/jira/browse/KAFKA-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2072: --- Fix Version/s: (was: 0.8.3) > Add StopReplica request/response to o.a.k.common.requests and replace the

[jira] [Updated] (KAFKA-2074) Add UpdateMetadata request/response to o.a.k.common.requests and replace its use in core module

[ https://issues.apache.org/jira/browse/KAFKA-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2074: --- Fix Version/s: (was: 0.8.3) Actually, KAFKA-2411 won't fix this completely since KafkaApis still uses the

[jira] [Commented] (KAFKA-1763) validate_index_log in system tests runs remotely but uses local paths

[ https://issues.apache.org/jira/browse/KAFKA-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726275#comment-14726275 ] Ewen Cheslack-Postava commented on KAFKA-1763: -- This is for the old system tests. I think

[jira] [Updated] (KAFKA-2120) Add a request timeout to NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2120: Fix Version/s: 0.8.3 > Add a request timeout to NetworkClient >

[jira] [Updated] (KAFKA-2210) KafkaAuthorizer: Add all public entities, config changes and changes to KafkaAPI and kafkaServer to allow pluggable authorizer implementation.

[ https://issues.apache.org/jira/browse/KAFKA-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Brahmbhatt updated KAFKA-2210: Attachment: KAFKA-2210_2015-09-01_15:36:02.patch > KafkaAuthorizer: Add all public

[jira] [Commented] (KAFKA-2499) kafka-producer-perf-test should use something more realistic than empty byte arrays

[ https://issues.apache.org/jira/browse/KAFKA-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726096#comment-14726096 ] Ben Stopford commented on KAFKA-2499: - Hi [~eribeiro] That's fantastic! There are guidelines for

[jira] [Updated] (KAFKA-1967) Support more flexible serialization in Log4jAppender

[ https://issues.apache.org/jira/browse/KAFKA-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1967: Fix Version/s: (was: 0.8.3) > Support more flexible serialization in Log4jAppender >

[jira] [Updated] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1853: Fix Version/s: (was: 0.8.3) > Unsuccessful suffix rename of expired LogSegment can leak open

[jira] [Updated] (KAFKA-2074) Add UpdateMetadata request/response to o.a.k.common.requests and replace its use in core module

[ https://issues.apache.org/jira/browse/KAFKA-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2074: --- Resolution: Duplicate Status: Resolved (was: Patch Available) Closing this jira since it's now

[jira] [Updated] (KAFKA-2412) Documentation bug: Add information for key.serializer and value.serializer to New Producer Config sections

[ https://issues.apache.org/jira/browse/KAFKA-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2412: --- Fix Version/s: 0.8.3 Those docs are auto generated. Perhaps we should fix ConfigDef.toHtmlTable() to add a

[jira] [Updated] (KAFKA-2378) Add Copycat embedded API

[ https://issues.apache.org/jira/browse/KAFKA-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2378: Assignee: Ewen Cheslack-Postava > Add Copycat embedded API > > >

[jira] [Updated] (KAFKA-2254) The shell script should be optimized , even kafka-run-class.sh has a syntax error.

[ https://issues.apache.org/jira/browse/KAFKA-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2254: Fix Version/s: (was: 0.8.3) > The shell script should be optimized , even kafka-run-class.sh

[jira] [Updated] (KAFKA-2075) Validate that all kafka.api requests has been removed and clean up compatibility code

[ https://issues.apache.org/jira/browse/KAFKA-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2075: Fix Version/s: (was: 0.8.3) > Validate that all kafka.api requests has been removed and clean

[jira] [Updated] (KAFKA-2449) Update mirror maker (MirrorMaker) docs

[ https://issues.apache.org/jira/browse/KAFKA-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2449: Assignee: Geoff Anderson > Update mirror maker (MirrorMaker) docs >

[jira] [Updated] (KAFKA-2417) Ducktape tests for SSL/TLS

[ https://issues.apache.org/jira/browse/KAFKA-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2417: Assignee: Geoff Anderson > Ducktape tests for SSL/TLS > -- > >

0.8.3 JIRA

Hi Team, I just went over the 0.8.3 Jiras that had no one assigned to them and either moved them out of the release (if they were important someone would be working on them) or assigned them to the guy who opened the jira (you reported it, you fix it). If I accidentally assigned a JIRA that you

[GitHub] kafka pull request: KAFKA-2332; Add quota metrics to old producer ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/176 --- 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-2332) Add quota metrics to old producer and consumer

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

[jira] [Reopened] (KAFKA-2074) Add UpdateMetadata request/response to o.a.k.common.requests and replace its use in core module

[ https://issues.apache.org/jira/browse/KAFKA-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reopened KAFKA-2074: > Add UpdateMetadata request/response to o.a.k.common.requests and replace its > use in core module >

[jira] [Updated] (KAFKA-2332) Add quota metrics to old producer and consumer

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

Build failed in Jenkins: Kafka-trunk #610

See Changes: [jjkoshy] KAFKA-2332; Add quota metrics to old producer and consumer -- [...truncated 900 lines...] kafka.integration.TopicMetadataTest > testTopicMetadataRequest PASSED

[jira] [Updated] (KAFKA-2069) Replace OffsetFetch request/response with their org.apache.kafka.common.requests equivalent

[ https://issues.apache.org/jira/browse/KAFKA-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2069: --- Fix Version/s: (was: 0.8.3) > Replace OffsetFetch request/response with their >

[jira] [Updated] (KAFKA-2338) Warn users if they change max.message.bytes that they also need to update broker and consumer settings

[ https://issues.apache.org/jira/browse/KAFKA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2338: --- Fix Version/s: 0.8.3 > Warn users if they change max.message.bytes that they also need to update > broker

[jira] [Created] (KAFKA-2492) Upgrade zkclient dependency to 0.6

Stevo Slavic created KAFKA-2492: --- Summary: Upgrade zkclient dependency to 0.6 Key: KAFKA-2492 URL: https://issues.apache.org/jira/browse/KAFKA-2492 Project: Kafka Issue Type: Task Affects

[jira] [Created] (KAFKA-2493) Add ability to fetch only keys in consumer

Ivan Balashov created KAFKA-2493: Summary: Add ability to fetch only keys in consumer Key: KAFKA-2493 URL: https://issues.apache.org/jira/browse/KAFKA-2493 Project: Kafka Issue Type: Wish

[GitHub] kafka pull request: KAFKA-2493 Upgraded zkclient dependency from 0...

GitHub user sslavic opened a pull request: https://github.com/apache/kafka/pull/184 KAFKA-2493 Upgraded zkclient dependency from 0.5 to 0.6 You can merge this pull request into a Git repository by running: $ git pull https://github.com/sslavic/kafka feature/KAFKA-2492

[jira] [Commented] (KAFKA-2493) Add ability to fetch only keys in consumer

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

Re:no Kafka KIP meeting tomorrow

Can I know what is KIP meeting? At 2015-09-01 12:30:18, "Jun Rao" wrote: >Since there are no new KIP issues for discussion, again, there is no >KIP meeting >tomorrow. > >Thanks, > >Jun

[jira] [Commented] (KAFKA-2453) enable new consumer in EndToEndLatency

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

[jira] [Created] (KAFKA-2494) Documetn ReplicaId in OffsetRequest in the protocol guide

Magnus Reftel created KAFKA-2494: Summary: Documetn ReplicaId in OffsetRequest in the protocol guide Key: KAFKA-2494 URL: https://issues.apache.org/jira/browse/KAFKA-2494 Project: Kafka

[jira] [Created] (KAFKA-2495) Protocol guide only partially updated after ConsumerMetadata* addition?

Magnus Reftel created KAFKA-2495: Summary: Protocol guide only partially updated after ConsumerMetadata* addition? Key: KAFKA-2495 URL: https://issues.apache.org/jira/browse/KAFKA-2495 Project: Kafka

[GitHub] kafka pull request: KAFKA-2453: Enable new consumer in EndToEndLat...

GitHub user benstopford reopened a pull request: https://github.com/apache/kafka/pull/158 KAFKA-2453: Enable new consumer in EndToEndLatency You can merge this pull request into a Git repository by running: $ git pull https://github.com/benstopford/kafka KAFKA-2453b

[jira] [Commented] (KAFKA-2453) enable new consumer in EndToEndLatency

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

[GitHub] kafka pull request: KAFKA-2453: Enable new consumer in EndToEndLat...

Github user benstopford closed the pull request at: https://github.com/apache/kafka/pull/158 --- 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-2453) enable new consumer in EndToEndLatency

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

[jira] [Updated] (KAFKA-2453) enable new consumer in EndToEndLatency

[ https://issues.apache.org/jira/browse/KAFKA-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-2453: Status: Patch Available (was: Open) [~junrao] please can you review or assign other reviewer.

[jira] [Created] (KAFKA-2496) New consumer from trunk doesn't work with 0.8.2.1 brokers

Serhey Novachenko created KAFKA-2496: Summary: New consumer from trunk doesn't work with 0.8.2.1 brokers Key: KAFKA-2496 URL: https://issues.apache.org/jira/browse/KAFKA-2496 Project: Kafka

[GitHub] kafka pull request: KAFKA-2453: Enable new consumer in EndToEndLat...

GitHub user benstopford reopened a pull request: https://github.com/apache/kafka/pull/158 KAFKA-2453: Enable new consumer in EndToEndLatency You can merge this pull request into a Git repository by running: $ git pull https://github.com/benstopford/kafka KAFKA-2453b

[GitHub] kafka pull request: KAFKA-2453: Enable new consumer in EndToEndLat...

Github user benstopford closed the pull request at: https://github.com/apache/kafka/pull/158 --- 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-2453) enable new consumer in EndToEndLatency

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

Open source Mysql -> Kafka connector

I thought this would be of interest: https://developer.zendesk.com/blog/introducing-maxwell-a-mysql-to-kafka-binlog-processor A copycat connector that parses MySQL binlogs would be rather useful I think. Streaming connectors using jdbc are tricky to implement because they rely on an indexed

  1   2   >