cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vovodroid (JIRA)" <>
Subject [jira] [Issue Comment Deleted] (CASSANDRA-10022) Add INSERT permission
Date Mon, 10 Aug 2015 15:14:46 GMT


Vovodroid updated CASSANDRA-10022:
    Comment: was deleted

(was: bq.Cassandra makes no distinction meaningful distinction between INSERT, UPDATE, and
DELETE queries
Internally yes, but from external point of view there is much difference between add new data
and change existing.

bq.I don't see a way to make it non-confusing.
Non-confusing for who? I guess it's quite clear: INSERT permission allow only perform INSERT
as if "IF NOT EXIST" specified, so forcing this condition (making INSERT behavior like MySQL
counterpart). Probably we can call it ADD, or ADDNEW, or INSERTNEW or something like this
to make it clearer.

bq.LWT updates are not a security mechanism
Yes, but it can be used in such way. That's why I would like to add INSERT permission (to
make issues less confusing )))).)

> Add INSERT permission
> ---------------------
>                 Key: CASSANDRA-10022
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Vovodroid
> Hi,
> currently there is MODIFY permission in C*. It would be nice to add specific INSERT permission,
that would act as 'IF NOT EXIST' option specified.
> Imagine distributed application (e.g. mobile), that each its instance should add something
to table, but shouldn't be able to alter/delete existing data.
> Regards.

This message was sent by Atlassian JIRA

View raw message