Unable to use DB names with prefixes for YDB

[vgvoleg]

Bug description

Superset with YDB works fine with queries like

SELECT * FROM db_name

in SQL Lab.

But if database has a prefix, which should be defined like:

SELECT * from `prefix/db_name`

It fails with parsing error

Screenshots/recordings

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot]

Superset's SQL parser handles special characters like '/' in database names or table names by escaping them correctly. The Table class in the parser converts names with special characters into a URL-encoded format. For example, a table name "table.name" with a schema "schema/name" and a catalog "catalog\nname" would be converted to "catalog%0Aname.schema%2Fname.table%2Ename" ^[1].

In your case, the parsing error might be due to the way the prefix is being handled. You might need to ensure that the prefix and database name are correctly formatted or escaped according to Superset's parsing rules. If the issue persists, it could be related to how the YDB engine is configured to handle such cases. The YDBEngineSpec class in Superset includes specific configurations for YDB, which might need to be adjusted to accommodate database names with prefixes ^[2].

To continue talking to Dosu, mention @dosu.

---

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