1. Supports multi-client concurrency and authentication 2. Supports one Spark application per account(SPA). 3. Supports QUEUE/NAMESPACE Access Control Lists (ACL) 4. Supports metadata & data Access SQL Client, etc, to operate with Kyuubi server concurrently. The SPA policy makes sure 1) a user account can only get computing resource with managed ACLs, e.g. Queue Access Control Lists, from cluster cluster managers, e.g. Apache Hadoop YARN, Kubernetes (K8s) to create the Spark application; 2) a user account can only access data and metadata from a storage system, e.g. Apache Hadoop HDFS, with permissions

1. Supports multi-client concurrency and authentication 2. Supports one Spark application per account(SPA). 3. Supports QUEUE/NAMESPACE Access Control Lists (ACL) 4. Supports metadata & data Access SQL Client, etc, to operate with Kyuubi server concurrently. The SPA policy makes sure 1) a user account can only get computing resource with managed ACLs, e.g. Queue Access Control Lists, from cluster cluster managers, e.g. Apache Hadoop YARN, Kubernetes (K8s) to create the Spark application; 2) a user account can only access data and metadata from a storage system, e.g. Apache Hadoop HDFS, with permissions

supplies with default values for SQL engine appli- cation too. These properties will override all settings in $SPARK_HOME/conf/spark-defaults.conf Via JDBC Connection URL Setting them in the JDBC Connection SQL engine appli- cation too. You can use properties with the additional prefix flink. to override settings in $FLINK_HOME/conf/ flink-conf.yaml. For example: flink.parallelism.default 2 flink.taskmanager SQL engine applica- tion too. You can use properties with the additional prefix trino. to override settings in $TRINO_HOME/etc/config. properties. For example: trino.query_max_stage_count 500 trino.par

supplies with default values for SQL engine appli- cation too. These properties will override all settings in $SPARK_HOME/conf/spark-defaults.conf Via JDBC Connection URL Setting them in the JDBC Connection SQL engine appli- cation too. You can use properties with the additional prefix flink. to override settings in $FLINK_HOME/conf/ flink-conf.yaml. For example: flink.parallelism.default 2 flink.taskmanager SQL engine applica- tion too. You can use properties with the additional prefix trino. to override settings in $TRINO_HOME/etc/config. properties. For example: trino.query_max_stage_count 500 trino.par

Kyuubi server. Add repository to your maven configuration file which may reside in $MAVEN_HOME/conf/settings.xml. central maven repo central maven repo https created/ list/delete engine pods in kubernetes. You should create your serviceAccount ( or reuse account with the appropriate privileges ) and set your serviceAc- countName for kyuubi pod, which you can defaults in $SPARK_HOME/conf/hive-site.xml and $KYUUBI_HOME/conf/ kyuubi-defaults.conf for each user account. With this feature, end users are possible to visit different Hive metastore server instance. Similarly

Kyuubi server. Add repository to your maven configuration file which may reside in $MAVEN_HOME/conf/settings.xml. central maven repo central maven repo https created/ list/delete engine pods in kubernetes. You should create your serviceAccount ( or reuse account with the appropriate privileges ) and set your serviceAc- countName for kyuubi pod, which you can defaults in $SPARK_HOME/conf/hive-site.xml and $KYUUBI_HOME/conf/ kyuubi-defaults.conf for each user account. With this feature, end users are possible to visit different Hive metastore server instance. Similarly

created/ list/delete engine pods in kubernetes. You should create your serviceAccount ( or reuse account with the appropriate privileges ) and set your serviceAc- countName for kyuubi pod, which you can defaults in $SPARK_HOME/conf/hive-site.xml and $KYUUBI_HOME/conf/ kyuubi-defaults.conf for each user account. With this feature, end users are possible to visit different Hive metastore server instance. Similarly supplies with default values for SQL engine appli- cation too. These properties will override all settings in $SPARK_HOME/conf/spark-defaults.conf Via JDBC Connection URL Setting them in the JDBC Connection

created/ list/delete engine pods in kubernetes. You should create your serviceAccount ( or reuse account with the appropriate privileges ) and set your serviceAc- countName for kyuubi pod, which you can defaults in $SPARK_HOME/conf/hive-site.xml and $KYUUBI_HOME/conf/ kyuubi-defaults.conf for each user account. With this feature, end users are possible to visit different Hive metastore server instance. Similarly supplies with default values for SQL engine appli- cation too. These properties will override all settings in $SPARK_HOME/conf/spark-defaults.conf Via JDBC Connection URL Setting them in the JDBC Connection

Kyuubi server. Add repository to your maven configuration file which may reside in $MAVEN_HOME/conf/settings.xml. central maven repo central maven repo https created/ list/delete engine pods in kubernetes. You should create your serviceAccount ( or reuse account with the appropriate privileges ) and set your serviceAc- countName for kyuubi pod, which you can defaults in $SPARK_HOME/conf/hive-site.xml and $KYUUBI_HOME/conf/ kyuubi-defaults.conf for each user account. With this feature, end users are possible to visit different Hive metastore server instance. Similarly

created/ list/delete engine pods in kubernetes. You should create your serviceAccount ( or reuse account with the appropriate privileges ) and set your serviceAc- countName for kyuubi pod, which you can defaults in $SPARK_HOME/conf/hive-site.xml and $KYUUBI_HOME/conf/ kyuubi-defaults.conf for each user account. With this feature, end users are possible to visit different Hive metastore server instance. Similarly supplies with default values for SQL engine appli- cation too. These properties will override all settings in $SPARK_HOME/conf/spark-defaults.conf Via JDBC Connection URL Setting them in the JDBC Connection