Upgrading from Kyuubi 1.8 to 1.9 • Since Kyuubi 1.9.0, kyuubi.session.conf.advisor can be set as a sequence, Kyuubi supported chaining SessionConfAdvisors. • Since Kyuubi 1.9.0, the support of Derby is removal which contacted with an expire_time in ‘yyyyMMd- dHHmm’ format and a MD5 signature generated with sequence of expire_time, username and a secret key. With the following example, an H2 in-memory database INFO client.ServiceDiscovery: Created a /kyuubi/ ˓→serviceUri=host:10009;version=1.3.1-incubating;sequence=0000000037 on ZooKeeper for␣ ˓→KyuubiServer uri: host:10009 2021-11-26 17:49:50.267 INFO server

516 INFO client.ServiceDiscovery: Created a /kyuubi/ ˓→serviceUri=localhost:10009;version=1.0.2;sequence=0000000000 on ZooKeeper for␣ ˓→KyuubiServer uri: localhost:10009 2021-01-16 03:27:36.516 INFO client INFO client.ServiceDiscovery: Created a /kyuubi/ ˓→serviceUri=host:10009;version=1.3.1-incubating;sequence=0000000037 on ZooKeeper for␣ ˓→KyuubiServer uri: host:10009 2021-11-26 17:49:50.266 INFO client of the Kyuubi system is shown in the following diagram. 142 Chapter 6. High Availability Kyuubi, Release 1.5.0-incubating The middle part of the diagram shows the Kyuubi server’s main component, which

516 INFO client.ServiceDiscovery: Created a /kyuubi/ ˓→serviceUri=localhost:10009;version=1.0.2;sequence=0000000000 on ZooKeeper for␣ ˓→KyuubiServer uri: localhost:10009 2021-01-16 03:27:36.516 INFO client INFO client.ServiceDiscovery: Created a /kyuubi/ ˓→serviceUri=host:10009;version=1.3.1-incubating;sequence=0000000037 on ZooKeeper for␣ ˓→KyuubiServer uri: host:10009 2021-11-26 17:49:50.266 INFO client of the Kyuubi system is shown in the following diagram. 142 Chapter 6. High Availability Kyuubi, Release 1.5.1-incubating The middle part of the diagram shows the Kyuubi server’s main component, which

516 INFO client.ServiceDiscovery: Created a /kyuubi/ ˓→serviceUri=localhost:10009;version=1.0.2;sequence=0000000000 on ZooKeeper for␣ ˓→KyuubiServer uri: localhost:10009 2021-01-16 03:27:36.516 INFO client INFO client.ServiceDiscovery: Created a /kyuubi/ ˓→serviceUri=host:10009;version=1.3.1-incubating;sequence=0000000037 on ZooKeeper for␣ ˓→KyuubiServer uri: host:10009 2021-11-26 17:49:50.266 INFO client of the Kyuubi system is shown in the following diagram. 142 Chapter 6. High Availability Kyuubi, Release 1.5.2-incubating The middle part of the diagram shows the Kyuubi server’s main component, which

Upgrading from Kyuubi 1.8 to 1.9 Since Kyuubi 1.9.0, kyuubi.session.conf.advisor can be set as a sequence, Kyuubi supported chaining SessionConfAdvisors. Since Kyuubi 1.9.0, the support of Derby is removal which contacted with an expire_time in ‘yyyyMMddHHmm’ format and a MD5 signature generated with sequence of expire_time, username and a secret key. With the following example, an H2 in-memory database INFO client.ServiceDiscovery: Created a /kyuubi/serviceUri=host:10009;version=1.3.1- incubating;sequence=0000000037 on ZooKeeper for KyuubiServer uri: host:10009 2021-11-26 17:49:50.267 INFO server.KyuubiServer:

which contacted with an expire_time in ‘yyyyMMd- dHHmm’ format and a MD5 signature generated with sequence of expire_time, username and a secret key. With the following example, an H2 in-memory database INFO client.ServiceDiscovery: Created a /kyuubi/ ˓→serviceUri=host:10009;version=1.3.1-incubating;sequence=0000000037 on ZooKeeper for␣ ˓→KyuubiServer uri: host:10009 2021-11-26 17:49:50.267 INFO server fundamental technical architecture of the Kyuubi system is shown in the following diagram. The middle part of the diagram shows the Kyuubi server’s main component, which handles the clients’ connection

which contacted with an expire_time in ‘yyyyMMd- dHHmm’ format and a MD5 signature generated with sequence of expire_time, username and a secret key. With the following example, an H2 in-memory database INFO client.ServiceDiscovery: Created a /kyuubi/ ˓→serviceUri=host:10009;version=1.3.1-incubating;sequence=0000000037 on ZooKeeper for␣ ˓→KyuubiServer uri: host:10009 2021-11-26 17:49:50.267 INFO server fundamental technical architecture of the Kyuubi system is shown in the following diagram. The middle part of the diagram shows the Kyuubi server’s main component, which handles the clients’ connection

which contacted with an expire_time in ‘yyyyMMd- dHHmm’ format and a MD5 signature generated with sequence of expire_time, username and a secret key. With the following example, an H2 in-memory database INFO client.ServiceDiscovery: Created a /kyuubi/ ˓→serviceUri=host:10009;version=1.3.1-incubating;sequence=0000000037 on ZooKeeper for␣ ˓→KyuubiServer uri: host:10009 2021-11-26 17:49:50.267 INFO server architecture of the Kyuubi system is shown in the following diagram. 184 Chapter 3. What’s Next Kyuubi, Release 1.8.1 The middle part of the diagram shows the Kyuubi server’s main component, which handles

which contacted with an expire_time in ‘yyyyMMd- dHHmm’ format and a MD5 signature generated with sequence of expire_time, username and a secret key. With the following example, an H2 in-memory database INFO client.ServiceDiscovery: Created a /kyuubi/ ˓→serviceUri=host:10009;version=1.3.1-incubating;sequence=0000000037 on ZooKeeper for␣ ˓→KyuubiServer uri: host:10009 2021-11-26 17:49:50.267 INFO server fundamental technical architecture of the Kyuubi system is shown in the following diagram. The middle part of the diagram shows the Kyuubi server’s main component, which handles the clients’ connection

which contacted with an expire_time in ‘yyyyMMd- dHHmm’ format and a MD5 signature generated with sequence of expire_time, username and a secret key. With the following example, an H2 in-memory database INFO client.ServiceDiscovery: Created a /kyuubi/ ˓→serviceUri=host:10009;version=1.3.1-incubating;sequence=0000000037 on ZooKeeper for␣ ˓→KyuubiServer uri: host:10009 2021-11-26 17:49:50.267 INFO server architecture of the Kyuubi system is shown in the following diagram. 174 Chapter 3. What’s Next Kyuubi, Release 1.7.0 The middle part of the diagram shows the Kyuubi server’s main component, which handles