Open yandongxiao opened 2 months ago
@yandongxiao thanks for the contribution. I wonder whether or not we only support alter use "xxx" set property
statement. And we don't support set property
anymore. This will make people can do this only in one way. We'd better to not provide many ways to finish one thing.
Currently, we have reused SHOW PROPERTY
to allow users to obtain a list of all properties. If users are aware of the SET PROPERTY
syntax, they will naturally attempt to use SET PROPERTY
to set user property information.
In the user documentation, we will only write the syntax of ALTER USER xxx SET PROPERTIES
, guiding users to use the new syntax. I think it might be a good choice to remove the SET PROPERTY
syntax (and perhaps also SHOW PROPERTY
) in a future version.
@yandongxiao thanks for the contribution. I wonder whether or not we only support
alter use "xxx" set property
statement. And we don't supportset property
anymore. This will make people can do this only in one way. We'd better to not provide many ways to finish one thing.
Done
@yandongxiao
Besides SHOW PROPERTIES
, is there other command to show user's properties?
@yandongxiao Besides
SHOW PROPERTIES
, is there other command to show user's properties?
I did not find any other commands.
Feature request
In order to let the newly established JDBC connection default to connecting to the external catalog and the database, and since it is not possible to specify the external catalog and external database in the BI tool (client side), so we can save user's properties on the FE(the server side).
When the user connects to FE SQL, the Session variables need to be initialized according to the user's attribute information.
We can support to set more attributes, including: catalog, database, and session.xxx.
Describe the solution you'd like
We can use the following methods to CRUD user's properties
For example:
The implementation details to consider
When setting up user's property:
When the user connects to FE SQL:
When Replaying Journal: