🚨 Default Behavior Change: PATCH API endpoints 🚨

The data.world public API supports several options for programmatically making updates to resources on the platform. PATCH is a method for making partial updates to individual records, such as adding tags, changing a description, or modifying a title.

In the next two weeks, we will be making a change to the way PATCH endpoints modify list values. We outline these changes below.


Existing Merge Behavior

Lists are merged with existing values on PATCH requests

  1. A dataset has tags: [tag A , tag B
  2. A PATCH request is sent to /datasets/democorp/my-example-dataset with body: { "tags": [ "tag C", "tag D" ]  }
  3. The dataset is updated to reflect tags: [ tag A, tag B, tag C ,tag D]
  4. A PATCH request is sent to /datasets/democorp/my-example-dataset with payload: { "tags": []  }
  5. No change is applied and the tags remain: [ tag A, tag B, tag C ,tag D]


New Replace Behavior

Lists replace existing values on PATCH requests

  1. A dataset has tags: [tag A , tag B
  2. A PATCH request is sent to /datasets/democorp/my-example-dataset with body: { "tags": [ "tag C", "tag D" ]  }
  3. The dataset is now updated to have tags: [ tag C ,tag D].  tag A and tag B have been removed.
  4. I send a PATCH request to /datasets/democorp/my-example-dataset with body: { "tags": []  }
  5. The dataset has been updated to remove all tags.


Why we are making this change

Today, PATCH can be used to add, modify, or remove fields for all non-list values. With the current merge logic, items can only be appended to list values using PATCH. As a consequence, if you want to remove or reorder the items in a list, you must use the PUT method, which does not support partial updates and requires a full overwrite of the existing record. The new logic to overwrite list values will allow users to make partial updates to records that remove or modify the order of items in the list without needing to modify the entire record.

This new logic primarily impacts tags, file labels, collections, and multi-select custom metadata fields.

Metrics update: July 28, 2021

For enterprise customers, updated metrics have been released today to your Usage and Governance Reporting (ddw-metrics-*) dataset to address some minor bugs and performance improvements.

Potential observable changes:

  • For both single-tenant and multi-tenant customers, some reports were not reflecting de-provisioned user accounts. With this fix, multi-tenant customers may find a slight increase in counts in Visits - Return Visitors - Daily, Visits - Return Visitor Days, Visits - Unique Visitor Days and Visits - Unique Visitors - Monthly now properly reflecting de-provisioned user accounts in addition to active user accounts. Single-tenant customers may find a slight increase in Visits - Unique Visitors Daily and Visits - Unique Visitor Days.
  • For multi-tenant customers, under certain circumstances some reports could duplicate-count users that were members of multiple sub-organizations. With this fix, you may find a slight decrease in counts in Membership - By Date, Visits - Adoption Daily and Visits - Avg Visits Weekly.

If you have any questions or concerns, please let us know at support@data.world or via your customer success representative.

DockerHub and metadata collector enhancement roundup

Our metadata collector (dwcc, aka the data.world Catalog Collector) is now available on DockerHub! Simply run docker pull datadotworld/dwcc:x.xx where x.xx is your desired version, and you're in business. It's that easy.

Other enhancements to the metadata collector:

  • Updated Domo collector to improve relationship modeling
  • Various Tableau & Manta collector fixes & enhancements
  • Denodo metadata collector support shifted to Denodo 8
  • --config-file option for metadata collector (Beta): We've heard your feedback on wanting a simplified way to manage the configurations for your metadata collectors. The config file will become the default way in the near future to set your parameters going forward. Lots more info on this coming soon! 

Bug roundup 🐞

In the last few weeks, several minor bugs and enhancements have been made. Here are some notable ones:

Improved help text for tags, including on pressing “Enter” to add tags

Improved empty state messaging for adding contributors to a dataset

Consistent use of timestamps in alerts and notifications

Navigation tabs on various pages are now keyboard-navigable (left and right arrow keys) for ease of browsing and improved accessibility

“Share” button directly opens “Grant access” modal

Consistent use of display name in emails

Text truncation fixed for filter bars and the project workbench

Various layout, text, and navigational misalignments or inconsistencies

Coming Soon: Addressing timezone inconsistency

🚨 Default behavior change coming next week 🚨

We have recently discovered that when executing queries, there are some cases where our DATETIME columns contain timezone information, and other cases where they do not. This is primarily an issue that arises with columns containing date/time information in uploaded files (we do not see this with live tables). We have decided to address this inconsistency. Starting next week, query result columns of type DATETIME will no longer contain timezone information, while columns of type DATETIMESTAMP will always contain timezone information.

The impact of this change shouldn’t be significant, and most users will see no change. However, if you have queries across ingested data which aggregate on DATETIME columns, or do DATE_ADD() style calculations, you may notice differences in your results depending on your current timezone.

If you are impacted by this change, here are some ways to clarify your intent w.r.t. timezones:

  1. CAST the resulting column to a DATETIMESTAMP to force timezones, or DATETIME to strip timezones (documentation)
  2. Use AT_TIME_ZONE() to explicitly state your timezone (documentation)
  3. Ensure that the table column type is set to be of type DATETIMESTAMP or DATETIME (documentation)

Note: If timezone information is desired, but not defined, UTC is assumed. 

Please contact support@data.world with any questions or concerns. As always, we’re happy to help.

Lineage panel moved closer to technical details

For customers leveraging data artifact lineage, it was a little counterintuitive that the high-level business lineage diagram would show up below your dataset relationships but above all your other relationships. So, we've moved it to just above the Technical details section.

Metrics update: Nov 18, 2020

First of all, this update includes a couple fixes:

  • Visits - New Users By Month was based off of pageviews, which can be affected by ad blockers or restrictive browser settings. It has been switched to use a more robust source of events. This may slightly increase this metric going forward.
  • Visits - Unique Visitors to Date was based off of pageviews, which can be affected by ad blockers or restrictive browser settings. It has been switched to use a more robust source of events. This may slightly increase this metric going forward.

Next, we've added an additional table/report:

  • Users love leveraging our built-in query workbench and federated query capabilities, however often it could be challenging for administrators to easily troubleshoot when queries go wrong or audit what queries are being executed.
  • The new Events - Queries report in your ddw-metrics dataset now provides quick access to audit level details on what queries are being run, by whom, including what the query text is, for fast troubleshooting and effective auditing.
  • This report is currently only available for multi-tenant enterprise customers -- it will be rolled out to single-tenant customers in the next few business days.


Naming update: Members, access, and grant access

Previously, data.world used the words people, contributors, invite, share, and a few other names in various places in the application, which caused confusion.

We now use Members to show the users that are part of an organization, Access as the tab where you can manage access at a more granular level on datasets or other resource pages, and Grant access as a consistent call to action to add additional members.

Also, the Member organization role has been updated to be Basic member to be clear and unique from members more generally.


What's new? We'll tell you!

Thank you for checking out the data.world Product - What's New changelog to learn about all the new and updated features hot off the presses. We wanted to have an interactive, rapidly and frequently updated newsfeed that reflects on data.world's continuous integration and continuous deployment approach -- where multiple product releases happen every week, and the product is constantly evolving.

As always, if you have questions or feedback feel free to reach out to us at support@data.world or your Customer Success Manager, and if you are looking for older release notes, you can click here.