[
https://issues.apache.org/jira/browse/TINKERPOP-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712054#comment-17712054
]
ASF GitHub Bot commented on TINKERPOP-2891:
-------------------------------------------
vkagamlyk opened a new pull request, #2021:
URL: https://github.com/apache/tinkerpop/pull/2021
Fixed optimization of `count` step inside `CountStrategy`.
queries like
` g.V().where(__.in().count().is(eq(-3)))` and
`g.V().where(__.in().count().is(eq(-2)))` are now correctly optimized as
`g.V().where(__.in().limit(0).count().is(eq(-2)))`
> Inconsistent behavior when comparing a counted value with a negative value
> --------------------------------------------------------------------------
>
> Key: TINKERPOP-2891
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2891
> Project: TinkerPop
> Issue Type: Bug
> Components: process
> Affects Versions: 3.5.5
> Reporter: Lei Tang
> Priority: Critical
>
> I compare a value that should be greater than or equal to 0 with a negative
> value.
> {code:java}
> gremlin> :> g.V().where(__.in().count().is(eq(-3)))
> Not a legal range: [0, -2]
> gremlin> :> g.V().where(__.in().count().is(eq(-2))){code}
> I find that Tinkergraph throws an exception when comparing negative values
> less than -2, but does nothing when comparing with -2.
> I'm curious why they behave differently.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
