[MDEV-14074] Please implement ignorable SET PROXY command Created: 2017-10-16  Updated: 2022-05-30  Resolved: 2022-05-30

Status: Closed
Project: MariaDB Server
Component/s: Parser
Fix Version/s: N/A

Type: Task Priority: Minor
Reporter: Michaël de groot Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None

Issue Links:
Relates
relates to MXS-1475 Create on-demand caching that can eas... Closed

 Description   

Hi,

Please create a SET PROXY command in the parser. The PROXY keyword indicates that it is actually a proxy setting (such as MaxScale). Normally, the SET PROXY command is not sent to the server but in some cases (for example in development environment or if MaxScale is removed) the server may receive it.

Please ignore any SET PROXY command, but produce a warning that the proxy is not properly configured.

Thank you,
Michaël



 Comments   
Comment by Ralf Gebhardt [ 2017-12-22 ]

michaeldg Why not using comments like /!maxscale SET ..../ in a query? This would allow all kinds of commands to be sent to MaxScale while the Server will ignore them. Adding Proxy awareness to the server would still limit the use case to exactly the statements filtered by the parser.

Comment by Johan Wikman [ 2018-03-16 ]

In MXS-1475 we have implemented it so that user variables with the prefix @maxscale. are used for controlling MaxScale.
For instance:

set @maxscale.cache.soft_ttl=600;
 
SELECT a, b FROM table;

Generated at Thu Feb 08 08:10:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.