linghengqian opened a new issue, #33206:
URL: https://github.com/apache/shardingsphere/issues/33206
## Feature Request
**For English only**, other languages will not be accepted.
Please pay attention on issues you submitted, because we maybe need more
details.
If no response anymore and we cannot make decision by current information,
we will **close it**.
Please answer these questions before submitting your issue. Thanks!
### Is your feature request related to a problem?
- See #33179 .
### Describe the feature you would like.
- GraalVM Tracing Agent is collecting unreasonable GRMs for unit tests
related to `org.apache.shardingsphere.test.natived.proxy.features`. Taking
`org.apache.shardingsphere.test.natived.proxy.features.ShardingTest` as an
example, using `./mvnw -PgenerateMetadata -DskipNativeTests -T 1C -e clean test
native:metadata-copy` will write some error GraalVM Reachability Metadata
similar to the following to
`infra/reachability-metadata/src/main/resources/META-INF/native-image/org.apache.shardingsphere/generated-reachability-metadata/resource-config.json`.
This is apparently because the unit test is generating an absolute path for
the server side of ShardingSphere Proxy.
```json
{
"condition":{"typeReachable":"org.apache.shardingsphere.proxy.backend.config.ProxyConfigurationLoader"},
"pattern":"\\QcustomPath/shardingsphere/test/native/src/test/resources/test-native/yaml/proxy/databases/postgresql//global.yaml\\E"
}, {
"condition":{"typeReachable":"org.apache.shardingsphere.proxy.backend.config.ProxyConfigurationLoader"},
"pattern":"\\QcustomPath/shardingsphere/test/native/src/test/resources/test-native/yaml/proxy/databases/postgresql/\\E"
}, {
"condition":{"typeReachable":"org.apache.shardingsphere.proxy.backend.config.ProxyConfigurationLoader"},
"pattern":"\\QcustomPath/shardingsphere/test/native/src/test/resources/test-native/yaml/proxy/features/sharding//global.yaml\\E"
}, {
"condition":{"typeReachable":"org.apache.shardingsphere.proxy.backend.config.ProxyConfigurationLoader"},
"pattern":"\\QcustomPath/shardingsphere/test/native/src/test/resources/test-native/yaml/proxy/features/sharding/\\E"
}
```
- But in fact, there is no way to control the JSON content generated by
GraalVM Tracing Agent for `resource-config.json`. The current solution is to
require contributors to manually clean up this JSON in the documentation. This
is independent of whether Safe Composition of Metadata is enabled.
- The current issue aims to track the situation reported in
https://github.com/oracle/graal/issues/8417 and find a way to control the
generated content of `resource-config.json`.
--
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]
