ETL Parquet Import: Fix Unexpected Failure When Session Token Expires During Execution
Details
| Detail name | Value |
|---|---|
| Changelog Number | 30601 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 2025.1.0 |
| Fix Versions | Exasol 2026.1.1, Exasol 2025.1.12 |
| Resolution Date | 2026-07-02 |
Description
ETL Parquet import jobs could fail unexpectedly when the session token expired during execution. Although the session token was valid when the import started, token expiration during a long-running import caused the tool process to terminate with error
Internal error - A tool process exited unexpectedly
instead of reporting a session or authentication failure.
Workaround
Ensure that the session token remains valid for the entire duration of the import job by using a token with a longer expiration time or renewing the session before starting long-running imports.
Fix
Token expiration during the import process will result in an exception being thrown to the user
Parquet file (<AWS URL>) not found. IOError: When reading information for key '<Object Path>' in bucket '<Bucket Name>': AWS Error UNKNOWN (HTTP status 400) during HeadObject operation: No response body.
and the query execution will be terminated.
