Do you have a stack trace to share? Andrés
On Fri, Aug 26, 2011 at 10:55 AM, Aseem Kishore <aseem.kish...@gmail.com>wrote: > I spoke too soon -- this doesn't seem to scale very far with many UUIDs > being looked up together. Here's a query looking up 76 things that returns > a > 500 error -- due to a stack overflow exception. > > > *START*node=(node_auto_index,'uuid_indexed:(f93d416a-40ae-4b5a-87d7-53b6bc4b54ab > OR > ceaad2cf-1afb-4cdd-b98a-8706dc4c471a OR > 7bb157dd-ff76-49d3-9b01-0c506909400c > OR 18b06833-b763-419c-b0ba-78e43dd0898d OR > fdbaf139-053c-4886-8855-47efc4802f60 OR > 8de5a2fb-5a42-4386-9b5a-8d5cbbb3a491 > OR a9a54c63-6fb4-489e-bf55-ebca2ef8e2c3 OR > 17c2c15e-f116-4092-afbe-336674f7b3ed OR > 0c241168-8b41-4fc5-b86c-db7dfe4bfc3d > OR 352de030-1414-4469-af34-46a968d44409 OR > d48769af-0f7a-401d-8e8e-0383d687e87c OR > 923bbc53-9012-435f-ac09-a71fd9b27b21 > OR 879011a1-e26d-4fd1-ae78-c2d8d1f2ec7d OR > 5f0100d5-7be7-48a0-bcd2-4ff706162b3a OR > e5cd6233-24c6-4977-8c49-5d13cb386684 > OR fb331814-5d8e-44c1-bbca-e9a38cd5b1b7 OR > 3fe36ba3-feb2-4e9a-9a83-bd8c42c59960 OR > 33f35e99-107f-43cc-9fd8-0e09ec28490a > OR c10623a4-082b-455d-aa87-5467a97108d6 OR > a2a5cbd6-4cce-4dcb-ba6c-8f4c3fda8349 OR > 8a1e21d8-e407-4795-a841-ca891b53eb77 > OR c3181928-9f7c-4b90-a658-c19c2513c42c OR > ebb867cd-3e40-40ad-8dbd-8e7cd64ef057 OR > 62ae80c2-2f61-4318-ae0c-d352c75295b6 > OR 103b1113-6afa-48d6-a158-8988d3813589 OR > 853fca76-dbfa-4e89-b0db-c059a153101d OR > 7a514103-66b9-4dee-9da0-4a02eec1b516 > OR f88ab591-6989-4908-8856-83efd8a79df1 OR > f4b2aae8-ab7c-4e93-b0db-2dfc7230cc11 OR > 074324dc-5194-46b7-a1bc-34f41b719bd0 > OR 1d82f823-c76d-4f60-aeed-01f1896fa19f OR > 273ea5d5-7ba3-4df1-af1f-e9e12490dc40 OR > 6f06879e-a03e-4239-ab1c-6f2301831319 > OR 96b77c3a-da52-424a-8a0d-90eaa4563b5f OR > f413419c-2269-4dcf-b249-49b5828feadf OR > 0e159ace-32e3-48bc-90f9-735528979726 > OR 885e6466-d5be-45a6-907c-ff6945a7a147 OR > ddbf1468-4714-4001-a695-36d84debfe0e OR > df280b6c-f06b-4b06-9581-56434db22d02 > OR ddaec953-5194-43c6-b2da-7e168c8c6189 OR > f792a366-2654-4702-a095-f546d65005ec OR > f45179f5-a4e0-4f0c-bdb0-30f37f7986c5 > OR deb11e05-6920-461f-a198-b943caac97e8 OR > bca6d42c-df7f-4ccb-bc7a-054223a1c456 OR > 65925c96-19c0-47bf-8ae1-30d39918ba0a > OR 3909bb89-e361-49fa-950e-d24dc0f4b598 OR > d000239e-0e43-4fe2-884a-4baf3a088795 OR > fc5481af-6537-4bd7-b717-83c609a50995 > OR f897b591-ae71-47c8-8d7f-2088dfb64746 OR > fd46e90f-da43-46be-a53f-1f6d301b039d OR > 7bda73ad-a80b-4b47-933f-6bf0f3de47f4 > OR a2a29161-cda2-4aec-85b8-53ef494a945e OR > 8290618b-c6eb-4902-9068-616f0df84040 OR > 75b56851-d53a-4069-8d90-cc9a94186579 > OR d344990d-96da-43f4-8680-a61b38692841 OR > 35898e0b-44e1-4023-855d-a56eb4e07d45 OR > 2081ace8-94df-4841-94e7-08e4ea583f2c > OR 18d77916-e240-4760-9b7f-9c9ad2687860 OR > 5a0d07f9-6635-4544-9f89-7770e2746d37 OR > edd3fdee-1545-48e2-8c3b-e8dccfc6d69a > OR ff88eade-ffd1-4d98-9170-c43ebef04554 OR > bc823ddd-3fd5-448c-926a-414b8742d2bc OR > e5cd635e-33be-43bd-bb6f-e9cde367b7ef > OR b2f7414d-a751-424a-9786-f6acbb1eae7a OR > 50a7ef92-e19d-4bf9-a767-15bc8c9b3481 OR > fd64a857-41ac-41bc-8967-5b123042a921 > OR 9b0c1dad-e7da-4a94-8a06-41eed34c739c OR > 953f6857-30a4-44a2-aa97-b23371a3d3af OR > 62d983d9-8790-4105-8370-ac1e2ff76857 > OR 4ac9c5de-09e7-4b43-8841-fd4df3ccc472 OR > b0cfd10c-ae9c-4efc-96d9-0884c50fc835 OR > 68195e2a-a387-4ea9-98a0-c45ba9ffd342 > OR 0962c97e-d4e0-4e91-a917-63b3b9148095 OR > 09939999-3479-4785-b381-44259eeb5bd4 OR > cab20da4-54d2-4212-ad2f-cd413246c557 > OR 6730e381-000a-4753-bfd7-3482e8e27bd6)') > *RETURN* node > > I guess we'll try a batch API request? > > Aseem > > On Fri, Aug 26, 2011 at 12:31 AM, Aseem Kishore <aseem.kish...@gmail.com > >wrote: > > > Hey, FWIW, we ended up needing this for actual queries in our app, not > just > > the console, so we ended up adding a UUID property to every node in our > > graph, just so we can efficiently query collections of node pairs (where > > nodes may be duplicated many times across pairs). We (auto-)index this > UUID > > property so we can then do a second lookup for the nodes' data. > > > > If Cypher supported IDs or URLs natively, that would have made this a bit > > more convenient. =) > > > > Aseem > > > > > > On Wed, Aug 24, 2011 at 6:41 PM, Aseem Kishore <aseem.kish...@gmail.com > >wrote: > > > >> I was asking really only for the console. I don't see myself needing to > >> use the ID programmatically -- except it might be a minor optimization > to be > >> able to get only node URLs if I already have node data, and I just want > to > >> compare the output of this query with the nodes I already have. > >> > >> For the console, the only thing is that nodes w/ many properties (and > >> possibly long values, e.g. descriptions) totally litter the console, > making > >> output impossible to read or make sense of. Shortening the results to > just > >> IDs (along with selected properties) would be convenient in some cases. > In > >> many cases, just the properties aren't identifying enough. > >> > >> Hope this helps, and thanks for the consideration! > >> > >> Aseem > >> > >> > >> On Wed, Aug 24, 2011 at 5:58 PM, Andres Taylor < > >> andres.tay...@neotechnology.com> wrote: > >> > >>> Hi Aseem, > >>> > >>> For various reasons, we've (so far) decided against allowing the id to > be > >>> something you can output. Could you tell me a bit more about why you > >>> would > >>> like to return just the id? > >>> > >>> It's not hard to do, but it would make future parts of Cypher harder to > >>> do. > >>> If there are valid use cases we've missed, we'll reconsider. > >>> > >>> Regards, > >>> > >>> Andrés > >>> > >>> On Wed, Aug 24, 2011 at 5:39 PM, Aseem Kishore < > aseem.kish...@gmail.com > >>> >wrote: > >>> > >>> > Hey guys, > >>> > > >>> > Is there any way I can have Cypher return/print node IDs? If I > specify > >>> for > >>> > it to return a node, it returns/prints all data about that node, > which > >>> can > >>> > be excessive. But the problem is, the node's ID isn't a property on > >>> that > >>> > node. I've tried both node~ID and node~SELF, like rel~TYPE, but > neither > >>> > works. > >>> > > >>> > If this isn't possible today, consider it a feature request. =) > Thanks! > >>> > > >>> > Aseem > >>> > _______________________________________________ > >>> > Neo4j mailing list > >>> > User@lists.neo4j.org > >>> > https://lists.neo4j.org/mailman/listinfo/user > >>> > > >>> _______________________________________________ > >>> Neo4j mailing list > >>> User@lists.neo4j.org > >>> https://lists.neo4j.org/mailman/listinfo/user > >>> > >> > >> > > > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
