Release 1.7.3 (continued from previous page) | kyuubi-defaults.conf.template kyuubi-env.sh.template log4j2.properties.template docker Dockerfile helm kyuubi-configmap.yaml kyuubi-deployment.yaml kyuubi-pod org.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, jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too. Note: Alternatively, it can run in the foreground, with the logs and other output written

Release 1.7.1 (continued from previous page) | kyuubi-defaults.conf.template kyuubi-env.sh.template log4j2.properties.template docker Dockerfile helm kyuubi-configmap.yaml kyuubi-deployment.yaml kyuubi-pod org.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, jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too. Note: Alternatively, it can run in the foreground, with the logs and other output written

Release 1.7.3 (continued from previous page) | kyuubi-defaults.conf.template kyuubi-env.sh.template log4j2.properties.template docker Dockerfile helm kyuubi-configmap.yaml kyuubi-deployment.yaml kyuubi-pod org.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, jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too. Note: Alternatively, it can run in the foreground, with the logs and other output written

Release 1.7.2 (continued from previous page) | kyuubi-defaults.conf.template kyuubi-env.sh.template log4j2.properties.template docker Dockerfile helm kyuubi-configmap.yaml kyuubi-deployment.yaml kyuubi-pod org.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, jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too. Note: Alternatively, it can run in the foreground, with the logs and other output written

Release 1.7.2 (continued from previous page) | kyuubi-defaults.conf.template kyuubi-env.sh.template log4j2.properties.template docker Dockerfile helm kyuubi-configmap.yaml kyuubi-deployment.yaml kyuubi-pod org.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, jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too. Note: Alternatively, it can run in the foreground, with the logs and other output written

previous page) RELEASE beeline-jars bin conf | kyuubi-defaults.conf.template kyuubi-env.sh.template log4j2.properties.template docker Dockerfile helm kyuubi-configmap.yaml kyuubi-deployment.yaml kyuubi-pod /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

previous page) RELEASE beeline-jars bin conf | kyuubi-defaults.conf.template kyuubi-env.sh.template log4j2.properties.template docker Dockerfile helm kyuubi-configmap.yaml kyuubi-deployment.yaml kyuubi-pod /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 1.7.0 (continued from previous page) | kyuubi-defaults.conf.template kyuubi-env.sh.template log4j2.properties.template docker Dockerfile helm kyuubi-configmap.yaml kyuubi-deployment.yaml kyuubi-pod org.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, jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too. Note: Alternatively, it can run in the foreground, with the logs and other output written

Release 1.7.0 (continued from previous page) | kyuubi-defaults.conf.template kyuubi-env.sh.template log4j2.properties.template docker Dockerfile helm kyuubi-configmap.yaml kyuubi-deployment.yaml kyuubi-pod org.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, jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too. Note: Alternatively, it can run in the foreground, with the logs and other output written

Release 1.7.0 (continued from previous page) | kyuubi-defaults.conf.template kyuubi-env.sh.template log4j2.properties.template docker Dockerfile helm kyuubi-configmap.yaml kyuubi-deployment.yaml kyuubi-pod org.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, jdbc:hive2://localhost:10009/ If something goes wrong, you shall be able to find some clues in the log file too. Note: Alternatively, it can run in the foreground, with the logs and other output written