[jira] [Resolved] (CARBONDATA-3345) Presto query in Carbondata-streaming failed

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (CARBONDATA-3345) Presto query in Carbondata-streaming failed

Akash R Nilugal (Jira)

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

kumar vishal resolved CARBONDATA-3345.
--------------------------------------
    Resolution: Fixed

> Presto query in Carbondata-streaming failed
> -------------------------------------------
>
>                 Key: CARBONDATA-3345
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-3345
>             Project: CarbonData
>          Issue Type: Bug
>          Components: presto-integration
>    Affects Versions: 1.5.2
>            Reporter: zjy
>            Priority: Blocker
>              Labels: features
>         Attachments: image-2019-04-09-01-39-45-724.png, image-2019-04-09-01-50-37-797.png, image-2019-04-09-01-51-11-120.png, image-2019-04-09-01-51-53-115.png, image-2019-04-09-01-53-18-685.png, image-2019-04-09-01-54-05-491.png
>
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> I use streaming for saving switch' s syslog, here' s my table ddl
> CREATE TABLE IF NOT EXISTS syslog(id LONG, device_id LONG, ip STRING, message STRING, level SHORT, message_type CHAR(1), port_index INT, area_id LONG, createdon TIMESTAMP) STORED AS carbondata TBLPROPERTIES ('INVERTED_INDEX'='device_id,level,area_id','SORT_COLUMNS'='device_id,level,area_id,id','streaming'='true')
>  
> Here' s a record example
> !image-2019-04-09-01-39-45-724.png!
>  I mock ten thousand switchs,each one produced a record every 10 seconds on a day.
> On the early time, the presto' s query is normally.
> However, when the data growing, the presto query result is diffent from the spark sql.
>  
> !image-2019-04-09-01-50-37-797.png!
>  
> !image-2019-04-09-01-51-11-120.png!
>  
> !image-2019-04-09-01-51-53-115.png!
>  
>  
> !image-2019-04-09-01-53-18-685.png!
>  
> !image-2019-04-09-01-54-05-491.png!
>  
> I am looking forward to resolving it, thanks !



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)