This is a placeholder for Apache SkyWalking GSOC 2023 ideas, we are currently brainstorming for projects and will update asap. 

There will be at least two projects, one around AIOps algorithms.

Apache ShardingSphere

Apache ShardingSphere is positioned as a Database Plus, and aims at building a standard layer and ecosystem above heterogeneous databases. It focuses on how to reuse existing databases and their respective upper layer, rather than creating a new database. The goal is to minimize or eliminate the challenges caused by underlying databases fragmentation.

Page: https://shardingsphere.apache.org
Github: https://github.com/apache/shardingsphere 

Background

The ShardingSphere SQL federation engine provides support for complex SQL statements, and it can well support cross-database join queries, subqueries, aggregation queries and other statements. An important part of SQL federation engine is to convert the SQL statement parsed by ShardingSphere into SqlNode, so that Calcite can be used to implement SQL optimization and federated query.

Task

This issue is to solve the MySQL exception that occurs during SQLNodeConverterEngine conversion. The specific case list is as follows.

• select_char
• select_extract
• select_from_dual
• select_from_with_table
• select_group_by_with_having_and_window
• select_not_between_with_single_table
• select_not_in_with_single_table
• select_substring
• select_trim
• select_weight_string
• select_where_with_bit_expr_with_ampersand
• select_where_with_bit_expr_with_caret
• select_where_with_bit_expr_with_div
• select_where_with_bit_expr_with_minus_interval
• select_where_with_bit_expr_with_mod
• select_where_with_bit_expr_with_mod_sign
• select_where_with_bit_expr_with_plus_interval
• select_where_with_bit_expr_with_signed_left_shift
• select_where_with_bit_expr_with_signed_right_shift
• select_where_with_bit_expr_with_vertical_bar
• select_where_with_boolean_primary_with_comparison_subquery
• select_where_with_boolean_primary_with_is
• select_where_with_boolean_primary_with_is_not
• select_where_with_boolean_primary_with_null_safe
• select_where_with_expr_with_and_sign
• select_where_with_expr_with_is
• select_where_with_expr_with_is_not
• select_where_with_expr_with_not
• select_where_with_expr_with_not_sign
• select_where_with_expr_with_or_sign
• select_where_with_expr_with_xor
• select_where_with_predicate_with_in_subquery
• select_where_with_predicate_with_regexp
• select_where_with_predicate_with_sounds_like
• select_where_with_simple_expr_with_collate
• select_where_with_simple_expr_with_match
• select_where_with_simple_expr_with_not
• select_where_with_simple_expr_with_odbc_escape_syntax
• select_where_with_simple_expr_with_row
• select_where_with_simple_expr_with_tilde
• select_where_with_simple_expr_with_variable
• select_window_function
• select_with_assignment_operator
• select_with_assignment_operator_and_keyword
• select_with_case_expression
• select_with_collate_with_marker
• select_with_date_format_function
• select_with_exists_sub_query_with_project
• select_with_function_name
• select_with_json_value_return_type
• select_with_match_against
• select_with_regexp
• select_with_schema_name_in_column_projection
• select_with_schema_name_in_shorthand_projection
• select_with_spatial_function
• select_with_trim_expr
• select_with_trim_expr_from_expr

You need to compare the difference between actual and expected, and then correct the logic in SQLNodeConverterEngine so that actual can be consistent with expected.

After you make changes, remember to add case to SUPPORTED_SQL_CASE_IDS to ensure it can be tested.

 
Notice, these issues can be a good example.
https://github.com/apache/shardingsphere/pull/14492

Relevant Skills

 
1. Master JAVA language

2. Have a basic understanding of Antlr g4 file

3. Be familiar with MySQL and Calcite SqlNode

Targets files

 
SQLNodeConverterEngineIT

https://github.com/apache/shardingsphere/blob/master/test/it/optimizer/src/test/java/org/apache/shardingsphere/test/it/optimize/SQLNodeConverterEngineIT.java 

Mentor

Zhengqiang Duan, PMC of Apache ShardingSphere, duanzhengqiang@apache.org

Chuxin Chen, Committer of Apache ShardingSphere, tuichenchuxin@apache.org

Apache ShardingSphere

Apache ShardingSphere is positioned as a Database Plus, and aims at building a standard layer and ecosystem above heterogeneous databases. It focuses on how to reuse existing databases and their respective upper layer, rather than creating a new database. The goal is to minimize or eliminate the challenges caused by underlying databases fragmentation.

Page: https://shardingsphere.apache.org
Github: https://github.com/apache/shardingsphere 

Background

ShardingSphere provides two adapters: ShardingSphere-JDBC and ShardingSphere-Proxy.

Now, ShardingSphere uses logback for logging, but consider the following situations:

• Users may need to switch the logging framework to meet special needs, such as log4j2 can provide better asynchronous performance;
• When using the JDBC adapter, the user application may not use logback, which may cause some conflicts.

Why doesn't the log facade suffice? Because ShardingSphere provides users with clustered logging configurations (such as changing the log level online), this requires dynamic construction of logger, which cannot be achieved with only the log facade.

Task

1. Design and implement logging SPI to support multiple logging frameworks (such as logback and log4j2)
2. Allow users to choose which logging framework to use through the logging rule

Relevant Skills

1. Master JAVA language

2. Basic knowledge of logback and log4j2

3. Maven

Mentor

Longtao Jiang, Committer of Apache ShardingSphere, jianglongtao@apache.org

Apache ShardingSphere

Apache ShardingSphere is positioned as a Database Plus, and aims at building a standard layer and ecosystem above heterogeneous databases. It focuses on how to reuse existing databases and their respective upper layer, rather than creating a new database. The goal is to minimize or eliminate the challenges caused by underlying databases fragmentation.

Page: https://shardingsphere.apache.org
Github: https://github.com/apache/shardingsphere 

Background

ShardingSphere has designed its own metadata database to simulate metadata queries that support various databases.

More details:

https://github.com/apache/shardingsphere/issues/21268
https://github.com/apache/shardingsphere/issues/22052

Task

• Support PostgreSQL And openGauss `\d tableName`
• Support PostgreSQL And openGauss `\d+`
• Support PostgreSQL And openGauss `\d+ tableName`
• Support PostgreSQL And openGauss `l`
• Support query for MySQL metadata `TABLES`
• Support query for MySQL metadata `COLUMNS`
• Support query for MySQL metadata `schemata`
• Support query for MySQL metadata `ENGINES`
• Support query for MySQL metadata `FILES`
• Support query for MySQL metadata `VIEWS`

Notice, these issues can be a good example.

https://github.com/apache/shardingsphere/pull/22053
https://github.com/apache/shardingsphere/pull/22057/
https://github.com/apache/shardingsphere/pull/22166/
https://github.com/apache/shardingsphere/pull/22182

Relevant Skills

•  Master JAVA language
•  Have a basic understanding of Zookeeper
•  Be familiar with MySQL/Postgres SQLs 

Mentor

Chuxin Chen, Committer of Apache ShardingSphere, tuichenchuxin@apache.org

Zhengqiang Duan, PMC of Apache ShardingSphere, duanzhengqiang@apache.org