cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksei Zotov (Jira)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-16806) Allow DELETE and TRUNCATE to work on Virtual Tables if the implementation allows it
Date Sun, 29 Aug 2021 21:29:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-16806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406470#comment-17406470
] 

Aleksei Zotov commented on CASSANDRA-16806:
-------------------------------------------

[~blerer]

That makes sense to me. I'm almost done with the change, the only remaining part is to update
the tests to work with multiple partition keys and clustering columns to ensure the current
conversion logic is convenient for composite types.

In the meantime, I have a question on the VTs design. Currently TTL is not supported on VTs
(restricted on the query level) which makes perfect sense to me. Similarly, I expected to
see that custom timestamp ({{USING TIMESTAMP}} statement) is restricted on the query level.
However, it seems to be supported. If it is just an oversight, I'd like to fix it as a part
of the current ticket. If it is a part of the original design, I'd like to understand the
use cases to incorporate it to  the current change. Please, let me know your thoughts.

> Allow DELETE and TRUNCATE to work on Virtual Tables if the implementation allows it
> -----------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-16806
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16806
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Feature/Virtual Tables
>            Reporter: Benjamin Lerer
>            Assignee: Aleksei Zotov
>            Priority: Normal
>             Fix For: 4.x
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> {{TRUNCATE}} statements are currently not supported by Virtual Tables. For some Virtual
Tables it makes sense to allow it.
> It can be done by adding a {{truncate}} method to the {{VirtualTable}} interface and
calling that method from {{TruncateStatement}}. The default implementation of the method should
be to fire an {{InvalidRequestException}} saying that truncate is not supported on that specific
table.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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


Mime
View raw message