Raigor
Raigor
Hi community, This issue is for #18811, to refactor parameter definition in module **`shardingsphere-readwrite-splitting-distsql-parser`** ### Aim - [ ] Redefine identifier and literals in g4 grammar (Literals.g4, Keyword.g4) - [...
Hi community, This issue is for #18811, to refactor parameter definition in module **`shardingsphere-encrypt-distsql-parser`** ### Aim - [ ] Redefine identifier and literals in g4 grammar (Literals.g4, Keyword.g4) - [...
Hi community, This issue is for #18811, to refactor parameter definition in module **`shardingsphere-sharding-distsql-parser`** ### Aim - [ ] Redefine identifier and literals in g4 grammar (Literals.g4, Keyword.g4) - [...
Hi community, This issue is for #18811, to refactor parameter definition in module **`shardingsphere-shadow-distsql-parser`** ### Aim - [ ] Redefine identifier and literals in g4 grammar (Literals.g4, Keyword.g4) - [...
Hi community, This issue is for #18811, to refactor parameter definition in module **`shardingsphere-db-discovery-distsql-parser`** ### Aim - [ ] Redefine identifier and literals in g4 grammar (Literals.g4, Keyword.g4) - [...
## Feature Request ### Is your feature request related to a problem? No. ### Describe the feature you would like. In DistSQL, we can create shadow algorithms alone, but we...
`YamlDatabaseConfigurationImportExecutor` is used to implement the rule import function for `ImportDatabaseConfigurationExecutor`. But now `YamlDatabaseConfigurationImportExecutor` relies heavily on various features. In fact, it should use SPI to manage rules like `ExportDatabaseConfigurationExecutor`...
Now we have some syntax for querying SPI implementations (https://github.com/apache/shardingsphere/issues/28984) However, their implementation can be simplified. It is hoped that like `CountRuleStatement` and `RuleCountExecutor`, only a group of `statement` and...
Hi community, Now, in ShardingSphere-Proxy, we provide two privilege providers: `ALL_PERMITTED` and `DATABASE_PERMITTED`. Some users are confused when using it, especially in cluster mode, modifying the local yaml file does...
`Alter rule` is not a standard SQL, it belongs to the PG dialect. Therefore `AlterRuleStatement` should not exist under the `common` package. Since `ALTER RULE` is a PostgreSQL language extension...