Notifier 1.2.10. System 1.2.11. Network socket 1.2.12. JMS 1.2.13. MQTT 1.2.14. Kafka 1.2.15. Rest Servlet 1.3. Appenders 1.3.1. Log 1.3.2. Elasticsearch & Kibana 1.3.3. JDBC 1.3.4. JMS 1.3.5 installs the eventadmin collector: By default, the eventadmin collector is listening for all OSGi framework and Karaf internal events. You can specify additional events to trap by providing a ‘etc/ org similar to the Decanter Kafka appender. Please, see Kafka collector for details. 1.2.15. Rest Servlet The Decanter Rest Servlet collector registers a servlet on the OSGi HTTP service (by default on /decanter/collect

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 1.2.16. Rest Servlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . feature:install decanter-collector-eventadmin By default, the eventadmin collector is listening for all OSGi framework and Karaf internal events. You can specify additional events to trap by providing a ‘etc/org properties, appending the following to the org.osgi.framework.system.packages.extra property: Apache Karaf Decanter 2.x - Documentation - 8 org.osgi.framework.system.packages.extra = \ ... javax.remote

么是上下文呢？ 首先我们要理解 docker build 的工作原理。Docker 在运行时分为 Docker 引擎（也就是服 务端守护进程）和客户端工具。Docker 的引擎提供了一组 REST API，被称为 Docker Remote API，而如 docker 命令这样的客户端工具，则是通过这组 API 与 Docker 引擎交 互，从而完成各种功能。因此，虽然表面上我们好像是在本机执行各种 器。 为了加强对服务端的保护，Docker 的 REST API（客户端用来跟服务端通信）在 0.5.2 之后 使用本地的 Unix 套接字机制替代了原先绑定在 127.0.0.1 上的 TCP 套接字，因为后者容易遭 受跨站脚本攻击。现在用户使用 Unix 权限检查来加强套接字的访问安全。 用户仍可以利用 HTTP 提供 REST API 访问。建议使用安全机制，确保只有可信的网络或 set the output format (fields, json, protobuf, s imple, table) 数据库操作 数据库操作围绕对键值和目录的 CRUD （符合 REST 风格的一套操作：Create）完整生命周 期的管理。 使用 etcdctl 240 etcd 在键的组织上采用了层次化的空间结构（类似于文件系统中目录的概念），用户指定的 键可以为单独的名字，如

optimized experience exploring their data universe in a serverless way, using either JDBC + SQL or REST + code. For most scenarios, the superpower of corresponding engines, such as Spark, and Flink, is ******* Services ******* ************************ REST: - To access kyuubi-rest service within the cluster, use the following URL: kyuubi-rest.kyuubi.svc.cluster.local THRIFT_BINARY: - To access logs. duration 1.6.0 kyuubi.ctl.rest.auth.schema basic The authentication schema. Valid values are: basic, spnego. string 1.6.0 kyuubi.ctl.rest.base.url The REST API base URL, which contains

optimized experience exploring their data universe in a serverless way, using either JDBC + SQL or REST + code. For most scenarios, the superpower of corresponding engines, such as Spark, and Flink, is logs. duration 1.6.0 kyuubi.ctl.rest.auth.schema basic The authentication schema. Valid values are: basic, spnego. string 1.6.0 kyuubi.ctl.rest.base.url The REST API base URL, which contains contains the scheme (http:// or https://), hostname, port number string 1.6.0 kyuubi.ctl.rest.connect.timeout PT30S The timeout[ms] for establishing the connection with the kyuubi server. A timeout value of

optimized experience exploring their data universe in a serverless way, using either JDBC + SQL or REST + code. For most scenarios, the superpower of corresponding engines, such as Spark, and Flink, is 1.7.0 to 1.7.1 Since Kyuubi 1.7.1, protocolVersion is removed from the request parameters of the REST API Open(create) a session. All removed or unknown parameters will be silently ignored and affects affects nothing. Since Kyuubi 1.7.1, confOverlay is supported in the request parameters of the REST API Create an operation with EXECUTE_STATEMENT type. Upgrading from Kyuubi 1.6 to 1.7 In Kyuubi 1.7, kyuubi

optimized experience exploring their data universe in a serverless way, using either JDBC + SQL or REST + code. For most scenarios, the superpower of corresponding engines, such as Spark, and Flink, is durati on 1.6.0 kyuubi.ctl.rest.aut h.schema basic The authentication schema. Valid values are: basic, spnego. string 1.6.0 kyuubi.ctl.rest.bas e.url The REST API base URL, which contains contains the scheme (http:// or https://), hostname, port number string 1.6.0 kyuubi.ctl.rest.con nect.timeout PT30S The timeout[ms] for establishing the connection with the kyuubi server. A timeout value

optimized experience exploring their data universe in a serverless way, using either JDBC + SQL or REST + code. For most scenarios, the superpower of corresponding engines, such as Spark, and Flink, is durati on 1.6.0 kyuubi.ctl.rest.aut h.schema basic The authentication schema. Valid values are: basic, spnego. string 1.6.0 kyuubi.ctl.rest.bas e.url The REST API base URL, which contains contains the scheme (http:// or https://), hostname, port number string 1.6.0 kyuubi.ctl.rest.con nect.timeout PT30S The timeout[ms] for establishing the connection with the kyuubi server. A timeout value

optimized experience exploring their data universe in a serverless way, using either JDBC + SQL or REST + code. For most scenarios, the superpower of corresponding engines, such as Spark, and Flink, is durati on 1.6.0 kyuubi.ctl.rest.aut h.schema basic The authentication schema. Valid values are: basic, spnego. string 1.6.0 kyuubi.ctl.rest.bas e.url The REST API base URL, which contains contains the scheme (http:// or https://), hostname, port number string 1.6.0 kyuubi.ctl.rest.con nect.timeout PT30S The timeout[ms] for establishing the connection with the kyuubi server. A timeout value