FlyingZC opened a new issue, #27021:
URL: https://github.com/apache/shardingsphere/issues/27021

   # Background
   Hi community,
   This issue is for #26878.
   
   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 Oracle SQL parsing in 
ShardingSphere.
   
   More details:
   
https://shardingsphere.apache.org/document/current/en/reference/sharding/parse/
   
   # Task
   This issue is to support more oracle sql parse, as follows:
   ```sql
   CREATE CLUSTER cust_orders (customer_id NUMBER(6))
      SIZE 512 SINGLE TABLE HASHKEYS 100;
   ```
   
   ```sql
   CREATE CLUSTER personnel
      (department NUMBER(4))
   SIZE 512 
   STORAGE (initial 100K next 50K);
   ```
   
   ```sql
   CREATE CONTEXT
   DROP CONTEXT
   ```
   
   ```sql
   CREATE DATABASE LINK
   CREATE PUBLIC DATABASE LINK
   DROP DATABASE LINK
   DROP PUBLIC DATABASE LINK
   ```
   
   ```sql
   CREATE DATABASE LINK link_name CONNECT TO CURRENT_USER
     USING connect_string;
   ```
   
   # Process
   1. First confirm that this is a correct oracle sql syntax, if not please 
ignore;
   2. Compare SQL definitions in Oficial 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 Statment 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 Oracle 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]

Reply via email to