Enable Azure/AWS SDK logs for CSV/FBV

Details

Detail name Value
Changelog Number 30906
Type Improvement
Status Resolved
Fix Versions Exasol 2025.1.12
Resolution Date 2026-07-02

Background

Previously we did not have Azure SDK logs (for CSV/FBV) and AWS SDK logs (for CSV/FBV) for analysis which created a gap in issue analysis.

Improvement

New configuration parameter Debugmode added to enable capture of AWS/Azure SDK logs.

Usage of Debugmode to enable Azure SDK logging

IMPORT INTO demo FROM <CSV/FBV> AT CLOUD AZURE BLOBSTORAGE
'https://<AccountName>.blob.<EndpointSuffix>/;debugmode=<debug_level>'
USER '<accountName>' IDENTIFIED BY '<account key>'
FILE '<container>/<filename>';

EXPORT FROM <CSV/FBV> AT CLOUD AZURE BLOBSTORAGE
'https://<AccountName>.blob.<EndpointSuffix>/;debugmode=<debug_level>'
USER '<accountName>' IDENTIFIED BY '<account key>'
FILE '<container>/<filename>';

{{debug_level }}→ Level of Azure SDK logs customer wants to capture. The range supported for Azure SDK logging is 0>={{debug_level }}>=4
Default value is 1
where,
0/1 → Error
2 → Warn
3 → Info
4 → Verbose
Any value above or below this range will be considered as invalid and an exception will be raised Invalid debugmode value (for CSV/FBV).

If customer does not provide any Debugmode value as part of query

IMPORT INTO demo FROM <CSV/FBV> AT CLOUD AZURE BLOBSTORAGE
'<https://<AccountName>>.blob.<EndpointSuffix>/'
USER '<accountName>' IDENTIFIED BY '<account key>'
FILE '<container>/<filename>';

EXPORT FROM <CSV/FBV> AT CLOUD AZURE BLOBSTORAGE
'<https://<AccountName>>.blob.<EndpointSuffix>/'
USER '<accountName>' IDENTIFIED BY '<account key>'
FILE '<container>/<filename>';

it will be set to default 0/1 → Error level logs

Usage of Debugmode to enable AWS SDK logging

IMPORT INTO demo FROM <CSV/FBV> AT CLOUD AWS S3
'https://<<bucket>>.s3.amazonaws.com;debugmode=<debug_level>'
USER '<access_key_id>' IDENTIFIED BY '<secret_access_key>'
FILE '<filename>';

EXPORT FROM <CSV/FBV> AT CLOUD AWS S3
'https://<<bucket>>.s3.amazonaws.com;debugmode=<debug_level>'
USER '<access_key_id>' IDENTIFIED BY '<secret_access_key>'
FILE '<filename>';

debug_level }}→ Level of AWS SDK logs customer wants to capture. The range supported for AWS SDK logging is 0>={{DebugMode>=6
Default value is 0
where,
0 → Off
1 → Fatal
2 → Error
3 → Warn
4 → Info
5 → Debug
6 → Trace
Any value above or below this range and any non-integer values will be considered as invalid and an exception will be raised Invalid debugmode value(for CSV/FBV)

If customer does not provide any Debugmode value as part of query

IMPORT INTO demo FROM <CSV/FBV> AT CLOUD AWS S3
'https://<<bucket>>.s3.amazonaws.com'
USER '<access_key_id>' IDENTIFIED BY '<secret_access_key>'
FILE '<filename>';

EXPORT FROM <CSV/FBV> AT CLOUD AWS S3
'https://<<bucket>>.s3.amazonaws.com'
USER '<access_key_id>' IDENTIFIED BY '<secret_access_key>'
FILE '<filename>';

it will be set to default 0 → Off level logs

Note:

  • Debugmode is supported for file types CSV/FBV for Azure SDK from Exasol version 2025.1.11 and 2026.2.0.
  • Debugmode is supported for file types CSV/FBV for AWS SDK from Exasol version 2026.2.0 only.
  • This Debugmode will not be supported for curl based SQL statements and customer should specifically mention the cloud type to use the Debugmode otherwise it will throw an exception.
    ex: ✅ Correct:
IMPORT INTO demo FROM <CSV/FBV> AT CLOUD AWS S3
'<https://<<bucket>>>.s3.amazonaws.com;debugmode=<debug_level>'
USER '<access_key_id>' IDENTIFIED BY '<secret_access_key>'
FILE '<filename>';

EXPORT FROM <CSV/FBV> AT CLOUD AWS S3
'<https://<<bucket>>>.s3.amazonaws.com;debugmode=<debug_level>'
USER '<access_key_id>' IDENTIFIED BY '<secret_access_key>'
FILE '<filename>';

❌ Incorrect:

IMPORT INTO demo FROM <CSV/FBV>
'<https://<<bucket>>>.s3.amazonaws.com;debugmode=<debug_level>'
USER '<access_key_id>' IDENTIFIED BY '<secret_access_key>'
FILE '<filename>';

EXPORT FROM <CSV/FBV>
'<https://<<bucket>>>.s3.amazonaws.com;debugmode=<debug_level>'
USER '<access_key_id>' IDENTIFIED BY '<secret_access_key>'
FILE '<filename>';