Re: [Neo4j] Cypher: node IDs
We finally decided that it should be added. http://docs.neo4j.org/chunked/snapshot/query-function.html#functions-id It's in snapshot, and will be part of our next stable release. Andrés On Thu, Aug 25, 2011 at 2:39 AM, Aseem Kishore aseem.kish...@gmail.comwrote: 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
Re: [Neo4j] Cypher: node IDs
Nice! Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Wed, Sep 14, 2011 at 9:56 PM, Andres Taylor andres.tay...@neotechnology.com wrote: We finally decided that it should be added. http://docs.neo4j.org/chunked/snapshot/query-function.html#functions-id It's in snapshot, and will be part of our next stable release. Andrés On Thu, Aug 25, 2011 at 2:39 AM, Aseem Kishore aseem.kish...@gmail.comwrote: 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
Re: [Neo4j] Cypher: node IDs
Awesome! Great to hear. Thanks Andrés! Aseem On Wed, Sep 14, 2011 at 12:58 PM, Peter Neubauer peter.neuba...@neotechnology.com wrote: Nice! Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/- Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Wed, Sep 14, 2011 at 9:56 PM, Andres Taylor andres.tay...@neotechnology.com wrote: We finally decided that it should be added. http://docs.neo4j.org/chunked/snapshot/query-function.html#functions-id It's in snapshot, and will be part of our next stable release. Andrés On Thu, Aug 25, 2011 at 2:39 AM, 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
Re: [Neo4j] Cypher: node IDs
Yep. Sorry for the delay in responding. For that query, here's the stack
trace:
java.lang.Character.codePointAt(Character.java:2335)
java.util.regex.Pattern$CharProperty.match(Pattern.java:3344)
{
java.util.regex.Pattern$Branch.match(Pattern.java:4114)
java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)
java.util.regex.Pattern$Loop.match(Pattern.java:4295)
java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)
java.util.regex.Pattern$BranchConn.match(Pattern.java:4078)
java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)
}
... [the part in {} keep repeating; there are 1024 total lines in the stack
trace]
And it's a java.lang.StackOverflowError exception.
The same query works over the index REST API, e.g.:
http://localhost:7474/db/data/index/node/node_auto_index?query=uuid_indexed:(ea024173-9740-4ed6-875b-813ba9801571%20OR%20d74b846a-437f-4ff3-88e2-cc6303b1d137%20OR%207ae40c9d-94a0-4c47-8823-833c8e33cfa9%20OR%20c8f40938-2746-4b6b-87aa-0f653671c81f%20OR%20805d0391-a228-4279-b46d-df2d48b0de84%20OR%20231d56ef-5ccc-46ec-bbfa-581115efbb22%20OR%20efaf7c78-3835-433e-86e3-22915c962cca%20OR%203abceafd-e691-4537-a146-49f0af92fabc%20OR%20d80829f4-5671-4344-8dce-162c86cd769b%20OR%203943443c-e780-464f-85fb-8526157c72c9%20OR%20041d7cd5-1d3d-4ec1-943b-1bb59eff39e5%20OR%204fe02747-a7f0-4d48-91be-38544a870934%20OR%203efe3397-36ad-45d1-99e2-97fa04a3fb2d%20OR%20e8d72867-6939-43f4-bc1b-2b4e7e8eb5c9%20OR%208bf755b7-6580-4573-8aee-18a6d6f314e1%20OR%20f122cc05-8937-4175-a713-fee5c3d2a377%20OR%20d05c5824-79ff-42d0-b975-a2da54313d42%20OR%20a71d5af6-089b-47d0-8cfe-16e8059a8306%20OR%2007dc48d6-6256-4ba0-bb26-835ab1c9152a%20OR%20cb8dac45-273f-496b-90e6-3e38eb85f32d%20OR%201735ef28-0b90-443f-b8af-eb77219d5283%20OR%20b705503e-522f-49e2-aaad-571d9b007978%20OR%20f6e43634-b23e-4ff8-895f-6a6c246b95a3%20OR%20d0d9ba5d-ed6e-4493-88ff-93fc75a98a9b%20OR%20688b11fa-03d4-4b6e-8151-733b7e33bd50%20OR%20d6da65c3-e864-4d69-acd0-3ee88eb9cb5c%20OR%20da4bf760-c844-4b36-ae9c-86e65b8be70b%20OR%203c36c953-9757-4874-9620-ab530233a9c2%20OR%20c6ea8316-3eed-4a59-b357-4d6639fa1778%20OR%205231ede6-407b-497c-8081-358c5d03d997%20OR%205f0cf4f2-9225-4eef-85bd-baa31e95634e%20OR%204707f732-7b9c-4703-a269-1f7f0320b495%20OR%20f6136c77-dfd0-4f00-8f03-4508ec8bc234%20OR%2046793cc8-8984-4efe-b958-81a50d126601%20OR%20a1249bda-2c90-4bfd-a2de-e3afd4492a63%20OR%20790372af-6ff4-424d-8668-fa606d585e92%20OR%2018697862-6f8f-40fb-9c3f-9b65daad7b6a%20OR%204467c415-3d2d-4569-a82b-441d8507617c%20OR%2090bc8bcb-8078-4dad-935d-c6feccaa2e41%20OR%2078cf6f7a-250e-4cf7-9ed8-cc790fc23540%20OR%20f65b4132-d646-416f-ba4a-42683afaf821%20OR%20cffa88a9-33b7-411b-81d5-7b65b50736df%20OR%201beaf9b7-086d-4fc3-8ec9-8e1af406a132%20OR%2096249323-ea95-4ab5-9dbd-2bf58965c224%20OR%20cc04cb76-0c94-4c6a-a26d-1fcae979ec92%20OR%2073174682-00ed-4bfd-89d3-0f7efd6736b3%20OR%200cfb807b-45b5-40f7-a418-4ad62f540910%20OR%203f446054-c18a-47c3-a82d-473ed85a50e9%20OR%20a81ffda4-3cae-4e01-8fb1-e0e6c320c9b2%20OR%206c8b5ca8-65c9-4edd-a479-9645cb1ab767%20OR%20d6c22d84-2a6b-4407-bd77-c471fe3662ed%20OR%207d695ebd-b2b2-4611-9b30-39f4ce713a45%20OR%2020486616-db45-4da2-9749-87da3126d1ec%20OR%2051e1107e-9adc-4a2a-ac8b-877a2e2d8b49%20OR%20df5ae476-9b88-4371-91d9-ec8e871ce69e%20OR%20a0540ccd-037e-4247-bbab-8deefd113450%20OR%203a6fd8b4-7a4e-4acb-bdb1-0d7bfe281d3b%20OR%208234cf3b-d0ff-402c-b3ac-7d7ce6838378%20OR%200dda199a-e348-4f90-8fcf-2418c13a5978%20OR%206d752af1-f7e5-488e-94c4-b270f2ef57a9%20OR%2069633e3f-d4ff-4a53-8bd7-77e67fcfc1a5%20OR%2014142a0e-6f61-4bcc-a8b9-b030d20bad6b%20OR%209f55e828-cab0-4bb3-a91a-26bd14529e59%20OR%2031e0e7c7-9aa6-4f44-9c14-2be5d0192b55%20OR%20a17de99f-3348-4cd6-9aa3-30203befc0ac%20OR%20f95af42c-d8c4-43e2-b597-967cf73404f9%20OR%20d9c7c9b4-2e05-4044-a7f0-2b9238d1624a%20OR%2021140f57-c8f2-4746-a47b-abed95c0bed2%20OR%209c3b8c5a-ed1b-4c5c-ac60-7016b5846468%20OR%2038857947-ff47-4da7-8425-761d57bfcfd3%20OR%20422b65a8-59d7-48fb-8853-15f6d372654c%20OR%20597779c5-490b-4e10-b0a6-131315d4198c%20OR%208a5833fe-500a-4c55-8031-713ee093655c%20OR%207c02f1b6-c99b-42f4-9ac6-049c09fa49c7%20OR%20c0bceba8-84d3-4b04-a4f5-1d8d1dcaa233%20OR%2060b0b178-98a9-4819-859b-4d36eed7f3a3)
Hope that helps!
Aseem
On Fri, Aug 26, 2011 at 5:01 AM, Andres Taylor
andres.tay...@neotechnology.com wrote:
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
Re: [Neo4j] Cypher: node IDs
Doesn't seem to be a character escaping issue, as doing the same query w/
the same syntax w/ just fewer UUIDs works just fine. E.g.:
POST /db/data/ext/CypherPlugin/graphdb/execute_query {query: START
node=(node_auto_index,'uuid_indexed:(f93d416a-40ae-4b5a-87d7-53b6bc4b54ab
OR ceaad2cf-1afb-4cdd-b98a-8706dc4c471a OR
7bb157dd-ff76-49d3-9b01-0c506909400c)') RETURN node}
Let me know if I'm misunderstanding you!
Aseem
On Tue, Aug 30, 2011 at 12:15 AM, Peter Neubauer
peter.neuba...@neotechnology.com wrote:
Aseem,
this sounds like a parsing exception. Maybe there are characters escaped in
REST, but not in plain Cypher. Is there a way you could create a graph with
only one or two UUID nodes and reproduce the stack trace so we can look at
it?
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter http://twitter.com/peterneubauer
http://www.neo4j.org - Your high performance graph database.
http://startupbootcamp.org/- Öresund - Innovation happens HERE.
http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party.
On Tue, Aug 30, 2011 at 8:13 AM, Aseem Kishore aseem.kish...@gmail.com
wrote:
Yep. Sorry for the delay in responding. For that query, here's the stack
trace:
java.lang.Character.codePointAt(Character.java:2335)
java.util.regex.Pattern$CharProperty.match(Pattern.java:3344)
{
java.util.regex.Pattern$Branch.match(Pattern.java:4114)
java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)
java.util.regex.Pattern$Loop.match(Pattern.java:4295)
java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)
java.util.regex.Pattern$BranchConn.match(Pattern.java:4078)
java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)
}
... [the part in {} keep repeating; there are 1024 total lines in the
stack
trace]
And it's a java.lang.StackOverflowError exception.
The same query works over the index REST API, e.g.:
Re: [Neo4j] Cypher: node IDs
Uhh,
so the there is a parsing-syntax error that purely depends on the length of
the index argument? That is VERY strange. Maybe you can find out if it is
dependent on the total length of characters in the argument (maybe fill out
with some random long string)? Also, this sounds like an issue that we need
more info on, could you raise one at
https://github.com/neo4j/community/issues to track this down?
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter http://twitter.com/peterneubauer
http://www.neo4j.org - Your high performance graph database.
http://startupbootcamp.org/- Öresund - Innovation happens HERE.
http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party.
On Tue, Aug 30, 2011 at 9:37 AM, Aseem Kishore aseem.kish...@gmail.comwrote:
Doesn't seem to be a character escaping issue, as doing the same query w/
the same syntax w/ just fewer UUIDs works just fine. E.g.:
POST /db/data/ext/CypherPlugin/graphdb/execute_query {query: START
node=(node_auto_index,'uuid_indexed:(f93d416a-40ae-4b5a-87d7-53b6bc4b54ab
OR ceaad2cf-1afb-4cdd-b98a-8706dc4c471a OR
7bb157dd-ff76-49d3-9b01-0c506909400c)') RETURN node}
Let me know if I'm misunderstanding you!
Aseem
On Tue, Aug 30, 2011 at 12:15 AM, Peter Neubauer
peter.neuba...@neotechnology.com wrote:
Aseem,
this sounds like a parsing exception. Maybe there are characters escaped
in
REST, but not in plain Cypher. Is there a way you could create a graph
with
only one or two UUID nodes and reproduce the stack trace so we can look
at
it?
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter http://twitter.com/peterneubauer
http://www.neo4j.org - Your high performance graph
database.
http://startupbootcamp.org/- Öresund - Innovation happens HERE.
http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party.
On Tue, Aug 30, 2011 at 8:13 AM, Aseem Kishore aseem.kish...@gmail.com
wrote:
Yep. Sorry for the delay in responding. For that query, here's the
stack
trace:
java.lang.Character.codePointAt(Character.java:2335)
java.util.regex.Pattern$CharProperty.match(Pattern.java:3344)
{
java.util.regex.Pattern$Branch.match(Pattern.java:4114)
java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)
java.util.regex.Pattern$Loop.match(Pattern.java:4295)
java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)
java.util.regex.Pattern$BranchConn.match(Pattern.java:4078)
java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)
}
... [the part in {} keep repeating; there are 1024 total lines in the
stack
trace]
And it's a java.lang.StackOverflowError exception.
The same query works over the index REST API, e.g.:
Re: [Neo4j] Cypher: node IDs
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.comwrote: 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
Re: [Neo4j] Cypher: node IDs
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 0993-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.comwrote: 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.comwrote: 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,
Re: [Neo4j] Cypher: node IDs
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.comwrote: 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
Re: [Neo4j] Cypher: node IDs
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
