You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While this #21380 is most welcome addition, I think there is still an use case, which is missing but would be very useful.
The specific use case I have in mind is as follows:
Asset A (Hourly) -> Asset B (Daily). The default mapping behaviour for this is that for Asset B 2024-05-01 partition, partitions [2024-05-01-00:00...2024-05-01-23:00] in Asset A must be materialized.
I would like to be able to shift it by an hour so that for Asset B's partition, in this example 2024-05-01, partitions [2024-05-01-01:00...2024-05-02-00:00] in Asset A must be materialized.
So when currently the offsets in TimeWindowPartitionMapping are in the units of the downstream asset, it would be very good to have an option to have the offsets in the units of the upstream asset.
Ideas of implementation
No response
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
The text was updated successfully, but these errors were encountered:
What's the use case?
While this #21380 is most welcome addition, I think there is still an use case, which is missing but would be very useful.
The specific use case I have in mind is as follows:
Asset A (Hourly) -> Asset B (Daily). The default mapping behaviour for this is that for Asset B 2024-05-01 partition, partitions [2024-05-01-00:00...2024-05-01-23:00] in Asset A must be materialized.
I would like to be able to shift it by an hour so that for Asset B's partition, in this example 2024-05-01, partitions [2024-05-01-01:00...2024-05-02-00:00] in Asset A must be materialized.
So when currently the offsets in TimeWindowPartitionMapping are in the units of the downstream asset, it would be very good to have an option to have the offsets in the units of the upstream asset.
Ideas of implementation
No response
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
The text was updated successfully, but these errors were encountered: