[
https://issues.apache.org/jira/browse/TINKERPOP3-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969143#comment-14969143
]
Marko A. Rodriguez commented on TINKERPOP3-909:
-----------------------------------------------
Ah. Yea. We should definitely resolve this by 3.1.0. Perhaps if people know
their data, we can then make {{MaxStep<S,Double>}} be {{MaxStep<S,E extends
Number>}} and then people do:
{code}
g.V().values("age").<Integer>max()
{code}
This would be good as it will provide typecasting and (as a side benefit) with
the "quantum Gremlin"-work, we can do:
{code}
g.V().values("age").<Complex>max()
{code}
As {{apache.math3.Complex}} extends {{Number}}. I thought I was going to have
to do some "lambda barrier" stuff for that....Your proposal here will kill many
birds with one stone.
> Improve steps that handle numeric data
> --------------------------------------
>
> Key: TINKERPOP3-909
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-909
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.1.0-incubating
> Reporter: Daniel Kuppitz
> Assignee: Daniel Kuppitz
> Fix For: 3.1.0-incubating
>
>
> Use the new {{NumberHelper}} (implemented in
> https://issues.apache.org/jira/browse/TINKERPOP3-861) in steps that are
> supposed to handle numeric data (e.g. {{Sum(Global)Step}},
> {{Min(Global)Step)}}, {{Max(Global)Step}}, etc.). These steps currently
> simply convert everything into a {{Double}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
