engine: Once the connection is set up, we shall be able to see the default catalog, databases(namespaces) as below. 6.1. Quick Start 27 Kyuubi, Release 1.3.0 Operations Now, we can use the SQL editor managers such as K8S and Yarn manage the cluster compute resources, divided into different queues or namespaces with different ACLs and quotas. In Kyuubi, we acquire computing resources from the cluster manager different users, the step 2 and 3 will be repeated. This is because in the service discovery layer, the namespaces used to store the address of the engine instances are isolated based on the user(by default), and

engine: Once the connection is set up, we shall be able to see the default catalog, databases(namespaces) as below. 6.1. Quick Start 27 Kyuubi, Release 1.3.0 Operations Now, we can use the SQL editor managers such as K8S and Yarn manage the cluster compute resources, divided into different queues or namespaces with different ACLs and quotas. In Kyuubi, we acquire computing resources from the cluster manager different users, the step 2 and 3 will be repeated. This is because in the service discovery layer, the namespaces used to store the address of the engine instances are isolated based on the user(by default), and

engine: Once the connection is set up, we shall be able to see the default catalog, databases(namespaces) as below. 2.4.2. Operations Now, we can use the SQL editor to write queries to interact with managers such as K8S and Yarn manage the cluster compute resources, divided into different queues or namespaces with different ACLs and quotas. In Kyuubi, we acquire computing resources from the cluster manager users, the step 2 and 3 will be repeated. This is because in the service discovery layer, the namespaces used to store the address of the engine instances are isolated based on the user(by default), and

engine: Once the connection is set up, we shall be able to see the default catalog, databases(namespaces) as below. 2.4.2. Operations Now, we can use the SQL editor to write queries to interact with managers such as K8S and Yarn manage the cluster compute resources, divided into different queues or namespaces with different ACLs and quotas. In Kyuubi, we acquire computing resources from the cluster manager users, the step 2 and 3 will be repeated. This is because in the service discovery layer, the namespaces used to store the address of the engine instances are isolated based on the user(by default), and

engine: Once the connection is set up, we shall be able to see the default catalog, databases(namespaces) as below. 6.1. Quick Start 31 Kyuubi, Release 1.4.1-incubating Operations Now, we can use managers such as K8S and Yarn manage the cluster compute resources, divided into different queues or namespaces with different ACLs and quotas. In Kyuubi, we acquire computing resources from the cluster manager different users, the step 2 and 3 will be repeated. This is because in the service discovery layer, the namespaces used to store the address of the engine instances are isolated based on the user(by default), and

engine: Once the connection is set up, we shall be able to see the default catalog, databases(namespaces) as below. 6.1. Quick Start 31 Kyuubi, Release 1.3.0 Operations Now, we can use the SQL editor managers such as K8S and Yarn manage the cluster compute resources, divided into different queues or namespaces with different ACLs and quotas. In Kyuubi, we acquire computing resources from the cluster manager different users, the step 2 and 3 will be repeated. This is because in the service discovery layer, the namespaces used to store the address of the engine instances are isolated based on the user(by default), and

engine: Once the connection is set up, we shall be able to see the default catalog, databases(namespaces) as below. 34 Chapter 6. High Availability Kyuubi, Release 1.5.0-incubating Operations Now managers such as K8S and Yarn manage the cluster compute resources, divided into different queues or namespaces with different ACLs and quotas. In Kyuubi, we acquire computing resources from the cluster manager different users, the step 2 and 3 will be repeated. This is because in the service discovery layer, the namespaces used to store the address of the engine instances are isolated based on the user(by default), and

engine: Once the connection is set up, we shall be able to see the default catalog, databases(namespaces) as below. 3.4.2. Operations Now, we can use the SQL editor to write queries to interact with managers such as K8S and Yarn manage the cluster compute resources, divided into different queues or namespaces with different ACLs and quotas. In Kyuubi, we acquire computing resources from the cluster manager users, the step 2 and 3 will be repeated. This is because in the service discovery layer, the namespaces used to store the address of the engine instances are isolated based on the user(by default), and

engine: Once the connection is set up, we shall be able to see the default catalog, databases(namespaces) as below. 34 Chapter 6. High Availability Kyuubi, Release 1.5.1-incubating Operations Now managers such as K8S and Yarn manage the cluster compute resources, divided into different queues or namespaces with different ACLs and quotas. In Kyuubi, we acquire computing resources from the cluster manager different users, the step 2 and 3 will be repeated. This is because in the service discovery layer, the namespaces used to store the address of the engine instances are isolated based on the user(by default), and

engine: Once the connection is set up, we shall be able to see the default catalog, databases(namespaces) as below. 3.4.2. Operations Now, we can use the SQL editor to write queries to interact with managers such as K8S and Yarn manage the cluster compute resources, divided into different queues or namespaces with different ACLs and quotas. In Kyuubi, we acquire computing resources from the cluster manager users, the step 2 and 3 will be repeated. This is because in the service discovery layer, the namespaces used to store the address of the engine instances are isolated based on the user(by default), and