Thank you.
--- On Wed, 3/11/09, Prasad Chakka <[email protected]> wrote: > From: Prasad Chakka <[email protected]> > Subject: Re: Call sequence > To: "[email protected]" <[email protected]>, > "[email protected]" <[email protected]> > Date: Wednesday, March 11, 2009, 3:11 PM > Hi Shyam, > > I find Eclipse especially useful for these kind of things. > Follow the instructions at > http://wiki.apache.org/hadoop/Hive/GettingStarted/EclipseSetup > and run a unit test in debug mode and observe the stack. > > Thanks, > Prasad > > > ________________________________ > From: Ashish Thusoo <[email protected]> > Reply-To: <[email protected]> > Date: Wed, 11 Mar 2009 15:08:13 -0700 > To: <[email protected]>, > <[email protected]> > Subject: RE: Call sequence > > That should be Driver.java. Look at the run() method. That > calls ParseDriver.parse() to get the AST. And them > sem.analyze() to do semantic analysis, optimization and plan > generation. Finally it goes through the Task list and runs > the tasks according to the dependencies. > > Ashish > > -----Original Message----- > From: Shyam Sarkar [mailto:[email protected]] > Sent: Wednesday, March 11, 2009 2:49 PM > To: [email protected] > Subject: Call sequence > > > Hello, > > I am trying to understand the call sequence of Java classes > from the top level (command processor). I can see Parser and > Lexer generated by Antlr. Can someone please help me on the > call sequence ? Where is the front level command processor > that collects a query as a string and then calls parser? > > thanks, > [email protected]
