Re: Missing version identifier - Thrift::API::HiveClient2

Sorry for not answering the question, but for pure curiosity, why are you using

try sub { ... }, catch sub { ... };
[download]

instead of

try { ... } catch { ... };
[download]

($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,
[download]

Comment on Re: Missing version identifier - Thrift::API::HiveClient2 Select or Download Code

Replies are listed 'Best First'.
Re^2: Missing version identifier - Thrift::API::HiveClient2 by kwh78239 (Novice) on Jul 25, 2018 at 16:00 UTC
Force of habit, I suppose. Works the same. Any thoughts on the hadoop issue?	[reply]
Re^3: Missing version identifier - Thrift::API::HiveClient2 by kwh78239 (Novice) on Jul 27, 2018 at 20:44 UTC
OK, did more research and found on the github of the authors of Thrift::API::HiveClient2 some good information. Need to add sasl => 1 to the client creation method. Then it will get past the SASL issue, but will complain about Kerberos issues. Having to look further at that now (but on the trail) as the consultant we had in to set up hadoop for us set it up with no security at all. Java can digest that it seems, but not sure about the Perl module. When I get this fully resolved, I'll update this post as others have hit this issue but didn't post solutions for others to see, or at least were simple enough for me to understand. Sort of Red Book information. Meanwhile, has anyone run hive server2 without Kerberos and got it to work? The .pm developers notes say they've only tested with Kerberos. Ken Hylton	[reply]
Re^4: Missing version identifier - Thrift::API::HiveClient2 by kwh78239 (Novice) on Jul 31, 2018 at 19:17 UTC
ok, final message on this thread from me anyhow. It looks like the sasl=>1 in the create fixes the sasl issue. The Kerberos issue as more problematic because I did not want to go back set up Kerberos on all the boxes. A total effort because we do not use kerberos at all, so a total from the ground up effort. From what I gathered, the easiest way to do that was to start all over from the ground up with hadoop, and I have no time for that now. So, I moved on to getting it to work via Impala and ODBC. Hopefully, that will go smoother.	[reply]