Trying to think of a design pattern for this scenario:
• assets produced using a file system IO Manager -> writing to local disk for speed
• one all assets have materialized, some of these are then uploaded to a database -> but this would be triggered as a separate job
• Should each asset then have a second asset with a different IOManager (DB upload)?
• Then have a "define_asset_job" which just selects those assets that will be uploaded?