Release Note 20141111

Table of Contents

Features & Improvements

This is a summary of the new features and improvements introduced in this release:

Console: Data Collection Introduction Video

We embedded the “Choosing the Right Method to Collect Data” tutorial video in the Collect Data landing page.

Console: Data Collection Introduction Video

Console: Storage Utilization In # of Records

We switched the storage utilization chart in the Console utilization page to display the metric in number of records instead compressed size.

Console: Storage Utilization In # of Records

Console: Free User’s Global Notifications

We added the Notifications back for Free users whose account life-span has gone beyond the 14-days trial period. It was previously not visible for them.

Client Libraries: Released Java Client Library v0.5.5

  • Resolved an issue with using the Java client library and attempting to communicate with a different SSL endpoint. The Java client library was overwriting the default javax.net.ssl.trustStore value.

SDKs: Released Java SDK v0.2.2

This new version bundles the above mentioned Java Client Library v0.5.5.

Bug Fixes

These are the most important Bug Fixes made in this release:

APIs: New Accounts Can’t Query The Sample Database

  • [Problem]
    A freshly signed up user cannot query the shared ‘sample_datasets’ database using the REST APIs and/or CLI.
    [Solution]
    This is due to the lookup method that determines whether the database the user intends to query exists or not. The method only looked up those databases that belonged to the account but not any shared one.
    We modified the lookup method to list all the databases that can be queried by the account to allow the user to issue queries against shared databases.

APIs: Time Filtering Ineffective

  • [Problem]
    On Tuesday 11/11 all customer’s Hive queries slowed down significantly.
    [Solution]
    An operation problem in deploying the newly patched version of Hive caused the Time index filtering to become ineffective thus causing normally fast queries to scan the entire table they targeted instead of only the required portion. Because of the execution slowdown, all customers' jobs between ~2:30 PM and ~5:00 PM PST got queued up because the previously run jobs ran much slower than usual.
    The Hive fix was initially reverted, then applied properly. To aid with consuming the backlog, all Treasure Data’s Hadoop computation resources were doubled and all customers' computation plans were granted twice the amount of maximum mapper and reducer cores temporarily. As of ~2:00 AM on Wednesday 11/12 all the customers' job queues were back to normal.

Last modified: Nov 18 2014 02:24:41 UTC

If this article is incorrect or outdated, or omits critical information, please let us know. For all other issues, please see our support channels.