You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Chen Liang (JIRA)" <ji...@apache.org> on 2017/05/02 21:02:05 UTC
[jira] [Updated] (HDFS-11698) Ozone: SCM: CLI: Add Debug command
[ https://issues.apache.org/jira/browse/HDFS-11698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chen Liang updated HDFS-11698:
------------------------------
Attachment: HDFS-11698.001.patch
Post v001 patch. This patch adds basic structure for the convert. And only adds converting container.db to sqlite db file. Will file JIRAs for other levelDB file, which will be following the same code structure like in this one.
> Ozone: SCM: CLI: Add Debug command
> -----------------------------------
>
> Key: HDFS-11698
> URL: https://issues.apache.org/jira/browse/HDFS-11698
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Affects Versions: HDFS-7240
> Reporter: Anu Engineer
> Assignee: Chen Liang
> Attachments: HDFS-11698.001.patch
>
>
> This is not discussed as part of the standard command line set, since these are internal debug only commands.
> We have levelDB that stores key, value pairs and value is always binary blobs. These binary blobs can only be decoded using protobuf classes that are part of ozone.
> We would like to add an extension to SCM CLI which allows us to convert levelDB to SQLlite, since SQLlite would have structured data and standard SQL will work against it.
> The reason to use SQLlite instead of some dump file like json is the scale, it is possible that some levelDB files will have millions of keys, so having an SQL DB with proper index will make debugging much easier.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org