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

Posted to dev@tinkerpop.apache.org by "Stephen Mallette (Jira)" <ji...@apache.org> on 2022/02/01 15:21:00 UTC

[jira] [Reopened] (TINKERPOP-2687) Gremlin Boolean Value Expressions 2.0 with Ternary Boolean Logics

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

Stephen Mallette reopened TINKERPOP-2687:
-----------------------------------------

> Gremlin Boolean Value Expressions 2.0 with Ternary Boolean Logics
> -----------------------------------------------------------------
>
>                 Key: TINKERPOP-2687
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2687
>             Project: TinkerPop
>          Issue Type: New Feature
>          Components: language
>    Affects Versions: 3.6.0
>            Reporter: Mike Personick
>            Assignee: Stephen Mallette
>            Priority: Major
>             Fix For: 3.6.0
>
>
> Comparability is currently limited to same type or both Numeric comparisons, and even for same type the objects must implement Comparable, which is not the case for many valid Gremlin types (all Elements, Properties, collections, etc.)
> This is closely related to the Orderability Semantics work, but Comparability Semantics will be defined slightly differently. Comparability (and other boolean value expressions) will be extended to a ternary binary syntax (TRUE, FALSE, and UNDEF). Comparison across types would be one example of an UNDEF result. However, UNDEF will not propagate to the user as an Exception, it will be handled at an appropriate level and ultimately converted to a Boolean result. For example, OR(TRUE, UNDEF) = TRUE.
> Also see:
> [https://tinkerpop.apache.org/docs/3.6.0-SNAPSHOT/dev/provider/#_comparability_vs_orderability]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)