[jira] [Updated] (KAFKA-3086) unused handle method in MirrorMakerMessageHandler
[
https://issues.apache.org/jira/browse/KAFKA-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Nowak updated KAFKA-3086:
---
Status: Patch Available (was: Open)
> unused handle method in MirrorMakerMessageHandler
> -
>
> Key: KAFKA-3086
> URL: https://issues.apache.org/jira/browse/KAFKA-3086
> Project: Kafka
> Issue Type: Improvement
>Affects Versions: 0.9.0.0
>Reporter: Jun Rao
>Assignee: Jakub Nowak
> Labels: newbie
>
> The following method is never used by MirrorMaker.
> trait MirrorMakerMessageHandler {
> def handle(record: MessageAndMetadata[Array[Byte], Array[Byte]]):
> util.List[ProducerRecord[Array[Byte], Array[Byte]]]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KAFKA-3086) unused handle method in MirrorMakerMessageHandler
[
https://issues.apache.org/jira/browse/KAFKA-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Nowak updated KAFKA-3086:
---
Assignee: Jakub Nowak
> unused handle method in MirrorMakerMessageHandler
> -
>
> Key: KAFKA-3086
> URL: https://issues.apache.org/jira/browse/KAFKA-3086
> Project: Kafka
> Issue Type: Improvement
>Affects Versions: 0.9.0.0
>Reporter: Jun Rao
>Assignee: Jakub Nowak
> Labels: newbie
>
> The following method is never used by MirrorMaker.
> trait MirrorMakerMessageHandler {
> def handle(record: MessageAndMetadata[Array[Byte], Array[Byte]]):
> util.List[ProducerRecord[Array[Byte], Array[Byte]]]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KAFKA-3082) Make LogManager.InitialTaskDelayMs configurable
[ https://issues.apache.org/jira/browse/KAFKA-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Nowak updated KAFKA-3082: --- Assignee: Jakub Nowak > Make LogManager.InitialTaskDelayMs configurable > --- > > Key: KAFKA-3082 > URL: https://issues.apache.org/jira/browse/KAFKA-3082 > Project: Kafka > Issue Type: Improvement >Affects Versions: 0.9.0.0 >Reporter: Rado Buransky >Assignee: Jakub Nowak >Priority: Minor > > At the moment it is hardcoded to 30 seconds which makes it difficult to > simulate some scenarios for application testing purposes. > Specifically I am trying to write integration tests for a Spark Streaming > application to ensure that it behaves correctly even in case when Kafka log > starts to be cleaned up and I have to wait 30 seconds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-3082) Make LogManager.InitialTaskDelayMs configurable
[ https://issues.apache.org/jira/browse/KAFKA-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Nowak updated KAFKA-3082: --- Status: Patch Available (was: Open) > Make LogManager.InitialTaskDelayMs configurable > --- > > Key: KAFKA-3082 > URL: https://issues.apache.org/jira/browse/KAFKA-3082 > Project: Kafka > Issue Type: Improvement >Affects Versions: 0.9.0.0 >Reporter: Rado Buransky >Assignee: Jakub Nowak >Priority: Minor > > At the moment it is hardcoded to 30 seconds which makes it difficult to > simulate some scenarios for application testing purposes. > Specifically I am trying to write integration tests for a Spark Streaming > application to ensure that it behaves correctly even in case when Kafka log > starts to be cleaned up and I have to wait 30 seconds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KAFKA-2963) Replace server internal usage of TopicAndPartition with TopicPartition
[ https://issues.apache.org/jira/browse/KAFKA-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Nowak reassigned KAFKA-2963: -- Assignee: Jakub Nowak > Replace server internal usage of TopicAndPartition with TopicPartition > -- > > Key: KAFKA-2963 > URL: https://issues.apache.org/jira/browse/KAFKA-2963 > Project: Kafka > Issue Type: Sub-task >Reporter: Grant Henke >Assignee: Jakub Nowak > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KAFKA-2963) Replace server internal usage of TopicAndPartition with TopicPartition
[ https://issues.apache.org/jira/browse/KAFKA-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-2963 started by Jakub Nowak. -- > Replace server internal usage of TopicAndPartition with TopicPartition > -- > > Key: KAFKA-2963 > URL: https://issues.apache.org/jira/browse/KAFKA-2963 > Project: Kafka > Issue Type: Sub-task >Reporter: Grant Henke >Assignee: Jakub Nowak > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-2963) Replace server internal usage of TopicAndPartition with TopicPartition
[ https://issues.apache.org/jira/browse/KAFKA-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15054252#comment-15054252 ] Jakub Nowak commented on KAFKA-2963: I am working on this ticket, but I have a question. By server internal usage you also mean classes in package kafka.api (eg. FetchRequest) or should I leave them unchanged by adding some conversion? > Replace server internal usage of TopicAndPartition with TopicPartition > -- > > Key: KAFKA-2963 > URL: https://issues.apache.org/jira/browse/KAFKA-2963 > Project: Kafka > Issue Type: Sub-task >Reporter: Grant Henke >Assignee: Jakub Nowak > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KAFKA-2959) Remove temporary mapping to deserialize functions in RequestChannel
[ https://issues.apache.org/jira/browse/KAFKA-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Nowak reassigned KAFKA-2959: -- Assignee: Jakub Nowak > Remove temporary mapping to deserialize functions in RequestChannel > > > Key: KAFKA-2959 > URL: https://issues.apache.org/jira/browse/KAFKA-2959 > Project: Kafka > Issue Type: Sub-task >Reporter: Grant Henke >Assignee: Jakub Nowak > > Once the old Request & Response objects are no longer used we can delete the > legacy mapping maintained in RequestChannel.scala -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KAFKA-2959) Remove temporary mapping to deserialize functions in RequestChannel
[ https://issues.apache.org/jira/browse/KAFKA-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-2959 started by Jakub Nowak. -- > Remove temporary mapping to deserialize functions in RequestChannel > > > Key: KAFKA-2959 > URL: https://issues.apache.org/jira/browse/KAFKA-2959 > Project: Kafka > Issue Type: Sub-task >Reporter: Grant Henke >Assignee: Jakub Nowak > > Once the old Request & Response objects are no longer used we can delete the > legacy mapping maintained in RequestChannel.scala -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-2959) Remove temporary mapping to deserialize functions in RequestChannel
[ https://issues.apache.org/jira/browse/KAFKA-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Nowak updated KAFKA-2959: --- Assignee: (was: Jakub Nowak) > Remove temporary mapping to deserialize functions in RequestChannel > > > Key: KAFKA-2959 > URL: https://issues.apache.org/jira/browse/KAFKA-2959 > Project: Kafka > Issue Type: Sub-task >Reporter: Grant Henke > > Once the old Request & Response objects are no longer used we can delete the > legacy mapping maintained in RequestChannel.scala -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-2959) Remove temporary mapping to deserialize functions in RequestChannel
[ https://issues.apache.org/jira/browse/KAFKA-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15047393#comment-15047393 ] Jakub Nowak commented on KAFKA-2959: Yes, I didn't notice that earlier, so for now I will leave this ticket. > Remove temporary mapping to deserialize functions in RequestChannel > > > Key: KAFKA-2959 > URL: https://issues.apache.org/jira/browse/KAFKA-2959 > Project: Kafka > Issue Type: Sub-task >Reporter: Grant Henke >Assignee: Jakub Nowak > > Once the old Request & Response objects are no longer used we can delete the > legacy mapping maintained in RequestChannel.scala -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KAFKA-2870) Support configuring operationRetryTimeout of underlying ZkClient through ZkUtils constructor
[
https://issues.apache.org/jira/browse/KAFKA-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Nowak reassigned KAFKA-2870:
--
Assignee: Jakub Nowak
> Support configuring operationRetryTimeout of underlying ZkClient through
> ZkUtils constructor
>
>
> Key: KAFKA-2870
> URL: https://issues.apache.org/jira/browse/KAFKA-2870
> Project: Kafka
> Issue Type: Improvement
>Affects Versions: 0.9.0.0
>Reporter: Stevo Slavic
>Assignee: Jakub Nowak
>Priority: Minor
>
> Currently (Kafka 0.9.0.0 RC3) it's not possible to have underlying
> {{ZkClient}} {{operationRetryTimeout}} configured and use Kafka's
> {{ZKStringSerializer}} in {{ZkUtils}} instance.
> Please support configuring {{operationRetryTimeout}} via another
> {{ZkUtils.apply}} factory method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KAFKA-2870) Support configuring operationRetryTimeout of underlying ZkClient through ZkUtils constructor
[
https://issues.apache.org/jira/browse/KAFKA-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Nowak updated KAFKA-2870:
---
Status: Patch Available (was: Open)
> Support configuring operationRetryTimeout of underlying ZkClient through
> ZkUtils constructor
>
>
> Key: KAFKA-2870
> URL: https://issues.apache.org/jira/browse/KAFKA-2870
> Project: Kafka
> Issue Type: Improvement
>Affects Versions: 0.9.0.0
>Reporter: Stevo Slavic
>Assignee: Jakub Nowak
>Priority: Minor
>
> Currently (Kafka 0.9.0.0 RC3) it's not possible to have underlying
> {{ZkClient}} {{operationRetryTimeout}} configured and use Kafka's
> {{ZKStringSerializer}} in {{ZkUtils}} instance.
> Please support configuring {{operationRetryTimeout}} via another
> {{ZkUtils.apply}} factory method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KAFKA-2690) Protect passwords from logging
[ https://issues.apache.org/jira/browse/KAFKA-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Nowak updated KAFKA-2690: --- Status: Patch Available (was: In Progress) > Protect passwords from logging > -- > > Key: KAFKA-2690 > URL: https://issues.apache.org/jira/browse/KAFKA-2690 > Project: Kafka > Issue Type: Sub-task > Components: security >Reporter: Ismael Juma >Assignee: Jakub Nowak > Fix For: 0.9.0.0 > > > We currently store the key (ssl.key.password), keystore > (ssl.keystore.password) and truststore (ssl.truststore.password) passwords as > a String in `KafkaConfig`, `ConsumerConfig` and `ProducerConfig`. > The problem with this approach is that we may accidentally log the password > when logging the config. > A possible solution is to introduce a new `ConfigDef.Type` that overrides > `toString` so that the value is hidden. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-2690) Protect passwords from logging
[ https://issues.apache.org/jira/browse/KAFKA-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Nowak updated KAFKA-2690: --- Status: Patch Available (was: Open) > Protect passwords from logging > -- > > Key: KAFKA-2690 > URL: https://issues.apache.org/jira/browse/KAFKA-2690 > Project: Kafka > Issue Type: Sub-task > Components: security >Reporter: Ismael Juma >Assignee: Jakub Nowak > Fix For: 0.9.0.0 > > > We currently store the key (ssl.key.password), keystore > (ssl.keystore.password) and truststore (ssl.truststore.password) passwords as > a String in `KafkaConfig`, `ConsumerConfig` and `ProducerConfig`. > The problem with this approach is that we may accidentally log the password > when logging the config. > A possible solution is to introduce a new `ConfigDef.Type` that overrides > `toString` so that the value is hidden. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-2690) Protect passwords from logging
[ https://issues.apache.org/jira/browse/KAFKA-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Nowak updated KAFKA-2690: --- Status: In Progress (was: Patch Available) > Protect passwords from logging > -- > > Key: KAFKA-2690 > URL: https://issues.apache.org/jira/browse/KAFKA-2690 > Project: Kafka > Issue Type: Sub-task > Components: security >Reporter: Ismael Juma >Assignee: Jakub Nowak > Fix For: 0.9.0.0 > > > We currently store the key (ssl.key.password), keystore > (ssl.keystore.password) and truststore (ssl.truststore.password) passwords as > a String in `KafkaConfig`, `ConsumerConfig` and `ProducerConfig`. > The problem with this approach is that we may accidentally log the password > when logging the config. > A possible solution is to introduce a new `ConfigDef.Type` that overrides > `toString` so that the value is hidden. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KAFKA-2690) Protect passwords from logging
[ https://issues.apache.org/jira/browse/KAFKA-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Nowak reassigned KAFKA-2690: -- Assignee: Jakub Nowak > Protect passwords from logging > -- > > Key: KAFKA-2690 > URL: https://issues.apache.org/jira/browse/KAFKA-2690 > Project: Kafka > Issue Type: Sub-task > Components: security >Reporter: Ismael Juma >Assignee: Jakub Nowak > Fix For: 0.9.0.0 > > > We currently store the key (ssl.key.password), keystore > (ssl.keystore.password) and truststore (ssl.truststore.password) passwords as > a String in `KafkaConfig`, `ConsumerConfig` and `ProducerConfig`. > The problem with this approach is that we may accidentally log the password > when logging the config. > A possible solution is to introduce a new `ConfigDef.Type` that overrides > `toString` so that the value is hidden. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KAFKA-2617) Move protocol field default values to Protocol
[ https://issues.apache.org/jira/browse/KAFKA-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Nowak reassigned KAFKA-2617: -- Assignee: Jakub Nowak > Move protocol field default values to Protocol > -- > > Key: KAFKA-2617 > URL: https://issues.apache.org/jira/browse/KAFKA-2617 > Project: Kafka > Issue Type: Bug >Reporter: Guozhang Wang >Assignee: Jakub Nowak > Labels: newbie > Fix For: 0.9.0.0 > > > Right now the default values are scattered in the Request / Response classes, > and some duplicates already exists like JoinGroupRequest.UNKNOWN_CONSUMER_ID > and OffsetCommitRequest.DEFAULT_CONSUMER_ID. We would like to move all > default values into org.apache.kafka.common.protocol.Protocol since > org.apache.kafka.common.requests depends on org.apache.kafka.common.protocol > anyways. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-2617) Move protocol field default values to Protocol
[ https://issues.apache.org/jira/browse/KAFKA-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Nowak updated KAFKA-2617: --- Status: Patch Available (was: In Progress) > Move protocol field default values to Protocol > -- > > Key: KAFKA-2617 > URL: https://issues.apache.org/jira/browse/KAFKA-2617 > Project: Kafka > Issue Type: Bug >Reporter: Guozhang Wang >Assignee: Jakub Nowak > Labels: newbie > Fix For: 0.9.0.0 > > > Right now the default values are scattered in the Request / Response classes, > and some duplicates already exists like JoinGroupRequest.UNKNOWN_CONSUMER_ID > and OffsetCommitRequest.DEFAULT_CONSUMER_ID. We would like to move all > default values into org.apache.kafka.common.protocol.Protocol since > org.apache.kafka.common.requests depends on org.apache.kafka.common.protocol > anyways. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KAFKA-2617) Move protocol field default values to Protocol
[ https://issues.apache.org/jira/browse/KAFKA-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-2617 started by Jakub Nowak. -- > Move protocol field default values to Protocol > -- > > Key: KAFKA-2617 > URL: https://issues.apache.org/jira/browse/KAFKA-2617 > Project: Kafka > Issue Type: Bug >Reporter: Guozhang Wang >Assignee: Jakub Nowak > Labels: newbie > Fix For: 0.9.0.0 > > > Right now the default values are scattered in the Request / Response classes, > and some duplicates already exists like JoinGroupRequest.UNKNOWN_CONSUMER_ID > and OffsetCommitRequest.DEFAULT_CONSUMER_ID. We would like to move all > default values into org.apache.kafka.common.protocol.Protocol since > org.apache.kafka.common.requests depends on org.apache.kafka.common.protocol > anyways. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
