`new Date()` in aggregation node.js

[mbfakourii]

New Issue Checklist

• Report security issues confidentially.
• Any contribution is under this license.
• Before posting search existing issues.

Issue Description

Steps to reproduce

I have an Aggregation in mongo shell that works fine.

But it doesn't output anything in node.js !

var pipeline = [
    {
        $match: {
            _p_enx: "Entrix$" + req.params[KEY_ENTRIX_ID],
        },
    },
    {
        $lookup: {
            from: "KeyLink",
            let: {
                tempPointer: {
                    $substr: ["$_p_klk", 8, -1],
                },
            },
            pipeline: [
                {
                    $match: {
                        $expr: {
                            $and: [
                                {
                                    $eq: ["$$tempPointer", "$_id"],
                                },
                            ],
                        },
                    },
                },
            ],
            as: "klk",
        },
    },
    {
        $match: {
            $or: [
                {
                    "klk.exp": {
                        $gt: new Date(),
                    },
                },
            ],
        },
    },
];

var query = new Parse.Query(EntrixKeyLink);

let responseAggregation = await query.aggregate(pipeline, {useMasterKey: true});

I think there is a problem in new Date().

Actual Outcome

Nothing is output !

Expected Outcome

It should output like the image above

Environment

Server

• Parse Server version: 6.3.1 and 7.0.0
• Operating system: Windows

Database

• System (MongoDB or Postgres): MongoDB
• Database version: 7.0.8

Client

• SDK (iOS, Android, JavaScript, PHP, Unity, etc): API
• SDK version: n/a

Logs

n/a

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mtrezza]

Please test with Parse Server 7, the best would be to add a PR with a failed test. We only fix security bugs in Parse Server 6.

[mbfakourii]

Please test with Parse Server 7, the best would be to add a PR with a failed test. We only fix security bugs in Parse Server 6.

I tested in Parse Server 7.0.0 and the problem is not solved !

[mtrezza]

If you remove the date match, then you get the same output on both sides? Did you try { $toDate: new Date() }?

[mbfakourii]

If you remove the date match, then you get the same output on both sides?

Yes

Did you try { $toDate: new Date() }?

I tried this method as below, but it didn't work !

{
    $match: {
        $or: [
            {
                "klk.exp": {
                    $gt: {$toDate: new Date()},
                },
            },
        ],
    },
},

[mtrezza]

Could you write a failing test and submit a PR? The pipeline should be as simple as possible.

[mbfakourii]

Could you write a failing test and submit a PR? The pipeline should be as simple as possible.

What do I expect in this test?
what should I compare the pipeline output with?

[mtrezza]

Just could just add the necessary data to the DB to replicate the issue. You expect the query response to be what it should return.

[parseplatformorg]

🎉 This change has been released in version 9.9.0-alpha.1

[mtrezza]

This is addressed by #10438 which adds opt-in rawValues and rawFieldNames options for aggregation queries. With rawValues: true, date values use MongoDB Extended JSON ({ $date: '...' }) for explicit typing instead of relying on schema-based conversion. With rawFieldNames: true, native MongoDB field names like _p_enx are used directly without transformation.