96498844d3
# 🔍 Description Discussion in mailing thread: https://lists.apache.org/thread/tnmz71o3rypy7qvs3899p3jkkq4xqb4r I propose to rename the `bin/beeline` to `bin/kyuubi-beeline`, while for compatibility, we may still want to keep the alias `bin/beeline` for a while. In a real Hadoop cluster, it’s likely to add `$HIVE_HOME/bin`, `$SPARK_HOME/bin`, `$KYUUBI_HOME/bin` to the `$PATH`, at the current state, when performing `beeline`, which one is called depends on the declaration order. It does not matter for Spark’s `bin/beeline` because it’s a vanilla Hive BeeLine, but in Kyuubi, we have made some improvements based on vanilla Hive BeeLine, so the behavior is not exactly same as Hive’s BeeLine. An identical name would solve this problem. And I saw some vendors[1] who shippes Kyuubi already have done the same thing. [1] https://help.aliyun.com/zh/emr/emr-on-ecs/user-guide/connect-to-kyuubi ## Types of changes 🔖 - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Test Plan 🧪 Manual test. ``` $ bin/beeline -u 'jdbc:kyuubi://0.0.0.0:10009/' Warning: beeline is deprecated and will be removed in the future, please use kyuubi-beeline instead. Connecting to jdbc:kyuubi://0.0.0.0:10009/ Connected to: Spark SQL (version 3.4.1) Driver: Kyuubi Project Hive JDBC Client (version 1.10.0-SNAPSHOT) Beeline version 1.10.0-SNAPSHOT by Apache Kyuubi 0: jdbc:kyuubi://0.0.0.0:10009/> ``` ``` $ bin/kyuubi-beeline -u 'jdbc:kyuubi://0.0.0.0:10009/' Connecting to jdbc:kyuubi://0.0.0.0:10009/ Connected to: Spark SQL (version 3.4.1) Driver: Kyuubi Project Hive JDBC Client (version 1.10.0-SNAPSHOT) Beeline version 1.10.0-SNAPSHOT by Apache Kyuubi 0: jdbc:kyuubi://0.0.0.0:10009/> ``` --- # Checklist 📝 - [x] This patch was not authored or co-authored using [Generative Tooling](https://www.apache.org/legal/generative-tooling.html) **Be nice. Be informative.** Closes #6239 from pan3793/kyuubi-beeline. Closes #6239 cec8f56e2 [Cheng Pan] docs b3446baf1 [Cheng Pan] docs 46a115077 [Cheng Pan] Remove `bin/beeline` to `bin/kyuubi-beeline` Authored-by: Cheng Pan <chengpan@apache.org> Signed-off-by: Cheng Pan <chengpan@apache.org>
74 lines
2.6 KiB
ReStructuredText
74 lines
2.6 KiB
ReStructuredText
.. Licensed to the Apache Software Foundation (ASF) under one or more
|
|
contributor license agreements. See the NOTICE file distributed with
|
|
this work for additional information regarding copyright ownership.
|
|
The ASF licenses this file to You under the Apache License, Version 2.0
|
|
(the "License"); you may not use this file except in compliance with
|
|
the License. You may obtain a copy of the License at
|
|
|
|
.. http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
.. Unless required by applicable law or agreed to in writing, software
|
|
distributed under the License is distributed on an "AS IS" BASIS,
|
|
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
See the License for the specific language governing permissions and
|
|
limitations under the License.
|
|
|
|
Inject Session Conf with Custom Config Advisor
|
|
==============================================
|
|
|
|
.. versionadded:: 1.5.0
|
|
|
|
Session Conf Advisor
|
|
--------------------
|
|
|
|
Kyuubi supports inject session configs with custom config advisor. It is usually used to append or overwrite session configs dynamically, so administrators of Kyuubi can have an ability to control the user specified configs.
|
|
|
|
The steps of injecting session configs
|
|
--------------------------------------
|
|
|
|
1. create a custom class which implements the ``org.apache.kyuubi.plugin.SessionConfAdvisor``.
|
|
2. compile and put the jar into ``$KYUUBI_HOME/jars``
|
|
3. adding configuration at ``kyuubi-defaults.conf``:
|
|
|
|
.. code-block:: java
|
|
|
|
kyuubi.session.conf.advisor=${classname}
|
|
|
|
The ``org.apache.kyuubi.plugin.SessionConfAdvisor`` has a zero-arg constructor, holds one method with user and session conf and returns a new conf map.
|
|
|
|
.. code-block:: java
|
|
|
|
public interface SessionConfAdvisor {
|
|
default Map<String, String> getConfOverlay(String user, Map<String, String> sessionConf) {
|
|
return Collections.EMPTY_MAP;
|
|
}
|
|
}
|
|
|
|
.. note:: The returned conf map will overwrite the original session conf.
|
|
|
|
Example
|
|
-------
|
|
|
|
We have a custom class ``CustomSessionConfAdvisor``:
|
|
|
|
.. code-block:: java
|
|
|
|
public class CustomSessionConfAdvisor implements SessionConfAdvisor {
|
|
@Override
|
|
Map<String, String> getConfOverlay(String user, Map<String, String> sessionConf) {
|
|
if ("uly".equals(user)) {
|
|
return Collections.singletonMap("spark.driver.memory", "1G");
|
|
} else {
|
|
return Collections.EMPTY_MAP;
|
|
}
|
|
}
|
|
}
|
|
|
|
If a user `uly` creates a connection with:
|
|
|
|
.. code-block:: java
|
|
|
|
jdbc:kyuubi://localhost:10009/;hive.server2.proxy.user=uly;#spark.driver.memory=2G
|
|
|
|
The final Spark application will allocate ``1G`` rather than ``2G`` for the driver jvm.
|