Skip to content

[DOC] Fix non-consecutive header level increase #7339

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dnskr wants to merge 1 commit into from
+11 −11
Closed

[DOC] Fix non-consecutive header level increase #7339

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions docs/connector/spark/kudu.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,21 +39,21 @@ Before integrating Kyuubi with Kudu, we strongly suggest that you integrate and

## Kudu Integration with Kyuubi

#### Install Kudu Spark Dependency
### Install Kudu Spark Dependency

Confirm your Kudu cluster version and download the corresponding kudu spark dependency library, such as [org.apache.kudu:kudu-spark3_2.12-1.14.0](https://repo1.maven.org/maven2/org/apache/kudu/kudu-spark3_2.12/1.14.0/kudu-spark3_2.12-1.14.0.jar) to `$SPARK_HOME`/jars.

#### Start Kyuubi
### Start Kyuubi

Now, you can start Kyuubi server with this kudu embedded Spark distribution.

#### Start Beeline Or Other Client You Prefer
### Start Beeline Or Other Client You Prefer

```shell
bin/kyuubi-beeline -u 'jdbc:kyuubi://<host>:<port>/;principal=<if kerberized>;#spark.yarn.queue=kyuubi_test'
```

#### Register Kudu table as Spark Temporary view
### Register Kudu table as Spark Temporary view

```sql
CREATE TEMPORARY VIEW kudutest
Expand All @@ -79,7 +79,7 @@ options (
2 rows selected (0.29 seconds)
```

#### Query Kudu Table
### Query Kudu Table

```sql
0: jdbc:kyuubi://spark5.jd.163.org:10009/> select * from kudutest;
Expand All @@ -100,7 +100,7 @@ options (
5 rows selected (1.083 seconds)
```

#### Join Kudu table with Hive table
### Join Kudu table with Hive table

```sql
0: jdbc:kyuubi://spark5.jd.163.org:10009/> select t1.*, t2.* from hive_tbl t1 join kudutest t2 on t1.userid=t2.userid+1;
Expand All @@ -118,7 +118,7 @@ options (
3 rows selected (1.63 seconds)
```

#### Insert to Kudu table
### Insert to Kudu table

You should notice that only `INSERT INTO` is supported by Kudu, `OVERWRITE` data is not supported

Expand Down
8 changes: 4 additions & 4 deletions docs/monitor/logging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,11 +187,11 @@ Meanwhile, it also includes how all the services of an engine start/stop, how it

In general, when an exception occurs, we are able to find more information and clues in the engine's logs.

#### Configuring Engine Logging
### Configuring Engine Logging

Please refer to Apache Spark online documentation [Configuring Logging](https://spark.apache.org/docs/latest/configuration.html#configuring-logging) for instructions.

#### Where to Find the Engine Log
### Where to Find the Engine Log

The engine logs are located differently based on the deploy mode and the cluster manager.
When using local backend or `client` deploy mode for other cluster managers, such as YARN, you can find the whole engine log in `$KYUUBI_WORK_DIR_ROOT/${session username}/kyuubi-spark-sql-engine.log.${num}`.
Expand All @@ -207,11 +207,11 @@ Meanwhile, it also includes how all the services of an engine start/stop, how do

In general, when an exception occurs, we are able to find more information and clues in the engine's logs.

#### Configuring Engine Logging
### Configuring Engine Logging

Please refer to Apache Flink online documentation [Configuring Logging](https://nightlies.apache.org/flink/flink-docs-stable/docs/deployment/advanced/logging) for instructions.

#### Where to Find the Engine Log
### Where to Find the Engine Log

The engine logs are located differently based on the deploy mode and the cluster manager.
When using local backend or `client` deploy mode for other cluster managers, such as YARN, you can find the whole engine log in `$KYUUBI_WORK_DIR_ROOT/${session username}/kyuubi-flink-sql-engine.log.${num}`.
Expand Down