,
To speed up the query like:
select from (select expand(in()) from User where status = 'active')
where foo = bar LIMIT 10
You should have an index on User.status to avoid scanning all User. Can
you elaborate more the query that is slow?
Lvc@
On 5 March 2015 at 22:28, Jamie Blair jamie.bl
):
*SELECT expand(in()) FROM #27:819*
If you want to filter by vertex's properties you can do:
*SELECT FROM (*
* SELECT expand(in()) FROM #27:819) WHERE age = 18*
Lvc@
On 3 March 2015 at 11:42, Jamie Blair jamie.bl...@gmail.com wrote:
Luigi,
Thanks, but there is an extra part to our problem
doesn't collect metrics from sub-queries.
Lvc@
On 4 March 2015 at 14:20, Jamie Blair jamie.bl...@gmail.com wrote:
Given the query
EXPLAIN select from (select from Vertex) LIMIT 1
I get the results
elapsed: 2514.5999
recordReads: 1
documentReads: 1
resultSize: 1
evaluated: 1
Given
Hi,
My aim is to fetch all Friends for a user, which I can do with the
following
SELECT expand(both(Friend)) FROM User WHERE @rid = #27:0
# Returns 3 rows
Now I want to paginate this example lets start of by limiting
SELECT expand(both(Friend)) FROM User WHERE @rid = #27:0 LIMIT 2
# Returns
Given the query
EXPLAIN select from (select from Vertex) LIMIT 1
I get the results
elapsed: 2514.5999
recordReads: 1
documentReads: 1
resultSize: 1
evaluated: 1
Given the query took 2.5seconds I would have expected some of those numbers
to be a lot higher (recordReads, documentReads,
as a full development process, but if you want you
can create a specific issue for this
Regards
Luigi
2015-03-02 18:11 GMT+01:00 Jamie Blair jamie...@gmail.com javascript::
Luigi,
Have you any idea how I would make this fast, or is there a work around
for the present query optimizer
Hi,
First off my knowledge of maven and java are very limited, however it looks
like there is a problem with the '2.1-SNAPSHOT' maven package. Running the
following command which worked for orient 2.0-SNAPSHOT/2.0.1/2.0.2 now
doesn't work for '2.1-SNAPSHOT'
mvn
The following query returns a set of `@rid` and completes in about `0.012sec
`
SELECT in FROM SomeEdge WHERE out IN #27:819
Now if I were to select from another Vertex using those `@rid`s in there
literal form, this would take a very long time and I get a timeout (above
4seconds). I'm
are working hard on the new query parser and
executor and one of the main goals of all this is query optimization.
Thanks
Luigi
2015-03-02 17:11 GMT+01:00 Jamie Blair jamie...@gmail.com javascript::
The following query returns a set of `@rid` and completes in about `
0.012sec`
SELECT
