Azure Storage Library Upgrade
Overview
As part of 437patches27146
, The Azure Storage library is upgraded from v3.0.0 to v8.3.0. This library driver upgrade has resulted in specific changes in the error messages, status codes, and success and failure messages. This table lists these changes:
Hadoop Snaps | Scenario | Error from the Azure Storage v3.0.0 | Error from Azure Storage v8.3.0 |
When you use an expired SASURI. (OR) When you use a valid SASURI in Snap Settings and an invalid Azure Storage Account. | error=Failed to read data from Azure Blob Storage., reason=The request failed with error code ACCESS_DENIED and HTTP code 403. Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature., resolution=Verify that the account settings and file path are correct., status_code=error} | {error=Failed to read data from Azure Blob Storage., reason=The request failed with error code AuthenticationFailed and HTTP code 403. Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature., resolution=Verify that the account settings and file path are correct., status_code=error} | |
When you use incorrect WASB protocol and HTTPS SASURI. | {error=Failed to initialize parquet writer, reason=May be due to an invalid account or directory path, detail: This request is not authorized to perform this operation using this protocol., resolution=Address the reported issue., status_code=error} | {error=Failed to initialize parquet writer, reason=May be due to an invalid account or directory path, detail: Cannot use HTTP with credentials that only support HTTPS., resolution=Address the reported issue., status_code=error} | |
When you use invalid credentials for the WASB protocol. | reason=The request failed with error code SERVICE_INTERNAL_ERROR and HTTP code 500. The server encountered an unknown failure: , status_code=error | reason=The request failed with error code null and HTTP code 0. , status_code=error |
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.