Closed godber closed 2 months ago
The bucket does not exist before the job starts. Perhaps I should have had the test repeated with the 3.0.1
file asset.
There was a type error in the v3.0.0
file-assets
that only manifests in Teraslice v2.2.0
, this is resolved in the v3.0.1
release of the file-assets
. All of the release have been updated with warnings.
Fixed in this mr: https://github.com/terascope/file-assets/pull/1048
Closing.
Our internal testing of the Teraslice 2.2.0 release experienced issues with the
s3_exporter
,v2.2.0
withfile_asset
versions3.0.0
.v2.1.0
withfile_asset
versions3.0.0
.the job is as follows:
Stack trace from the logs:
Full Logs from the worker:
Maybe this should be filed on the
file_asset
project.