FAQ
Santhakumar – sorry for the delayed response. If you haven't already, can
you make sure MicroStrategy is configured to use the 2.0 ODBC API? You
should be able to set this through the advanced settings in the DB
instance. Not sure if you've already made this change, but if not please
give it a try and let us know if that helps.

Thanks.

Jonathan



On Wed, May 22, 2013 at 10:58 PM, Santha Kumar wrote:

Hi Jonathan,

We are successfully able to connect to Hive and Impala from Microstrategy
in AWS Environment. And also we are able to run some of the report without
any error.

But in some of the reports, its not getting executed and throws out an
ODBC error, please find the attached screen shot for error message. I am
really confused, *while few reports gets executed sccessfully, why some
of the reports are throwing an error*. Looked for information on this
error, but couldn't find a one. Can you please help us out in resolving
this isssue?

Please verify the attached screen shot.

On Wed, May 8, 2013 at 5:39 PM, Jonathan Seidman wrote:

Great news Santhakumar. Let us know if there's anything else we can do to
help.

On Wed, May 8, 2013 at 11:37 AM, Santha Kumar wrote:

Hi Jonathan,

Thank you for responding. We are very much glad that, we are able to
connect to both Hive and Impala from Microstrategy in AWS Environment. And
also generate reports out of that. We were using Microstrategy 9.3.0
version.

Thank you Jonathan for clarifying all the queries. It was really helpful
for establishing the connectivity.

Regards,
Santhakumar


On Mon, May 6, 2013 at 5:06 PM, Jonathan Seidman wrote:

Hey Santhakumar – note that with EC2 you'll need to ensure that you've
opened up the ports that the Impala or HiveServer processes are listening
on. So for Impala, the first thing to check is that you've added port 21000
(or whichever port you've specified for the Impala daemons) to a security
group for your EC2 nodes. Otherwise you should be able to connect without
any issues, as long as the Impala process is running properly. If you
haven't already, I'd also recommend testing connectivity with the Impala
shell on one of the EC2 nodes.

Thanks.

Jonathan

On Mon, May 6, 2013 at 12:08 AM, Santha Kumar wrote:

Hi Jonathan,

I am again facing an issue with respect to connectivity. This time, i
am trying to connet to impala through Microstrategy and both are available
in AWS. We installed the cloudera connector and tried to access the impala
tables. But we are not able to connect, getting the same error as attached,

Is there a difference in connecting in AWS?
Please verify and let me know the issue.




On Fri, Apr 19, 2013 at 4:55 PM, Jonathan Seidman <
jseidman@cloudera.com> wrote:
Thanks for the update Santhakumar. Glad to hear this helped, although
it's interesting that you still needed to change this with 9.3. I'll follow
up with MSTR to see if this is expected behavior.

On Fri, Apr 19, 2013 at 10:40 AM, Santha Kumar wrote:

Hi Jonathan,

That was awesome. It really solved my issue which i mentioned above.
I am able to connect to Impala through microstrategy. Thank you so
much...:)

Regards,
Santhakumar


On Thu, Apr 18, 2013 at 9:39 PM, Jonathan Seidman <
jseidman@cloudera.com> wrote:
Yes, as far as I know you should not be seeing this with 9.3.
Here's some follow up from a MSTR resource – see if the following helps,
and if not we'll need to follow up:

If they RMC on the MicroStrategy Database Instance…VLDB
Properties…Report Pre/Post SQL…Pre SQL Statement 5, they should see this
statement in there. They can just blank that out, save and close, restart
I-server and give this a try.


Thanks.

Jonathan
On Thu, Apr 18, 2013 at 10:35 AM, Santha Kumar wrote:

Hi Jonathan,

We are using MSTR version 9.3. So i think there won't be much
issue. Can you please clarify on " the setting ‘Report Pre
statement 1’ under pre/post statements in the MSTR VLDB settings". It would
be very much helpful if you can elaborate a little.

Regards,
San


On Wed, Apr 17, 2013 at 3:11 AM, Jonathan Seidman <
jseidman@cloudera.com> wrote:
Santha,

You should be able to fix this by changing the setting ‘Report
Pre statement 1’ under pre/post statements in the MSTR VLDB settings. Note
that this shouldn't be an issue with more recent versions of MSTR, but if
you're using an earlier version than you'll need to modify this setting.

Thanks.

Jonathan


On Tue, Apr 16, 2013 at 7:42 AM, Santha Kumar <cr.mhsan@gmail.com
wrote:
On Monday, December 3, 2012 3:28:54 PM UTC+5:30, Suresh K wrote:

HI,

I have one cluster with 2 nodes running on Amazon EC2 with
impala configured and working.

On my windows PC, i installed MSTR ODBC driver and configured
as outlined here,

https://ccp.cloudera.com/**display/IMPALA10BETADOC/**
Configuring+Impala+to+Work+**with+ODBC<https://ccp.cloudera.com/display/IMPALA10BETADOC/Configuring+Impala+to+Work+with+ODBC>

but when i try to connect from php script, i get following
error,
------------------------------**------------------------------*
*------------------------------**------------------------------
**------------------------------**
------------------------------**------
Thrift: Mon Dec 03 15:19:03 2012 TSocket::open() connect()
<Host: ec2-*.*.*.*.compute-1.**amazonaws.com<http://compute-1.amazonaws.com>Port: 21000>errno = 0
DBOpenConnection: connect() failed: errno = 0

Warning: odbc_connect(): SQL error: Communication link failure,
SQL state 08S01 in SQLConnect in TestImpala.php on line 4
------------------------------**------------------------------*
*------------------------------**------------------------------
**------------------------------**
------------------------------**------

What am i missing?

Thanks in Advance.
Regards,
Suresh

Hi Jonathan,
I am getting the below error when running the report
Microstrategy which is connected to IMPALA Server. I am able to connect to
warehouse catalog and also able to import the required table and create
facts and attribute. But when i run the report i am getting the below
error, can u please help me out to resolve this issue...


""Error type: Odbc error. Odbc operation attempted:
SQLExecDirect. [42000:0: on HSTMT]
com.cloudera.impala.common.AnalysisException: Syntax error at:

set hive.auto.convert.join=true

^

Encountered: IDENTIFIER

Expected: DESCRIBE, SELECT, SHOW, USE, INSERT

at
com.cloudera.impala.analysis.AnalysisContext.analyze(AnalysisContext.java:135)

at
com.cloudera.impala.service.Frontend.createExecRequest(Frontend.java:221)

at
com.cloudera.impala.service.JniFrontend.createExecRequest(JniFrontend.java:91)

Caused by: java.lang.Exception: Syntax error

at com.cloudera.impala.analysis.SqlParser.unrecovere Connection
String:
DSN=DSN_POC_IMP;DATABASE=aham;HOST=10.155.100.140;PORT=21000;FRAMED=;. SQL
Statement: set hive.auto.convert.join=true.""



Regards,

Santhakumar

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 14 of 19 | next ›
Discussion Overview
groupimpala-user @
categorieshadoop
postedApr 16, '13 at 12:42p
activeJun 28, '13 at 6:35p
posts19
users6
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase