Protocol – A MySQL-compatible interface that allows end users to use MySQL Connectors, such as Connector/J, to communicate with Kyuubi. ## • We’ve planned to add more – Please join our mailing lists com/apache/kyuubi https://spark.apache.org/docs/latest/sql-data-sources.html ## Hive The Kyuubi Hive Connector is a datasource for both reading and writing Hive table. It is implemented based on Spark DataSource multiple Hive metastore at the same time. This connector can be used to federate queries of multiple hives warehouse in a single Spark cluster. ## Hive Connector Integration To enable the integration of kyuubi

Java/Jakarta EE application server Apache ActiveMQ Artemis provides its own fully functional Java Connector Architecture (JCA) adaptor which enables it to be integrated easily into any Java/Jakarta EE (henceforth Whether there is one or many host:port combinations in the URL they are treated as the initial connector(s) for the underlying connection. The udp scheme is also supported which should use a host:port and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have • (tcp://remote-host1:5445?httpEnabled=true,remote-host2:5445?httpEnabled=true)

Java/Jakarta EE application server Apache ActiveMQ Artemis provides its own fully functional Java Connector Architecture (JCA) adaptor which enables it to be integrated easily into any Java/Jakarta EE (henceforth Whether there is one or many host:port combinations in the URL they are treated as the initial connector(s) for the underlying connection. The udp scheme is also supported which should use a host:port and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have • (tcp://remote-host1:5445?httpEnabled=true,remote-host2:5445?httpEnabled=true)

Java/Jakarta EE application server Apache ActiveMQ Artemis provides its own fully functional Java Connector Architecture (JCA) adaptor which enables it to be integrated easily into any Java/Jakarta EE (henceforth Whether there is one or many host:port combinations in the URL they are treated as the initial connector(s) for the underlying connection. The udp scheme is also supported which should use a host:port and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have • (tcp://remote-host1:5445?httpEnabled=true,remote-host2:5445?httpEnabled=true)

Java/Jakarta EE application server Apache ActiveMQ Artemis provides its own fully functional Java Connector Architecture (JCA) adaptor which enables it to be integrated easily into any Java/Jakarta EE (henceforth Whether there is one or many host:port combinations in the URL they are treated as the initial connector(s) for the underlying connection. The udp scheme is also supported which should use a host:port and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have • (tcp://remote-host1:5445?httpEnabled=true,remote-host2:5445?httpEnabled=true)

Java/Jakarta EE application server Apache ActiveMQ Artemis provides its own fully functional Java Connector Architecture (JCA) adaptor which enables it to be integrated easily into any Java/Jakarta EE (henceforth Whether there is one or many host:port combinations in the URL they are treated as the initial connector(s) for the underlying connection. The udp scheme is also supported which should use a host:port and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have • (tcp://remote-host1:5445?httpEnabled=true,remote-host2:5445?httpEnabled=true)

hostname in the client's URL. This is the recommended option with regard to security. Update any connector using sslEnabled=true to also use verifyHost=false. Using this option means that you won't get the acceptor which has the problem. - The CLI will now read the broker.xml to find the default connector URL for commands which require it (e.g. consumer, producer, etc.) #### 2.11. 0 Full release notes Java/Jakarta EE application server Apache ActiveMQ Artemis provides its own fully functional Java Connector Architecture (JCA) adaptor which enables it to be integrated easily into any Java/Jakarta EE (henceforth

hostname in the client's URL. This is the recommended option with regard to security. Update any connector using sslEnabled=true to also use verifyHost=false. Using this option means that you won't get the acceptor which has the problem. - The CLI will now read the broker.xml to find the default connector URL for commands which require it (e.g. consumer, producer, etc.) #### 2.11. 0 Full release notes Java/Jakarta EE application server Apache ActiveMQ Artemis provides its own fully functional Java Connector Architecture (JCA) adaptor which enables it to be integrated easily into any Java/Jakarta EE (henceforth

hostname in the client's URL. This is the recommended option with regard to security. Update any connector using sslEnabled=true to also use verifyHost=false. Using this option means that you won't get the acceptor which has the problem. - The CLI will now read the broker.xml to find the default connector URL for commands which require it (e.g. consumer, producer, etc.) #### 2.11. 0 Full release notes Java/Jakarta EE application server Apache ActiveMQ Artemis provides its own fully functional Java Connector Architecture (JCA) adaptor which enables it to be integrated easily into any Java/Jakarta EE (henceforth

hostname in the client's URL. This is the recommended option with regard to security. Update any connector using sslEnabled=true to also use verifyHost=false. Using this option means that you won't get the acceptor which has the problem. - The CLI will now read the broker.xml to find the default connector URL for commands which require it (e.g. consumer, producer, etc.) #### 2.11. 0 Full release notes Java/Jakarta EE application server Apache ActiveMQ Artemis provides its own fully functional Java Connector Architecture (JCA) adaptor which enables it to be integrated easily into any Java/Jakarta EE (henceforth