Closed tangobravo62 closed 3 years ago
S3 file paths returned to the ingestor contain a leading blank, see field registeredFilesList in following Ingestor log:
registeredFilesList
2020-06-25 11:38:44.570 DEBUG 1 --- [nio-8080-exec-5] org.apache.http.wire : http-outgoing-0 << "HTTP/1.1 201 Created[\r][\n]" 2020-06-25 11:38:44.571 DEBUG 1 --- [nio-8080-exec-5] org.apache.http.wire : http-outgoing-0 << "Server: nginx/1.16.1[\r][\n]" 2020-06-25 11:38:44.571 DEBUG 1 --- [nio-8080-exec-5] org.apache.http.wire : http-outgoing-0 << "Date: Thu, 25 Jun 2020 11:38:44 GMT[\r][\n]" [...] 2020-06-25 11:38:44.571 DEBUG 1 --- [nio-8080-exec-5] org.apache.http.wire : http-outgoing-0 << "{"productId":"406","sourceStorageType":"S3","sourceFilePaths":["s3://proseo-s5p-main/esa-itt-a10180/S2/TDS2_ORBIT_15533/S2B_OPER_MSI_L1C_DS_MTI__20200226T105549_S20200226T070436_N02.09.tar"],"targetStorageId":"proseo-data-001","targetStorageType":"S3","registeredFilePath":"s3://proseo-data-001/406//","registered":true,"registeredFilesCount":1,"registeredFilesList":[" s3://proseo-data-001/406/esa-itt-a10180/S2/TDS2_ORBIT_15533/S2B_OPER_MSI_L1C_DS_MTI__20200226T105549_S20200226T070436_N02.09.tar"],"deleted":false,"message":"registration executed on node proseo-integration-k8s-node-nf-1"}"
Apparently this does not cause malfunctions, but it should be cleaned up.
Fixed: Unnecessary blank was hard coded in file name generation (string " s3:" instead of "s3:").
" s3:"
"s3:"
S3 file paths returned to the ingestor contain a leading blank, see field
registeredFilesList
in following Ingestor log:Apparently this does not cause malfunctions, but it should be cleaned up.