FilterParser
AST ¤
A base class for nodes of an abstract syntax tree for metadata filters. Its descriptor
property provides a python
friendly name (e.g. potentially used as a method name)
Source code in src/neo4j_haystack/metadata_filter/parser.py
LogicalOp ¤
Bases: AST
AST
node which represents a logical operator e.g. "AND", "OR", "NOT".
Logical operator is comprised of an operator (e.g. "AND") and respective operands - expressions participating in
the logical evaluation syntax. For example one could read it the following way: "operand1 AND operand2"
, where
"AND"
is the operator and "operand1", "operand2"
are AST
nodes which might evaluate into:
- simple expressions like
"field1 = 1 AND field2 >= 2"
- more complex expressions like
"(field1 = 1 OR field2 < 4) AND field3 > 2"
Please notice the actual representation of expressions is managed by a separate component which knows how to parse
the syntax tree and translate its nodes (AST
) into DocumentStore's specific filtering syntax.
Source code in src/neo4j_haystack/metadata_filter/parser.py
ComparisonOp ¤
Bases: AST
This AST
node represents a comparison operator in filters syntax tree (e.g. "==", "in", "<=" etc).
Comparison operator is comprised of an operator, a field name and field value. For example one could
read it in the following way: "age == 20"
, where
"=="
- is the operator"age"
- is a field name- "20" - is a comparison value.
Please notice the actual representation of comparison expressions is managed by a separate component which knows how
to translate the ComparisonOp
into DocumentStore's specific filtering syntax.
Source code in src/neo4j_haystack/metadata_filter/parser.py
FilterParser ¤
The implementation of metadata filter parser into an abstract syntax tree comprised of respective
AST
nodes. The tree structure has a single root node and, depending on actual filters provided, can result
into a number of Logical nodes as well as Comparison (leaf) nodes. The parsing logic takes into consideration rules
documented in the following document Metadata Filtering.
FilterParser
does not depend on actual DocumentStore implementation. Its single purpose is to parse filters into a
tree of AST
nodes by applying metadata filtering rules (including default operators behavior).
With a given example of a metadata filter parsing below:
filters = {
"operator": "OR",
"conditions": [
{
"operator": "AND",
"conditions": [
{"field": "meta.type", "operator": "==", "value": "news"},
{"field": "meta.likes", "operator": "!=", "value": 100},
],
},
{
"operator": "AND",
"conditions": [
{"field": "meta.type", "operator": "==", "value": "blog"},
{"field": "meta.likes", "operator": ">=", "value": 500},
],
},
],
}
op_tree = FilterParser().parse(filters)
We should expect the following tree structure (op_tree
) after parsing:
+-------------+
| <LogicalOp> |
| op: "OR" |
+-------------+
+-------------+ operands +----------------+
| +-------------+ |
| |
+-----+-------+ +-----+-------+
| <LogicalOp> | | <LogicalOp> |
| op: "AND" | | op: "AND" |
+-------------+ +-------------+
+--------+ operands +----+ +-------+ operands +-------+
| +-------------+ | | +-------------+ |
| | | |
+----------+---------+ +--------------+------+ +------+-------------+ +-----------+---------+
| <ComparisonOp> | | <ComparisonOp> | | <ComparisonOp> | | <ComparisonOp> |
| | | | | | | |
| field_name: "type" | | field_name: "likes" | | field_name: "type" | | field_name: "likes" |
| op: "==" | | op: ">=" | | op: "==" | | op: "!=" |
| field_value: "blog"| | field_value: 500 | | field_value: "news"| | field_value: 100 |
+--------------------+ +---------------------+ +--------------------+ +---------------------+
Having such a tree DocumentStore should be able to traverse it and interpret into a Document Store specific syntax.
Source code in src/neo4j_haystack/metadata_filter/parser.py
113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 |
|
combine ¤
combine(
*operands: Optional[OperatorAST], default_op: str = LOGICAL_OPS.OP_AND
) -> Optional[OperatorAST]
Combines several operands (standalone filter values) into a logical operator if number of operands is greater
than one. Operands with None
value are skipped (e.g. empty strings).
Parameters:
-
default_op
(str
, default:OP_AND
) –Default operator to be used to construct the
LogicalOp
, defaults toOP_AND
Returns:
-
Optional[OperatorAST]
–Logical operator with
operands
or the operand itself if it is the only provided in arguments.
Source code in src/neo4j_haystack/metadata_filter/parser.py
_parse_comparison_op ¤
Parsing a comparison operator dictionary.
Parameters:
-
filters
(FilterType
) –Comparison filter dictionary with
field
,operator
andvalue
keys expected.
Raises:
-
Neo4jFilterParserError
–If required
field
orvalue
comparison dictionary keys are missing.
Returns:
-
ComparisonOp
–AST
node representing the comparison expression in abstract syntax tree.
Source code in src/neo4j_haystack/metadata_filter/parser.py
_parse_logical_op ¤
This method is responsible of parsing logical operators. It returns LogicalOp
with specific operator
(e.g. "OR") and its operands (list of AST
nodes). Operands are parsed by calling self._parse_tree
which might result in further recursive parsing flow.
Parameters:
-
filters
(FilterType
) –Logical filter with conditions.
Raises:
-
Neo4jFilterParserError
–If required
conditions
logic dictionary key is missing or is not alist
with at least one item.
Returns:
-
LogicalOp
–The instance of
LogicalOp
with the list parsed operands.
Source code in src/neo4j_haystack/metadata_filter/parser.py
_parse_tree ¤
This parses filters dictionary and identifies operations based on its "operator" type,
e.g. "AND" would be resolved to a logical operator type (OpType.LOGICAL
). Once recognized the parsing
of the operator and its filter will be delegated to a respective method (e.g. self._parse_logical_op
or
self._parse_comparison_op
).
Parameters:
-
filters
(FilterType
) –Metadata filters dictionary. Could be the full filter value or a smaller filters chunk.
Raises:
-
Neo4jFilterParserError
–If required
operator
dictionary key is missing. -
Neo4jFilterParserError
–If
filters
is not a dictionary. -
Neo4jFilterParserError
–If operator value is unknown.
Returns:
-
OperatorAST
–A root
AST
node of parsed filter.
Source code in src/neo4j_haystack/metadata_filter/parser.py
parse ¤
This is the entry point to parse a given metadata filter into an abstract syntax tree. The implementation
delegates the parsing logic to the private self._parse_tree
method.
Parameters:
-
filters
(FilterType
) –Metadata filters to be parsed.
Raises:
-
Neo4jFilterParserError
–In case parsing results in empty
AST
tree or more than one root node has been created after parsing.
Returns:
-
OperatorAST
–Abstract syntax tree representing
filters
. You should expect a single root operator returned, which -
OperatorAST
–could used to traverse the whole tree.