hasura / hasura/graphql-engine
Uploading metadata to hdb_catalog.hdb_metadata instead of using API
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
### Version Information
Server Version: v2.37.1
### Environment
OSS
### What is the current behaviour?
When uploading metadata and reloading it through the Hasura API, the process is slow.
### Question
Could you provide insights on whether directly updating the **hdb_catalog.hdb_metadata** table and triggering a metadata reload is a recommended and safe practice? If not, are there alternative approaches to improve the performance of metadata upload and reload operations?
Contributor guide
Research direction
Start by reviewing the Hasura API metadata upload and reload flow described in the issue, along with the hdb_catalog.hdb_metadata table. Determine whether direct table updates are supported and identify the documented or implementable alternatives for improving upload and reload performance; done means the safe approach and its performance implications are clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, postgres
- Domain
- api, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100