Aqua Data Studio 17.0.0-dev-76
Build #: 44689
Built on: 2015-Jul-10 05:19:20 PM
ADS RAM: 4GB
OS: Ubuntu 14.04 LTE
Linux (3.13.0-55-generic, amd64) / UTF-8 / en / IN / Oracle Corporation 1.8.0_40-b26
Memory: Max=4,433,379,328; Total=1,329,070,080; Free=986,494,304; CPUs=8Database: Cloudera CDH 5.4.0 - Impala 2.2.0
Steps to reproduce issue:
|
177 KB
|
142 KB
|
39 KB
|
55 KB
|
119 KB
@Tariq:
Please find below queries, which helps for issue analysis.
@Sachin:
Beeline interface - Insert records into table, using insert command.
Please refer screenshot: beeline-interface.png, beeline-interface-2.png, beeline-interface-3.png for different examples.
In beeline-interface-3.png , ADS displayed proper result for select * query , while impala beeline interface displays only 1st column in result for same query.
@Sachin:
Beeline interface - Insert records into table, using insert command.
Please refer screenshot: beeline-interface.png, beeline-interface-2.png, beeline-interface-3.png for different examples.
In beeline-interface-3.png , ADS displayed proper result for select * query , while impala beeline interface displays only 1st column in result for same query.
The Driver Parameter is already set to AuthMech=0.
Still the issue occurs.
The Driver Parameter is already set to AuthMech=0.
Still the issue occurs.
Hi Team, This works correctly with the Apache drivers so I suspect that beeline will also work correctly. It is a problem with the newer Cloudera Connector drivers. I tested an older version of the Cloudera Connector driver and there was no exception. I also checked for open issues against this error and could not find anything. I think we should resolve this issue as "won't fix". Anil, Sachin, Thoughts on this?? Thanks, Tom
Hi Team, This works correctly with the Apache drivers so I suspect that beeline will also work correctly. It is a problem with the newer Cloudera Connector drivers. I tested an older version of the Cloudera Connector driver and there was no exception. I also checked for open issues against this error and could not find anything. I think we should resolve this issue as "won't fix". Anil, Sachin, Thoughts on this?? Thanks, Tom
Marking as Won't Fix based upon Tom's analysis.
Marking as Won't Fix based upon Tom's analysis.
Issue #13479 |
Closed |
Won't Fix |
Resolved |
Completion |
No due date |
No fixed build |
No time estimate |
@Tariq:
Please find below queries, which helps for issue analysis.