You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by Ken Hu <ke...@gmail.com> on 2025/10/02 23:28:37 UTC

[DISCUSS] Prevent SupplyingBarriers inside Repeat

Hi All,

I propose preventing SupplyingBarriers from running inside repeat().
SupplyingBarriers, of which SideEffectCapStep is currently the only
implementation, are similar to ReducingBarriers in that they consume all
starts and supply a single traverser to the next Step.

This consumption process destroys the loop information that serves as a
terminating condition for many repeat traversals. To prevent user errors,
we should prevent SupplyingBarriers from being used inside repeat in the
StandardVerificationStrategy like it is for ReducingBarriers.

Does anyone have any thoughts regarding this?

Thanks,
Ken

Re: [DISCUSS] Prevent SupplyingBarriers inside Repeat

Posted by Ken Hu <ke...@gmail.com>.

I've CTR'd a change for this.
Commit 0516a7d5b8655346854ea162e0f6171a15e0281b.

On Thu, Oct 2, 2025 at 4:28 PM Ken Hu <ke...@gmail.com> wrote:

> Hi All,
>
> I propose preventing SupplyingBarriers from running inside repeat().
> SupplyingBarriers, of which SideEffectCapStep is currently the only
> implementation, are similar to ReducingBarriers in that they consume all
> starts and supply a single traverser to the next Step.
>
> This consumption process destroys the loop information that serves as a
> terminating condition for many repeat traversals. To prevent user errors,
> we should prevent SupplyingBarriers from being used inside repeat in the
> StandardVerificationStrategy like it is for ReducingBarriers.
>
> Does anyone have any thoughts regarding this?
>
> Thanks,
> Ken
>