[jira] [Commented] (CASSANDRA-9367) Expose builtin-in CQL functions via schema data dictionary

["Aleksey Yeschenko (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550763#comment-14550763 ] 

Aleksey Yeschenko commented on CASSANDRA-9367:
----------------------------------------------

This is no different from the way we store {{system}} tables metadata itself in {{system.schema_*}}.

It only seems to be different b/c for some reason UDFs and UDAs definitions aren't currently part of {{KSMetaData}}. They should be.

I agree that virtual tables could help here, but there is nothing specific about functions and virtual tables. When we have CASSANDRA-7622 we'll just serve all our schema via virtual tables, no exception for functions.

> Expose builtin-in CQL functions via schema data dictionary
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-9367
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9367
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Michaël Figuière
>            Priority: Minor
>             Fix For: 3.x
>
>
> As CASSANDRA-6717 will not be part of Cassandra 2.2, my comment there got to be considered for the current {{system.schema_functions}} table, to avoid creating a special case just for 2.2:
> {quote}
> Builtin CQL functions are not described in the {{system}} keyspace in its current representation, this new schema should include them next to the user defined ones as:
> * The {{system}} keyspace and its tables are described in the {{system}} keyspace, therefore it would be consistent.
> * Having builtin CQL functions described there would allow external tools to manipulate all the functions in a similar way.
> * This would document the available builtin function for users that don't remember the ones available in their current version of Cassandra.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)