When creating KPIs, Chaos Genius does not let us use legacySQL for the query despite adding #legacySQL at the top of the query.
Explain the environment
Chaos Genius version: 0.4.0
OS Version / Instance: macOS 11.6.3
Deployment type: Setup from scratch
Current behavior
An error message saying "Test Connection Failed" appears with an API 400 POST response describing that the query text entered specifies to use legacySQL, while the API options specify not to use legacySQL. If "#legacySQL" is included at the top of any query, this message pops up.
Expected behavior
I wanted to use legacySQL for a query to set up a KPI, but, I am currently being forced to use standardSQL. I need the functionality of legacySQL to easily set up some KPIs.
Describe the bug
When creating KPIs, Chaos Genius does not let us use legacySQL for the query despite adding #legacySQL at the top of the query.
Explain the environment
Current behavior
An error message saying "Test Connection Failed" appears with an API 400 POST response describing that the query text entered specifies to use legacySQL, while the API options specify not to use legacySQL. If "#legacySQL" is included at the top of any query, this message pops up.
Expected behavior
I wanted to use legacySQL for a query to set up a KPI, but, I am currently being forced to use standardSQL. I need the functionality of legacySQL to easily set up some KPIs.
Screenshots
Additional context
N/A
Logs
N/A