Spec |
Details |
---|---|
Date: |
6.30.20 |
New Feature/Fix: |
New Feature |
Product: |
Platform |
PR#: |
5654 |
Add'l information: |
This PR adds a new context for the open in app menu to support live tables. Previously, we explicitly blocked live tables from using integrations because we were unsure of how they would behave when the datasource had millions of rows. This PR adds a gating mechanism for us to individually enable integrations JUST for the live table context. For integrations that rely on queries, rather than files, we handle them in the same way tabular files are handled by creating a SELECT * FROM table query with a limit of 5000 rows.Integrations must have the live tag to appear in this context. The open in app menu should now appear on live table file preview cards and in the workspace file view header. |
Spec |
Details |
---|---|
Date: |
6.26.20 |
New Feature/Fix: |
Bug Fix |
Product: |
Platform |
PR#: |
5621 |
Add'l information: |
This change fixes a bug with the example code we provide for downloading a file for use in Python or R that occurs when downloading a file synced from a query result . |
Spec |
Details |
---|---|
Date: |
6.26.20 |
New Feature/Fix: |
New Feature |
Product: |
Platform |
PR#: |
|
Add'l information: |
With this release we have added the ability to request a row count from a table that has more than 10,000 rows in it. Prior to this feature, there was no way of knowing how large a file would be when it was downloaded or saved as a derived table. |
Spec |
Details |
---|---|
Date: |
6.26.20 |
New Feature/Fix: |
Bug fix |
Product: |
Platform |
PR#: |
6714 |
Add'l information: |
Fixed a bug where Redshift Spectrum tables wouldn't appear in the UI. |
Spec |
Details |
---|---|
Date: |
6.26.20 |
New Feature/Fix: |
Bug Fix |
Product: |
Platform |
PR#: |
6763 |
Add'l information: |
Fixed an issue where queries against virtualized tables with a double _ in the names were not running correctly. |
Spec |
Details |
---|---|
Date: |
6.22.20 |
New Feature/Fix: |
Bug Fix |
Product: |
Cataloger |
PR#: |
5647 |
Add'l information: |
We fixed a bug where concept schemes in the "More Information" section on Metadata assets (tables, analysis) were not hydrating. |
Spec |
Details |
---|---|
Date: |
6.22.20 |
New Feature/Fix: |
New feature |
Product: |
Platform |
PR#: |
6784 |
Add'l information: |
Added a pragma statement allowing a user to specify a specific Snowflake Warehouse to use when running a query on data.world. See the SQL Pragma doc for more information. |
Spec |
Details |
---|---|
Date: |
6.18.20 |
New Feature/Fix: |
New Feature |
Product: |
Metadata Cataloger and core platform |
PR#: |
|
Add'l information: |
We have added the ability to link a Dataset or Project from/to the Metadata catalog, like between a TableauDashboard and a Dataset. |
Spec |
Details |
---|---|
Date: |
6.11.20 |
New Feature/Fix: |
Bug Fix |
Product: |
Platform |
PR#: |
6790 |
Add'l information: |
If a query in data.world against a virtualized data source times out on data.world, we now cancel the query on the external data source too. Previously when queries timed out on data.world (and were thus cancelled) they continued to run on the host database server. |
Spec |
Details |
---|---|
Date: |
6.02.20 |
New Feature/Fix: |
Bug Fix |
Product: |
Grafo |
PR#: |
|
Add'l information: |
There was a problem where verification codes for new users in Grafo were failing. It was determined that users in the data.world platform were requesting a login for Grafo (triggering a verification code to be sent) and then mistakenly requesting one again thinking the first request hadn't gone through. The result was that the final verification code sent cancelled out all the others, making it possible for the user to use one that wouldn't work. Now multiple requests for verification codes from the same address result in the same code being sent out. |
Spec |
Detail |
---|---|
Date: |
6.01.20 |
New Feature/ Bug Fix: |
New feature |
Product: |
Metadata Catalog |
PR#: |
|
Add'l information: |
As of dwcc 1.12, data.world now supports cataloging an AWS Glue source. Both Glue ETL jobs, and Glue Data Catalog tables and columns are cataloged. See the help document on the Glue metadata catalog connector for more information. |