[
https://issues.apache.org/jira/browse/SAMZA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961499#comment-14961499
]
Navina Ramesh commented on SAMZA-626:
-------------------------------------
Ok. I figured it out.
When I was testing, there was no SST file on the disk. The data was not yet
flushed to the disk and it was all in memory. Since memtable cannot be accessed
from outside the process that owns the memory, the read fails on keys that are
in memory and not on disk.
I verified this by persisting the local state and restarting the job. After
that I was able to read using the tool. So, I guess the tool works. The users
need to be aware of this scenario. We need to explicitly call it out in the
document. I will update the patch and put it up again. Thanks!
> Read KV state store for a running job
> -------------------------------------
>
> Key: SAMZA-626
> URL: https://issues.apache.org/jira/browse/SAMZA-626
> Project: Samza
> Issue Type: Sub-task
> Components: kv
> Affects Versions: 0.10.0
> Reporter: Yan Fang
> Assignee: Yan Fang
> Fix For: 0.10.0
>
> Attachments: SAMZA-626.2.patch
>
>
> Provide the tool to connect to kv state store and read the content of the
> store.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
