The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

It looks like a version &gt;1.1.8 of `dagster` removed/moved `dagster.__core.storage.db__io_manager.TablePartition` . Is there way to find out what it should be replaced with?

it was replaced with `TablePartitionDimension` . the purpose of this change was to allow DB IO managers to handle multiple-dimensional partitions

fyi <@U030M2AL48M>

Poked around a bit in the new version but am unable to understand how to convert the following

Untitled.py

This is so we are able to delete a partition before its replacement is run, but accessing the time-window for the multi-dimensional partitions is throwing me off

hey <@U04HW1B0MPX> with the change to `TablePartitionDimension` we now store a list of `TablePartitionDimension`s as the `partition_dimensions` attr of the `TableSlice` object. so you may need to iterate through that attr to access the `partition_expr` for each dimension

would also love to know how you’re using all of these db io manager concepts, i wasn’t expecting community use of them yet so it’d be great to know more about what you’re up to!

<@U030M2AL48M> Noah’s colleague here!  We implemented a Big Query IO manager based on the Snowflake IO manager.

Although, I saw that you just made changes to the official BigQuery IO manager - will check it out!

:clap:

oh nice! it’d be awesome to get any feedback you have on the built in one based on your experience building your own