You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@carbondata.apache.org by "Akshay (Jira)" <ji...@apache.org> on 2020/02/21 06:40:00 UTC

[jira] [Updated] (CARBONDATA-3716) Fixed spark 2.4 UT failures

     [ https://issues.apache.org/jira/browse/CARBONDATA-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Akshay updated CARBONDATA-3716:
-------------------------------
    Description: 
Issue:
a) In 2.4 subquery alias produces an output set with alias identifier(that is both database_name and table_name) which causes failures.

b) In 2.4 a new variable was introduced "spark.sql.legacy.allowCreatingManagedTableUsingNonemptyLocation" which is by default set to "false".
While refreshing table In 2.4 we need to set this variable to "true" in order to create table in non empty location.

> Fixed spark 2.4 UT failures 
> ----------------------------
>
>                 Key: CARBONDATA-3716
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-3716
>             Project: CarbonData
>          Issue Type: Test
>            Reporter: Akshay
>            Priority: Minor
>
> Issue:
> a) In 2.4 subquery alias produces an output set with alias identifier(that is both database_name and table_name) which causes failures.
> b) In 2.4 a new variable was introduced "spark.sql.legacy.allowCreatingManagedTableUsingNonemptyLocation" which is by default set to "false".
> While refreshing table In 2.4 we need to set this variable to "true" in order to create table in non empty location.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)