Aias00 opened a new issue, #6443:
URL: https://github.com/apache/shenyu/issues/6443
### Current Behavior
The OpenGauss E2E docker-compose storage file starts `shenyu-admin` with
MySQL profile and MySQL dialect while pointing the datasource at an OpenGauss
database.
Evidence:
`shenyu-e2e/shenyu-e2e-case/compose/storage/shenyu-storage-opengauss.yml:56-61`
```yaml
- SPRING_PROFILES_ACTIVE=mysql
- shenyu.database.dialect=mysql
- spring.datasource.username=gaussdb
- spring.datasource.password=ShenYuE2E@123
-
spring.datasource.url=jdbc:opengauss://shenyu-opengauss:5432/shenyu?useUnicode=true&characterEncoding=utf-8&useSSL=false
```
The Kubernetes OpenGauss deployment uses the expected `og` profile:
`shenyu-e2e/shenyu-e2e-case/shenyu-e2e-case-storage/k8s/shenyu-deployment-opengauss.yml:38-45`
```yaml
- name: SPRING_PROFILES_ACTIVE
value: og
...
- name: spring.datasource.url
value:
jdbc:opengauss://shenyu-opengauss:5432/shenyu?useUnicode=true&characterEncoding=utf-8&useSSL=false
```
### Expected Behavior
The OpenGauss docker-compose E2E environment should use the OpenGauss admin
profile and dialect, consistent with `application-og.yml` and the Kubernetes
OpenGauss E2E manifests.
### Steps To Reproduce
Run the OpenGauss storage compose scenario:
```bash
cd shenyu-e2e/shenyu-e2e-case/compose/storage
docker compose -f shenyu-storage-opengauss.yml up
```
`shenyu-admin` is configured as MySQL while connecting to
`jdbc:opengauss://...`, so profile-specific SQL/dialect behavior is
inconsistent with the database under test.
### Suggested Fix
Change the compose environment to use the OpenGauss profile/dialect, for
example:
```yaml
- SPRING_PROFILES_ACTIVE=og
- shenyu.database.dialect=opengauss
```
or align with the exact dialect value expected by `application-og.yml`.
--
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]
