Summary
Feedback from Dylan (STF) that this is an approach that they use to fetch the latest data as of a certain date. With the versions defaulting to timestamps, this should be pretty straightforward.
Considerations
This should be achieved by either using existing (kw)args or by adding new, optional kwargs. There are two optional architectures to do this. One is to include comparison operators to the version parsing (>, <, <=, >=) in the same way they are used in dependencies. This would make for far less programatic change. the other is to as an optional kwarg or two (version_gte, version_lte).
Sub-tasks
- Choose the ideal architecture
- Implement
- Test
Definition of Done
New functionality reviewed as PR and merged to main branh
Additional Notes
This could be a useful way of also retrieving multiple versions and, in the case of dataframes, concatenating them together
Summary
Feedback from Dylan (STF) that this is an approach that they use to fetch the latest data as of a certain date. With the versions defaulting to timestamps, this should be pretty straightforward.
Considerations
This should be achieved by either using existing (kw)args or by adding new, optional kwargs. There are two optional architectures to do this. One is to include comparison operators to the version parsing (
>,<,<=,>=) in the same way they are used in dependencies. This would make for far less programatic change. the other is to as an optional kwarg or two (version_gte,version_lte).Sub-tasks
Definition of Done
New functionality reviewed as PR and merged to main branh
Additional Notes
This could be a useful way of also retrieving multiple versions and, in the case of dataframes, concatenating them together