github-actions[bot] commented on code in PR #64208:
URL: https://github.com/apache/doris/pull/64208#discussion_r3401576867
##########
fe/pom.xml:
##########
@@ -403,8 +403,10 @@ under the License.
<jakarta.annotation-api.version>2.1.1</jakarta.annotation-api.version>
<asm.version>9.4</asm.version>
<airlift.concurrent.version>202</airlift.concurrent.version>
- <azure.sdk.version>1.3.4</azure.sdk.version>
+ <azure.sdk.version>1.3.7</azure.sdk.version>
Review Comment:
Separate from the existing `grpc-netty` thread, this also breaks the Azure
filesystem runtime path. `fe/fe-filesystem/fe-filesystem-azure/pom.xml` depends
on `azure-storage-blob` and `azure-identity`, and `AzureObjStorage` builds a
`BlobServiceClient` from those SDKs. With this BOM bump, `azure-identity`
1.18.3 brings `azure-core-http-netty` 1.16.4, whose published POM declares its
Netty dependencies at `4.1.132.Final` and reactor-netty at `1.2.16`. Because
this parent imports `netty-bom` as `4.2.15.Final`, Doris dependency management
will force the Azure HTTP client onto Netty 4.2.x even though the Azure SDK
version in use is built against the 4.1.x line. That can surface as runtime
HTTP/TLS/classpath failures for Azure Blob and OAuth-backed access. Please
either keep the FE Netty BOM on a 4.1.x version compatible with these Azure SDK
artifacts, or isolate/shade the Azure HTTP client Netty stack until the Azure
SDK version used here explicitly supports Netty 4.2.x.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
