RELEASE ├── bin ├── conf | ├── kyuubi-defaults.conf.template │ ├── kyuubi-env.sh.template │ └── log4j.properties.template ├── docker │ ├── Dockerfile │ ├── kyuubi-configmap.yaml │ ├── kyuubi-pod KYUUBI_CONF_DIR: /Users/kentyao/svn-kyuubi/v1.3.1-incubating- rc0/apache-kyuubi-1.3.1-incubating-bin/conf KYUUBI_LOG_DIR: /Users/kentyao/svn-kyuubi/v1.3.1-incubating-rc0/apache- kyuubi-1.3.1-incubating-bin/logs KYUUBI_PID_DIR: of the log file, e.g. ThriftFrontendService: Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too

RELEASE ├── bin ├── conf | ├── kyuubi-defaults.conf.template │ ├── kyuubi-env.sh.template │ └── log4j.properties.template ├── docker │ ├── Dockerfile │ ├── kyuubi-configmap.yaml │ ├── kyuubi-pod KYUUBI_CONF_DIR: /Users/kentyao/svn-kyuubi/v1.3.1-incubating- rc0/apache-kyuubi-1.3.1-incubating-bin/conf KYUUBI_LOG_DIR: /Users/kentyao/svn-kyuubi/v1.3.1-incubating-rc0/apache- kyuubi-1.3.1-incubating-bin/logs KYUUBI_PID_DIR: of the log file, e.g. ThriftFrontendService: Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too

beeline-jars ├── bin ├── conf | ├── kyuubi-defaults.conf.template │ ├── kyuubi-env.sh.template │ └── log4j2.properties.template ├── docker │ ├── Dockerfile │ ├── helm │ ├── kyuubi-configmap.yaml │ KYUUBI_CONF_DIR: /Users/kentyao/svn-kyuubi/v1.3.1-incubating- rc0/apache-kyuubi-1.3.1-incubating-bin/conf KYUUBI_LOG_DIR: /Users/kentyao/svn-kyuubi/v1.3.1-incubating-rc0/apache- kyuubi-1.3.1-incubating-bin/logs KYUUBI_PID_DIR: of the log file, e.g. ThriftFrontendService: Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too

beeline-jars ├── bin ├── conf | ├── kyuubi-defaults.conf.template │ ├── kyuubi-env.sh.template │ └── log4j2.properties.template ├── docker │ ├── Dockerfile │ ├── helm │ ├── kyuubi-configmap.yaml │ KYUUBI_CONF_DIR: /Users/kentyao/svn-kyuubi/v1.3.1-incubating- rc0/apache-kyuubi-1.3.1-incubating-bin/conf KYUUBI_LOG_DIR: /Users/kentyao/svn-kyuubi/v1.3.1-incubating-rc0/apache- kyuubi-1.3.1-incubating-bin/logs KYUUBI_PID_DIR: of the log file, e.g. ThriftFrontendService: Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too

beeline-jars ├── bin ├── conf | ├── kyuubi-defaults.conf.template │ ├── kyuubi-env.sh.template │ └── log4j2.properties.template ├── docker │ ├── Dockerfile │ ├── helm │ ├── kyuubi-configmap.yaml │ KYUUBI_CONF_DIR: /Users/kentyao/svn-kyuubi/v1.3.1-incubating- rc0/apache-kyuubi-1.3.1-incubating-bin/conf KYUUBI_LOG_DIR: /Users/kentyao/svn-kyuubi/v1.3.1-incubating-rc0/apache- kyuubi-1.3.1-incubating-bin/logs KYUUBI_PID_DIR: of the log file, e.g. ThriftFrontendService: Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too

RELEASE ├── bin │ └── kyuubi ├── conf │ ├── kyuubi-defaults.conf │ ├── kyuubi-env.sh │ └── log4j.properties ├── externals │ ├── engines │ └── spark-3.0.1-bin-hadoop2.7 ├── jars ├── logs ├── 2-bin-spark-3.0.1 KYUUBI_CONF_DIR: /Users/kentyao/kyuubi/kyuubi-1.0.2-bin-spark- 3.0.1/conf KYUUBI_LOG_DIR: /Users/kentyao/kyuubi/kyuubi-1.0.2-bin-spark-3.0.1/logs KYUUBI_PID_DIR: /Users/kentyao/kyuubi/kyuubi-1 end of the log file, e.g. FrontendService: Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too.

RELEASE ├── bin │ └── kyuubi ├── conf │ ├── kyuubi-defaults.conf │ ├── kyuubi-env.sh │ └── log4j.properties ├── externals │ ├── engines │ └── spark-3.0.1-bin-hadoop2.7 ├── jars ├── logs ├── 2-bin-spark-3.0.1 KYUUBI_CONF_DIR: /Users/kentyao/kyuubi/kyuubi-1.0.2-bin-spark- 3.0.1/conf KYUUBI_LOG_DIR: /Users/kentyao/kyuubi/kyuubi-1.0.2-bin-spark-3.0.1/logs KYUUBI_PID_DIR: /Users/kentyao/kyuubi/kyuubi-1 end of the log file, e.g. FrontendService: Starting and exposing JDBC connection at: jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too.

beeline-jars ├── bin ├── conf | ├── kyuubi-defaults.conf.template │ ├── kyuubi-env.sh.template │ └── log4j2.properties.template ├── docker │ ├── Dockerfile │ ├── helm │ ├── kyuubi-configmap.yaml │ g.apache.kyuubi.server.KyuubiServer.pid. And you are able to get the JDBC connection URL from the log file - logs/kyuubi-- org.apache.kyuubi.server.KyuubiServer-.out. For example, unsupported Scala versions. If something goes wrong, you shall be able to find some clues in the log file too. Operate Clients Kyuubi delivers a beeline client, enabling a similar experience to Apache

beeline-jars ├── bin ├── conf | ├── kyuubi-defaults.conf.template │ ├── kyuubi-env.sh.template │ └── log4j2.properties.template ├── docker │ ├── Dockerfile │ ├── helm │ ├── kyuubi-configmap.yaml │ g.apache.kyuubi.server.KyuubiServer.pid. And you are able to get the JDBC connection URL from the log file - logs/kyuubi-- org.apache.kyuubi.server.KyuubiServer-.out. For example, unsupported Scala versions. If something goes wrong, you shall be able to find some clues in the log file too. Operate Clients Kyuubi delivers a beeline client, enabling a similar experience to Apache

beeline-jars ├── bin ├── conf | ├── kyuubi-defaults.conf.template │ ├── kyuubi-env.sh.template │ └── log4j2.properties.template ├── docker │ ├── Dockerfile │ ├── helm │ ├── kyuubi-configmap.yaml │ g.apache.kyuubi.server.KyuubiServer.pid. And you are able to get the JDBC connection URL from the log file - logs/kyuubi-- org.apache.kyuubi.server.KyuubiServer-.out. For example, unsupported Scala versions. If something goes wrong, you shall be able to find some clues in the log file too. Operate Clients Kyuubi delivers a beeline client, enabling a similar experience to Apache