Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
Aqua Data Studio 17.0.0-dev-76
Build #: 44689
Built on: 2015-Jul-10 05:19:20 PM
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=8
Steps to reproduce issue:
1. Copy the drivers JDBC41- in ADS- /datastudio/lib/drivers directory.
2. Launch ADSv17, Starting from Register server 'Test connection' to Table option->Script object to Window AS>Create [all options] , script generation, it shows error message in View Log for all visual operations.
StackTrace: java.sql.SQLException: [Simba][ImpalaJDBCDriver](500051) ERROR processing query/statement. Error Code: 0, SQL state: TStatus(statusCode:ERROR_STATUS, sqlState:HY000, errorMessage:AnalysisException: Syntax error in line 1:
|
|
173 KB
Observation:
1. The issue is not observed for ADSv16 build using any driver JDBC4 or JDBC41.[Tested for latest v16 build-ADS16.0.5-13]
2. The issue is observed starting from build ADS17.0.0-dev-65 .
Does this still occur using the latest ADS alpha builds?
Does this still occur using the latest ADS alpha builds?
@Sachin
->Yes, the error message is still displayed in latest build- ADS17-alpha-24
Tested on last 2 versions of cloudera Distribution.- CDH 5.4.0 and CDH 5.4.2
@Sachin
->Yes, the error message is still displayed in latest build- ADS17-alpha-24
Tested on last 2 versions of cloudera Distribution.- CDH 5.4.0 and CDH 5.4.2
Hi Anil, I think I know what the problem is.. The set -v call at connection time is used to query the server about the following parameters:
hive.support.concurrency
hive.enforce.bucketing
hive.exec.dynamic.partition.mode
hive.txn.manager
hive.compactor.initiator.on
hive.compactor.worker.threads
In Hive v.14, this was added to test these parameters in order to know whether the server supports inserts, updates and deletes. The Apache v.14 drivers supported this. As I recall, this worked for both Impala and Hive2 without issue. It now seems to only work for Hive2. I'm testing using Cloudera 5.4. Maybe it works for older servers? I tested all the latest Apache drivers(.14 and up) and the latest Simba drivers. The results are the same.
What I need to know is whether we need to test these parameters anymore for Hive2 to do inserts, updates and deletes. If this changed, at what version did it change? As for Impala, is this needed at all. Does Impala support inserts, updates and deletes like Hive2?
Since you have more experience with hive, I'm hoping that you know the answers or know a way to find out.
I will also do some research tomorrow and see what I can come up with.
Thanks for all of your help, Tom
Hi Anil, I think I know what the problem is.. The set -v call at connection time is used to query the server about the following parameters:
hive.support.concurrency
hive.enforce.bucketing
hive.exec.dynamic.partition.mode
hive.txn.manager
hive.compactor.initiator.on
hive.compactor.worker.threads
In Hive v.14, this was added to test these parameters in order to know whether the server supports inserts, updates and deletes. The Apache v.14 drivers supported this. As I recall, this worked for both Impala and Hive2 without issue. It now seems to only work for Hive2. I'm testing using Cloudera 5.4. Maybe it works for older servers? I tested all the latest Apache drivers(.14 and up) and the latest Simba drivers. The results are the same.
What I need to know is whether we need to test these parameters anymore for Hive2 to do inserts, updates and deletes. If this changed, at what version did it change? As for Impala, is this needed at all. Does Impala support inserts, updates and deletes like Hive2?
Since you have more experience with hive, I'm hoping that you know the answers or know a way to find out.
I will also do some research tomorrow and see what I can come up with.
Thanks for all of your help, Tom
@Tom
What I need to know is whether we need to test these parameters anymore for Hive2 to do inserts, updates and deletes. If this changed, at what version did it change? As for Impala, is this needed at all. Does Impala support inserts, updates and deletes like Hive2?
>> Impala supports Insert statement [ 'Insert into' and 'Load' statement].
Impala doesn't support update and delete statements.
@Tom
What I need to know is whether we need to test these parameters anymore for Hive2 to do inserts, updates and deletes. If this changed, at what version did it change? As for Impala, is this needed at all. Does Impala support inserts, updates and deletes like Hive2?
>> Impala supports Insert statement [ 'Insert into' and 'Load' statement].
Impala doesn't support update and delete statements.
Hi Anil, Looking at the latest documentation, the server tests are still required for Hive2. Looks like inserts, updates and deletes are only Hive2 and not Impala. You have to use .14 or greater Apache drivers or 2.5.10 or greater Simba drivers for inserts, updates and deletes to work. I added this in and don't do any server tests for Impala. Please give it a try.. Thanks, Tom
Hi Anil, Looking at the latest documentation, the server tests are still required for Hive2. Looks like inserts, updates and deletes are only Hive2 and not Impala. You have to use .14 or greater Apache drivers or 2.5.10 or greater Simba drivers for inserts, updates and deletes to work. I added this in and don't do any server tests for Impala. Please give it a try.. Thanks, Tom
Issue #13476 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build ADS 17.0.0-alpha-32 |
| No time estimate |
Observation:
1. The issue is not observed for ADSv16 build using any driver JDBC4 or JDBC41.[Tested for latest v16 build-ADS16.0.5-13]
2. The issue is observed starting from build ADS17.0.0-dev-65 .