drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Parth Chandra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5659) C++ Client (master) behavior is unstable resulting incorrect result or exception in API calls
Date Wed, 12 Jul 2017 17:51:00 GMT

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

Parth Chandra commented on DRILL-5659:
--------------------------------------

I can also reproduce it reading from the tpch lineitem table, though Laurent's is clearly
the smallest reproduction of the issue. FWIW, valgrind shows no corruption or leaks when this
issue crops up.


> C++ Client (master) behavior is unstable resulting incorrect result or exception in API
calls
> ---------------------------------------------------------------------------------------------
>
>                 Key: DRILL-5659
>                 URL: https://issues.apache.org/jira/browse/DRILL-5659
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Rob Wu
>             Fix For: 1.11.0
>
>         Attachments: 1-10cppClient-1.10.0Drillbit-hive.log, 1-10cppClient-1.10.0Drillbit-metadata
and catalog test.log, 1-10cppClient-1.9.0Drillbit-dfs.log, 1-10cppClient-1.9.0Drillbit-hive.log,
1-10cppClient-1.9.0Drillbit-metadata and catalog test.log, 1-11cppClient-1.10.0Drillbit-hive.log,
1-11cppClient-1.10.0Drillbit-metadata and catalog test.log, 1-11cppClient-1.9.0Drillbit-dfs.log,
1-11cppClient-1.9.0Drillbit-hive.log, 1-11cppClient-1.9.0Drillbit-metadata and catalog test.log
>
>
> I recently compiled the C++ client (on windows) from master and tested against a 1.9.0
drillbit. The client's behavior does not meet the stable release requirement.
> Some API functionalities are broken and should be investigated.
> Most noticeable is the getColumns(...) call. It will throw an exception with "Cannot
decode getcolumns results" when the number of rows (column records) exceeds a certain number.

> I also noticed that: during query execution + data retrieval, if the table is large enough,
the result coming back will start to become NULL or empty.
> I will see if I can generate some drillclient logs to put in the attachment.
> I will also compile and test on other platforms.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message