[jira] [Updated] (CASSGO-30) RowsResult metadata is not prioritized over the prepared metadata

["João Reis (Jira)" <ji...@apache.org>]

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

João Reis updated CASSGO-30:
----------------------------
    Reviewers: James Hartig, João Reis  (was: João Reis)

> RowsResult metadata is not prioritized over the prepared metadata
> -----------------------------------------------------------------
>
>                 Key: CASSGO-30
>                 URL: https://issues.apache.org/jira/browse/CASSGO-30
>             Project: Apache Cassandra Go driver
>          Issue Type: Bug
>          Components: Core
>            Reporter: João Reis
>            Priority: Normal
>             Fix For: 2.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> If the query was prepared with "SkipMetadata" then gocql will always use the metadata from the prepare response even if the RowsResult response has metadata.
> For example, in DSE Search, the server returns metadata that is different from the metadata on the prepare response: https://github.com/apache/cassandra-gocql-driver/issues/1689
> Also, in protocol v5, the rows response can have metadata if the result metadata id is different (e.g. a schema change happened).



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

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org