asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Taewoo Kim <wangs...@gmail.com>
Subject Re: Physical Operator Tag Change (SPLIT -> REPLICATE)
Date Wed, 28 Sep 2016 00:11:15 GMT
@Yingyi: Thanks for the suggestion. Actually, I have crated a separate
patch for this change only: https://asterix-gerrit.ics.uci.edu/#/c/1219/.
Once this is merged, the review for the second step would be much easier.

Best,
Taewoo

On Tue, Sep 27, 2016 at 5:08 PM, Yingyi Bu <buyingyi@gmail.com> 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 <wangsaeu@gmail.com> 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
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message