linghengqian opened a new pull request, #38721:
URL: https://github.com/apache/shardingsphere/pull/38721
For #38682 .
Changes proposed in this pull request:
- Make ProxyConfigurationLoader compatible with classless runtime
environments. Split from https://github.com/apache/shardingsphere/pull/38682 .
- Previously, the test class
`org.apache.shardingsphere.test.natived.proxy.databases.**` passed the absolute
file system path to
`org.apache.shardingsphere.proxy.backend.config.ProxyConfigurationLoader`.
`org.apache.shardingsphere.proxy.backend.config.ProxyConfigurationLoader` first
resolved the path using the classpath, causing the GraalVM native image to
encounter abnormal paths during resource matching. Now,
`org.apache.shardingsphere.proxy.backend.config.ProxyConfigurationLoader` first
checks the file system path and then falls back to the classpath, avoiding
passing absolute path errors to
`java.lang.Class#getResource(java.lang.String)`. This is the root cause change
that fixed the CompressedGlobTrie in the GraalVM native image.
- As for why GraalVM CE for JDK 24.0.2 did not trigger this problem, but
GraalVM CE for JDK 25.0.2 did, I think only Oracle employees know the
answer.🤷♂️🤦♂️
---
Before committing this PR, I'm sure that I have checked the following
options:
- [x] My code follows the [code of
conduct](https://shardingsphere.apache.org/community/en/involved/conduct/code/)
of this project.
- [x] I have self-reviewed the commit code.
- [x] I have (or in comment I request) added corresponding labels for the
pull request.
- [x] I have passed maven check locally : `./mvnw clean install -B -T1C
-Dmaven.javadoc.skip -Dmaven.jacoco.skip -e`.
- [ ] I have made corresponding changes to the documentation.
- [ ] I have added corresponding unit tests for my changes.
- [ ] I have updated the Release Notes of the current development version.
For more details, see [Update Release
Note](https://shardingsphere.apache.org/community/en/involved/contribute/contributor/)
--
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]
