[
https://issues.apache.org/jira/browse/TINKERPOP-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18032593#comment-18032593
]
ASF GitHub Bot commented on TINKERPOP-3196:
-------------------------------------------
xiazcy commented on code in PR #3246:
URL: https://github.com/apache/tinkerpop/pull/3246#discussion_r2457184490
##########
docs/src/upgrade/release-3.8.x.asciidoc:
##########
@@ -319,6 +319,34 @@ This is a breaking change for .NET applications that rely
on byte values. Existi
See: link:https://issues.apache.org/jira/browse/TINKERPOP-3161[TINKERPOP-3161]
+==== Split bulked traversers for `local()`
+
+Prior to 3.8.0, the `local()` exhibited "traverser-local" semantics, where the
local traversal would independently to
+each individual Traverser. This often led to confusion, especially in the
presence of reducing barrier steps as the
+presence of bulked traversers would lead to multiple objects being processed
at once. `local()` has been updated to
+automatically split any bulked traversers and thus now exhibits true
"object-local" semantics.
Review Comment:
```suggestion
Prior to 3.8.0, local() exhibited "traverser-local" semantics, where the
local traversal would apply independently to each individual
Traverser. This often led to confusion, especially in the presence of
reducing barrier steps, as bulked traversers would cause multiple
objects to be processed at once. local() has been updated to automatically
split any bulked traversers and thus now exhibits true
"object-local" semantics.
```
> Implement proposal 5 regarding changes to local
> -----------------------------------------------
>
> Key: TINKERPOP-3196
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3196
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Reporter: Ken Hu
> Priority: Major
> Fix For: 3.8.0
>
>
> [This discuss
> thread|https://lists.apache.org/thread/nhv6sopypylpf2j1rb9tr7k9r8gjcdvt] and
> its subsequent
> [proposal|https://github.com/apache/tinkerpop/blob/master/docs/src/dev/future/proposal-scoping-5.asciidoc]
> outline semantic changes that should be made to the local() step. LocalStep
> should now be used as a way to control traverser flow and enable lazy
> evaluation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)