anubhav tarar created CARBONDATA-698:
----------------------------------------

             Summary: no_inverted_index is not working
                 Key: CARBONDATA-698
                 URL: https://issues.apache.org/jira/browse/CARBONDATA-698
             Project: CarbonData
          Issue Type: Bug
          Components: spark-integration
    Affects Versions: 1.0.1-incubating
         Environment: spark1.6,2.1
            Reporter: anubhav tarar
            Priority: Trivial


i am creating no_inverted_index with invalid values using both spark 1.6 and 
2.1 and it works 
spark 2.1 logs

0: jdbc:hive2://localhost:10000> DROP TABLE IF EXISTS  productSalesTable;
+---------+--+
| Result  |
+---------+--+
+---------+--+
No rows selected (3.621 seconds)
0: jdbc:hive2://localhost:10000>   CREATE TABLE productSalesTable( 
productNumber Int, productName String, storeCity String, storeProvince String, 
productCategory String, productBatch String, saleQuantity Int, revenue Int) 
STORED BY 'carbondata' TBLPROPERTIES ('COLUMN_GROUPS'='( 
productName)','DICTIONARY_INCLUDE'='productName', 'NO_INVERTED_INDEX'='1');

spark 1.6 logs

cc.sql("DROP TABLE IF EXISTS  productSalesTable").show();

    cc.sql("""CREATE TABLE productSalesTable( productNumber Int, productName 
String, storeCity String, storeProvince String, productCategory String, 
productBatch String, saleQuantity Int, revenue Int) STORED BY 'carbondata' 
TBLPROPERTIES ('COLUMN_GROUPS'='( 
productName)','DICTIONARY_INCLUDE'='productName', 
'NO_INVERTED_INDEX'='1')""").show()

AUDIT 07-02 15:48:14,485 - [knoldus][knoldus][Thread-1]Creating Table with 
Database name [default] and Table name [productsalestable]
AUDIT 07-02 15:48:14,868 - [knoldus][knoldus][Thread-1]Table created with 
Database name [default] and Table name [productsalestable]

while debugging the code i found out in carbon ddl sql parser tablePropertiess 
map contain the properties in lower case
and we are checking tableProperties.get("NO_INVERTED_INDEX")

so it is failing due to string mismatch



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to