You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Hai Lu (Jira)" <ji...@apache.org> on 2019/11/07 00:06:04 UTC
[jira] [Updated] (SAMZA-2318) Empty config values from coordinator
stream shouldn't be filtered
[ https://issues.apache.org/jira/browse/SAMZA-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hai Lu updated SAMZA-2318:
--------------------------
Fix Version/s: 1.3
> Empty config values from coordinator stream shouldn't be filtered
> -----------------------------------------------------------------
>
> Key: SAMZA-2318
> URL: https://issues.apache.org/jira/browse/SAMZA-2318
> Project: Samza
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Dengpan Yin
> Assignee: Dengpan Yin
> Priority: Major
> Fix For: 1.3
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> In the previous PR: [https://github.com/apache/samza/pull/1010/files]
> config with null/empty values will be filter out when reading the coordinator stream, this will cause some problems when the user expects an empty string to be a value config.
>
> Some user may expect configs with null value to be valid as well, we will not fix this part for now since when reading from coordinator stream, the job runner can't differentiate the null value generated from delete or update.
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)