GRANT

Syntax

GRANT [TRANSFERABLE] priv_type [, priv_type [ ... ]] ON priv_level
    TO user_or_role [, user_or_role [ ... ]]
    [WITH GRANT OPTION]
    [REQUIRE {SSL | NONE}]

priv_type:
    | SELECT
    | INSERT
    | UPDATE
    | DELETE
    | CREATE
    | DROP
    | RELOAD
    | PROCESS
    | INDEX
    | ALTER
    | SHOW METADATA
    | GRANT OPTION
    | SYSTEM_VARIABLE_ADMIN
    | CREATE TEMPORARY TABLES
    | LOCK TABLES
    | CREATE VIEW
    | SHOW VIEW
    | CREATE USER
    | ALTER USER
    | ALTER VIEW
    | DROP VIEW
    | BACKUP
    | CREATE DATABASE
    | DROP DATABASE
    | CREATE PIPELINE
    | DROP PIPELINE
    | ALTER PIPELINE
    | START PIPELINE
    | SHOW PIPELINE
    | EXECUTE
    | CREATE ROUTINE
    | ALTER ROUTINE
    | SHOW ROUTINE 
    | CREATE POOL  (SingleStore Helios Premium)
    | DROP POOL    (SingleStore Helios Premium)
    | CREATE LINK
    | DROP LINK
    | SHOW LINK
    | OUTBOUND
    | ALTER TRACE
   
priv_level:
      *
    | *.*
    | database.*
    | database.table

user_or_role:
      user [, user]
    | role

user:
   'user_name'[@'host_name'] [IDENTIFIED BY 'password']

role:
   ROLE 'role_name'

Arguments

priv_type: The privileges to grant the specified user.

priv_level: The resource on which to grant privileges.

• * - USAGE privilege only. See Permissions Matrix for more detailed information on which commands can be executed with minimal USAGE privilege.

• *.* - Global privileges are administrative or apply to all databases on a given server.

• database.* - Database privileges apply to all objects in a given database. Wildcards (%) are accepted in database names. The underscore character (_) can also be used as a wildcard to match any single character. A backspace (\) can precede an underscore to indicate the underscore is a literal part of a database name, e.g. db_1. A sharp character (#) must precede the database name if wildcards are used in a GRANT command. This will allow users to be granted permissions to any database that fits the pattern. See the following examples.

  Grant access to user1 for all databases that starts with "db" and is followed by a single character, e.g. db1, db2, or dba:

  SQL

  Copy

  GRANT ALL ON `#db_`.* TO user1;

  Grant access to user2 for all databases that start with "db" and followed by zero or more characters, e.g. db, db1, db123, or db_456:

  SQL

  Copy

  GRANT ALL ON `#db%`.* TO user2;

  Grant access to user3 for all databases that start with "db_" and followed by zero or more characters, e.g. db_, db_1, db_abc, or db_123:

  SQL

  Copy

  GRANT ALL ON `#db\_%`.* TO user3;

• database.table - Table privileges apply to all columns in a given table in a given database.

user_or_role: One or more user attributes or a role attribute. The @'host_name' part is optional. If a hostname is not specified, @'%' will be appended to the user string. For example, 'demo-user' is equivalent to 'demo-user'@'%'.The '%' wildcard matches any hostname. user and host_name need not be quoted if they are legal as unquoted identifiers. Quotes must be used if a host_name string contains wildcard characters (such as %), or a user string contains special characters (such as space or -) or is a restricted keyword.

Remarks

• The creation of users by using GRANT is disallowed and NO_AUTO_CREATE_USER is enabled by default.

• Refer to the Permission Matrix for the required permission.

• USAGE privilege allows users to connect to the cluster, view some SHOW Commands, and view objects on the information_schema database.

• PROCESS, FILE READ, FILE WRITE, SHOW METADATA, SUPER, CREATE USER, SYSTEM_VARIABLES_ADMIN, CLUSTER, CREATE POOL, and DROP POOL are global privileges. They can be granted only on *.* and not on specific databases or tables.

• The SYSTEM_VARIABLES_ADMIN permission allows users to set certain engine variables. These engine variables can be found by running the SHOW VARIABLES EXTENDED command and confirming the value is "Yes" in the In_Allow_List column.

• The WITH GRANT OPTION clause grants the GRANT OPTION privilege, which allows a user to grant all privileges that the user already has to other users within a scoped database. The privilege_transfer_modeengine variable must be left on the default value grant_option for the WITH GRANT OPTION clause to work as expected. The GRANT ... WITH GRANT OPTION and GRANT GRANT OPTION ... statements are synonymous. See Default Mode Permissions Changes for more information.

  Note: Different users with GRANT OPTION privilege may be able to combine their privileges.

• The TRANSFERABLE clause allows a user to grant individual privileges to another user. The privilege_transfer_modeengine variable must be set to per_privilege for the TRANSFERABLE clause to work as expected. If privilege_transfer_mode is left on the default value grant_option and the TRANSFERABLE clause is attempted, the user will receive an error. If a non-transferable privilege is granted to a user with the same privilege level as the grantee, then transferability is revoked.

  Note

  The user must have the SYSTEM_VARIABLES_ADMIN privilege to change the value of privilege_transfer_mode.

  For example, after this statement, both SELECT and INSERT on db.* will be available to 'user'@'%' and 'user'@'%' will be able to grant them to others:

  SQL

  Copy

  GRANT TRANSFERABLE SELECT, INSERT ON db.* TO 'user'@'%'

• The EXECUTE permission allows a user to execute an extensibility object. For example, having this permission for UDFs, UDAFs, and TVFs allows the user to run them in SELECT queries. Similarly, a user with EXECUTE privileges for a stored procedure can run the SP using the CALL or ECHO statements.

• The CREATE ROUTINE privilege allows a user to create an extensibility object (for example, a UDF, UDAF, TVF, or SP).

• The ALTER ROUTINE privilege allows a user to replace or delete an extensibility object (for example, a UDF, UDAF, TVF, or SP).

• The OUTBOUND privilege is required to create an outbound connection between SingleStore and an a 3rd party object store via the following commands:

  • SELECT ... INTO S3, HDFS, Azure Blob, GCS, or Kafka.

    Note

    SELECT ... INTO a file system storage requires both SELECT and FILE WRITE privileges. Users will still be able to execute SELECT ... FROM, but only if outbound connectivity is not created.

  • BACKUP ... TO S3, Azure Blob, or GCS.

  • CREATE PIPELINE with S3, HDFS, Azure Blob, GCS, or Kafka.

  Without the required privileges, an error will be generated. For example:

  SQL

  Copy

  SELECT ... INTO:
  singlestore> SELECT * FROM t1 
      INTO S3 'testing/output' 
      CONFIG '{"region":"us-east-1"}' 
      CREDENTIALS '{"aws_access_key_id":"your_access_key_id","aws_secret_access_key":"your_secret_access_key"}';
  ERROR 1142 (42000): OUTBOUND command denied to user 'user1'@'%' for table 't1'
  
  BACKUP ... INTO:
  singlestore> BACKUP t1 INTO TO S3 'testing/output' 
      CONFIG '{"region":"us-east-1"}' 
      CREDENTIALS '{"aws_access_key_id":"your_access_key_id","aws_secret_access_key":"your_secret_access_key"}';
  ERROR 1227 (42000): Access denied; you need (at least one of) the OUTBOUND privilege(s) for this operation
  
  CREATE PIPELINE:
  singlestore> CREATE PIPELINE pipeline1 
      AS LOAD DATA S3 'my-bucket-name' 
      CONFIG '{"region": "us-east-1"}'
      CREDENTIALS '{"aws_access_key_id": "your_access_key_id", "aws_secret_access_key": "your_secret_access_key", "aws_session_token": "your_session_token"}'
      INTO TABLE 't1'
      FIELDS TERMINATED BY ',';
  ERROR 1227 (42000): Access denied; you need (at least one of) the OUTBOUND privilege(s) for this operation 

  Here's how to set the privileges for a user to execute these commands:

  SQL

  Copy

  SELECT ... INTO:
  singlestore> GRANT SELECT, FILE WRITE, OUTBOUND on *.* to user1;
  
  BACKUP ... INTO:
  singlestore> GRANT SELECT, FILE WRITE, BACKUP, OUTBOUND on *.* to user1;
  
  CREATE PIPELINE:
  singlestore> GRANT SELECT, FILE WRITE, CREATE PIPELINE, OUTBOUND on *.* to user1;

  The OUTBOUND privilege will be displayed in the SHOW GRANTS command:

  SQL

  Copy

  SHOW GRANTS FOR user1;

  +-----------------------------------------------------------------------------------+
  | Grants for user1@%                                                                |
  +-----------------------------------------------------------------------------------+
  | GRANT SELECT, FILE WRITE, BACKUP, CREATE PIPELINE, OUTBOUND ON *.* TO 'user1'@'%' |
  +-----------------------------------------------------------------------------------+

• The ALTER USER permission can be used to execute ALTER USER and SET PASSWORD commands.

• This command causes implicit commits. Refer to COMMIT for more information.

• The GRANT command holds a global lock on the cluster until the processing of the command is completed. See Workspace Level Locks for more info.

GRANT
  SELECT,
  INSERT,
  UPDATE,
  DELETE,
  CREATE,
  PROCESS,
  INDEX,
  ALTER,
  DROP,
  SHOW METADATA,
  CREATE TEMPORARY TABLES,
  CREATE VIEW,
  SHOW VIEW,
  ALTER VIEW,
  DROP VIEW,
  BACKUP,
  CREATE DATABASE,
  DROP DATABASE,
  CREATE PIPELINE,
  DROP PIPELINE,
  ALTER PIPELINE,
  START PIPELINE,
  SHOW PIPELINE,
  CREATE ROUTINE,
  ALTER ROUTINE,
  CREATE USER,
  CREATE LINK,
  DROP LINK,
  SHOW LINK,
  EXECUTE,
  USAGE,
  RELOAD,
  LOCK TABLES,
  CREATE POOL,
  DROP POOL,
  SYSTEM_VARIABLES_ADMIN,
  OUTBOUND
ON *.*
TO 'TEST_DBA';

GRANT ALL PRIVILEGES ON *.* TO 'singlestore_admin' IDENTIFIED BY 'password' WITH GRANT OPTION;

Examples

Note: The privilege_transfer_modeengine variable must be left on the default value grant_option for the WITH GRANT OPTION clause to work as expected. The user must have SYSTEM_VARIABLES_ADMIN privilege to be able to change the value of privilege_transfer_mode.

GRANT TRANSFERABLE SELECT, INSERT ON db.* TO 'singlestore_admin';

Note: The privilege_transfer_modeengine variable must be set to value per_privilege to grant transferable privileges. The user must have SYSTEM_VARIABLES_ADMIN privilege to be able to change the value of privilege_transfer_mode.

The following example demonstrates how to grant the specified privileges to all databases to the full_backup_role role.

GRANT BACKUP, RELOAD ON *.* TO ROLE 'full_backup_role';

The following example demonstrates how to grant permissions for a resource pool p1 to a user u1:

GRANT USAGE ON RESOURCE POOL p1 to 'u1';

The following example demonstrates how to grant the execute permission for a stored procedure or function:

GRANT EXCUTE ON dbname.procname TO username;

Related Topics

• GRANT GROUP

• GRANT ROLE