Last active
October 25, 2018 04:47
-
-
Save bobvanluijt/a6f812589095f7435e4e8a99a7f8fef6 to your computer and use it in GitHub Desktop.
Idea for grouping
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
### | |
# The result below shows the sum of population of all cities. | |
### | |
{ | |
Local { | |
Get(where:{ | |
operands: [{ | |
path: ["Things", "City", "population"], | |
operator: GreaterThan | |
valueInt: 1000000 | |
}] | |
},{ | |
group:{ | |
operands: [{ | |
path: ["Things", "City", "population"], | |
aggregate: SUM # other options: COUNT, MAX, MIN, SUM, AVG, | |
}] | |
} | |
}) { | |
Things { | |
City { | |
population | |
} | |
} | |
} | |
} | |
} |
Maybe they are simple to implement. I would expect so, based on my experience with SQL. However, Gremlin is not as well rounded, and I did not research this yet for Gremlin.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
That indeed sounds reasonable. Not necessarily in favor for one or the other but syntactically it might absolutely be preferable to introduce a
Stats{}
function.Naming wise, maybe
Aggregate{}
would suit better. Any thoughts @laura-ham and @moretea?It would also be possible to add all aggregation functions as GQL-functions.
@moretea would it be fair to say that splitting these aggregate functions (except for
GroupBy()
) would be relatively easier to implement?