[
https://issues.apache.org/jira/browse/CARBONDATA-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837266#comment-15837266
]
anubhav tarar commented on CARBONDATA-598:
------------------------------------------
@Naresh P R should it be closed
> 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: spark 2.1
> 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)
