-
Notifications
You must be signed in to change notification settings - Fork 537
HDDS-11746. Support arbitrary schemas as an option in ozone debug ldb. #7652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from 5 commits
a890c9c
8e43cec
55f8ab3
c05126b
91d1dab
b4c8949
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -43,11 +43,19 @@ public class RDBParser implements DebugSubcommand { | |
description = "Database File Path") | ||
private String dbPath; | ||
|
||
@CommandLine.Option(names = {"--schema"}, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Instead of taking a schema, I would rather take an input of codec to decode the value of a column family. For instance if I want to read snapshot diff DB, the DB doesn't have DB definition since we create new column families on the fly based on the snapdiff job. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We should open a rocksdb in read only mode and decode value based on the ValueCodec There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This seems like a good approach. Currently we don't have any operations that work on multiple column families so just one key and value codec will suffice for each operation. Codec interface should be lighter weight than DBDefinitions if we need to make new ones on the fly for some reason as well. |
||
description = "DBDefinition of the database") | ||
private String dbDefinition; | ||
|
||
public String getDbPath() { | ||
return dbPath; | ||
} | ||
|
||
public void setDbPath(String dbPath) { | ||
this.dbPath = dbPath; | ||
} | ||
|
||
public String getDbDefinition() { | ||
return dbDefinition; | ||
} | ||
} |
Uh oh!
There was an error while loading. Please reload this page.