Improve fwdctl dump

[rkuris]

Right now, the dump command only takes a database name. It would be easy to add options now:

• output formats json and/or csv (these would need to be streaming for large databases)
• specific starting key
• specific stop key
• maximum number of keys
• if we stopped, have an option to render the next key for resuming

Some of these stream limits are already implemented for range proofs, so you can use the code there as a template of how to stop iterating.

(depends on #347)

[rkuris]

import from json (or any format) would also be amazing

[sergerad]

@rkuris are there any unit or integration tests that cover the relevant flow here to help get my head around the stack? Or perhaps the examples/insert.rs might be relevant to look at? Thanks.

[zdf1230]

@rkuris Hi Ron, I am trying to work on this change and have a question regarding to "if we stopped, have an option to render the next key for resuming".

1. Does the stopping here mean interrupt in the middle / crush or it reached the stopped key or max number of keys?
2. Is storing a temporary file locally a good approach to resume? or do you have any ideas in mind?

Thanks!

[rkuris]

Let's say you have keys A to Z and ask for a limit of 10 keys. In that case, it would be nice if it told you that you can get the next set by starting at K (the 11th key). I imagine the output could look like this: A B ... J Next key is K, resume with "--start-key=K"

…

On Mon, Dec 16, 2024, 9:28 PM zdf ***@***.***> wrote: @rkuris <https://github.com/rkuris> Hi Ron, I am trying to work on this change and have a question regarding to "if we stopped, have an option to render the next key for resuming". 1. Does the stopping here mean interrupt in the middle / crush or it reached the stopped key or max number of keys? 2. Is storing a temporary file locally a good approach to resume? or do you have any ideas in mind? Thanks! — Reply to this email directly, view it on GitHub <#348 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYLR3FBOLLEWZQOLRSKT3D2F6Y7RAVCNFSM6AAAAABSGKBPZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBXGUZTQMRYGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[zdf1230]

Let's say you have keys A to Z and ask for a limit of 10 keys. In that

case, it would be nice if it told you that you can get the next set by

starting at K (the 11th key). I imagine the output could look like this:

A

B

...

J

Next key is K, resume with "--start-key=K"

On Mon, Dec 16, 2024, 9:28 PM zdf @.***> wrote:

@rkuris https://github.com/rkuris Hi Ron, I am trying to work on this

change and have a question regarding to "if we stopped, have an option to

render the next key for resuming".

1. Does the stopping here mean interrupt in the middle / crush or it

reached the stopped key or max number of keys?

2. Is storing a temporary file locally a good approach to resume? or

do you have any ideas in mind?

Thanks!

—

Reply to this email directly, view it on GitHub

#348 (comment),

or unsubscribe

https://github.com/notifications/unsubscribe-auth/AAYLR3FBOLLEWZQOLRSKT3D2F6Y7RAVCNFSM6AAAAABSGKBPZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBXGUZTQMRYGI

.

You are receiving this because you were mentioned.Message ID:

@.***>

Got it. Thanks for the explanation!