You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "jiangpengcheng (via GitHub)" <gi...@apache.org> on 2026/08/13 08:58:16 UTC

[PR] [fix][client] Restore OAuth2 HTTP client after deserialization [pulsar]

jiangpengcheng opened a new pull request, #26324:
URL: https://github.com/apache/pulsar/pull/26324

   (no comment)


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] [fix][client] Restore OAuth2 HTTP client after deserialization [pulsar]

Posted by "Technoboy- (via GitHub)" <gi...@apache.org>.
Technoboy- merged PR #26324:
URL: https://github.com/apache/pulsar/pull/26324


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] [fix][client] Restore OAuth2 HTTP client after deserialization [pulsar]

Posted by "lhotari (via GitHub)" <gi...@apache.org>.
lhotari commented on PR #26324:
URL: https://github.com/apache/pulsar/pull/26324#issuecomment-5279780350

   @jiangpengcheng @Technoboy- Just curious to know what is the requirement of serialization in Pulsar. Is it required for Pulsar Flink connector? Are there other use cases where it's required?


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org