anubhav tarar created CARBONDATA-598:
----------------------------------------
Summary: 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
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 t3q(ID String)USING org.apache.spark.sql.CarbonSource
OPTIONS("bucketnumber"="1","bucketcolumns"="id","tableName"="t3qqqq")""");
here tables get created
then again
it does the checking when fired another query
spark.sql("""CREATE TABLE t3qqqq219(ID Int)USING
org.apache.spark.sql.CarbonSource
OPTIONS("bucketnumber"="1","bucketcolumns"="id","tableName"="t3q21000")""");
org.apache.carbondata.spark.exception.MalformedCarbonCommandException: Table
default.t3q21000 can not be created without key columns. Please use
DICTIONARY_INCLUDE or DICTIONARY_EXCLUDE to set at least one key column if all
specified columns are numeric types
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)
