Bug report: Databricks Queries not displaying special characters (Umlauts etc) correctly

Hi everyone, I just wanted to re-raise this bug / issue that seems to affect all kinds of queries using the databricks connector.

When loading data from a databricks table, special characters like "ö", "ä" or "⌀" are all displayed as "��". Within Databricks, all text is displayed correctly with the Umlauts present. There is a known workaround using a transformer (Displaying Umlauts / special characters in table from databricks query - #4 by Paulo), however, it is getting really tedious to set up the transformer for every query containing text columns (a LOT of Umlauts in German).

We are using self-hosted Retool version 3.52.2.

It would be great if someone from the Retool team could provide an update regarding this. Thanks in advance! :slight_smile:

1 Like

Hello @jonas_09!

Sorry to hear this issue is still present. I can double check with the eng team and add your +1 to the current ticket.

I totally understand that running transformers on the query results can get tedious. Is Paulo's solutions of iterating through and replacing chars slowing down the applications speed?

1 Like

Hi @Jack_T ,
is there any update on this issue?
We are using databricks a lot in our team and a solution would help saving a lot of time and work.

Thanks in advance and kind regards :slight_smile:

1 Like

Hello @flaschenpost-wha!

Unfortunately there is no update on this issue, our engineering team has a lot of projects in the works :sweat:

But I can add your +1 to this issue which will bump it to the teams and help it to build more momentum!

I will keep you updated on any and all news I hear on this feature request in this thread :+1:

1 Like

Hello @Jack_T
is there any update now?

1 Like

Hello @PhilippKraut

Unfortunately there aren't any updates, our engineering team has a lot on their plate.

But I did and you in as a +1 so that should help increase the weight of the request for the team to see :+1:

1 Like

Hi, are there any updates for this topic? Can we expect a fix in the near future?

Hello @flaschenpost-wha,

Our eng team is currently working on this. It seems that it is only occurring for on-prem instances and not on our cloud.

Which version of Retool are you running? It may be fixable with an update.

Hi @Jack_T ,

we use self-hosting in version 3.114.2

Hi, is there any progress on this bug?

Hi @flaschenpost-wha,

Apologies for the delay and thank you for the patients. It looks like the ticket was added to our most recent engineering cycle and has been assigned to an engineer.

So hopefully will have this fixed shortly and will update you with any news from the ticket :saluting_face:

Hi @flaschenpost-wha,

Just got word that this ticket has been marked as completed by our engineering team! It should be getting rolled out in the newest patch/update on cloud!

Hi @Jack_T , thx for the update. Will it be available on self-hosted also?

1 Like

Hi @flaschenpost-wha,

It should be live on our newest Edge version that comes out every week!

@flaschenpost-wha Looks like the ticket had been in review but has now been labeled as done and should be getting rolled out to our most recent stable release shortly!