Mailing-List: contact issues-help@carbondata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@carbondata.apache.org
Date: Fri, 9 Jun 2017 12:58:18 +0000 (UTC)
From: "Vandana Yadav (JIRA)" <jira@apache.org>
To: issues@carbondata.apache.org
Message-ID: <JIRA.13067269.1493277541000.38765.1497013098099@Atlassian.JIRA>
In-Reply-To: <JIRA.13067269.1493277541000@Atlassian.JIRA>
References: <JIRA.13067269.1493277541000@Atlassian.JIRA> <JIRA.13067269.1493277541297@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (CARBONDATA-997) Correct result does not display
 in presto integration as compare to CarbonData
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 09 Jun 2017 12:58:23 -0000


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

Vandana Yadav resolved CARBONDATA-997.
--------------------------------------
    Resolution: Fixed

not a bug any more


> Correct result does not display in presto integration as compare to CarbonData
> ------------------------------------------------------------------------------
>
>                 Key: CARBONDATA-997
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-997
>             Project: CarbonData
>          Issue Type: Bug
>          Components: data-query, presto-integration
>    Affects Versions: 1.1.0
>         Environment: spark 2.1, presto 0.166
>            Reporter: Vandana Yadav
>            Priority: Minor
>         Attachments: 2000_UniqData.csv
>
>
> Correct result does not display in presto integration as compare to CarbonData
> Steps to reproduce :
> 1. In CarbonData:
> a) Create table:
> CREATE TABLE uniqdata (CUST_ID int,CUST_NAME String,ACTIVE_EMUI_VERSION string, DOB timestamp, DOJ timestamp, BIGINT_COLUMN1 bigint,BIGINT_COLUMN2 bigint,DECIMAL_COLUMN1 decimal(30,10), DECIMAL_COLUMN2 decimal(36,10),Double_COLUMN1 double, Double_COLUMN2 double,INTEGER_COLUMN1 int) STORED BY 'org.apache.carbondata.format' TBLPROPERTIES ("TABLE_BLOCKSIZE"= "256 MB");
> b) Load data : 
> LOAD DATA INPATH 'hdfs://localhost:54310/2000_UniqData.csv' into table uniqdata OPTIONS('DELIMITER'=',' , 'QUOTECHAR'='"','BAD_RECORDS_ACTION'='FORCE','FILEHEADER'='CUST_ID,CUST_NAME,ACTIVE_EMUI_VERSION,DOB,DOJ,BIGINT_COLUMN1,BIGINT_COLUMN2,DECIMAL_COLUMN1,DECIMAL_COLUMN2,Double_COLUMN1,Double_COLUMN2,INTEGER_COLUMN1');
> 2. In presto 
> a) Execute the query:
> select BIGINT_COLUMN1, BIGINT_COLUMN1 from UNIQDATA where DECIMAL_COLUMN1<=BIGINT_COLUMN1 order by BIGINT_COLUMN1
> Actual result :
> In CarbonData:
> "| 123372038849    | 123372038849    |
> | 123372038850    | 123372038850    |
> | 123372038851    | 123372038851    |
> | 123372038852    | 123372038852    |
> | 123372038853    | 123372038853    |
> +-----------------+-----------------+--+
> 2,000 rows selected (1.087 seconds)
> "
> In presto:
> "Query 20170420_091614_00065_hd7jy failed: line 1:100: Column 'bigint_column1' is ambiguous
> select BIGINT_COLUMN1, BIGINT_COLUMN1 from UNIQDATA where DECIMAL_COLUMN1<=BIGINT_COLUMN1 order by BIGINT_COLUMN1"
> Expected result: it should display the same result as showing in CarbonData.


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