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] [Updated] (CASSANDRA-11466) Add Dynamic Type to the Native Protocol
Date Thu, 31 Mar 2016 16:20:25 GMT

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

Aleksey Yeschenko updated CASSANDRA-11466:
------------------------------------------
    Issue Type: Sub-task  (was: Improvement)
        Parent: CASSANDRA-9362

> Add Dynamic Type to the Native Protocol
> ---------------------------------------
>
>                 Key: CASSANDRA-11466
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11466
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: CQL
>            Reporter: Tyler Hobbs
>              Labels: client-impacting, doc-impacting
>
> There are several cases where the native protocol limits our ability to support functions
due to argument or result types that are only known at execution time.  For example, we can't
support {{fromJson()}} in the selection clause or {{toJson()}} outside of the selection clause.
> To support these functions and other use cases, we should add a dynamic type to the native
protocol.  The serialization format for this would be a {{<type>}} field (i.e. a numeric
typecode, as defined in the native protocol spec) followed by the serialized value.  When
deserializing values, drivers would first read the typecode to determine the type, then decode
the remainder of the bytes accordingly.  How this type information is exposed to the end user
is up to the driver authors.



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

Mime
View raw message