Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B454B9C3D for ; Sat, 13 Dec 2014 11:15:13 +0000 (UTC) Received: (qmail 79929 invoked by uid 500); 13 Dec 2014 11:15:13 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 79888 invoked by uid 500); 13 Dec 2014 11:15:13 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 79876 invoked by uid 99); 13 Dec 2014 11:15:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Dec 2014 11:15:13 +0000 Date: Sat, 13 Dec 2014 11:15:13 +0000 (UTC) From: "Robert Stupp (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-7708) UDF schema change events/results MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14245283#comment-14245283 ] Robert Stupp commented on CASSANDRA-7708: ----------------------------------------- Makes sense. And the first point is one step towards CASSANDRA-6717 (removing {{AbstractType}}). > 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)