Annotation Interface UserFunction
Functions accept input, use that input to perform work, and then return a value. The work performed usually
involves one or more resources, such as a GraphDatabaseService
. Functions are read-only, i.e
can't update neither the graph nor update schema.
Input declaration
A function can accept input arguments, which is defined in the arguments to the annotated method. Each method argument must be a valid Function input type, and each must be annotated with theName
annotation, declaring the input name.
Valid input types are as follows:
String
Long
orlong
Double
ordouble
Number
Boolean
orboolean
Node
Relationship
Path
Map
with keyString
and value of any type in this list, includingMap
List
with element type of any type in this list, includingList
Object
, meaning any valid input types above
Output declaration
A function must always return a single value.Valid return types are as follows:
String
Long
orlong
Double
ordouble
Number
Boolean
orboolean
Node
Relationship
Path
Map
with keyString
and value of any type in this list, includingMap
List
of elements of any valid field type, includingList
Object
, meaning any of the valid field types above
Resource declarations
The function method itself can contain arbitrary Java code - but in order to work with the underlying graph, it must have access to the graph API. This is done by declaring fields in the function class, and annotating them with theContext
annotation. Fields declared this way are automatically injected with the
requested resource. This is how functions gain access to APIs to do work with.
All fields in the class containing the function declaration must either be static; or it must be public, non-final
and annotated with Context
.
Resources supported by default are as follows:
GraphDatabaseService
Log
TerminationGuard
Lifecycle and state
The class that declares your function method may be re-instantiated before each call. Because of this, no regular state can be stored in the fields of the function.If you want to maintain state between invocations to your procedure, simply use a static field. Note that procedures may be called concurrently, meaning you need to take care to ensure the state you store in static fields can be safely accessed by multiple callers simultaneously.
-
Optional Element Summary
Modifier and TypeOptional ElementDescriptionWhen deprecating a function it is useful to indicate a possible replacement procedure that clients might show in warnings.Synonym forvalue()
The namespace and name for the function, as a period-separated string.
-
Element Details
-
value
String valueThe namespace and name for the function, as a period-separated string. For instancemyfunctions.myfunction
. If this is left empty, the name defaults to the package name of the class the procedure is declared in, combined with the method name. Notably, the class name is omitted.- Returns:
- the namespace and procedure name
- Default:
- ""
-
name
String nameSynonym forvalue()
- Returns:
- the namespace and procedure name.
- Default:
- ""
-
deprecatedBy
String deprecatedByWhen deprecating a function it is useful to indicate a possible replacement procedure that clients might show in warnings.- Returns:
- a string representation of the replacement procedure.
- Default:
- ""
-