[jira] [Closed] (TINKERPOP-3049) onCreate for mergeV() doesn't handle Cardinality functions

2024-02-06 Thread Stephen Mallette (Jira) 


 [ 
https://issues.apache.org/jira/browse/TINKERPOP-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Mallette closed TINKERPOP-3049.
---
Fix Version/s: 4.0.0
   3.7.2
   Resolution: Fixed

https://github.com/apache/tinkerpop/commit/66db18e17ad2937c71a3b2167fd0d7989ab2cbd7

> onCreate for mergeV() doesn't handle Cardinality functions
> --
>
> Key: TINKERPOP-3049
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3049
> Project: TinkerPop
>  Issue Type: Bug
>  Components: process
>Affects Versions: 3.7.1
>Reporter: Stephen Mallette
>Assignee: Stephen Mallette
>Priority: Critical
> Fix For: 4.0.0, 3.7.2
>
>
> {{option(onCreate, 'k', set(1))}} doesn't do anything. it only works for 
> {{onMatch}}. i think the reason was that the expectation was that providers 
> would implement this functionality natively but that looking back, i don't 
> think that's right. it should work out of the box even if it isn't performant.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (TINKERPOP-3049) onCreate for mergeV() doesn't handle Cardinality functions

2024-02-06 Thread Stephen Mallette (Jira) 
Stephen Mallette created TINKERPOP-3049:
---

 Summary: onCreate for mergeV() doesn't handle Cardinality functions
 Key: TINKERPOP-3049
 URL: https://issues.apache.org/jira/browse/TINKERPOP-3049
 Project: TinkerPop
  Issue Type: Bug
  Components: process
Affects Versions: 3.7.1
Reporter: Stephen Mallette
Assignee: Stephen Mallette


{{option(onCreate, 'k', set(1))}} doesn't do anything. it only works for 
{{onMatch}}. i think the reason was that the expectation was that providers 
would implement this functionality natively but that looking back, i don't 
think that's right. it should work out of the box even if it isn't performant.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (TINKERPOP-3045) EarlyLimitStrategy is too aggresive to promote Limit and thus causing incorrect results

2024-02-06 Thread ASF GitHub Bot (Jira) 


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

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

spmallette merged PR #2475:
URL: https://github.com/apache/tinkerpop/pull/2475




> EarlyLimitStrategy is too aggresive to promote Limit and thus causing 
> incorrect results
> ---
>
> Key: TINKERPOP-3045
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3045
> Project: TinkerPop
>  Issue Type: Bug
>  Components: process
>Affects Versions: 3.6.6
>Reporter: Prashant
>Assignee: Stephen Mallette
>Priority: Major
>  Labels: easyfix
> Fix For: 3.6.7
>
>
> {code:java}
> gremlin>   g.V().map(__.in().hasId('1')).limit(2).values('name')
> ==>marko{code}
> {code:java}
> gremlin>   
> g.withoutStrategies(EarlyLimitStrategy).V().map(__.in().hasId('1')).limit(2).values('name')
> ==>marko
> ==>marko {code}
> Early Limit strategy pulls Limit in front of map steps. However not all map 
> steps allow the cardinality of the results flowing to be same. 
>  
> As is shown in example above.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Closed] (TINKERPOP-3045) EarlyLimitStrategy is too aggresive to promote Limit and thus causing incorrect results

2024-02-06 Thread Stephen Mallette (Jira) 


 [ 
https://issues.apache.org/jira/browse/TINKERPOP-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Mallette closed TINKERPOP-3045.
---
Resolution: Fixed

> EarlyLimitStrategy is too aggresive to promote Limit and thus causing 
> incorrect results
> ---
>
> Key: TINKERPOP-3045
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3045
> Project: TinkerPop
>  Issue Type: Bug
>  Components: process
>Affects Versions: 3.6.6
>Reporter: Prashant
>Assignee: Stephen Mallette
>Priority: Major
>  Labels: easyfix
> Fix For: 3.6.7
>
>
> {code:java}
> gremlin>   g.V().map(__.in().hasId('1')).limit(2).values('name')
> ==>marko{code}
> {code:java}
> gremlin>   
> g.withoutStrategies(EarlyLimitStrategy).V().map(__.in().hasId('1')).limit(2).values('name')
> ==>marko
> ==>marko {code}
> Early Limit strategy pulls Limit in front of map steps. However not all map 
> steps allow the cardinality of the results flowing to be same. 
>  
> As is shown in example above.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)