[
https://issues.apache.org/jira/browse/CASSANALYTICS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18058639#comment-18058639
]
Francisco Guerrero commented on CASSANALYTICS-120:
--------------------------------------------------
I'm concerned about this patch. This is breaking behavior change for existing
use cases where they have mixed case for TTL column or timestamp column. This
means that it could break jobs, and the remediation requires a rewrite of spark
jobs, compilation and deployment of new code.
When I originally worked on the quoteIdentitifiers feature we had this
consideration, with the idea of erring on the safe side to avoid any breakage
and disruption to existing workloads that potentially upgrade to the version
with the change.
We should strive to avoid behavior changes, so I'm leaning towards -1 the patch.
> Quote identifiers option must be set to true if ttl has mixed case column name
> ------------------------------------------------------------------------------
>
> Key: CASSANALYTICS-120
> URL: https://issues.apache.org/jira/browse/CASSANALYTICS-120
> Project: Apache Cassandra Analytics
> Issue Type: Improvement
> Components: Writer
> Reporter: Saranya Krishnakumar
> Assignee: Saranya Krishnakumar
> Priority: Normal
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If users set TTL column name or timestamp column name to be mixed case, they
> have to set quote identifiers option to true for Cassandra to resolve the
> column name correctly. Sometimes users miss setting quote identifiers option
> and perRowTTL setting incorrectly overrides their existing TTL with null
> values when bulk write job runs. This patch fixes this, by checking for mixed
> case column names and setting quote identifiers option when required.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
