Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Drill >> mail # dev >> Executing Logical Plan


Copy link to this message
-
RE: Executing Logical Plan
Good thing that you can run the test case from RunSimplePlan.java. That is a good way of knowing the flow too.

And for the simple_plan.json, It is not correctly written.
There have been few changes in how logical plans must be written, and simple_plan.json is still in the old style.
You would be able to run the simple_join.json for your work.
Try:
mvn exec:java -Dexec.mainClass="org.apache.drill.exec.ref.ReferenceInterpreter" -Dexec.classpathScope=test -Dexec.args="src/test/resources/simple_join.json"

I would raise a JIRA for the simple_plan & update the wiki :)

- Yash
-----Original Message-----
From: naru116 . [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 13, 2013 12:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Executing Logical Plan

Yash,

RunSimplePlan.java worked for me and that should be a good starting point.

However, running the interpreter from exec/ref  using the maven exec command did not output any results on the console, which is surprising.
On Tue, Nov 12, 2013 at 10:09 PM, Yash Sharma <[EMAIL PROTECTED]>wrote:

> Hi Narendra,
> You should be able to run the reference interpreter directly from
> /exec/ref/
>
> cd exec/ref
> mvn exec:java
> -Dexec.mainClass="org.apache.drill.exec.ref.ReferenceInterpreter"
> -Dexec.classpathScope=test -Dexec.args="src/test/resources/simple_plan.json"
>
> Can you send us the error you are getting there.
>
> Also like I mentioned, you can call your logical plan from the
> RunSimplePlan.java class and execute the test case from your IDE directly.
> By that way you can also debug where exactly your flow is failing.
>
> Let us know if you are stuck somewhere.
> - Yash
>
>
>
> -----Original Message-----
> From: naru116 . [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 13, 2013 11:15 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Executing Logical Plan
>
> Hi Dhruv & Yash,
>
> thanks for the pointers. I downloaded the source code from git,
> compiled but I don't seen any bin directory being created after doing mvn install.
> However, submit_plan is located under
> incubator-drill/distribution/src/resources/ folder and executing  from
> there doesn't help.
>
> I tried running the referenceinterpreter from IDE (intellij) with
> simple_plan.json.  However, the program doesn't terminate for unknown
> reasons.
>
> So, what options do I have to move fwd??
>
> -narendra
>
>
> On Mon, Nov 11, 2013 at 11:24 PM, naru116 .
> <[EMAIL PROTECTED]
> >wrote:
>
> > Hi,
> >
> > I'm newbie to the Apache Drill and so please bear with me. I'm
> > trying to play around with the code adding few string/math functions
> > (e.g reverse
> > etc) and I have been told by Jacques that one could use Logical plan
> > to test these functions even if there's no support in the sqlline parser.
> >
> > If I create a logical plan in json file (say testreverse.json) , how
> > do I execute this json file? In other words, how do I feed the json
> > to interpreter to get the output??
> >
> > Thanks,
> > Narendra
> >
>
> ________________________________
>
>
>
>
>
>
> NOTE: This message may contain information that is confidential,
> proprietary, privileged or otherwise protected by law. The message is
> intended solely for the named addressee. If received in error, please
> destroy and notify the sender. Any use of this email is prohibited
> when received in error. Impetus does not represent, warrant and/or
> guarantee, that the integrity of this communication has been
> maintained nor that the communication is free of errors, virus, interception or interference.
>

________________________________
NOTE: This message may contain information that is confidential, proprietary, privileged or otherwise protected by law. The message is intended solely for the named addressee. If received in error, please destroy and notify the sender. Any use of this email is prohibited when received in error. Impetus does not represent, warrant and/or guarantee, that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference.