[
https://issues.apache.org/jira/browse/CASSANDRA-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244955#comment-14244955
]
Tyler Hobbs commented on CASSANDRA-7708:
----------------------------------------
A few thoughts on this:
The use of {{signature}} as part of the PK in {{schema_functions}} and
{{schema_aggregates}} conflicts with the events here, because the drivers can't
really compute the signature from the data in the events. (Technically they
could, but it's not straightforward, and kind of strange.) Now that we have
frozen types, I think the {{signature}} column should be replaced with
{{argument_types frozen<list<text>>}} in both tables. This would allow drivers
to easily fetch the right row from the schema tables when these events occur.
Regardless of that, the return type doesn't help to uniquely identify a
function or aggregate, so I think we can omit it from events.
Last, it would be nice to make an {{AbstractMigrationListener}} class with
no-op default methods so that we can stop repeating those everywhere.
> UDF schema change events/results
> --------------------------------
>
> Key: CASSANDRA-7708
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7708
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Labels: protocolv4
> Fix For: 3.0
>
> Attachments: 7708-1.txt
>
>
> Schema change notifications for UDF might be interesting for client.
> This covers both - the result of {{CREATE}} + {{DROP}} statements and events.
> Just adding {{FUNCTION}} as a new target for these events breaks previous
> native protocol contract.
> Proposal is to introduce a new target {{FUNCTION}} in native protocol v4.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
