[CASSANDRA-9665] Improve handling of UDF and UDA metadata

• Type: Sub-task
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0 alpha 1
• Assignee: Aleksey Yeschenko
• Reporter: Aleksey Yeschenko

Authors

Aleksey Yeschenko

Reviewers

Robert Stupp

• Created: 26/Jun/15 22:03
• Updated: 16/Apr/19 09:31
• Resolved: 30/Jun/15 12:05

Description

A while ago we decided to make all functions and types keyspace local, but haven't updated our assumption in the code accordingly.

One consequence is that in addition to Schema and KSMetaData we got ourselves a completely separate registry singleton for built-in functions, UDFs, and UDAs - the Functions class.

The linked branch makes UDAs and UDFs be a part of KSMetaData, as they should be, and gets rid of the old Functions class.

A new Functions class is introduced - an immutable container for a given keyspace's functions, and all the definitions are now spread between the keyspaces.

Additionally, this moves all the built-in functions to SystemKeyspace. This sneaks in a bit of CASSANDRA-9425, makes CASSANDRA-9367 easier, and is a minore pre-requisite for a proper implementation of CASSANDRA-6717.

Issue Links

• is part of: CASSANDRA-9425 Make node-local schema fully immutable
• links to: 9665 on GitHub