[ https://issues.apache.org/jira/browse/CASSGO-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912518#comment-17912518 ]
João Reis commented on CASSGO-40: --------------------------------- Well the next release will be 2.0.0 so what I'm really asking is if this needs to go on this release (2.0.0) or if it can wait until the next one which might take a while > Don't skip metadata if none was returned in prepared statement > -------------------------------------------------------------- > > Key: CASSGO-40 > URL: https://issues.apache.org/jira/browse/CASSGO-40 > Project: Apache Cassandra Go driver > Issue Type: Improvement > Components: Core > Reporter: James Hartig > Assignee: James Hartig > Priority: Normal > Fix For: 2.0.0 > > > Currently the driver defaults to skipping metadata when the query was > prepared but a prepared query might return no metadata (including setting the > No_metadata flag). We shouldn't skip metadata for the rows if the prepared > query did not contain metadata. > This comes from Yugabyte returning no metadata for prepared queries that > utilize a secondary index [0]. Without this handling users need to explicitly > call NoSkipMetadata() for queries that use a secondary index or they need to > disable metadata skipping for the whole cluster. > Despite encountering this using Yugabyte, this does feel like a footgun in > general. I believe the desired behavior I described above does match the Java > driver if my understanding of the code is correct. > [0]https://github.com/yugabyte/yugabyte-db/issues/1312 -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org