SAP HANA calculation view call with PLACEHOLDER parameters is re-cased by Superset 6.0.0 and causes "invalid table name" (HANA error 259) #39328

Activity

1. dosubot

   added

   #bug:regressionBugs that are identified as regessionsBugs that are identified as regessions

   data:connect:hanaRelated to HanaRelated to Hana

   sqllabNamespace | Anything related to the SQL LabNamespace | Anything related to the SQL Lab

   on Apr 13, 2026
2. dosubot commented on Apr 13, 2026

   

   dosubotBot

   on Apr 13, 2026 – with DosuBot

   Last edited by dosubot

   More actions

   Hi @ku7mich! I'm Dosu and I’m helping the superset team.

   This is caused by Superset 6.0.0 always parsing and regenerating SQL queries through sqlglot before execution [1]. SAP HANA is mapped to the PostgreSQL dialect in sqlglot [2], and when sqlglot regenerates your SQL, it uppercases the quoted identifier "zbw.10_001/INVENTORY" → "ZBW.10_001/INVENTORY", which breaks the case-sensitive HANA lookup.

   Between Superset 5.0.0 and 6.0.0, sqlglot was upgraded from v27 to v28, which likely changed how the PostgreSQL dialect handles quoted identifiers with special characters like . and /. This is part of a broader pattern — several databases (PostgreSQL, SQL Server, Oracle, ClickHouse) have reported sqlglot regeneration corrupting queries in 6.0.0.

   Workaround options:

   1. Create a HANA view that wraps the calculation view with PLACEHOLDERs, and query that view from Superset instead.
   2. Downgrade to Superset 5.0.0 if this is a blocker.

   For a proper fix, this likely needs either:

   • A custom sqlglot dialect for SAP HANA (similar to what was done for Pinot) that preserves identifier casing correctly.
   • Or a change to the HANA dialect mapping in superset/sql/parse.py to use a dialect that doesn't uppercase quoted identifiers.
   • Or reporting the specific identifier uppercasing behavior to the sqlglot project as a bug.

   You can verify this is the root cause by checking what SQL Superset actually sends to HANA — look at the executed_sql field in the query history, or test parsing/regenerating your query directly with sqlglot v28 using the PostgreSQL dialect.

   To reply, just mention @dosu.

   ---

   Docs are dead. Just use Dosu.

   
3. hainenber

   self-assigned this

   on Apr 14, 2026
4. rusackas

   added 2 commits that reference this issue on Aug 4, 2026

   fix(sql): preserve quoted-identifier casing for the HANA dialect (#39328

   ...

   42168e4

   fix(sql): preserve quoted-identifier casing for the HANA dialect (#39328

   ...

   2f9bde5
5. rusackas

   closed this as completedin #42731on Aug 5, 2026