Error codes

  • [FOCA0002] - A value that is not lexically valid for a particular type has been encountered.

  • [FODC0002] - Error retrieving resource.

  • [JNDY0003] - Duplicate pair name. It is a dynamic error if two pairs in an object constructor or in a simple object union have the same name.

  • [JNTY0004] - Unexpected non-atomic element. Raised when objects or arrays are supplied where an atomic element is expected.

  • [JNTY0024] - Error getting the string value for array and object items

  • [JNTY0018] - Invalid selector error code. It is a type error if there is not exactly one supplied parameter for an object or array selector.

  • [RBML0001] - Unrecognized Rumble ML Class Reference An unrecognized classname is used in query while accessing the Rumble ML API.

  • [RBML0002] - Unrecognized Rumble ML Param Reference An unrecognized parameter is used in query while operating with a Rumble ML class.

  • [RBML0003] - Invalid Rumble ML Param Provided parameter does not match the expected type or value for the referenced Rumble ML class.

  • [RBML0004] - Input is not a DataFrame Provided input of items does not form a DataFrame as expected by RumbleML.

  • [RBML0005] - Invalid schema for DataFrame in annotate() The provided schema can not be applied to the item data while converting the data to a DataFrame

  • [RBST0001] - CLI error. Raised when invalid parameters are supplied at launch.

  • [RBST0002] - Unimplemented feature error. Raised when a JSONiq feature that is not yet implemented in Rumble is used.

  • [RBST0003] - Invalid for clause expression error. Raised when an expression produces a different, big sequence of items for each binding within a big tuple, which would lead to a data flow explosion and to a nesting of jobs on the Spark cluster.

  • [RBST0004] - Implementation Error. We should investigate this 🙈. Please contact us or file an issue on GitHub with your query. Link: https://github.com/RumbleDB/rumble/issues

  • [SENR0001] - Serialization error. Function items can not be serialized

  • [XPDY0002] - It is a dynamic error if evaluation of an expression relies on some part of the dynamic context that is absent.

  • [XPDY0050] - Dynamic type treat error. It is a dynamic error if the dynamic type of the operand of a treat expression does not match the sequence type specified by the treat expression. This error might also be raised by a path expression beginning with "/" or "//" if the context node is not in a tree that is rooted at a document node. This is because a leading "/" or "//" in a path expression is an abbreviation for an initial step that includes the clause treat as document-node().

  • [XPDY0130] - Generic runtime exception [check error message].

  • [XPST0003] - Parsing error. Invalid syntax or unsupported feature in query.

  • [XPST0008] - Undefined element reference. It is a static error if an expression refers to an element name, attribute name, schema type name, namespace prefix, or variable name that is not defined in the static context, except for an ElementName in an ElementTest or an AttributeName in an AttributeTest.

  • [XPST0017] - Invalid function call error. It is a static error if the expanded QName and number of arguments in a static function call do not match the name and arity of a function signature in the static context.

  • [XPST0080] - Invalid cast error - It is a static error if the target type of a cast or castable expression is NOTATION anySimpleType, or anyAtomicType.

  • [XPST0081] - Unknown namespace prefix - It is a static error if a QName used in a query contains a namespace prefix that cannot be expanded into a namespace URI by using the statically known namespaces.

  • [XPTY0004] - Unexpected Type Error. It is a type error if, during the static analysis phase, an expression is found to have a static type that is not appropriate for the context in which the expression occurs, or during the dynamic evaluation phase, the dynamic type of a value does not match a required type. Example: using subtraction on strings.

  • [XQST0016] - Module declaration error. Current implementation does not support the Module Feature raises a static error if it encounters a module declaration or a module import.

  • [XQST0031] - Invalid JSONiq version. It is a static error if the version number specified in a version declaration is not supported by the implementation. For now, only version 1.0 is supported.

  • [XQST0034] - Function already exists. It is a static error if multiple functions declared or imported by a module have the same number of arguments and their expanded QNames are equal (as defined by the eq operator).

  • [XQST0039] - Duplicate parameter name. It is a static error for a function declaration or an inline function expression to have more than one parameter with the same name.

  • [XQST0052] - Simple type error. The type must be the name of a type defined in the in-scope schema types, and the {variety} of the type must be simple.

  • [XQST0094] - Invalid variable in group-by clause. The name of each grouping variable must be equal (by the eq operator on expanded QNames) to the name of a variable in the input tuple stream.