[ 
https://issues.apache.org/jira/browse/CASSANDRA-18037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andres de la Peña updated CASSANDRA-18037:
------------------------------------------
    Test and Documentation Plan: 
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/2236]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/2721/workflows/ec2cb321-5cea-4364-9ba7-3048c19ae706]
 
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/2721/workflows/1513002f-d37e-49a4-9ef7-c76b77ecab84]|
|[dtest|https://github.com/apache/cassandra-dtest/pull/217]||
                         Status: Patch Available  (was: In Progress)

> Use snake case for the names CQL native functions
> -------------------------------------------------
>
>                 Key: CASSANDRA-18037
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18037
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL/Syntax
>            Reporter: Andres de la Peña
>            Assignee: Andres de la Peña
>            Priority: Normal
>
> Most native functions are named all lower case, without underscore nor
> hyphen to separate words. That's the case, for example, of "intasblob" or
> "blobasint".
> We also have some functions using camel case, as in "castAsInt" or
> "castAsTimestamp". Note that the came cased names require quoting due to
> CQL's case insensitivity.
> Differently to CQL native functions, system keyspaces, tables and columns
> consistently use snake case. For example, we have "system_schema",
> "dropped_columns", "default_time_to_live".
> As discussed in [this 
> thread|https://lists.apache.org/thread/k9ml1k4fg6o7mfby1nr3y0mnq9r90dym], we 
> should adopt snake_case for CQL native function names. Also we should provide 
> aliases for the current function names, so we don't break compatibility.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to