hasura / hasura/graphql-engine
No change database capture (CDC) on Hasura Cloud
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
Cannot see the database change capture (CDC) in hdb_catalog when applying migration on Hasura Cloud, but works fine on local Hasura deployment.
On Hasura Cloud hdb_catalog has the following tables after 1 migration = [event_log, event_invocations_log, hdb_source_catalog_version]
On local deployment, hdb_catalog has many tables after 1 migration, including hdb_version which contains migration info.
Any ideas?
Contributor guide
Research direction
The report focuses on the hdb_catalog schema after one migration in Hasura Cloud versus a local Hasura deployment; start by reproducing and comparing those database schemas. Done means determining whether the missing migration metadata is an expected Cloud limitation or a defect, with the behavior and reproduction details documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, postgres
- Domain
- api, backend, cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100