You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2015/03/13 02:42:38 UTC
[jira] [Commented] (SAMZA-598) Provide a tool to debug state stores
[ https://issues.apache.org/jira/browse/SAMZA-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359766#comment-14359766 ]
Chris Riccomini commented on SAMZA-598:
---------------------------------------
Should probably look similar to CheckpointTool, in terms of implementation, and CLI usage.
> Provide a tool to debug state stores
> ------------------------------------
>
> Key: SAMZA-598
> URL: https://issues.apache.org/jira/browse/SAMZA-598
> Project: Samza
> Issue Type: Bug
> Components: kv
> Affects Versions: 0.9.0
> Reporter: Chris Riccomini
> Fix For: 0.10.0
>
>
> There is currently no easy way to debug a Samza job when there are problems with the state store data. It would be nice to provide a tool that will:
> # Connect to a local KV state store, and dump its content.
> # Consume a changelog to and materialize a state store locally.
> Optionally, it would be nice to allow users to fetch values for a give key via a REPL. This is a little tricky, though, since the key might be serialized in Protobu, Avro, etc.
> Between 1-2, users will be able to inspect local stores of jobs that are running (1), and create a local copy of a state store for jobs that have lost their local state already (2).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)