cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9233) Allow system variables to be retrieved and set via CQL
Date Fri, 24 Apr 2015 01:04:38 GMT

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

Aleksey Yeschenko commented on CASSANDRA-9233:
----------------------------------------------

This is actually very neat - both the code and how it works.

I wonder though if this should be built on virtual tables instead, with all the variables
in one table, and strictly typed (see CASSANDRA-7622).

> Allow system variables to be retrieved and set via CQL
> ------------------------------------------------------
>
>                 Key: CASSANDRA-9233
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9233
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jeff Jirsa
>            Assignee: Jeff Jirsa
>            Priority: Minor
>         Attachments: 9233.txt
>
>
> Other database systems allow system variables to be retrieved and set via their query
interface:
> https://dev.mysql.com/doc/refman/5.1/en/set-statement.html
> http://www.postgresql.org/docs/8.2/static/sql-set.html
> Proposing the following CQL syntax for retrieving variables:
> {{SHOW VARIABLES;}}
> {{SHOW VARIABLE 'variable';}}
> Proposing the following CQL syntax for setting variables:
> {{SET VARIABLE 'variable'='value' ;}}
> The output of {{SHOW VARIABLES;}} will be a superset of the actual values that can be
set with {{SET VARIABLE}}, as not all values are safe to change after starting the node. 



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

Mime
View raw message