execute_open_cypher_query
async
¶
execute_open_cypher_query(
open_cypher_query: str,
*,
config_overrides: Optional[AsyncneptunedataClientConfig] = None,
parameters: Optional[str] = None,
) -> ExecuteOpenCypherQueryOutput
Executes an openCypher query. See Accessing the Neptune Graph with openCypher for more information.
Neptune supports building graph applications using openCypher, which is currently one of the most popular query languages among developers working with graph databases. Developers, business analysts, and data scientists like openCypher's declarative, SQL-inspired syntax because it provides a familiar structure in which to querying property graphs.
The openCypher language was originally developed by Neo4j, then open-sourced in 2015 and contributed to the openCypher project under an Apache 2 open-source license.
Note that when invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows one of the following IAM actions in that cluster, depending on the query:
Note also that the neptune-db:QueryLanguage:OpenCypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
Parameters:
-
open_cypher_query(str) –The openCypher query string to be executed.
-
parameters(Optional[str], default:None) –The openCypher query parameters for query execution. See Examples of openCypher parameterized queries for more information.
Raises:
-
BadRequestException–Raised when a request is submitted that cannot be processed.
-
CancelledByUserException–Raised when a user cancelled a request.
-
ClientTimeoutException–Raised when a request timed out in the client.
-
ConcurrentModificationException–Raised when a request attempts to modify data that is concurrently being modified by another process.
-
ConstraintViolationException–Raised when a value in a request field did not satisfy required constraints.
-
FailureByQueryException–Raised when a request fails.
-
IllegalArgumentException–Raised when an argument in a request is not supported.
-
InvalidArgumentException–Raised when an argument in a request has an invalid value.
-
InvalidNumericDataException–Raised when invalid numerical data is encountered when servicing a request.
-
InvalidParameterException–Raised when a parameter value is not valid.
-
MalformedQueryException–Raised when a query is submitted that is syntactically incorrect or does not pass additional validation.
-
MemoryLimitExceededException–Raised when a request fails because of insufficient memory resources. The request can be retried.
-
MissingParameterException–Raised when a required parameter is missing.
-
ParsingException–Raised when a parsing issue is encountered.
-
PreconditionsFailedException–Raised when a precondition for processing a request is not satisfied.
-
QueryLimitExceededException–Raised when the number of active queries exceeds what the server can process. The query in question can be retried when the system is less busy.
-
QueryLimitException–Raised when the size of a query exceeds the system limit.
-
QueryTooLargeException–Raised when the body of a query is too large.
-
TimeLimitExceededException–Raised when the an operation exceeds the time limit allowed for it.
-
TooManyRequestsException–Raised when the number of requests being processed exceeds the limit.
-
UnsupportedOperationException–Raised when a request attempts to initiate an operation that is not supported.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_neptunedata/_services/async_neptunedata.py
1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 | |