[orientdb] Re: "out_" array empty when there's too many outgoing edges
Hi Alexandre, could you post your code to replicate your problem ? Thanks, Alessandro -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[orientdb] Re: "out_" array empty when there's too many outgoing edges
Hello Oleksandr, Thanks for your reply. Unfortunately, the problem I'm having does not have to do with limiting the number of records in the result set, which is what the LIMIT filter does. My problem is with the "out_" property coming up empty when a node has too many outgoing edges, in my case, more than 100 edges. Things work fine when the number of outgoing edges is small. On Tuesday, October 11, 2016 at 2:08:00 PM UTC-4, Oleksandr Gubchenko wrote: > > You can try implementing it with a SQL query inside your function, using: > LIMIT > > see: http://orientdb.com/docs/last/SQL-Query.html > > Il giorno martedì 11 ottobre 2016 19:57:25 UTC+2, Alexandre DeFreitas ha > scritto: >> >> Hello, >> >> I'm using OrientJS's query builder to fetch records (nodes) each of which >> has multiple outgoing edges to other records. When the number of outgoing >> edges for a record is relatively small, such as 15 or so, the "out_" >> property of the query result contains the outgoing references to the other >> records as expected. >> >> However, I have a node that has 101 outgoing edges that keeps returning >> an empty "out_" property. I searched Google, SO, and the OrientDB docs >> high and low and played with various settings in orientdb-server-config.xml >> such as db.pool.max, graph.pool.max, and distributed.queueMaxSize, but >> "out_" still comes back empty. >> >> I hope my explanation makes sense. Is there a setting in a config file >> somewhere that limits the number of nodes that can be referenced and >> returned in a result set? >> >> Thanks >> > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[orientdb] Re: "out_" array empty when there's too many outgoing edges
You can try implementing it with a SQL query inside your function, using: LIMIT see: http://orientdb.com/docs/last/SQL-Query.html Il giorno martedì 11 ottobre 2016 19:57:25 UTC+2, Alexandre DeFreitas ha scritto: > > Hello, > > I'm using OrientJS's query builder to fetch records (nodes) each of which > has multiple outgoing edges to other records. When the number of outgoing > edges for a record is relatively small, such as 15 or so, the "out_" > property of the query result contains the outgoing references to the other > records as expected. > > However, I have a node that has 101 outgoing edges that keeps returning an > empty "out_" property. I searched Google, SO, and the OrientDB docs high > and low and played with various settings in orientdb-server-config.xml such > as db.pool.max, graph.pool.max, and distributed.queueMaxSize, but "out_" > still comes back empty. > > I hope my explanation makes sense. Is there a setting in a config file > somewhere that limits the number of nodes that can be referenced and > returned in a result set? > > Thanks > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
