You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Florian Hockmann (Jira)" <ji...@apache.org> on 2022/03/28 13:17:00 UTC
[jira] [Created] (TINKERPOP-2727) HasContainer should allow a null key
Florian Hockmann created TINKERPOP-2727:
-------------------------------------------
Summary: HasContainer should allow a null key
Key: TINKERPOP-2727
URL: https://issues.apache.org/jira/browse/TINKERPOP-2727
Project: TinkerPop
Issue Type: Improvement
Components: process
Affects Versions: 3.5.2
Reporter: Florian Hockmann
TINKERPOP-2605 changed {{null}} semantics to allow {{null}} as an argument in more places so that {{has(null)}} should not throw a NPE any more and instead filter all traversers out.
{{HasContainer}} however still throws a NPE if the {{key}} is {{{}null{}}}.
I discovered this when trying to update JanusGraph [as that folds in a {{HasContainer}} like this|https://github.com/JanusGraph/janusgraph/blob/4246d49cee46d549d752515f3956cd2d59f1fd0a/janusgraph-core/src/main/java/org/janusgraph/graphdb/tinkerpop/optimize/step/HasStepFolder.java#L266] which leads to the NPE and thus failing tests.
The same behavior can also be produced with just TinkerGraph and for example the following traversals:
{code:java}
g.V().has(null, 1)
g.V().has(null, P.neq(null)){code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)