Qubole Release Notes - 20-Jan-2016

What is New

Locking Notebooks

With Qubole First Class Notebooks, users now have the ability to lock and unlock notes. When a user locks a note, he can prevent edits on the note from other users in the account. Once the notebook is ready to be used, he can unlock the note to make it available to all the users in the account. This simplifies the user experience in a multi-user qubole account.

 

List of Changes and Bug Fixes in this Release

HADOOP-2

Fix

SPAR-793: Allow S3 failure to be propagated to the caller.

 

HIVE 1.2

Fix
QBOL-4920: Add execution engine and hive version metrics in qlog.

 
HIVE 0.13
 
Change
Updating query result schema as soon as it is available to help ODBC-based queries.
Fix
QBOL-4920: Add execution engine and hive version metrics in qlog.
Fix
HIVE-1179: Adding a shutdownhook to clear the tmp files/directories when a command is cancelled/killed.


QDS

New
HIVE-1126: Updating query result schema in db as soon as it is available.
New
QBOL-4768: Adding command exceptions in log file.

New
QBOL-4897:  Add new user to a group by name.
Fix
UI-3000: Added support for pushing of security groups to roles enabled accounts.
Fix
QBOL-4941: Optimize MySQL query to fetch list of commands.
Fix
QBOL-4763: Support to enable/disable users in an account.
Fix
QBOL-4904: Fix for Elastic Plan’s billing issues.
Fix
QBOL-4760: Repetition of log snippets for running commands in Analyze.

TEZ
 
Fix
QTEZ-47: Application UI link is navigated to application specific page for running job.



ZEPPELIN/NOTEBOOK
 
New
ZEP-37: Qubole’s First Class Notebooks now has an ability to lock notes with the following functions:

  • Makes a note aware of the user, who is using it. .
  • A user can acquire a lock on a note.  

Lock here means exclusive control over the note. Once a note is locked by user no other user in account can do any changes on the note.  


 

Have more questions? Submit a request

Comments

Powered by Zendesk