bakingbad-hicdex-metadata-indexer-1 | 2022-06-30 18:58:55 INF Waiting database is up and runnning
bakingbad-hicdex-metadata-indexer-1 | 2022-06-30 18:58:55 ERR [0 ms] ERROR #42P16 cannot change name of view column "name" to "index_name" : CREATE OR REPLACE VIEW dipdup_head_status AS
bakingbad-hicdex-metadata-indexer-1 | SELECT
bakingbad-hicdex-metadata-indexer-1 | index_name,
bakingbad-hicdex-metadata-indexer-1 | CASE
bakingbad-hicdex-metadata-indexer-1 | WHEN timestamp < NOW() - interval '3 minutes' THEN 'OUTDATED'
bakingbad-hicdex-metadata-indexer-1 | ELSE 'OK'
bakingbad-hicdex-metadata-indexer-1 | END AS status,
bakingbad-hicdex-metadata-indexer-1 | created_at,
bakingbad-hicdex-metadata-indexer-1 | updated_at
bakingbad-hicdex-metadata-indexer-1 | FROM
bakingbad-hicdex-metadata-indexer-1 | dipdup_state;
bakingbad-hicdex-metadata-indexer-1 |
bakingbad-hicdex-metadata-indexer-1 | 2022-06-30 18:58:55 ERR createViews error="ERROR #42P16 cannot change name of view column \"name\" to \"index_name\""
A workaround by 852Kerfunkle:
rename the metadata indexer head status view (as you've already done)
run hasura with a separate metadata database
create three databases in the same postgres instance: hasura-metadata, hixdex, metadata-indexer
set both dipdup and the metadata indexer to create_source/add_source = true and set the correct source name for each
in the metadata indexer (or dipdup, but dipdup doesn't support it yet), create custom hasura configs that set up (remote schema) relations between the dipdup db and the midx db
figure out a way to stop dipdup from overwriting the metadata when it restarts (because the hash will change)
also, you probably want to make sure they aren't messing with each others hasura metadata on startup - I chose to delay the metadata indexer by a minute (edited)
A workaround by 852Kerfunkle: