Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Type error in AzureDataFactory-AzureMLExecutePipelineActivityTypeProperties-mlPipelineParameters #31561

Open
HarveyLink opened this issue Nov 15, 2024 · 0 comments
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Data Factory Mgmt This issue is related to a management-plane library. Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@HarveyLink
Copy link
Member

API Spec link

API Spec version

2018-06-01

Describe the bug

Original customer issue: Azure/azure-sdk-for-net#45401
It's possible that the response value contains object type instead of string.
The x-ms-format should be dfe-key-object-value-pairs

Expected behavior

"x-ms-format": "dfe-key-object-value-pairs"

Actual behavior

"x-ms-format": "dfe-key-value-pairs"

Reproduction Steps

Call GetDataFactoryPipeline on a Pipeline with AzureMLExecutePipelineActivity that contains expression parameter

Environment

No response

@HarveyLink HarveyLink added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Nov 15, 2024
@v-jiaodi v-jiaodi added the Mgmt This issue is related to a management-plane library. label Nov 18, 2024
@v-jiaodi v-jiaodi added Data Factory Service Attention Workflow: This issue is responsible by Azure service team. labels Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Data Factory Mgmt This issue is related to a management-plane library. Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants