[
https://issues.apache.org/jira/browse/SAMZA-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389391#comment-14389391
]
Chris Riccomini commented on SAMZA-598:
---------------------------------------
Cool! If you want we can blow this out into two subtasks (listed above), and
focus on the changelog restoration version of the tool first. The 3.9.1 RocksDB
release was built against JDK8, so we can't pull that in. I checked with the FB
folks a week or two ago, and they said that they were about to ship the next
release. If it takes too long, we can always do a re-build release of 3.9.1
built against JDK6, so we can suck that in. I have access to do RocksDB JNI
builds and Maven releases, and so does [~naveenatceg].
> 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
> Assignee: Yan Fang
> 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)
