[
https://issues.apache.org/jira/browse/SAMZA-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Navina Ramesh updated SAMZA-982:
--------------------------------
Fix Version/s: 0.11.0
> Add null check for offset update in OffsetManager
> -------------------------------------------------
>
> Key: SAMZA-982
> URL: https://issues.apache.org/jira/browse/SAMZA-982
> Project: Samza
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Xinyu Liu
> Assignee: Xinyu Liu
> Priority: Blocker
> Fix For: 0.11.0
>
> Attachments: SAMZA-982.0.patch
>
>
> During the process of making offsetManager thread-safe, I changed the impl of
> lastProcessedOffsets to use ConcurrentHashMap. However, I didn't realize
> offset can be null so it will trigger null pointer exception when
> ConcurrentHashMap.put(key, null). The fix will add the null check so null
> offset will be still supported such as in our hello-samza example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
