Hello Sudarshan, Nishidha, You don't need to wait for the ASF CLA to post a preview patch. My suggestion would be to post a preview patch as soon as reasonably possible as (1) it makes it easier to get help and (2) we avoid duplication of work as we are starting to work on some parts that you've touched as well, such as upgrading LLVM.
If you decide to to this way, the easiest way to post a preview patch would be to send it for code review to the Impala gerrit. If it's a preview, please prefix the CR subject with "PREVIEW:" to make it clear it's just for discussion. https://github.com/cloudera/Impala/wiki/Using-Gerrit-to-submit-and-review-patches Silvius On Wed, Feb 24, 2016 at 9:50 AM, Henry Robinson <[email protected]> wrote: > (bcc:[email protected], [email protected]. Please > use the incubator mailing lists going forward). > > Hi Sudarshan - > > That's great to hear! > > Since Impala is in the process of becoming an Apache Incubator project, I > think the best thing is if you examine the ASF's requirements for CLAs: > > http://www.apache.org/licenses/ (see Contributor License Agreements) > > We are in the process of granting all our source code to the ASF - which > should happen soon, with any luck! - and as a result the agreement should > be between you (or your employers) and the ASF. > > Best, > Henry > > On 24 February 2016 at 09:41, Sudarshan Jagadale <[email protected]> > wrote: > >> Dear Tim and Cloudera Team, >> >> Its been really pleasure to work with Coludera team since last 1-2 >> months, we receive quick responses from community. >> >> We really want to take this activity 100% conclusion/working on Power >> platform, >> >> We are almost done, just testing has some issues, are in progress. >> >> To take this ahead, We could like to know if you have CLA -"Contributor >> License Agreement" (or anything like this for contributors like us) for >> development and porting on power etc. >> >> Thanks and Regards, >> Sudarshan Jagadale >> Power System Solutions >> >> [image: Inactive hide details for Tim Armstrong ---02/24/2016 03:45:29 >> AM---HI Nishidha, Sorry for the slow response - we're approach]Tim >> Armstrong ---02/24/2016 03:45:29 AM---HI Nishidha, Sorry for the slow >> response - we're approach Impala 2.5.0 code freeze and >> >> From: Tim Armstrong <[email protected]> >> To: nishidha panpaliya <[email protected]> >> Cc: Impala Dev <[email protected]>, Nishidha >> Panpaliya/Austin/Contr/IBM@IBMUS, Sudarshan >> Jagadale/Austin/Contr/IBM@IBMUS >> Date: 02/24/2016 03:45 AM >> Subject: Re: Hive error while running tests >> ------------------------------ >> >> >> >> HI Nishidha, >> Sorry for the slow response - we're approach Impala 2.5.0 code freeze >> and things have been hectic. >> >> Just to confirm, were the hive servers up and working normally? If you >> source bin/impala-config.sh then run "hive" you should get the hive CLI and >> be able to interact with the database normally. >> >> I think buildall.sh with -noclean won't restart Hive, so it's possible >> it's just not running. >> >> On Mon, Feb 22, 2016 at 4:48 AM, nishidha panpaliya < >> *[email protected]* <[email protected]>> wrote: >> >> Hi, >> >> I'm trying to run Impala tests on ppc64le using below command - >> ${IMPALA_HOME}/buildall.sh -noclean -testdata >> >> While loading test data, I see error as below in >> Impala/cluster_logs/data_loading/data-load-functional-exhaustive.log >> Error: Could not open client transport with JDBC Uri: >> jdbc:hive2://localhost:11050/default: null (state=08S01,code=0) >> java.sql.SQLException: Could not open client transport with >> JDBC Uri: jdbc:hive2://localhost:11050/default: null >> at >> >> org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:221) >> at >> >> org.apache.hive.jdbc.HiveConnection.<init>(HiveConnection.java:167) >> at >> org.apache.hive.jdbc.HiveDriver.connect(HiveDriver.java:105) >> at >> java.sql.DriverManager.getConnection(DriverManager.java:571) >> at >> java.sql.DriverManager.getConnection(DriverManager.java:187) >> at >> >> org.apache.hive.beeline.DatabaseConnection.connect(DatabaseConnection.java:137) >> at >> >> org.apache.hive.beeline.DatabaseConnection.getConnection(DatabaseConnection.java:178) >> at org.apache.hive.beeline.Commands.close(Commands.java:953) >> at >> org.apache.hive.beeline.Commands.closeall(Commands.java:935) >> at org.apache.hive.beeline.BeeLine.close(BeeLine.java:823) >> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:769) >> at >> >> org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:480) >> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:463) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native >> Method) >> at >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >> at >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:606) >> at org.apache.hadoop.util.RunJar.run(RunJar.java:221) >> at org.apache.hadoop.util.RunJar.main(RunJar.java:136) >> Caused by: org.apache.thrift.transport.TTransportException >> at >> >> org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:132) >> at >> >> org.apache.thrift.transport.TTransport.readAll(TTransport.java:86) >> at >> >> org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:178) >> at >> >> org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:307) >> at >> >> org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37) >> at >> >> org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:196) >> ... 18 more >> Error executing file from Hive: >> load-functional-query-exhaustive-hive-generated.sql >> >> >> I also checked hive.log and it shows error as below - >> 2016-02-22 15:53:36,230 ERROR server.TThreadPoolServer >> (TThreadPoolServer.java:run(294)) - Thrift error occurred during >> processing >> of message. >> org.apache.thrift.protocol.TProtocolException: Missing >> version in readMessageBegin, old client? >> at >> >> org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:228) >> at >> org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:27) >> at >> >> org.apache.hive.service.auth.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:56) >> at >> >> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:285) >> at >> >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >> at >> >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >> at java.lang.Thread.run(Thread.java:745) >> >> I tried setting hive auth argument value to "none" or "nosasl" or >> even nothing while making JDBC connection >> jdbc:hive2://localhost:11050/default. But found same error. >> >> One thing that I noticed is difference in libthrift.jar version which >> is inside hive*/lib and thrift jar installed by thirdparty/thrift-0.9.0. >> One which is inside hive is 0.9.2 and installed one is 0.9.0. I also tried >> copying 0.9.0 jar in thirdparty/hive*/lib and other directories like >> thirdparty/sentry*/lib, thirdparty/hbase*/lib. No luck so far. >> But I think this is also the case on x86 platform since those two >> versions of jar come from Impala source code. >> >> Could you anyone please help me? >> >> Thanks in advance, >> Nishidha >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Impala Dev" group. >> To unsubscribe from this group and stop receiving emails from it, >> send an email to *[email protected]* >> <[email protected]>. >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Impala Dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > > > > -- > Henry Robinson > Software Engineer > Cloudera > 415-994-6679 > > -- > You received this message because you are subscribed to the Google Groups > "Impala Dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. >
