[jira] [Updated] (KAFKA-2593) KeyValueStores should not require use of the context's default serializers and deserializers
[
https://issues.apache.org/jira/browse/KAFKA-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-2593:
---
Affects Version/s: 0.10.0.0
> KeyValueStores should not require use of the context's default serializers
> and deserializers
>
>
> Key: KAFKA-2593
> URL: https://issues.apache.org/jira/browse/KAFKA-2593
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
>Affects Versions: 0.10.0.0
>Reporter: Randall Hauch
>Assignee: Randall Hauch
> Fix For: 0.10.0.0
>
>
> Currently the {{InMemoryKeyValueStore}} is only able to use the key and value
> serializers and deserializers (aka, "serdes") from the {{ProcessingContext}}.
> This means that a {{Processor}} implementation that wants to use the
> {{InMemoryKeyValueStore}} can only do this if the key and value types match
> those set up as the default serdes in the topology's configuration.
> Additionally, the {{RocksDBKeyValueStore}} is only capable of {{byte[]}} keys
> and values.
> Both of these key-value stores should allow the component using them to
> specify the serdes for both the keys and values. As a convenience, the
> current behavior should still be supported, as should a way to infer the
> serdes for the "built-in" serializers and deserializers (e.g., strings,
> integers, longs, and byte arrays).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KAFKA-2593) KeyValueStores should not require use of the context's default serializers and deserializers
[
https://issues.apache.org/jira/browse/KAFKA-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-2593:
-
Fix Version/s: (was: 0.9.0.0)
0.9.1.0
> KeyValueStores should not require use of the context's default serializers
> and deserializers
>
>
> Key: KAFKA-2593
> URL: https://issues.apache.org/jira/browse/KAFKA-2593
> Project: Kafka
> Issue Type: Sub-task
> Components: kafka streams
>Reporter: Randall Hauch
>Assignee: Randall Hauch
> Fix For: 0.9.1.0
>
>
> Currently the {{InMemoryKeyValueStore}} is only able to use the key and value
> serializers and deserializers (aka, "serdes") from the {{ProcessingContext}}.
> This means that a {{Processor}} implementation that wants to use the
> {{InMemoryKeyValueStore}} can only do this if the key and value types match
> those set up as the default serdes in the topology's configuration.
> Additionally, the {{RocksDBKeyValueStore}} is only capable of {{byte[]}} keys
> and values.
> Both of these key-value stores should allow the component using them to
> specify the serdes for both the keys and values. As a convenience, the
> current behavior should still be supported, as should a way to infer the
> serdes for the "built-in" serializers and deserializers (e.g., strings,
> integers, longs, and byte arrays).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KAFKA-2593) KeyValueStores should not require use of the context's default serializers and deserializers
[
https://issues.apache.org/jira/browse/KAFKA-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-2593:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 255
[https://github.com/apache/kafka/pull/255]
> KeyValueStores should not require use of the context's default serializers
> and deserializers
>
>
> Key: KAFKA-2593
> URL: https://issues.apache.org/jira/browse/KAFKA-2593
> Project: Kafka
> Issue Type: Sub-task
> Components: kafka streams
>Reporter: Randall Hauch
>Assignee: Randall Hauch
> Fix For: 0.9.0.0
>
>
> Currently the {{InMemoryKeyValueStore}} is only able to use the key and value
> serializers and deserializers (aka, "serdes") from the {{ProcessingContext}}.
> This means that a {{Processor}} implementation that wants to use the
> {{InMemoryKeyValueStore}} can only do this if the key and value types match
> those set up as the default serdes in the topology's configuration.
> Additionally, the {{RocksDBKeyValueStore}} is only capable of {{byte[]}} keys
> and values.
> Both of these key-value stores should allow the component using them to
> specify the serdes for both the keys and values. As a convenience, the
> current behavior should still be supported, as should a way to infer the
> serdes for the "built-in" serializers and deserializers (e.g., strings,
> integers, longs, and byte arrays).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KAFKA-2593) KeyValueStores should not require use of the context's default serializers and deserializers
[
https://issues.apache.org/jira/browse/KAFKA-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Hauch updated KAFKA-2593:
-
Status: Patch Available (was: Open)
This contribution is ready for review.
> KeyValueStores should not require use of the context's default serializers
> and deserializers
>
>
> Key: KAFKA-2593
> URL: https://issues.apache.org/jira/browse/KAFKA-2593
> Project: Kafka
> Issue Type: Sub-task
> Components: kafka streams
>Reporter: Randall Hauch
>Assignee: Randall Hauch
> Fix For: 0.9.0.0
>
>
> Currently the {{InMemoryKeyValueStore}} is only able to use the key and value
> serializers and deserializers (aka, "serdes") from the {{ProcessingContext}}.
> This means that a {{Processor}} implementation that wants to use the
> {{InMemoryKeyValueStore}} can only do this if the key and value types match
> those set up as the default serdes in the topology's configuration.
> Additionally, the {{RocksDBKeyValueStore}} is only capable of {{byte[]}} keys
> and values.
> Both of these key-value stores should allow the component using them to
> specify the serdes for both the keys and values. As a convenience, the
> current behavior should still be supported, as should a way to infer the
> serdes for the "built-in" serializers and deserializers (e.g., strings,
> integers, longs, and byte arrays).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
