Details
-
Bug
-
Resolution: Fixed
-
Critical
-
6.5.0
-
Untriaged
-
Unknown
Description
Just like we detect recursion using bucket bindings, we can/must do recursion checks for static N1QL statements in eventing functions and fail deployment.
Attachments
Issue Links
- backports to
-
MB-39713 [BP MB-35394] - Do recursion checks for static N1QL statements in eventing functions
-
- Closed
-
For Gerrit Dashboard: MB-35394 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
120000,4 | [MB-35394] N1QL recursion check for static N1QL statements 1. Compilation worker will return N1QL keyspace names 2. New N1QL bucket bindings will be added based on keyspace names. Recursion check validation will be performed with new bindings and app will not be deployed if cycle formed 3. At pause/undeploy remove N1QL bindings added to be regenerated at deployment time after compilation worker returns new bindings | unstable | eventing | Status: ABANDONED | 0 | 0 |
122485,7 | [MB-35394] N1QL recursion check for static N1QL statements | unstable | eventing | Status: MERGED | +2 | +1 |
129709,2 | MB-39713: N1QL recursion check for static N1QL statements | mad-hatter | eventing | Status: MERGED | +2 | +1 |