n24q02m commented on PR #499:
URL: https://github.com/apache/hugegraph-doc/pull/499#issuecomment-6073707910

   Re-ran the documented examples against latest master; both pages updated in 
a49a8c3.
   
   Repro (fresh RocksDB graph): build master at 5039e5b, run bin/init-store.sh, 
start the server, then e.g.
   
   ```
   curl -u admin:pass -H "Content-Type: application/json" 
http://localhost:8080/graphspaces/DEFAULT/graphs/hugegraph/cypher -d 
"{\"cypher\":\"MATCH (n:person) WHERE n.name = \$name RETURN 
n.name\",\"parameters\":{\"name\":\"marko\"}}"
   ```
   
   Stack: Java 17.0.20.1 (Temurin), TinkerPop 3.8.1, 
org.opencypher.gremlin:translation:1.0.4, core 1.8.0.
   
   Results: both legacy forms, the JSON-object form, aggregation/order/limit, 
single-vertex CREATE, SET/REMOVE, edge DELETE and DETACH DELETE all behaved as 
documented, checked with native REST readback. A missing binding is an 
execution error (status.code 400) on all three request forms; 17 top-level 
bindings are rejected; one Map with 17 entries works via explicit property 
references; text/plain gives 415; non-object JSON bodies give 400.
   
   One addition: the two-vertex shorthand CREATE (a)-[:knows]->(b) fails on a 
PRIMARY_KEY label ("The primary keys: [name] of vertex label 'person' must be 
set", status.code 400) but works on an AUTOMATIC label; single-vertex CREATE is 
fine on both. I documented that caveat and pointed the example at separate 
CREATE statements in a49a8c3.
   
   The examples this PR documents go through the server REST endpoint, so I did 
not exercise the toolchain clients separately.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to