[
https://issues.apache.org/jira/browse/COMDEV-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Longtao Jiang updated COMDEV-490:
---------------------------------
Description:
h2. 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|https://shardingsphere.apache.org/]
{*}Github{*}: [https://github.com/apache/shardingsphere]
h2. 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.
h2. 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|https://github.com/apache/shardingsphere/tree/master/kernel/logging]
h2. Relevant Skills
1. Master JAVA language
2. Basic knowledge of logback and log4j2
3. Maven
h3. Mentor
Longtao Jiang, Committer of Apache ShardingSphere,
[jianglong...@apache.org|mailto:jianglong...@apache.org]
Trista Pan, PMC of Apache ShardingSphere,
[panj...@apache.org|mailto:panj...@apache.org]
was:
h2. 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|https://shardingsphere.apache.org/]
{*}Github{*}: [https://github.com/apache/shardingsphere]
h2. 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.
h2. 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|https://github.com/apache/shardingsphere/tree/master/kernel/logging]
h2. Relevant Skills
1. Master JAVA language
2. Basic knowledge of logback and log4j2
3. Maven
h3. Mentor
Longtao Jiang, Committer of Apache ShardingSphere, jianglong...@apache.org
> Apache ShardingSphere: Add the feature of switching logging framework
> ---------------------------------------------------------------------
>
> Key: COMDEV-490
> URL: https://issues.apache.org/jira/browse/COMDEV-490
> Project: Community Development
> Issue Type: Improvement
> Components: GSoC/Mentoring ideas
> Reporter: Longtao Jiang
> Priority: Major
> Labels: ShardingSphere, gsoc2023, mentor
>
> h2. 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|https://shardingsphere.apache.org/]
> {*}Github{*}: [https://github.com/apache/shardingsphere]
> h2. 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.
> h2. 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|https://github.com/apache/shardingsphere/tree/master/kernel/logging]
> h2. Relevant Skills
> 1. Master JAVA language
> 2. Basic knowledge of logback and log4j2
> 3. Maven
> h3. Mentor
> Longtao Jiang, Committer of Apache ShardingSphere,
> [jianglong...@apache.org|mailto:jianglong...@apache.org]
> Trista Pan, PMC of Apache ShardingSphere,
> [panj...@apache.org|mailto:panj...@apache.org]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
