Cypher
The read-only Cypher dialect WhisperGraph runs over HTTP: how a query is shaped, and where the clause and function references live.
In this chapter
- Syntax & ClausesThe Cypher clauses, operators, subqueries, parameters, and path syntax WhisperGraph supports, with a working example for each.
- FunctionsThe built-in Cypher function library: aggregation, string, numeric, collection, node, conversion, date and geospatial — with return values.
- Best PracticesThe habits that make WhisperGraph queries return in milliseconds, the traps that look like habits, and the graph's rules as instructions.
- Cheat SheetOne-page Cypher cheat sheet: schema, edge directions, traversal chains, procedures with their columns, and query rules.
On this page (1)
Cypher Documentation
WhisperGraph speaks a read-only dialect of Cypher, the graph query language, over HTTP. You POST a query to the HTTP API and get back columns and rows; there is no driver to install and no session to manage. If you have used Neo4j, you already know most of the language.
Almost every WhisperGraph query is anchor, traverse, return: pin a node by its indexed name, walk the edges you care about, project columns, cap the rows.
MATCH (h:HOSTNAME {name: "google.com"})-[:RESOLVES_TO]->(ip:IPV4)
RETURN ip.name AS ip
LIMIT 5
Every supported clause is documented with a runnable example in Syntax & Clauses. Full signatures, examples and return values for the function library are in Functions.
Where next
The clause, function, practice and cheat-sheet pages are listed at the top of
this chapter. To send what you write over the wire, the HTTP API
has the endpoint, the X-API-Key header and the response envelope. For patterns
that keep large or repetitive jobs fast, see
Cross-Layer Patterns; for whole investigations
already assembled, Workflows.