Expose the loaded_version and saved_version for AbstractVersionedDataSet
#1951
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Nok Chan [email protected]
Description
Related #1580
How current load version is determined when version=None?
Currently, this
load_version
information is buried deep down in the framework, and it is determined only when a dataset is loaded at runtime.The details of how "latest" version is in a method called
resolve_load_version
, which further calls_fetch_latest_load_version
kedro/kedro/io/core.py
Lines 558 to 564 in b2e59fa
How version is determined?
Development notes
Checklist
RELEASE.md
fileAlternatives
1st attempt - Add new attributes in
AbstractVersionedDataSet
It may not be a bad idea to add new attributes at all - we can update the
load_version
save_version
or theversion_cache
, but that way we also lost the initial input which makes things complicated.8fe0b1a
More Context