- Reference >
- Operators >
- Aggregation Pipeline Operators >
- $function (aggregation)
$function (aggregation)¶
On this page
Definition¶
-
$function¶ New in version 4.4.
Defines a custom aggregation function or expression in JavaScript.
You can use the
$functionoperator to define custom functions to implement behavior not supported by the MongoDB Query Language. See also$accumulator.Important
Executing JavaScript inside an aggregation expression may decrease performance. Only use the
$functionoperator if the provided pipeline operators cannot fulfill your application’s needs.
Syntax¶
The $function operator has the following syntax:
| Field | Type | Description |
|---|---|---|
| body | String or Code | The function definition. You can specify the function definition as either BSON type Code or String. See also lang.
or
|
| args | Array | Arguments passed to the function body.
If the body function does not take an
argument, you can specify an empty array The array elements can be any BSON type, including Code. See Example 2: Alternative to $where. |
| lang | String | The language used in the body. You
must specify |
Considerations¶
Schema Validation Restriction¶
You cannot use $function as part of schema validation
query expression.
Javascript Enablement¶
To use $function, you must have server-side scripting
enabled (default).
If you do not use $function (or $accumulator,
$where, or mapReduce), disable server-side
scripting:
For a
mongodinstance, seesecurity.javascriptEnabledconfiguration option or--noscriptingcommand-line option.For a
mongosinstance, seesecurity.javascriptEnabledconfiguration option or the--noscriptingcommand-line option starting in MongoDB 4.4.In earlier versions, MongoDB does not allow JavaScript execution onmongosinstances.
Alternative to $where¶
The query operator $where can also be used to specify
JavaScript expression. However:
- Starting in MongoDB 3.6, the
$exproperator allows the use of aggregation expressions within the query language. - Starting in MongoDB 4.4, the
$functionand$accumulatorallows users to define custom aggregation expressions in JavaScript if the provided pipeline operators cannot fulfill your application’s needs.
Given the available aggregation operators:
- The use of
$exprwith aggregation operators that do not use JavaScript (i.e. non-$functionand non-$accumulatoroperators) is faster than$wherebecause it does not execute JavaScript and should be preferred if possible. - However, if you must create custom expressions,
$functionis preferred over$where.
Examples¶
Example 1: Usage Example¶
Create a sample collection named players with the following
documents:
The following aggregation operation uses $addFields to
add new fields to each document:
isFoundwhose value is determined by the custom$functionexpression that checks whether the MD5 hash of the name is equal to a specified hash.messagewhose value is determined by the custom$functionexpression that format a string message using a template.
The operation returns the following documents:
Example 2: Alternative to $where¶
Aggregation Alternatives Preferred over $where
Starting in MongoDB 3.6, the $expr operator allows the use
of aggregation expressions within the
query language. And, starting in MongoDB 4.4, the
$function and $accumulator allows users to
define custom aggregation expressions in JavaScript if the provided
pipeline operators cannot
fulfill your application’s needs.
Given the available aggregation operators:
- The use of
$exprwith aggregation operators that do not use JavaScript (i.e. non-$functionand non-$accumulatoroperators) is faster than$wherebecause it does not execute JavaScript and should be preferred if possible. - However, if you must create custom expressions,
$functionis preferred over$where.
As an alternative to a query that uses the $where operator,
you can use $expr and $function. For example,
consider the following $where example.
The db.collection.find() operation returns the following document: