Diagnostic Misses Database Renaming

[rmbeddor14]

Describe the bug

• if you rename a database, the diagnostic will still use the old name
• this makes troubleshooting very difficult and confusing
  Contact Rachel for Customer Name

Thanks!!

Error message/log

To Reproduce

create a workload

• change the database name
• create more MVs with the new database name
• download the diagnostic
• you will notice the diagnostic shows the old name for MVs created before the name change

Expected behavior

I would expect diagnostic to be a reflection of the current workload - if the MVs are in a renamed db, I would expect them to be listed that way even if they were created before the renaming

How did you deploy RisingWave?

contact rachel for customer name to learn deployment detail

The version of RisingWave

They have the following versions and both show this behavior:
2.8.2
2.7.2

Additional context

No response

[hzxa21]

if the MVs are in a renamed db, I would expect them to be listed that way even if they were created before the renaming

@rmbeddor14 which section in the diagnose report are you referring to? The "STREAMING JOB" section lists database_id instead of database_name so renaming won't affect it. Are you referring to the "DATABASE" section, which will show the mapping between database id and the database name?