format: standardize an "escape hatch" for useful vendor-specific operations that can't be expressed in SQL
Open
Type: enhancement
- Dominant language
- C#
- Stars
- 627
- Forks
- 217
- Avg merge
- 22h 22m
- Merged PRs (30d)
- 64
Description
### What feature or improvement would you like to see?
There's at least one ad hoc version of this in the "HiveServer2" C# driver where we needed to make metadata requests that were not accessible through the normal SQL dialect and which did not fit into the then-current metadata contracts.
See https://github.com/adbc-drivers/bigquery/pull/279
Contributor guide
Research direction
Read the HiveServer2 C# driver example and the linked BigQuery PR #279 first, then compare them with the existing SQL dialect and metadata contracts. Done means a documented standard escape hatch can cover vendor-specific operations that do not fit those contracts without relying on an ad hoc mechanism.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend-api-design, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100