This is a summary of new Treasure Data features and improvements introduced in the October 1st, 2018 release. If you have any product feature requests, submit them at feedback.treasuredata.com.
- Export: Google Sheets Beta
- Import: YouTube Analytics Beta
- Import: Mailchimp
- Export: Cheetah Digital Mail Publisher Smart Beta Continues
- Export: Writing Job Results into CyberAgent Ameba
- Import: Marketo Improvement
- User Experience: Skip Integration Preview Errors
- User Experience: Create Source Data Transfer Directly from Connections
- Query: Presto 0.205 Now Live - SQL Changes Required
- Query: User-Defined Partitioning Now Available
Our new Google Sheet integration allows you to authenticate to Google without using the older Treasure Data Console (V2) as well as truncate or update the data you export to Google Sheets.
You must manually upgrade your legacy Google Sheets data transfers to take advantage of these new features. You must create a new connection with the new Google Sheets integration and copy over the legacy data transfer details over to your new data transfers.
For details, see the Google Sheets (BETA) article.
Our new YouTube Analytics Data Connector will help you to easily ingest analytics from your YouTube channel. With this connection, you can:
Ingest daily Analytics for videos and playlists
Choose from a large range of analytic presets
For details, see the Data Connector for YouTube Analytics (BETA) article.
Note: This integration is currently under private beta. Contact the Treasure Data team for further details. The connector documentation is available only to beta participants.
With our latest Mailchimp integration, you can able to ingest List Members, Member Activity, Campaigns and Lists data.
For details, see Data Connector for Mailchimp article.
Our Mail Publisher Smart data connector now supports:
Ability to schedule email delivery
Ability to support commas and carriage return in the fields to use with the Draft template
For details, see the Cheetah Digital Mail Publisher article.
Note: This integration is currently under private beta. Contact the Treasure Data team for further details. The connector documentation is available only to beta participants
Our new CyberAgent Ameba integration will help you to easily export your td_global_id from your account to Ameba. With this integration, you can make a user list in Treasure Data that targets a segment and then send the list to Ameba to use in your advertisement campaigns.
For details, see CyberAgent Ameba Export Integration.
We've enhanced our integration with Marketo to now allow for importing Program data directly into our Customer Data Platform.
For details, see Data Connector for Marketo article.
When creating integrations, you can now skip the preview of the data if Treasure Data is unable to fetch the data for the preview or an error happens when guessing the data schema.
For details, see the Skipping Data Preview when Defining Data Connectors.
You now have the option to directly create a source data transfer after you've created a new connection. You no longer have to go to the Input Transfer page to create a source data transfer.
The Presto 0.205 release environment is live as of October 1. It will be available side-by-side with Presto 0.188. until November 15. After November 15 Presto 0.205 will be the only available Presto release.
Note: Presto 0.205 enforces some ANSI SQL rules more strictly than previous releases. Several constructs that were legal in Presto 0.188 now cause syntax errors. Based on reviewing the code of Presto 0.205 and testing an extensive sample of customer queries, we have determined that only a few customers appear to be using syntax affected by the change. However, you must locate and update queries that contain incompatible syntax. For details see: Presto 0.205 Required SQL Updates article.
Queries run in Presto 0.188 by default until November 1. After November 1, queries run in 0.205 by default. To force a query to run in a specific engine release during the transition period, add one of the following query hints:
-- @TD engine_version: 0.205 or
-- @TD engine_version: 0.188 Review the required changes list and test affected Presto queries in 0.205 before November 1. The changes do not cause changes in the behavior or results of your queries in 0.188. You can also test individual queries in the Presto 0.205 environment to ensure compatibility.
As soon as you have tested your queries to your satisfaction, Treasure Data recommends that you contact support to have your default version changed to Presto 0.205 early, rather than wait for November 1.
Again, all customers are switched to using Presto 0.205 by default as of November 1, and Presto 0.188 will no longer be available as of November 15. If your migration efforts are not completed by November 1, contact Treasure Data support.
User-Defined Partitioning is now in production and, in some use cases, it may improve performance and memory usage on lookup, equijoin, and aggregation operations in Presto. See "User-Defined Partitioning for Presto" for details.