subqueries should be advised, explained and monitored

Description

A placeholder to track an annoyance in N1QL: subqueries are planned as part of execution, and thus are not explained.
Also, since the request plan is missing the subquery, they are not monitored.
We should have a way to hang a subquery plan to an expression.
And ideally, we should have a cache of plans so that we don't reprepare over and over again.

Components

Affects versions

Fix versions

Labels

Environment

None

Release Notes Description

None

Activity

Show:

Ray Offiah January 8, 2025 at 9:05 AM

 

Removing the releasenote tag. …

Ray Offiah January 7, 2025 at 3:06 PM

Agreed

Bingjie Miao January 6, 2025 at 7:06 PM

I’m not sure this is something that we should include in release note. This is more of a (feature) enhancement. Also this was done quite some time ago (version 7.1.2).

cc

Pierre Regazzoni January 6, 2025 at 6:05 PM

can you provide info for doc team. Thanks.

Ray Offiah January 6, 2025 at 9:02 AM

This is flagged for inclusion in the release notes (or maybe the What’s New page), so could you add a few liines for the Docs team?

Thanks.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created October 13, 2018 at 2:07 PM
Updated February 4, 2025 at 3:30 AM
Resolved June 6, 2022 at 4:29 PM
Instabug