Skip to main content
print this page

Directory path(S3 prefix) metadata for S3 connection type of datasets being removed when dataset schema is updated.

· 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

While performing the following operations, the directory path for S3 connection type datasets is getting deleted from the metadata:

  • Updating a dataset schema
  • Updating DataConversionParameters for Redshift datasets
  • Updating GlobalSecondaryIndexes for DynamoDB datasets
  • Conducting batch edit operations on datasets

Affected Versions: 2.6 2.6.1

Fix Version: 2.6* 2.6.1* 2.7

2.6* 2.6.1*

Customers upgrading to these versions after Aug 09, 2024 does not require explicit patching as the fix will be part of the release artifacts.

Root cause(s)​

While making few enhancements and refactors in 2.6 related to s3 connection type of datasets resulted in these errors.

Impact​

After upgrading to 2.6/2.6.1, When users try to update the dataset schema or above specified operations then DirectoryPath (S3 prefix) for s3 connection type of dataset will be deleted from the dataset metadata.

Mitigation​

Fix available

Fix will be available in Amorphic version 2.7.

Patch available

Patch is available for Amorphic versions v2.6, 2.6.1

Please contact amorphic-support@cloudwick.com to patch your application.

Timeline​

gantt
    title Timeline
    dateFormat YYYY-MM-DD
    tickInterval 7day
    axisFormat %b-%d
    todayMarker off
    section Tracker
        %% update the ticket number and date of bug report
        CLOUD-4810 : done, 2024-08-03, 0d
    section Identification
        Reported : crit, des1, 2024-08-04, 0d
    section Mitigation
        %% Update number of days took for each step below
        Bug Fixed: crit, done, 2024-08-05, 1d
    section Delivery
        %% update the date of each step below
        testing complete: milestone, 2024-08-07, 0d
        patch avaialble: milestone, 2024-08-07, 0d
  • 2024-08-03: Bug reported/identified (CLOUD-4810)
  • 2024-08-04: Bug triaged
  • 2024-08-05: Bug fixed
  • 2024-08-07: Testing of patch on v2.6 and v2.6.1 has been completed
  • 2024-08-07: Patch for v2.6 and v2.6.1 has been released