Question: Is there a way to remap/restore the materialization history for an asset if the asset key changes? (perhaps by tinkering directly with the Dagster database)

this is also something I'm interested in, more specifically with Dagster Cloud. I've been told in the past that we can ask the Dagster team to remap assets / jobs for us, but obviously I don't think they'll be too enthused if I want to do this multiple times. Would be great to have a first-class solution for this so we don't have to try to get naming conventions right on the first try

Would like to 👍 this question. Additionally, if someone can point to the tables in the db and code paths in the dagster repo where materialization history might be constructed, we could at least form an understanding of the various components that go into constructing the output of the graphql query as rendered on Dagit.

yea this comes up pretty often… we do have this issue if yall want to add your thoughts