[arangodb-google] Graph traversal and subgraphs

. It seems that filters are only applied on results and traverse itself is not affected by these filters. Same situation applies if I tried to filter on vertices. Is there a way how to run traverse on subgraph (define subset of edges and vertices and then run traverse on them). Thanks Roman -

[arangodb-google] Re: Graph traversal and subgraphs

If I looked to documentation https://docs.arangodb.com/3.0/AQL/Graphs/Traversals.html there should be something like this Traversals on graphs: Id Depth Vertex collections Edge collections Filter conditions 2 1..3circles edges `Path`.`edges`[0] ->

[arangodb-google] Managed ArangoDB servcie

Hi, I am doing a research about some needs in a database and I really liked ArangoDB, The only issue is that I couldn't find any managed services or managed hosts for ArangoDB. For an example in Amazon AWS services the RDS allows us to easily to scale up, without worrying about the clustering

[arangodb-google] Faceted Search Performance

We are evaluating ArangoDB performance in space of facets calculations. There are number of other products capable of doing the same, either via special API or query language: - MarkLogic Facets - ElasticSearch Aggregations

[arangodb-google] Re: Faceted Search Performance

Btw, Fyi, first query (AKA: LENGTH(g)) with an index on attribute1 runs almost same as second query (AKA: WITH COUNT). Here, 2nd query with an index takes 4.4 seconds. But it is still, just one facet. Usually you need a bunch, like in my "long" query in very first post. Let me re-write it using

[arangodb-google] Re: Faceted Search Performance

compiled your changes from feature/mmfiles-hash-lookup-performance indeed, on single facet we are down to 4 seconds from 6 seconds (in the test case provided above). And no indexes needed. hope it will make to master soon. -- You received this message because you are subscribed to the Google

[arangodb-google] Re: Faceted Search Performance

4 seconds per facet, thus adding 3 more it takes us to 16 seconds. btw, why is that, arango is doing full scan anyways. is it doing it 4 times with the query bellow? Is there any way to make it smarter? LET docs = (FOR a IN Asset RETURN a) LET attribute1 = ( FOR a in docs COLLECT attr =

[arangodb-google] Re: Faceted Search Performance

Thanks for a hint! We have wrote small service faced to calculate facets. It split my huge AQL provided above into 5 queries: - main - to filter, sort and retrieve matching entities: - LET docs = (FOR a IN Asset FILTER a.name like 'test-asset-%'

[arangodb-google] Re: Faceted Search Performance

Thanks Jan for your reply! But, yes, we have tried "2.x old school" approach* WITH COUNT*, as well as brand new* DISTINCT*. Both yields similar sluggish results :-/ -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group

[arangodb-google] Re: Faceted Search Performance

done -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to arangodb+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.