You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Adam Holmberg (JIRA)" <ji...@apache.org> on 2015/04/08 19:53:12 UTC
[jira] [Commented] (CASSANDRA-7660) Indicate PK columns in
"prepared" native protocol responses
[ https://issues.apache.org/jira/browse/CASSANDRA-7660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485643#comment-14485643 ]
Adam Holmberg commented on CASSANDRA-7660:
------------------------------------------
Sorry I missed the mention here earlier. Driver implementation lgtm. Merged on driver 3.0 branch [here|https://github.com/datastax/python-driver/tree/37677993faee7ec4c31da651cf67b13a7b34db03]
> Indicate PK columns in "prepared" native protocol responses
> -----------------------------------------------------------
>
> Key: CASSANDRA-7660
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7660
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: Tyler Hobbs
> Assignee: Tyler Hobbs
> Labels: client-impacting, protocolv4
> Fix For: 3.0
>
> Attachments: 7660-trunk-v2.txt, 7660-trunk.txt
>
>
> Currently, when native protocol drivers prepare statements, they need to check their internal representation of the schema to determine which, if any, of the columns are part of the partition key. If the native protocol response indicated this, it would remove the drivers' dependency on having an internal representation of the schema when preparing statements.
> This would need to go in the v4 protocol.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)