Couldn't check if table X exists, assuming it does

[CodeWithEmad]

Don't think this is normal. I get lots of warnings like this in the superset job.

Couldn't check if table course_overviews exists, assuming it does
2024-07-13 09:09:59,713:WARNING:superset.commands.dataset.importers.v1.utils:Couldn't check if table course_overviews exists, assuming it does
Couldn't check if table fact_instance_actors exists, assuming it does
2024-07-13 09:09:59,844:WARNING:superset.commands.dataset.importers.v1.utils:Couldn't check if table fact_instance_actors exists, assuming it does
Couldn't check if table fact_watched_video_segments_en exists, assuming it does
2024-07-13 09:10:01,041:WARNING:superset.commands.dataset.importers.v1.utils:Couldn't check if table fact_watched_video_segments_en exists, assuming it does
Couldn't check if table fact_at_risk_video_watches_uk exists, assuming it does
2024-07-13 09:10:01,732:WARNING:superset.commands.dataset.importers.v1.utils:Couldn't check if table fact_at_risk_video_watches_uk exists, assuming it does
Couldn't check if table fact_at_risk_watched_video_segments_tr_TR exists, assuming it does
2024-07-13 09:10:02,482:WARNING:superset.commands.dataset.importers.v1.utils:Couldn't check if table fact_at_risk_watched_video_segments_tr_TR exists, assuming it does
Couldn't check if table fact_problem_engagement_pt_BR exists, assuming it does
2024-07-13 09:10:03,030:WARNING:superset.commands.dataset.importers.v1.utils:Couldn't check if table fact_problem_engagement_pt_BR exists, assuming it does
Couldn't check if table fact_pageview_engagement_zh_CN exists, assuming it does

[bmtcril]

@CodeWithEmad this usually happens if MySQL isn't running when the job runs, or if init hasn't been run. Does this happen every time for you or is can you provide any other information about how it happened?

[CodeWithEmad]

Well, I can assure you that MySQL was up and running on an RDS instance.

Does this happen every time for you or can you provide ...

Well, I had an openedx instance with aspects v0.63.1 that I wanted to update to v1 but failed and mentioned it this slack post. tried to find a way to keep the data, but I removed the DBs and went with a clean install (no clickhouse and no MySQL). That was when I saw those warnings. I'll try to do it on a new org or reinstall it to see if anything happens or not.

[bmtcril]

I suppose more specifically this would happen when Superset can't connect to MySQL, I don't think we've tested running Superset against RDS so it's possible that there is a bug there. Depending on how much data you had it should be possible to rebuild the data on 1.0.x by dumping the event sinks and replaying the tracking logs (if they're still around). We can help out with that if you'd like.

If you end up trying to run Superset against RDS again and run into issues I'd love to hear about that and see what the Superset logs say.

[CodeWithEmad]

We can help out with that if you'd like.

Thank you for your kindness. I'll keep that in mind for the next time.

If you end up trying to run Superset against RDS again and run into issues I'd love to hear about that and see what the Superset logs say.

I have to set up aspects for another customer in the upcoming weeks. I will inform you about the results and will maintain the logs for any potential benefits. In the meantime, I close this one.