Hi Kai, Since the stored key and value in RocksDB are serialized bytes, it's not easy to read directly. You could consider to use State Processor API [1]. However, this needs you to know what the state name of the SQL operator. You could analysis the checkpoing _metadata [2] to know state names.
[1] https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/libs/state_processor_api/#state-processor-api [2] https://github.com/apache/flink/blob/0d2b945729df8f0a0149d02ca24633ae52a1ef21/flink-runtime/src/main/java/org/apache/flink/runtime/checkpoint/Checkpoints.java#L99 Best Yun Tang ________________________________ From: Kai Fu <zzfu...@gmail.com> Sent: Monday, August 9, 2021 13:01 To: user <user@flink.apache.org> Subject: Inspecting SST state of rocksdb Hi team, I'm trying to inspect SST files of flink's state with sst related tools like sst_dump, ldb in wiki<https://github.com/facebook/rocksdb/wiki/Administration-and-Data-Access-Tool>. But it seems I'm getting meaningless results as shown below. The tools I'm using are from RocksDB's trunk and built from source. Am I doing it the right way, or is there any alternative to inspect the state? We're aware of Flink's queryable state, while it seems not well supported for SQL generated operators. $ ./sst_dump --file=../db/000030.sst --command=scan --read_num=50 options.env is 0xba33e0 Process ../db/000030.sst Sst file format: block-based from [] to [] '� => '� => '� => '� => '� => '� => '� => '� => '� => '� => '� => -- Best wishes, - Kai
