Superset adding unecessory group by on deck.gl polygon map

[prasad-de001]

I'm trying to create a map for given polygon. polygon saved in bigquery (tried json and geography ). when loading into map I'm getting
400 POST https://bigquery.googleapis.com/bigquery/v2/projects/project-name/queries?prettyPrint=false: Grouping by expressions of type JSON is not allowed at [10:39] error.

my polygon looks like this
{
"type": "MultiPolygon",
"coordinates": [
[
[
[
-3.354396425071087,
47.814981686384485
],
[
-3.3545939098500175,
47.81497517119161
],
[
-3.354789492595091,
47.81495568836276
],
[
-3.354981289595744,
47.81492342554266
],
[
-3.35516745361132,
47.81487869346335
]
[
-3.354396425071087,
47.814981686384485
]
]
]
]
}

when I view the query it is look like this, I dont know why there is a group by clause there.

SELECT boundary AS boundary
FROM (-- 6dcd92a04feb50f14bbcf07c661680ba
SELECT boundary AS boundary
FROM dashboard.farm
WHERE boundary IS NOT NULL
LIMIT 10000
-- 6dcd92a04feb50f14bbcf07c661680ba
) AS virtual_table
WHERE boundary IS NOT NULL GROUP BY boundary
LIMIT 1000;

appreciate your help on this.

[dosubot[bot]]

Hello @prasad-de001! I'm here to help with any bugs, questions, or contributions you have. Let's work together to solve the issue you're encountering.

The error you're encountering is due to the GROUP BY clause being applied to a JSON data type, which is not allowed in BigQuery. This is likely happening because Superset is automatically adding a GROUP BY clause to the query, possibly due to its default query generation rules or configurations.

To address this issue, you can try the following approaches:

1. Check Chart Configuration: Ensure that there are no settings in your chart configuration that might be causing the GROUP BY clause to be added. Look for any group-by options or aggregations that might be enabled.

2. Modify the Query Manually: If possible, manually edit the query to remove the GROUP BY clause. This can be done by accessing the SQL Lab in Superset and adjusting the query to suit your needs.

3. Review Superset's Configuration: There might be a configuration setting in Superset that controls the automatic addition of GROUP BY clauses. Although I couldn't find specific documentation on this, reviewing the Superset configuration files or settings might provide insights.

4. Data Type Handling: Consider changing the data type of your polygon data in BigQuery if JSON is causing issues. Using a data type that is more compatible with grouping operations, such as GEOGRAPHY, might help, although you mentioned you've already tried this.

If these steps do not resolve the issue, you may need to delve deeper into the Superset codebase or configuration to identify why the GROUP BY clause is being added.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[prasad-de001]

Check Chart Configuration -> I checked but not able to find any configuration that causing group by.
Modify the Query Manually: -> not able to edit that query only view available.
Review Superset's Configuration: -> Not able to find
Data Type Handling: -> I change into String but then Map won't work.