[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 Components: consumer Reporter: Ivan Balashov Assignee: Neha Narkhede Priority: Minor Often clients need to find out which offsets contain necessary data. One of the possible solutions would be to iterate with small fetch size. However, this still leads to unnecessary data being transmitted in case keys already reference searched data. The ability to fetch keys only would simplify search for the necessary offset. Of course, there can be other scenarios where consumer needs keys only, without message part. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KAFKA-2093) Reduce noise in Kafka logs
Ivan Balashov created KAFKA-2093: Summary: Reduce noise in Kafka logs Key: KAFKA-2093 URL: https://issues.apache.org/jira/browse/KAFKA-2093 Project: Kafka Issue Type: Improvement Reporter: Ivan Balashov Priority: Trivial On failure, kafka producer logs error AND throws exception. This can pose problems, since client application cannot flexibly control if a particular exception should be logged, and logging becomes all-or-nothing choice for particular logger. We must remove logging error if we decide to throw exception. Some examples of this: kafka.client.ClientUtils$:89 kafka.producer.SyncProducer:103 If no one has objections, I can search around for other cases of logging + throwing which should also be fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-2093) Remove logging error if we throw exception
[ https://issues.apache.org/jira/browse/KAFKA-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Balashov updated KAFKA-2093: - Summary: Remove logging error if we throw exception (was: Reduce noise in Kafka logs) Remove logging error if we throw exception -- Key: KAFKA-2093 URL: https://issues.apache.org/jira/browse/KAFKA-2093 Project: Kafka Issue Type: Improvement Reporter: Ivan Balashov Priority: Trivial On failure, kafka producer logs error AND throws exception. This can pose problems, since client application cannot flexibly control if a particular exception should be logged, and logging becomes all-or-nothing choice for particular logger. We must remove logging error if we decide to throw exception. Some examples of this: kafka.client.ClientUtils$:89 kafka.producer.SyncProducer:103 If no one has objections, I can search around for other cases of logging + throwing which should also be fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-1502) source jar is empty
[ https://issues.apache.org/jira/browse/KAFKA-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077631#comment-14077631 ] Ivan Balashov commented on KAFKA-1502: -- http://repo1.maven.org/maven2/org/apache/kafka/kafka_2.10/0.8.1.1/kafka_2.10-0.8.1.1-sources.jar Still empty, any ideas how to fix? source jar is empty --- Key: KAFKA-1502 URL: https://issues.apache.org/jira/browse/KAFKA-1502 Project: Kafka Issue Type: Bug Components: build Affects Versions: 0.8.2 Reporter: Jun Rao Assignee: Joel Koshy Labels: newbie When doing a local publish, kafka_2.8.0-0.8.1.1-sources.jar only contains the following files. META-INF/ META-INF/MANIFEST.MF LICENSE NOTICE -- This message was sent by Atlassian JIRA (v6.2#6252)
