shangeyao opened a new pull request, #4424:
URL: https://github.com/apache/streampark/pull/4424

   ## Summary
   
   - Add `.sonarcloud.properties` and `sonar-project.properties` with ASF 
license headers
   - Configure CPD exclusions for versioned shims, connector, kubernetes, and 
packer modules
   - Document multicriteria issue suppressions for intentional Scala-to-Java 
migration patterns
   
   Closes #4423
   
   ## Motivation
   
   SonarCloud reports hundreds of issues on migration PRs (#4418, #4419, #4420) 
that are **configuration-level** concerns (shims naming, connector 
`Serializable` fields, deprecated Flink API bridges, SQL dialect regex, client 
exception stubs). Keeping these suppressions in feature PRs makes review harder 
and couples unrelated changes.
   
   This PR isolates Sonar configuration so feature PRs can focus on code fixes 
only.
   
   ## Suppression rules added
   
   | Rule | Scope | Reason |
   |------|-------|--------|
   | `javasecurity:S2083` | `SafePathUtils` | Validated user config paths |
   | `java:S100` | `streampark-flink-shims*/**` | Scala-compat `$method` names |
   | `java:S1948` | `streampark-flink-connector/**` | Connector config 
serialization |
   | `java:S6355` / `S1123` / `S1133` | Shims + `FlinkStreamTableTrait` | 
Deprecated Flink API bridges |
   | `java:S8786` | `SqlConvertUtils` | MySQL→PG dialect regex |
   | `java:S112` | `streampark-*-client*/**` | Client exception propagation |
   | `java:S1186` | `Silent*.java` | Intentional no-op watchers |
   
   ## Test plan
   
   - [ ] SonarCloud scan on this PR shows only the two property files changed
   - [ ] After merge, re-run Sonar on #4418 and confirm open-issue count drops 
without QG regressions from config drift
   - [ ] Verify `.sonarcloud.properties` is picked up by automatic analysis
   
   
   Made with [Cursor](https://cursor.com)


-- 
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