[
https://issues.apache.org/jira/browse/KAFKA-4613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833586#comment-15833586
]
ASF GitHub Bot commented on KAFKA-4613:
---------------------------------------
GitHub user jeyhunkarimov opened a pull request:
https://github.com/apache/kafka/pull/2420
KAFKA-4613: Treat null-key records the same way for joins and aggreations
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jeyhunkarimov/kafka KAFKA-4613
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2420.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2420
----
commit 70c23d0d77d9a3e863d6a16cce632fe23ced1a6c
Author: Jeyhun Karimov <je.kari...@gmail.com>
Date: 2017-01-22T16:35:54Z
KAFKA-4613: Treat null-key records the same way for joins and aggreations
----
> Treat null-key records the same way for joins and aggreations
> -------------------------------------------------------------
>
> Key: KAFKA-4613
> URL: https://issues.apache.org/jira/browse/KAFKA-4613
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
>
> Currently, on aggregation records with null-key get dropped while for joins
> we raise an exception.
> We might want to drop in both cases of raise an exception in both cases to be
> consistent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
