Hot-fixes Since 23rd January 2018

Release Version: 50.84.0

GDPR Readiness

As part of GDPR readiness, Qubole has updated its privacy policy. The updated privacy policy now states how Qubole will collect, use, disclose, and share personal data that belongs to QDS users.

As part of the Sign up process, when personal information such as name, email ID, company, title, location, and phone number is collected from a new user, he will be asked to give consent to Qubole’s Privacy Policy and Terms of Service, by selecting the associated check box before proceeding further in the Sign up process.

An existing user, during a fresh login, will be asked to provide consent to Qubole for processing his personal data by selecting the Privacy Policy and Terms of Service check boxes. This will be required to successfully log into the QDS platform. The consent will be collected using a one-time pop-up which will not be shown to users during subsequent sign-ins. The same pop-up requesting for consent will be displayed when a user is invited to join QDS.

AN-874: Fixes a problem that caused tables not to be displayed under the Analyze > Tables when Hive authorization was enabled.

INFRA-778: Fixes a problem that caused live logs for running queries not to be displayed.

EAM-1004: Fixes a problem that caused a command or query to be abruptly terminated.

EAM-911: The Ruby SAML version has been upgraded to the latest 1.7.2 version.

EAM-857: Qubole Scheduler has introduced a new re-run limit per scheduled job; it is applicable to all scheduled jobs. Its default value is 20. When the scheduled job re-runs exceed the limit, you will see this error message: A maximum of 20 reruns are allowed for scheduled job in your account: #<account_number>.

You can increase the number of re-runs for a QDS account by creating a ticket with Qubole Support. The new value will apply to all the jobs that run in the account.

HADTWO-1341: Fixes a problem that caused all re-tries to fail after a client running on another cluster node tried and failed to contact any daemon running on the coordinator. Address resolution is no longer done on the client side.