Thanks all. Now, the change has been merged to the master. So, ReplicatePOperator uses REPLICATE tag, instead of SPLIT tag. SPLIT tag will be used by real split operator.
Best, Taewoo On Tue, Sep 27, 2016 at 10:42 PM, Mike Carey <[email protected]> wrote: > +1 > > On Sep 27, 2016 10:11 PM, "Preston Carman" <[email protected]> wrote: > > > I always thought it was confusing that the ReplicatePOperator used the > > SPLIT tag. I think making the name consistent would be nice. > > > > On Tue, Sep 27, 2016 at 5:08 PM, Yingyi Bu <[email protected]> wrote: > > > Taewoo, > > > > > > I agree with you. > > > However, can you have two separate changes: > > > 1. Your current change https://asterix-gerrit.ics.uci.edu/#/c/1196/. > > Call > > > your "Split" "PartitionSplit" for now. > > > 2. Do what you proposed in the next change which only does the > renaming. > > > > > > That makes reviews less overwhelming and easier. > > > > > > Best, > > > Yingyi > > > > > > > > > On Tue, Sep 27, 2016 at 5:01 PM, Taewoo Kim <[email protected]> > wrote: > > > > > >> Hello All, > > >> > > >> Regarding the index-only plan, I am going to introduce an operator > named > > >> SplitOperator that propagates each tuple to only one output branch. > > >> Currently, ReplicateOperator propagates each tuple to all output > > branches. > > >> And ReplicatePOperator uses the physical operator tag as SPLIT. I > > suggest > > >> we change it to REPLICATE. Thus, SPLIT tag can be used for real Split > > >> operator. Any thoughts? > > >> > > >> Best, > > >> Taewoo > > >> > > >
