Skip to main content

18 posts tagged with "v2.1"

View All Tags
print this page
print this page

Amorphic upgrade Fail with TenantName and malformed service level permission error

· 2 min read
Fix Available
Fix Available
This bug has been fixed
Patch Available
Patch Available
This bug has a patch available for affected versions

Amorphic upgrade may fail for limited application due to missing TenantName attribute in the metadata of datasets.

When the above issue occurs, the application tries to send an email notification to the administrators. This causes a follow-up issue: In roleUtil.search_permissions, Malformed Service level Permissions Json, service requested apps, action name fullaccess.

Affected Versions: 2.1

Fix Version: 2.2

print this page

Failed to run data ingestion tasks with Redshift as targets with s3 Access Denied error

· 3 min read
Patch Available
Patch Available
This bug has a patch available for affected versions
Fix Available
Fix Available
This bug has been fixed

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*

print this page

Failed to ingest data into reload type of datasets with target location redshift(only in multi-tenant envs)

· 2 min read
Bug Reported
Bug Reported
Bug has been reported, and is being investigated
Fix In Progress
Fix In Progress
Bug identified and fix is in progress

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

print this page
print this page

Sessions(if created) are orphaned by notebook auto termination process

· 2 min read
Fix In Progress
Fix In Progress
Bug identified and fix is in progress

Sessions are remote apache spark runtime environments which can be created and managed in notebook for spark job development. with auto termination of notebook process, the active sessions are not being killed and causing additional cost for orphaned sessions until it reaches the session timeout(default is 48hours).

Affected Versions: 2.1

Fix Version: 2.2

print this page

Incorrect handling of failed data profiling job retries

· 2 min read
Fix In Progress
Fix In Progress
Bug identified and fix is in progress
Workaround Available
Workaround Available
Temporary workaround available

When data profiling job(backend job) is failed with an unhandled exception, the job does an inordinate number of retries causing additional cost to the customer.

This issue occurs if the Amorphic deployed with single tenancy and have datasets with data profiling enabled.

Affected Versions: 1.11, 1.12, 1.13, 1.14, 2.0, 2.1

Fix Version: 2.2

print this page

Amorphic workflows sending incorrect status notifications

· 2 min read
Fix In Progress
Fix In Progress
Bug identified and fix is in progress
Workaround Available
Workaround Available
Temporary workaround available

Workflows sending incorrect notifications in scenarios mentioned below(Only when user is subscribed to workflow alerts)

  • when we have non-etl nodes in the workflow, even after the successful execution of the workflow system sends incorrect node failure email alert.
  • when the any node in the workflow failed, push notification shows error message and details but the status in the push notification says success.

Sample incorrect email notification details:

Title: Workflow 'abcd' encountered one or more node failures.

EventType: Node Execution Failure

ErrorMessage: Job run succeeded

Affected Versions: 2.1 2.0 1.14 1.13

Fix Version: 2.2