Additional aggregation stages

Scott Colestock shared this question ago

Answered

I'm doing an aggregate (with a qb.where(...).where(...)) followed by a .project(...)

After that...I'd like to do more matching. It seems like I have to fall back on the standard match method with a json object at that point.

Is there a way to use the fluent api with aggregation where you can continue to use the where clause after projecting, etc. ?

The same question

Replies (1)

qinghai (support@nosqlbooster.com) ●

Like this?

db.testCols.aggregate()
.match(
qb.where("status").eq("A")
.where(qb.where("f1").eq("something").build()) //nested qb build
)
.project("gender _id f2")
.match(qb.where("f2").eq("something"))
.getShellScript() //use getShellScript to return MongoShell script

Reply URL

Scott Colestock ●

Thank you - missed that match would take a query builder. My mistake. Might want to add "match" function to the list here: https://mongobooster.com/FluentQueryAPI

URL