[jira] [Closed] (TINKERPOP-2605) Further enforce and refine null semantics

["Stephen Mallette (Jira)" <ji...@apache.org>]

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

Stephen Mallette closed TINKERPOP-2605.
---------------------------------------
    Fix Version/s: 3.5.2
                   3.6.0
       Resolution: Done

> Further enforce and refine null semantics
> -----------------------------------------
>
>                 Key: TINKERPOP-2605
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2605
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process, test-suite
>    Affects Versions: 3.5.1
>            Reporter: Stephen Mallette
>            Assignee: Stephen Mallette
>            Priority: Major
>             Fix For: 3.6.0, 3.5.2
>
>
> A number of areas where {{null}} is used in traversals result in some odd looking errors. Identify these situations and improve them to be more user friendly. Some specific items to take care of:
> {code}
> hasLabel(null) // currently results in exception, should just filter
> P.within(null) // TINKERPOP-2598
> sum() // NPE if null is present, should ignore nulls in calculation and return null if all values are null
> mean() // NPE if null is present, should ignore nulls in calculation and return null if all values are null
> max() // NPE if null is present, should ignore nulls in calculation and return null if all values are null
> min() // NPE if null is present, should ignore nulls in calculation and return null if all values are null
> inject(null) // NPE
> hasValue(null) // NPE if accidentally applied to hasValue(P), should just filter
> hasKey(null) // NPE, should just filter
> withSideEffect('k',null) // NPE, should just allow the assignment
> g.inject(1,null).as('a') // NPE and won't allow labelling 
> path() // NPE when encountering nulls
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)