wenjin272 opened a new issue, #1196:
URL: https://github.com/apache/flink-agents/issues/1196
### Search before asking
- [x] I searched existing issues for duplicates; related work is linked
below where applicable.
### Description
This is a child issue of #1055.
#### Problem
The integration uses the DashScope SDK/API, but public chat/embedding
classes, Python module paths, ResourceName constants, and YAML aliases still
use Tongyi naming. This makes the integration identity inconsistent across
configuration and code.
Renaming only the displayed names is insufficient: ResourceName values
include fully qualified Python class names that can be stored in serialized
ResourceDescriptors.
#### Proposed direction
Introduce canonical DashScope names for the affected chat/embedding modules,
connection/setup classes, ResourceName constants, and YAML aliases. Keep Java
resource references, Python exports, and YAML resolution aligned.
Explicitly choose a migration policy: retain old `Tongyi*` symbols/module
paths/constants and `tongyi` aliases as deprecated compatibility entry points,
or document an intentional breaking migration. Assess stored descriptors/plans
and existing state that may reference old fully qualified names; do not
silently leave those paths unloadable.
#### Acceptance criteria
- Canonical DashScope names resolve consistently through Python, Java
resource declarations, and YAML.
- The chosen old-name compatibility/migration policy is documented and
tested, including serialized descriptors containing old class paths.
- Provider behavior is unchanged by the naming cleanup; chat and embedding
examples/docs are updated consistently.
Relevant code:
`python/flink_agents/integrations/{chat_models,embedding_models}/tongyi_*`,
Java/Python ResourceName definitions, and Java/Python YAML aliases.
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
--
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]
