Why does sqlLab encypt long fieldnames?

[rluech]

We notice that when jumping from Chart to Run in SQL Lab, long fieldnames get hashed / encrypted (see printscreen attached). Is this a bug or a feature, and why? Is there a way to disable this encryption?

[dosubot[bot]]

Hey there, @rluech! I'm here to help you with any bugs, questions, or contributions you have. Let's squash those bugs together! 🤖

I couldn't find specific information in the Superset repository about why long field names are hashed or encrypted when transitioning from Chart to Run in SQL Lab. It is unclear whether this behavior is a bug or a feature, and there is no documentation or configuration setting mentioned that controls this behavior.

However, there is a test in the Superset codebase that verifies the behavior of field name handling when transitioning from Chart to SQL Lab, which suggests that this behavior might be intentional ^[1].

To continue talking to Dosu, mention @dosu.

---

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

[rluech]

Thank you @dosu for investigating. I found the critical length of fieldname is 30 characters above which hashing is applied.

[dosubot[bot]]

Thanks for sharing that insight! It seems like the hashing of field names longer than 30 characters is an intentional feature, likely to ensure compatibility with database systems that have limitations on identifier lengths. If you need to avoid this behavior, consider using shorter aliases for your field names in SQL Lab. If this feature is causing issues, you might want to raise it with the maintainers for further clarification or potential adjustments. Let me know if there's anything else I can assist you with!

To continue talking to Dosu, mention @dosu.

---

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

[rluech]

Closed and continued in new Q&A 33016