N1QL exception not bring propagated

Description

When I run below through eventing server, all requests return success though many N1QL statements failed.

I verified this with wireshark:

But the handler throws no exception when above happens.

Components

Affects versions

Fix versions

Labels

Environment

None

Link to Log File, atop/blg, CBCollectInfo, Core dump

None

Release Notes Description

None

Attachments

4

Activity

Show:

Vikas Chaudhary June 11, 2019 at 8:35 AM

Seeing n1ql error getting populated as LCB exceptions in stats

 

CB robot November 30, 2018 at 10:48 AM

Build couchbase-server-6.5.0-1764 contains eventing commit f2d4592 with commit message:
Conditionally parse to check for N1QL error

Gautham Banasandra November 29, 2018 at 1:47 PM

Fixed in this commit - https://github.com/couchbase/eventing/commit/f2d4592a584c1e0360336455b5b03ea3e3338ae5

We are now throwing 3 types of Errors - KVError, N1QLError and EventingError. All of these types inherit from JavaScript's Error class.

 

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

Details

Assignee

Reporter

Is this a Regression?

Unknown

Triage

Untriaged

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created November 16, 2018 at 7:59 PM
Updated June 13, 2019 at 6:27 PM
Resolved November 29, 2018 at 1:48 PM
Instabug