[
https://issues.apache.org/jira/browse/LENS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276640#comment-14276640
]
Amareshwari Sriramadasu commented on LENS-179:
----------------------------------------------
The test failures are happening because the explain is failing for hive driver
tests - Explain fails without the patch also, but execute passes so tests are
passing.
Explain on HiveDriver is failing because the session under which explain is
getting called gets changed, as it uses thread local variable right now. We
should have a proper contract on LensDriver.explain which passes
ExplainQueryContext which passes, user name and sessionid correctly, sothat
hive driver can map the correct version.
If no objections, i will go ahead and do the contract changes wrt signature
change - Makes the jira incompatible from driver signature changes.
> Seeing Driver Query Plan of the selected driver is null on explain
> ------------------------------------------------------------------
>
> Key: LENS-179
> URL: https://issues.apache.org/jira/browse/LENS-179
> Project: Apache Lens
> Issue Type: Bug
> Components: server
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Fix For: 2.0
>
> Attachments: LENS-179.2.patch
>
>
> Here is the stacktrace :
> {noformat}
> 30 Dec 2014 10:38:07,293 [Grizzly-worker(3)] ERROR
> org.apache.lens.server.query.QueryExecutionServiceImpl - Error during
> explain :
> org.apache.lens.api.LensException: Driver Query Plan of the selected driver
> is null
> at
> org.apache.lens.server.api.query.DriverSelectorQueryContext.getSelectedDriverQueryPlan(DriverSelectorQueryContext.java:157)
> at
> org.apache.lens.server.api.query.AbstractQueryContext.getSelectedDriverQueryPlan(AbstractQueryContext.java:151)
> at
> org.apache.lens.server.query.QueryExecutionServiceImpl.explain(QueryExecutionServiceImpl.java:1791)
> at
> org.apache.lens.server.query.QueryServiceResource.query(QueryServiceResource.java:223)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:151)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:171)
> at
> org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:195
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
