You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by Mikhail Petrov <pm...@gmail.com> on 2020/05/08 09:19:28 UTC

JDBC SQL query permissions.

Hello, Igniters.

At the moment execution of the following SQL queries via JDBC requires 
no security permissions:
ALTER TABLE ADD
ALTER TABLE DROP COLUMN
CREATE INDEX
DROP INDEX

Could someone clarify does this behavior considered desired or it is 
needed to be fixed?

Tests that shows described behavior can be found here - [1].

[1] - https://github.com/apache/ignite/pull/7691

Regards,
Mikhail.

Re: JDBC SQL query permissions.

Posted by Denis Magda <dm...@apache.org>.

Hello Mikhail,

Most likely that didn't get in the scope when those commands were being
added to Ignite. @Taras Ledkov <tl...@gridgain.com>, @Ivan Pavlukhin
<vo...@gmail.com>, @Yuriy Gerzhedovich <yg...@gridgain.com>,
could you please share your thoughts on this?

-
Denis

On Fri, May 8, 2020 at 2:19 AM Mikhail Petrov <pm...@gmail.com> wrote:

> Hello, Igniters.
>
> At the moment execution of the following SQL queries via JDBC requires
> no security permissions:
> ALTER TABLE ADD
> ALTER TABLE DROP COLUMN
> CREATE INDEX
> DROP INDEX
>
> Could someone clarify does this behavior considered desired or it is
> needed to be fixed?
>
> Tests that shows described behavior can be found here - [1].
>
> [1] - https://github.com/apache/ignite/pull/7691
>
> Regards,
> Mikhail.
>
>