This is a summary of new Arm Treasure Data features and improvements introduced in the August 1st, 2019 release. If you have any product feature requests, submit them to feedback.treasuredata.com.
Audience Studio Users Get Custom Scripting for Workflow
Treasure Data is offering TD Workflow's Custom Scripting feature to all users of Audience Studio. With Custom Scripting you can run containerized Python scripts from within Treasure Workflows to enrich your data through custom integration with different data sources, improved ETL, and use of machine learning algorithms. Check out our Custom Scripting overview video.
Accounts that include Audience Studio will be enabled with Custom Scripting for Workflow by August 15, 2019. To learn more about the capabilities offered, contact your Customer Success representative.
Data Connector: Export to Microsoft OneDrive
Last month we announced OneDrive Import into Treasure Data. Now you can also export your data to this cloud storage for further processing. For more information, see Writing Job Result to OneDrive.
Data Connector: Zendesk Input Improvement - Support End Time for Incremental Loading
Reduce the time of the first ingesting of your Zendesk data by specifying a smaller Start Time - End Time period. For more information, see Data Connector for Zendesk.
Data Connector: Intercom Input Improvement - Support Incremental Loading for Users and Conversations
Reduce the first ingestion load of Conversations and Users by specifying incremental loading. For more information, see Data Connector for Intercom
Data Connector: Tableau Server Export Improvement - Support New Tableau Server Version
You can add a new option for latest Tableau Server version to support the new version of Tableau Server 2019.2. For using Tableau Server Export Connector, see Tableau Server - Export.
Required Migration: Salesforce Data Connector
The deadline to migrate to the Salesforce V2 data connector connector has been extended. The legacy SFDC connector will be available until September 30, 2019.
The Salesforce V2 data connector is capable of asynchronous data transfer - with minimal impact to current users.
The Salesforce V2 data connector replaces the current Salesforce data connector. In TD Console, the existing SFDC connector is now labelled "Salesforce Legacy" and the V2 data connector is labelled "Salesforce."
If you are currently using the Salesforce data connector, you must complete migration steps to ensure that your integration continues to work. You must move from the legacy Salesforce data connector to the Salesforce V2 data connector.
New users of the Salesforce data connector can start using the Salesforce V2 data connector immediately.
Contact your Technical Support at firstname.lastname@example.org to learn more.
TD Global ID Cookie Update for Chrome 76: Action Required for Limited Customers
We've made a compatibility update to our third party cookie in order to continue operating under new preferences introduced in Chrome 76. The update appends 2 new attributes to the TD Global ID: SameSite=none and Secure.
When Arm Treasure Data's td_global_id is set in a Chrome browser, the following changes are in affect:
- Allow secure (HTTPS) access to your website
Continued Improvement: Profiles in Audience Studio
We've made improvements in the Profiles view that include:
- New table layout with column filtering
- New column to show campaigns associated with profile
- New charts for Page Views and Duration in Minutes
Also, Profile avatars and social links are removed. These changes to Profiles will be implemented in your account this month.
Control Panel: TD Console Change
The control panel groups administrator-level account maintenance features together in the Treasure Data Console. We are continuing to implement this improved navigation on all Treasure Data systems.
Some task steps in the administrative area and user profile area are impacted by this user interface change. You can review a summary of changes.
Presto: Limit Query Execution Time
Presto now allows customers to configure limits on Presto query execution time.
TD limits all Presto queries to 48 hours. You can request shorter limits for the following groups of queries:
- All Presto queries from your account
- Queries from the TD Console and ODBC/JDBC clients
- Scheduled queries and workflow queries
- Queries in any named resource pool
Also, you can set a limit for an individual query, using a query hint.
Because configuring query runtime limits can break your existing jobs, only technical support can configure account-level and query group-level limits for you. Contact email@example.com to request assistance with query execution limits.
Hive: TD Hive 2019.1 Generally Available
Hive 2019.1 is fully available. TD recommends its use for all workloads going forward, including new workloads and migration of existing jobs as soon as your business requirements will allow.
TD Hive 2019.1 is a major update to Hive-on-TD functionality. It brings syntax compatibility with Apache Hive 2.3 to the Arm Treasure Data platform, and fixes all known outstanding bugs in our Hive 0.13 service for greater reliability.
Hive 2019.1 generates MapReduce jobs, that execute on the same cluster and use the same execution resources as current Hive 0.13 jobs. Performance is generally similar, and in some cases faster. Report any performance regressions to our support team.
Future TD Hive releases will build on TD Hive 2019.1 with a focus on modernization for performance enhancements.
Hive 0.13 will continue to be available for an extended period (to be determined, but at least through 2020). Updates to Hive 0.13 are expected only as necessary to address critical bugs related to security or system stability.
The version selector in the TD Console shows Hive 0.13 and Hive 2019.1 releases as follows:
Hive 2019.1 is initially marked as "experimental" in the UI and CLI to indicate that it is a major release for which customers may want to retest complex workloads. "Experimental" does not indicate that the software is not production ready. When the rollout is complete, Hive 2019.1 will be labeled "stable" and become the default for new queries for all customers. If you wish to keep Hive 0.13 as your default after this date, contact your account representative or support.
Hive 2019.1 uses ANSI-compliant SQL syntax. The syntax is generally similar and most queries run unchanged, but there are new reserved words and some data types requiring casts. The documentation includes a guide to query rewriting.
If you are not ready to rewrite a query, you can explicitly select Hive 0.13 to run that query, from the command line, API, workflow or the TD Console, for as long as Hive 0.13 is available.
For more details on the roadmap for TD Hive, contact your account representative or support.