Needs to support `FT.AGGREGATE` / RediSearch aggregations.

This client needs to support RediSearch aggregations / FT.AGGREGATE.

[chayim]

Big fan of the second approach, and ensuring that we can do chained aggregations. This would both feel very much in spirit with this library, and align really well to other Python ORMs (I’m looking at Django!).

It feels “strange” that we’re not aggregating a query, if only because traditionally those things march in tandem.

One syntax I’m a fan of is:

model.agggregate(Avg=model.Fieldname, Sum=model.FieldName)

This makes chaining a little cleaner. Through approach this may eventually lead to class based aggregations. My biggest concern is that it feel “pythonic”. The downside from approaches like this are reserved names, leading to Capitalized variables.

@wiseaidev ?

[wiseaidev]

ensuring that we can do chained aggregations.

I recently started to realize that. That’s right!

The downside from approaches like this are reserved names, leading to Capitalized variables.

How about passing the aggregate functions as strings:

model.agggregate(model.Fieldname='sum', model.FieldName='min')

The user can enter whatever they like, however in the code, you can always do .lower thing.

Edit:

I think it requires a new proxy expression, something like:

@dataclasses.dataclass
class AggregationExpression:
    left: Optional[ExpressionOrModelField]
    right: RediSearchAggregationReducers
    parents: List[Tuple[str, "RedisModel"]]

Similar functionality to FindQuery, but here, we have = instead of ==.