Hi Richard, In my case, there is no store or dump involved. My code is like:
a = ... b = ... c = ... EXEC; d = ... e = ... ... By adding the "EXEC;", i try to stop multiquery optimizer from combining all a, b, c, d, e into a single MR plan. In other words, do a, b, c in one MR and d, e in another. I guess it is not doable right now except disable multiquery or add a "store c into ..." before EXEC. Shawn On Thu, Mar 17, 2011 at 12:20 PM, Richard Ding <[email protected]> wrote: > What you want is the 'run' command. With the run command, every store > triggers execution. > > Thanks > -- Richard > > > > On 3/17/11 10:48 AM, "Xiaomeng Wan" <[email protected]> wrote: > > Hi, > I tried to use exec to stop multiquery optimizer from combining too > many actions together, which will result in heap space problem. But it > seems multiquery just ignores exec, and still combines actions before > and after exec together. Disable multiquery works for me, just > wondering whether it is a bug? or my misunderstanding of exec? > > Regards, > Shawn > >
