Allow unknown function calls to specify an expression type #1618
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds new syntax:
function_name!number!measure(...)
to mark that the function should be treated as an aggregate expression, including handling distinct keys for joinsjoin1.join2.function_name!number!measure(...)
join1.join2.field1.function_name!number!measure(...)
field1.function_name!number!measure(...)
function_name!number!calculation(...)
to mark that the function should be treated as an analytic function, including adding anOVER (...)
clause afterward, and support for{ partition_by: ..., order_by: ... }
function_name!number!dimension(...)
is the same asfunction_name!number(...)
but more explicitThis all requires the
##! experimental.unknown_function_expression_types
experiment to be enabled.