Places queries need rework.

[namark]

The find requests for places and user places endpoints are not properly implemented:

vircadia-metaverse/vircadia_metaverse_v2_api/src/services/place/place.class.ts

Line 299 in aae404a

async find(params: Params): Promise<any> {

vircadia-metaverse/vircadia_metaverse_v2_api/src/services/place/user-places/user-places.class.ts

Line 67 in aae404a

async find(params?: Params): Promise<any> {

The filtering logic requires a cross referencing the domains collection, and this is done by first querying domains with maximum pagination limit (1000), then using that information in the places query filters.

The proper solution would be to use a $lookup aggregation, to join the two collections and then do filtering there. That will also take care of including the domain information in the place entries in the response, which is currently done in typescript.

In the long run we might need to avoid $lookup aggregation by restructuring the database to be more inline with recommended practices.

[namark]

$lookup aggregation is now implemented for places endpoint, but not user-places since the artificial limit is less of a problem there, and restructuring the whole database might still be necessary for performance.