Skip to content

http-client-java, use polling metadata in emitter for mgmt - #9109

Merged
Weidong Xu (weidongxu-microsoft) merged 6 commits into
microsoft:mainfrom
weidongxu-microsoft:http-client-java_use-PollingMetadata
Dec 1, 2025
Merged

http-client-java, use polling metadata in emitter for mgmt#9109
Weidong Xu (weidongxu-microsoft) merged 6 commits into
microsoft:mainfrom
weidongxu-microsoft:http-client-java_use-PollingMetadata

Conversation

@microsoft-github-policy-servicemicrosoft-github-policy-serviceBot added the emitter:client:java Issue for the Java client emitter: @typespec/http-client-java label Nov 28, 2025
@github-actions

Copy link
Copy Markdown
Contributor

No changes needing a change description found.

@azure-sdk

Azure SDK Bot (azure-sdk) commented Nov 28, 2025

Copy link
Copy Markdown
Collaborator

You can try these changes here

🛝 Playground🌐 Website🛝 VSCode Extension

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall LGTM. Just add two comments for clarification purpose. Thanks!

Merged via the queue into microsoft:main with commit c03ab1aDec 1, 2025
26 checks passed
@weidongxu-microsoft
Weidong Xu (weidongxu-microsoft) deleted the http-client-java_use-PollingMetadata branch December 1, 2025 09:17
github-merge-queueBot pushed a commit that referenced this pull request Dec 8, 2025
Caused by #9109
Happens in mgmt flow, where we clean up unused model.
Therefore, when we use FinalResult (instead of Response) model from LRO,
we'd need to change this logic too.
---
test Azure/autorest.java#3237Azure/azure-sdk-for-java#47475 (some model get
removed, Build pass)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

emitter:client:javaIssue for the Java client emitter: @typespec/http-client-java

Projects

None yet

Development

Successfully merging this pull request may close these issues.

mgmt, LRO response is wrong for some legacy typespec

3 participants

@weidongxu-microsoft@azure-sdk@haolingdong-msft