[jira] [Commented] (CARBONDATA-3914) We are getting the below error when executing select query on a carbon table when no data is returned from hive beeline.

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

[jira] [Commented] (CARBONDATA-3914) We are getting the below error when executing select query on a carbon table when no data is returned from hive beeline.

Akash R Nilugal (Jira)

    [ https://issues.apache.org/jira/browse/CARBONDATA-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205495#comment-17205495 ]

Prasanna Ravichandran commented on CARBONDATA-3914:
---------------------------------------------------

Attached the screenshot after the fix.

> We are getting the below error when executing select query on a carbon table when no data is returned from hive beeline.
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CARBONDATA-3914
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-3914
>             Project: CarbonData
>          Issue Type: Bug
>          Components: hive-integration
>    Affects Versions: 2.0.0
>         Environment: 3 node One track ANT cluster
>            Reporter: Prasanna Ravichandran
>            Priority: Minor
>             Fix For: 2.1.0
>
>         Attachments: Nodatareturnedfromcarbontable-IOexception.png
>
>          Time Spent: 6h 20m
>  Remaining Estimate: 0h
>
> If no data is present in the table, then we are getting the below IOException in carbon, while running select queries on that empty table. But in hive even if the table holds no data, then it is working for select queries.
> Expected results: Even the table holds no records it should return 0 or no rows returned. It should not throw error/exception.
> Actual result: It is throwing IO exception - Unable to read carbon schema.
>  
> Attached the screenshot for your reference.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)