Spencer Nelson
05/19/2023, 4:34 PMTable
. Details aren’t important - what matters is that dataframes and tables are not compatible.
So I have these old assets with keys like ztf_source_dataframe
, which are pandas dataframes. But I want to convert to `Table`s. Here are the options I see:
1. Reuse the ztf_source_dataframe
asset key, but return a non-dataframe type. Which is confusing, and will break dependents, which can possibly be managed with asset versioning in some way? But the name confusion would be unfortunate.
2. Write new ztf_source_table
asset, change dependents to use it, and then delete ztf_source_dataframe.
But this would destroy all history and orphan the materialized assets. Historical runs will be… broken? I don’t know what will happen to the dagit UI for them.
3. Write the new asset, but then keep ztf_source_dataframe
as relics of a bygone era. But they’ll clutter the UI and the codebase forever. Is there a way to mark assets as “archived” or “deprecated” or “just kept around in the attic?”
Gradual migrations like this are really important. I think Dagster could provide tools to manage this, and they could be fantastically better than anything else out there, since Dagster knows so much about my computation graph. I don’t have a concrete suggestion but think this is an important area for new features.Joel Olazagasti
05/19/2023, 4:45 PMAndras Somi
05/19/2023, 4:46 PMSpencer Nelson
05/19/2023, 4:51 PM