hasura / hasura/graphql-engine
support: naming convention feature for snowflake source
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
### Is your proposal related to a problem?
As per current implementation, naming convention feature is only supported for postgres source. Acc to this [doc](https://hasura.io/docs/latest/schema/postgres/naming-convention/#introduction),
> Naming conventions are only available on Postgres sources.
### Describe the solution you'd like
This feature request is aimed towards exploring possibility for implementing naming convention feature for snowflake source particularly.
### Workaround
You can set custom field name for table at root level , query level and mutation level. This is a bit tedious approach as you'll need to go and set it manually by visiting every "tracked" table under snowflake database.
Console -> Database -> Schema -> Table -> Modify -> Custom Field names. For reference, see the screenshot below.
Contributor guide
Research direction
Start by locating the existing Postgres naming-convention implementation and the Snowflake source integration. Define the supported naming-convention behavior for Snowflake and its completion criteria before identifying the affected code and tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100