Release Note 20140812
Table of Contents
Features & Improvements
This is a summary of the new features and improvements introduced in this release:
Console: Password Quality
Added a Password quality indicator to the Sign up, Account confirmation, and Profile pages when editing the password.
Vulnerable, easy to guess passwords are flagged as the user inputs them, thus prompting the use of more secure character combinations.
Console: Schedules' History Pagination
Added pagination to the Job History table on each Schedule’s details page.
Console: Schedules' Last Job Status
Added each Schedule’s Last Job’s status and ID in the Schedules list page.
Console: Schedules' Cron Helper
Added a helper shortcut to the Schedule’s ‘Cron Schedule’ form field of the New Query page. The helper links to the Cron Schedule reference page here on docs.treasuredata.com for quick reference.
The main change concerned the way cookies are handled: the change allows tracking of users moving across different subdomains.
These are the most important Bug Fixes made in this release:
APIs: Query Result Output
Query Result output to Treasure Data in ‘replace’ mode sets the destination table’s schema to ‘Manual’.
The APIs was validating the presence of the request’s ‘detect_schema’ parameter expecting the option to be a boolean represented as string (“true” or “false”). The check failed if the parameter as set by the Worker was in different format: e.g. integer 0 / 1, actual boolean false / true, integer as string “0” / “1”, etc…
Changed the validation of the ‘detect_schema’ REST API parameter to be more solid and cover all possible representations that can be interpreted as boolean true or false.
Query Result Output to Google Spreadsheets throws a ‘java.io.IOIException’ exception although the final Job status is ‘Success’.
This error occurs when the size of the import into Google Spreadsheets, which was partitioned in 1024 records chunks, exceeded certain limits found to be governing in the API in use. Those limits were not publicly exposed.
Once the number of records and size limits for the API library was determined, the implementation was modified to limit the partitioning based on the recording number and size.
Console: TSV File Uploader
TSV file upload through the File Uploader is not working.
This was due to the use of the wrong method when checking which field delimiter the user had provided for the file – the Rails String’s present? method returns false if the variable contains only whitespace characters, such as a tab ‘\t’ character as for the TSV file format.
Changed the method to check whether or not the delimiter is provided at all, irrespectively of the delimiter’s the value.
Last modified: Aug 14 2014 05:25:38 UTC