database/doris
2
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity
Files
e3daa9580a498ddc19ce1c7b318cc4e3a1c3da01
doris/new-docs/en/sql-manual/sql-reference-v2/Show-Statements/SHOW-PROPERTY.md
jiafeng.zhang c02625efa9 [refactor][doc] Doris official website new version documentation (#8757) 
I started a discussion on this before, you can check it in the mail group

https://lists.apache.org/thread/o770bc3k623kyfks2mzkt21qsc4g6328

In order to facilitate everyone to organize the documents, I created a new-docs directory under the incubator-doris directory. The new directory structure is below this. I just created a directory structure here, which needs to be rearranged.

In the data import scenario, in order to take into account the viewing habits of previous users, the import is organized in two ways:

1. According to the usage scenario: This will give users clearer guidance. For example, the user is the data source of kafka, then the user can directly select the routine to load
2. According to the import method: it is the introduction of the various import methods we provided before

In order to facilitate everyone to run and debug locally, I migrated the entire .vuepress under the original document. After completion, you only need to delete the original docs directory and rename the new new-docs directory to docs. At the same time, you can also run it locally, so that you can organize documents and know the content of each document directory.

In the local debugging execution, switch to the new-docs directory and execute the following command:

````
npm install
npm run dev
````
then through the browser
http://ip:port/zh-CN
http://ip:port/en
2022-03-31 12:01:02 +08:00

1.7 KiB
Raw Blame History

title, language
title language
SHOW-PROPERTY zh-CN

SHOW-PROPERTY

Description

This statement is used to view the attributes of the user

SHOW PROPERTY [FOR user] [LIKE key];

  • user

    View the attributes of the specified user. If not specified, check the current user's.

  • LIKE

    Fuzzy matching can be done by attribute name.

Return result description:

mysql> show property like'%connection%';
+----------------------+-------+
| Key | Value |
+----------------------+-------+
| max_user_connections | 100 |
+----------------------+-------+
1 row in set (0.01 sec)

  • Key

    Property name.

  • Value

    Attribute value.

Example

  1. View the attributes of the jack user

    SHOW PROPERTY FOR'jack';

  2. View the attribute of jack user connection limit

    SHOW PROPERTY FOR'jack' LIKE'%connection%';

Keywords

SHOW, PROPERTY

Best Practice