[ 
https://issues.apache.org/jira/browse/TINKERPOP-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18143961#comment-18143961
 ] 

ASF GitHub Bot commented on TINKERPOP-3295:
-------------------------------------------

Iryna-Kahamlyk opened a new pull request, #3802:
URL: https://github.com/apache/tinkerpop/pull/3802

   JIRA: https://issues.apache.org/jira/browse/TINKERPOP-3295
   
   Fixed write steps (`addV()`, `addE()`, `mergeV()`, `mergeE()`, `property()`) 
performing a single write for a bulked traverser instead of one write per bulk 
count. Each write step now runs once per bulk unit.
   
   The bug also reaches child traversals. It is fixed for parent steps that 
pass the bulked traverser into the child unchanged, such as `union()`, 
`choose()`, `optional()`, `local()` and `repeat()`. It is not fixed for parent 
steps that reset the bulk to 1 before running the child, such as `map()`, 
`flatMap()`, `sideEffect()`, `coalesce()`, `where()`, and traversal arguments 
like `addE().to(addV())`. A write inside those children still happens once per 
bulked traverser. This limitation is noted in the upgrade docs and left for a 
separate discussion.




> inject() and addV() has bulking issues
> --------------------------------------
>
>                 Key: TINKERPOP-3295
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-3295
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: process
>    Affects Versions: 3.7.7
>            Reporter: Stephen Mallette
>            Priority: Critical
>
> {code}
>   gremlin> g.inject(1,1).addV('X').id()
>   ==>0
>   ==>0
>   gremlin> g.V().count()
>   ==>1
> {code}
> the example is for {{addV()}} and the {{inject()}} start step but 
> investigation should probably cover other variations of mutations like, 
> {{addE()}}, {{mergeV/E()}} and {{drop()}} and steps and mid-traversal 
> {{inject()}}.
> Should also cover cases like: {{g.inject(1, 1).addV('X').property(T.id, 
> 'same')}}



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to