JSON field mapping

We are experiencing a scenario where a JSON data field is getting interpreted as a number (ID) when some values in our case are not restricted to numbers. Looks like Metabase is trying to infer types from the JSON stored in the column and is expecting data.id to be a number. The JSON from that endpoint looks something like
{
"tables": [
{
"name": "foo",
"fields": [
{
"name": "data -> id",
"database_type": "double precision",
"base_type": "type/Number"
}
]
}
]
}
But since it’s a JSON column obviously can’t promise that data.id is gonna be a number.
Can I override that and specify a data type?

Hi @speedom8
It's currently not possible for Metabase to handle mixed JSON content:
https://github.com/metabase/metabase/issues/25744 - upvote by clicking :+1: on the first post