Skip to content

sql: make sure unimplemented CREATE FUNCTION options to have telemetry support #83964

@chengxiong-ruan

Description

@chengxiong-ruan

Is your feature request related to a problem? Please describe.
Currently there're a few option clauses of CREATE FUNCTION statement unimplemented, and we throw unimplemented error at the parser level. It's sufficient to block users from using them, but we also need to make sure we have telemetry support for this unsupported features so that we can tell which features are most wanted and prioritize our work.

The options of CREATE FUNCTION statement in question are:
EXTERNAL SECURITY DEFINER
EXTERNAL SECURITY INVOKER
SECURITY DEFINER
SECURITY INVOKER
COST numeric_only
ROWS numeric_only
SUPPORT name
SET
RESET
PARALLEL
TRANSFORM
WINDOW

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Jira issue: CRDB-17373
Epic: CRDB-3405

Metadata

Metadata

Labels

A-sql-udfC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)GA-blockerT-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)branch-release-22.2Used to mark GA and release blockers, technical advisories, and bugs for 22.2

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions