[jira] [Created] (COMDEV-491) Apache ShardingSphere: Enhance ComputeNode reconciliation
Chuxin Chen created COMDEV-491: -- Summary: Apache ShardingSphere: Enhance ComputeNode reconciliation Key: COMDEV-491 URL: https://issues.apache.org/jira/browse/COMDEV-491 Project: Community Development Issue Type: Improvement Components: GSoC/Mentoring ideas Reporter: Chuxin Chen 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/] Github: [https://github.com/apache/shardingsphere |https://github.com/apache/shardingsphere%C2%A0] h1. Background There is a proposal about new CRD Cluster and ComputeNode as belows: * [WIP: [New Feature] Introduce new CRD Cluster #167|https://github.com/apache/shardingsphere-on-cloud/issues/167] * [[Feat] Introduce new CRD as ComputeNode for better usability #166|https://github.com/apache/shardingsphere-on-cloud/issues/166] Currently we try to promote ComputeNode as major CRD to represent a special ShardingSphere Proxy deployment. And plan to use Cluster indicating a special ShardingSphere Proxy cluster. h1. Task This issue is to enhance ComputeNode reconciliation availability. The specific case list is as follows. * Add IT test case for Deployment spec volume * Add IT test case for Deployment spec template init containers * Add IT test case for Deployment spec template spec containers * Add IT test case for Deployment spec volume mounts * Add IT test case for Deployment spec container ports * Add IT test case for Deployment spec container image tag * Add IT test case for Service spec ports * Add IT test case for ConfigMap data serverconfig * Add IT test case for ConfigMap data logback You need to Notice, these issues can be a good example. * [chore: add more Ginkgo tests for ComputeNode #203|https://github.com/apache/shardingsphere-on-cloud/pull/203] h1. Relevant Skills # Master Go language, Ginkgo test framework # Have a basic understanding of Apache ShardingSphere Concepts # Be familiar with Kubernetes Operator, kubebuilder framework h1. Targets files ComputeNode IT - [https://github.com/apache/shardingsphere-on-cloud/blob/main/shardingsphere-operator/pkg/reconcile/computenode/compute_node_test.go] -- 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
[jira] [Updated] (COMDEV-491) Apache ShardingSphere: Enhance ComputeNode reconciliation
[ https://issues.apache.org/jira/browse/COMDEV-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuxin Chen updated COMDEV-491: --- 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/] Github: [https://github.com/apache/shardingsphere |https://github.com/apache/shardingsphere%C2%A0] h1. Background There is a proposal about new CRD Cluster and ComputeNode as belows: * [WIP: [New Feature] Introduce new CRD Cluster #167|https://github.com/apache/shardingsphere-on-cloud/issues/167] * [[Feat] Introduce new CRD as ComputeNode for better usability #166|https://github.com/apache/shardingsphere-on-cloud/issues/166] Currently we try to promote ComputeNode as major CRD to represent a special ShardingSphere Proxy deployment. And plan to use Cluster indicating a special ShardingSphere Proxy cluster. h1. Task This issue is to enhance ComputeNode reconciliation availability. The specific case list is as follows. * Add IT test case for Deployment spec volume * Add IT test case for Deployment spec template init containers * Add IT test case for Deployment spec template spec containers * Add IT test case for Deployment spec volume mounts * Add IT test case for Deployment spec container ports * Add IT test case for Deployment spec container image tag * Add IT test case for Service spec ports * Add IT test case for ConfigMap data serverconfig * Add IT test case for ConfigMap data logback You need to Notice, these issues can be a good example. * [chore: add more Ginkgo tests for ComputeNode #203|https://github.com/apache/shardingsphere-on-cloud/pull/203] h1. Relevant Skills # Master Go language, Ginkgo test framework # Have a basic understanding of Apache ShardingSphere Concepts # Be familiar with Kubernetes Operator, kubebuilder framework h1. Targets files ComputeNode IT - [https://github.com/apache/shardingsphere-on-cloud/blob/main/shardingsphere-operator/pkg/reconcile/computenode/compute_node_test.go] h3. Mentor Liyao Miao, Committer of Apache ShardingSphere, maxwel...@126.com 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/] Github: [https://github.com/apache/shardingsphere |https://github.com/apache/shardingsphere%C2%A0] h1. Background There is a proposal about new CRD Cluster and ComputeNode as belows: * [WIP: [New Feature] Introduce new CRD Cluster #167|https://github.com/apache/shardingsphere-on-cloud/issues/167] * [[Feat] Introduce new CRD as ComputeNode for better usability #166|https://github.com/apache/shardingsphere-on-cloud/issues/166] Currently we try to promote ComputeNode as major CRD to represent a special ShardingSphere Proxy deployment. And plan to use Cluster indicating a special ShardingSphere Proxy cluster. h1. Task This issue is to enhance ComputeNode reconciliation availability. The specific case list is as follows. * Add IT test case for Deployment spec volume * Add IT test case for Deployment spec template init containers * Add IT test case for Deployment spec template spec containers * Add IT test case for Deployment spec volume mounts * Add IT test case for Deployment spec container ports * Add IT test case for Deployment spec container image tag * Add IT test case for Service spec ports * Add IT test case for ConfigMap data serverconfig * Add IT test case for ConfigMap data logback You need to Notice, these issues can be a good example. * [chore: add more Ginkgo tests for ComputeNode #203|https://github.com/apache/shardingsphere-on-cloud/pull/203] h1. Relevant Skills # Master Go language, Ginkgo test framework # Have a basic understanding of Apache ShardingSphere Concepts # Be familiar with Kubernetes Operator, kubebuilder framework h1. Targets files ComputeNode IT - [https://github.com/apache/shardingsphere-on-cloud/blob/main/shardingsphere-operator/pkg/reconcile/computenode/compute_node_test.go] > Apache ShardingSphere: Enhance ComputeNode reconciliation > - > > Key: COMDEV-491 > URL: https://issues.apache.org/jira/browse/COMDEV-491 > Project: Community Development > Issue Type:
[jira] [Updated] (COMDEV-491) Apache ShardingSphere: Enhance ComputeNode reconciliation
[ https://issues.apache.org/jira/browse/COMDEV-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuxin Chen updated COMDEV-491: --- 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/] Github: [https://github.com/apache/shardingsphere |https://github.com/apache/shardingsphere%C2%A0] h1. Background There is a proposal about new CRD Cluster and ComputeNode as belows: * [WIP: [New Feature] Introduce new CRD Cluster #167|https://github.com/apache/shardingsphere-on-cloud/issues/167] * [[Feat] Introduce new CRD as ComputeNode for better usability #166|https://github.com/apache/shardingsphere-on-cloud/issues/166] Currently we try to promote ComputeNode as major CRD to represent a special ShardingSphere Proxy deployment. And plan to use Cluster indicating a special ShardingSphere Proxy cluster. h1. Task This issue is to enhance ComputeNode reconciliation availability. The specific case list is as follows. * Add IT test case for Deployment spec volume * Add IT test case for Deployment spec template init containers * Add IT test case for Deployment spec template spec containers * Add IT test case for Deployment spec volume mounts * Add IT test case for Deployment spec container ports * Add IT test case for Deployment spec container image tag * Add IT test case for Service spec ports * Add IT test case for ConfigMap data serverconfig * Add IT test case for ConfigMap data logback Notice, these issues can be a good example. * [chore: add more Ginkgo tests for ComputeNode #203|https://github.com/apache/shardingsphere-on-cloud/pull/203] h1. Relevant Skills # Master Go language, Ginkgo test framework # Have a basic understanding of Apache ShardingSphere Concepts # Be familiar with Kubernetes Operator, kubebuilder framework h1. Targets files ComputeNode IT - [https://github.com/apache/shardingsphere-on-cloud/blob/main/shardingsphere-operator/pkg/reconcile/computenode/compute_node_test.go] h3. Mentor Liyao Miao, Committer of Apache ShardingSphere, miaoli...@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/] Github: [https://github.com/apache/shardingsphere |https://github.com/apache/shardingsphere%C2%A0] h1. Background There is a proposal about new CRD Cluster and ComputeNode as belows: * [WIP: [New Feature] Introduce new CRD Cluster #167|https://github.com/apache/shardingsphere-on-cloud/issues/167] * [[Feat] Introduce new CRD as ComputeNode for better usability #166|https://github.com/apache/shardingsphere-on-cloud/issues/166] Currently we try to promote ComputeNode as major CRD to represent a special ShardingSphere Proxy deployment. And plan to use Cluster indicating a special ShardingSphere Proxy cluster. h1. Task This issue is to enhance ComputeNode reconciliation availability. The specific case list is as follows. * Add IT test case for Deployment spec volume * Add IT test case for Deployment spec template init containers * Add IT test case for Deployment spec template spec containers * Add IT test case for Deployment spec volume mounts * Add IT test case for Deployment spec container ports * Add IT test case for Deployment spec container image tag * Add IT test case for Service spec ports * Add IT test case for ConfigMap data serverconfig * Add IT test case for ConfigMap data logback You need to Notice, these issues can be a good example. * [chore: add more Ginkgo tests for ComputeNode #203|https://github.com/apache/shardingsphere-on-cloud/pull/203] h1. Relevant Skills # Master Go language, Ginkgo test framework # Have a basic understanding of Apache ShardingSphere Concepts # Be familiar with Kubernetes Operator, kubebuilder framework h1. Targets files ComputeNode IT - [https://github.com/apache/shardingsphere-on-cloud/blob/main/shardingsphere-operator/pkg/reconcile/computenode/compute_node_test.go] h3. Mentor Liyao Miao, Committer of Apache ShardingSphere, maxwel...@126.com > Apache ShardingSphere: Enhance ComputeNode reconciliation > - > > Key: COMDEV-491 > URL: https://issues.apache.org/jira/browse/COMDEV-49
[Imaging] PR #278: [...] reduce Cyclomatic
Le sam. 18 févr. 2023 à 01:33, garydgregory (via GitHub) a écrit : > > > garydgregory commented on PR #278: > URL: > https://github.com/apache/commons-imaging/pull/278#issuecomment-1435423300 > >This might satisfy some static code analysis but it's -1 for me since this > PR now wastes memory allocating and building a List every single time. A bad > trade off IMO. > >To make this even worth, the PR also looses a code comment. Was this code > change machine generated? That often happens with machine transforms. > >What do others think? Shouldn't it be a "switch"? Regards, Gilles - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
