Description

During loading, If it is not necessary to judge based on --journalfile, handle it based on the existence of journalkv or journalfile;

• If trieJournal exists in the database, load it from the database first;
• If the journal file exists, load it from the journal file;
• If neither exists, treat it as a kv;

During persistence:
Handle it based on --journalfile, without considering whether it was journalkv or journalfile before;

Verification cases:

• Start and shut down using the kv method; Verify (type: journal kv);
• Start by specifying --journalfile to use journal file, and verify if it can start (type: journal kv), then shut down to save (type: journal file); Verify block tracking;
• Start using the kv method again (type: journal file); Verify block tracking; then shut down to save (type: journal kv); Verify block tracking again;
• Start by specifying --journalfile;

Rationale

tell us why we need these changes...

Example

add an example CLI or API response...

Changes

Notable changes:

• add each change in a bullet point here
• ...