It is observed that during consecutive runs of S3 ingestion for datasets of append type, existing files within the dataset are erroneously re-ingested.
Affected Versions: 2.3 2.2 2.1 2.0
Fix Version: 2.4
File upload, preview and download functionalities will fail for datasets with partitions.
Affected Versions: 2.2 2.1 2.0 1.14 1.13
Fix Version: 2.3
After updating the shared libraries, the associated ETL spark job exeuctions are getting failed
Affected Versions: 2.2 2.1 2.0 1.14 1.13
Fix Version: 2.2* 2.1* 2.0* 1.14* 1.13*
Notebook failed to create sessions after 'Update Resources' operation performed on the existing notebooks
Affected Versions: 2.2 2.1
Fix Version: 2.2* 2.1*
When performing the 'Update Partitions' operation for System Datasets, the partitions are mapped with incorrect s3 locations.
Affected Versions: 2.1 2.0 1.14 1.13
Fix Version: 2.2
While providing Dataset Level Access for a domain to users and groups, it is not providing the access. It is providing part of the datasets inside that domain before the error occurs. But it's not reverting back to these permissions when the error happens.
Affected Versions: 1.13, 1.14, 2.0, 2.1, 2.1.1
Fix Version: 2.2
Amorphic fresh installation impacted with AWS S3 logs bucket fails to install with Error: Bucket cannot have ACLs set with ObjectOwnership's BucketOwnerEnforced setting.
AWS has changed the default behavior of newly created S3 buckets which is not compatible with Amorphic logs bucket.
Affected Versions: 2.1 2.0 1.14 1.13
Fix Version: 2.2 2.1* 2.0* 1.14* 1.13*
When notebook with sessions is terminated by the auto termination process, the resource type in the email notification is incorrect. Also the notification type in push notification for the same event is displayed as Failure, instead of Info.
Affected Versions: 2.1 2.0
Fix Version: 2.2
Data ingestion using the connections(JDBC bulk-load type) for datasets with Redshift target are failing with S3 Access Denied error. AWS has changed the behavior of the replication instance provisioning call and not honoring the version passed that is passed in the input request and using a version(3.4.7) that is not compatible with Redshift.
Affected Versions: 2.1 2.0 1.14 1.13
Fix Version: 2.2 2.1 2.0* 1.14* 1.13*
In a multi-tenant environment(with non ra3 redshift nodes), Users were unable to process files in a reload type of dataset with target location as redshift when the selected domain is under a non-default tenant.
Ex: In a multi-tenant environment, User created a 'tenant01' tenant and created a domain 'domain01' under this tenant. Now user created a Reload type of redshift dataset and uploaded file to it. This will fail with below error.
Data load failed in previous run with error - Failed to rename temporary table after job success with error - DWH-1038 - Failed, ERROR: schema "abcd" does not exist
Affected Versions: 2.1 2.0 1.14 1.13
Fix Version: 2.2