You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now, when overriding the original model name by setting a target model name, only one fixed model can be configured; mapping configurations are not supported.
But the actual underlying mechanism is supported. A rule that is essentially a global mapping has been configured, and the following is the actual effective configuration:
It can support configuring more mapping strategies, for example:
apiVersion: extensions.higress.io/v1alpha1kind: WasmPluginmetadata:
name: model-mapper.internalnamespace: higress-systemspec:
defaultConfigDisable: truefailStrategy: FAIL_OPENmatchRules:
- config:
modelMapping:
'gpt-4-*': "qwen-max"'gpt-4o': "qwen-vl-plus"'*': "qwen-turbo"configDisable: false# This configuration takes effect when the following ingress and service match simultaneously.ingress:
- ai-route-dashscope.internalservice:
- llm-dashscope.internal.dnsphase: AUTHNpriority: 800url: oci://higress-registry.cn-hangzhou.cr.aliyuncs.com/plugins/model-mapper:1.0.0
For an introduction to the configuration of the model-mapper plugin, you can refer to this:
Yes, can we change the current target model input box to a "Model Mapping" button? After clicking, the key-value pairs can be configured in a pop-up window.
Now, when overriding the original model name by setting a target model name, only one fixed model can be configured; mapping configurations are not supported.

But the actual underlying mechanism is supported. A rule that is essentially a global mapping has been configured, and the following is the actual effective configuration:
It can support configuring more mapping strategies, for example:
For an introduction to the configuration of the model-mapper plugin, you can refer to this:
https://github.com/alibaba/higress/blob/main/plugins/wasm-cpp/extensions/model_mapper/README_EN.md
The text was updated successfully, but these errors were encountered: