IstioCon 2021 Partner Packages Keynotes ● 6 Keynotes for US TZ ● 2 Keynotes for China TZ Lightning talks ● 8 lightning talks of 10 minutes each for US TZ ● 4 for China TZ Tech Talks ● 14

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.1.1.3 Standalone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.1.1.4 YARN contains its own Python executable files and the installed Python packages. It is useful for local development to create a standalone Python environment and also useful when deploying a PyFlink job to output a path like the following: # /path/to/python/site-packages/pyflink # Check the logging under the log directory ls -lh /path/to/python/site-packages/pyflink/log # You will see the log file as following:

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.1.1.3 Standalone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.1.1.4 YARN contains its own Python executable files and the installed Python packages. It is useful for local development to create a standalone Python environment and also useful when deploying a PyFlink job to output a path like the following: # /path/to/python/site-packages/pyflink # Check the logging under the log directory ls -lh /path/to/python/site-packages/pyflink/log # You will see the log file as following:

Using shared jobs store 4.21. Tuning 4.21.1. Garbage Collection 4.21.2. Threads 4.21.3. System packages 5. Developer Guide 5.1. Developer commands 5.1.1. Dump 5.1.2. Diagnostic 5.1.3. Dynamic import Overview Apache Karaf is a modern polymorphic application container. Karaf can be used as a standalone container, supporting a wide range of applications and technologies. It also supports the "run run in a running Apache Karaf console. For convenience, the ssh:ssh command is "wrapped" as a standalone client: the bin/client Unix script ( bin\client.bat on Windows). For instance, to connect to

run into a running Apache Karaf console. For commodity, the ssh:ssh command is "wrapped" as a standalone client: the bin/client Unix script (bin\client.bat on Windows). bin/client --help Apache Karaf better solution is to simply let the OSGi framework know what your dependencies are by defining the packages or services you need. It is more robust than setting start levels. Start and stop You can install apache.karaf.config.core [77] The purpose of dynamic import is to allow a bundle to be wired up to packages that may not be knwon about in advance. DEVELOPER COMMANDS 91 When a class is requested, if it

contains all kinds of SQL engines that we support • licenses: a bunch of licenses included. • jars: packages needed by the Kyuubi server. • logs: where the logs of the Kyuubi server locates. • pid: stores mode for experimental purposes only. In a real production environment, we always have a communal standalone metadata store, to manage the metadata of persistent relational entities, e.g. databases, tables and prefer the Spark AQE to be off, while bob will activate his SQL engine application on a Spark standalone cluster with 8g heap memory for each executor and obey the Spark AQE behavior of Kyuubi system

contains all kinds of SQL engines that we support • licenses: a bunch of licenses included. • jars: packages needed by the Kyuubi server. • logs: where the logs of the Kyuubi server locates. • pid: stores mode for experimental purposes only. In a real production environment, we always have a communal standalone metadata store, to manage the metadata of persistent relational entities, e.g. databases, tables and prefer the Spark AQE to be off, while bob will activate his SQL engine application on a Spark standalone cluster with 8g heap memory for each executor and obey the Spark AQE behavior of Kyuubi system

contains all kinds of SQL engines that we support • licenses: a bunch of licenses included. • jars: packages needed by the Kyuubi server. • logs: where the logs of the Kyuubi server locates. • pid: stores mode for experimental purposes only. In a real production environment, we always have a communal standalone metadata store, to manage the metadata of persistent relational entities, e.g. databases, tables and prefer the Spark AQE to be off, while bob will activate his SQL engine application on a Spark standalone cluster with 8g heap memory for each executor and obey the Spark AQE behavior of Kyuubi system

contains all kinds of SQL engines that we support • licenses: a bunch of licenses included. • jars: packages needed by the Kyuubi server. • logs: where the logs of the Kyuubi server locates. • pid: stores mode for experimental purposes only. In a real production environment, we always have a communal standalone metadata store, to manage the metadata of persistent relational entities, e.g. databases, tables and prefer the Spark AQE to be off, while bob will activate his SQL engine application on a Spark standalone cluster with 8g heap memory for each executor and obey the Spark AQE behavior of Kyuubi system

contains all kinds of SQL engines that we support • licenses: a bunch of licenses included. • jars: packages needed by the Kyuubi server. • logs: where the logs of the Kyuubi server locates. • pid: stores mode for experimental purposes only. In a real production environment, we always have a communal standalone metadata store, to manage the metadata of persistent relational entities, e.g. databases, tables and prefer the Spark AQE to be off, while bob will activate his SQL engine application on a Spark standalone cluster with 8g heap memory for each executor and obey the Spark AQE behavior of Kyuubi system