FlyingZC opened a new issue, #27641: URL: https://github.com/apache/shardingsphere/issues/27641
# Background Hi community, ShardingSphere parser engine helps users parse a SQL to get the AST (Abstract Syntax Tree) and visit this tree to get SQLStatement (Java Object). Currently, we are planning to enhance the support for openGauss SQL parsing in ShardingSphere. More details: https://shardingsphere.apache.org/document/current/en/reference/sharding/parse/ # Task This issue is to support more openGauss sql parse, as follows: ```sql insert into doc(content) select 'abcd1234' from generate_series(1,10000) as content; INSERT 0 100000 --删除9000条数据 ``` ```sql delete from doc where id <= 9000; DELETE 9000 --optimize表 ``` ```sql optimize table doc; VACUUM --optimize表（查看处理详情） ``` ```sql optimize verbose table doc; INFO: vacuuming "public.doc"(primary pid=24692) INFO: "doc": found 9000 removable, 1000 nonremovable row versions in 55 pages(primary pid=24692) DETAIL: 0 dead row versions cannot be removed yet. CPU 0.00s/0.04u sec elapsed 0.04 sec. INFO: analyzing "public.doc"(primary pid=24692) INFO: ANALYZE INFO : "doc": scanned 6 of 6 pages, containing 1000 live rows and 0 dead rows; ``` ```sql BEGIN NULL; END; / --创建演示表格： ``` # Process 1. First confirm that this is a correct openGauss sql syntax, if not please leave a message under the issue and ignore it; 2. Compare SQL definitions in Official SQL Doc and ShardingSphere SQL Doc; 3. If there is any difference in ShardingSphere SQL Doc, please correct them by referring to the Official SQL Doc; 4. Run mvn install the current_file_module; 5. Check whether there are any exceptions. If indeed, please fix them. (Especially xxxVisitor.class); 6. Add new corresponding SQL case in SQL Cases and expected parsed result in Expected Statement XML; 7. Run SQLParserParameterizedTest to make sure no exceptions. # Relevant Skills 1. Master JAVA language 2. Have a basic understanding of Antlr `g4` file 3. Be familiar with openGauss SQLs -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
