Mailing-List: contact issues-help@carbondata.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@carbondata.incubator.apache.org
Date: Mon, 16 Jan 2017 11:13:26 +0000 (UTC)
From: "anubhav tarar (JIRA)" <jira@apache.org>
To: issues@carbondata.incubator.apache.org
Message-ID: <JIRA.13032223.1483613880000.14564.1484565206404@Atlassian.JIRA>
In-Reply-To: <JIRA.13032223.1483613880000@Atlassian.JIRA>
References: <JIRA.13032223.1483613880000@Atlassian.JIRA> <JIRA.13032223.1483613880264@jira-lw-us.apache.org>
Subject: [jira] [Updated] (CARBONDATA-598) Not using tableName option in
 Create table command Shows Strange Behaviour
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 16 Jan 2017 11:13:32 -0000


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

anubhav tarar updated CARBONDATA-598:
-------------------------------------
    Description: 
if you dont use the tableName Option when creating table with Bucketing it shows strange behaviour and do not validate any check

here are the logs

spark.sql("""CREATE TABLE t3qqqq219(ID Int)USING org.apache.spark.sql.CarbonSource OPTIONS("bucketnumber"="1","bucketcolumns"="id","tableName"="t3q21000")""");

here file t3q21000 get created in hdfs
which should not be created it is quite confusing
either there should be a check that both table name in create table statement and  tableName in Option both are same and if it is allowed it should valid all the checks  


  was:
if you dont use the tableName Option when creating table with Bucketing it shows strange behaviour and do not validate any check

here are the logs

spark.sql("""CREATE TABLE t3qqqq219(ID Int)USING org.apache.spark.sql.CarbonSource OPTIONS("bucketnumber"="1","bucketcolumns"="id","tableName"="t3q21000")""");

here file t3q21000 get created in hdfs
which should not be created
either there should be a check that both table name in create table statement and  tableName in Option both are same and if it is allowed it should valid all the checks  


> Not using tableName option in Create table command Shows Strange Behaviour 
> ---------------------------------------------------------------------------
>
>                 Key: CARBONDATA-598
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-598
>             Project: CarbonData
>          Issue Type: Bug
>          Components: spark-integration
>    Affects Versions: 1.0.0-incubating
>         Environment: cluster
>            Reporter: anubhav tarar
>            Assignee: Naresh P R
>
> if you dont use the tableName Option when creating table with Bucketing it shows strange behaviour and do not validate any check
> here are the logs
> spark.sql("""CREATE TABLE t3qqqq219(ID Int)USING org.apache.spark.sql.CarbonSource OPTIONS("bucketnumber"="1","bucketcolumns"="id","tableName"="t3q21000")""");
> here file t3q21000 get created in hdfs
> which should not be created it is quite confusing
> either there should be a check that both table name in create table statement and  tableName in Option both are same and if it is allowed it should valid all the checks  


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)