Cannot migrate from Supabase

Hi, I was trying to migrate from Supabase to the Appwrite database.

My database had around 190K columns. I tried it twice. Both times, after 2 days, the process got stuck on processing. I exceeded my Supabase egress bandwidth limit during those two days, and it was draining my usage like crazy.

On the Appwrite migration page, I see both migrations in the processing state, showing errors. Both are stuck on indexes, which are shown as pending and not processing.

Here is the report for one of them (both are the same).

I would really appreciate some help because this is unacceptable.

No support? disgusting, dishonour

cc @Arnab Chatterjee can you take a look? ^

@DogeGamer can you share me your projectid

Of course. Here: scoutlanguages

@Arnab Chatterjee

It was changed today to failed 'cause I deleted my database from Supabase

@DogeGamer I think 8000 rows get migrated right along with the database and 34 tables? but failed after that right?

Something like that, it was stucked on 8,8K rows, then it tried to migrate the indexes, which broke down the whole system, because every index was stuck on "pending" state. I resolved it by manually importing the data with scripts. But it is worth noting that it shouldn't drain the usage like crazy (on Supabase) or be stuck on "pending" when it is not doing anything. A cancel button would resolve this issue I believe.

@Chirag Aggarwal

cc @Arnab Chatterjee would be the best person to decide the actions here ^

yeah, I extracted the report
Seeming like after the 8.8 rows and dbs and 34tables, supabase just giving egress error and thats where things stuck
I mean egress usage part is highly dependent on the supabase api right 😅

I am finding the issue why it stuck on pending

Apparently something happened mid run and state failed didn't persist
and I think after that point the egress shouldn't get consumed at all

Yep, now it is not draining usage, but a little bug creating from 500MB database egress 14GB data : D