Visit our new documentation site! This documentation page is no longer updated.

Release Note 20140401

Table of Contents

Features & Improvements

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

Backend: Query Result Output to Redshift

  1. Disabled unnecessary Redshift protocol calls;
  2. Improved handling of the retry limit and timeouts.

Console: User Page

The user page of the currently logged in is accessible via the /users/current endpoint as well as the usual /users/:user_id;

Console: User Page

Console: Date/Time Format

Indicate the year in Schedules list, Jobs list, Database view, and Table view.

Console: Date/Time Format

JDBC v0.2.8

Upgraded Java Client Library dependency to v0.3.6.

Java Bulk Import Library v0.4.11

  1. Log Java Client Library and Java Bulk Import Library’s version in the bulk import log file;
  2. Log the time each import step takes to execute in the td-bulk-import.log log file.

Treasure Agent v1.1.19

  1. Use the new API endpoint in place of;
  2. Update msgpack-ruby to v0.5.8;
  3. Integrated various pull requests.

Bug Fixes

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

Backend: TD_TIME_RANGE and Time-Index Pushdown

  • [Problem]
    The TD_TIME_RANGE UDF behaved in an inconsistent manner relative to its documentation. When the end time and Timezone were set to null, it read the full time range.
    This was due to the Timezone parameter being set to null when normally it is either not null or omitted.
    Now the behavior is consistent with the documentation and it uses the default UTC timezone if the timezone is NULL.

APIs: CPU Cores Utilization Resolution

  • [Problem]
    Core utilization history cannot display non-integer values, causing hourly utilization that cumulates to less than 1 unit to be rounded down to 0.
    Core utilization is now using floating point numbers.

Console: Support Portal

  • [Problem]
    The integration between the Support Portal based off Salesforce’s and the Console does not cover all possible workflows and use cases required.
    Added the /auth/td integration endpoint and made it redirect to the signup page if the user is not logged in into the Console.
    [Known Limitation]
    Redirection back to upon successful login into the Console is not implemented. The user will need to click on the Support button after logging in to visit the support page and create cases.

Console: Support Portal

Last modified: Nov 06 2014 06:54:36 UTC

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