Sorting in filter values

[stanislav-dombrovskiy-dp]

Bug description

The same issue as here
#35008

It's about sorting Int values as String in filters
In 6.0.0RC2 it was fixed.
But in 6.0.0 it reproduces again

Screenshots/recordings

Superset version

6.0.0

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]

This is a confirmed regression: integer filter values are sorted as strings (lexicographically) in some Superset versions, so you see "1, 10, 100..." instead of "1, 2, 3..." as expected. The issue was fixed in 6.0.0RC2 (PR #34858), but the fix did not make it into the 6.0.0 final release and the problem reappeared. The regression is tracked in multiple issues and was addressed again in later PRs (#35130, #35155, #35152), which are now merged into the 6.0-bug-fixes branch and master—so the fix will be in RC3 and newer builds (discussion).

There is no user-level workaround or configuration option for affected versions; the only way to resolve this is to upgrade to a version that includes the fix. If you need a temporary solution, you would have to patch the frontend code or ensure the backend query for filter values sorts numerically, but this is not officially documented or supported.

For complex sorting, use the filter UI controls and structured format—raw SQL strings for sorting are no longer supported. If you need to sort by a custom order, create a calculated column or metric and sort by that metric in the filter config.

References:

• Original issue #35008
• Regression/fix timeline and details
• PR #35130
• PR #35155
• PR #35152

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[stanislav-dombrovskiy-dp]

@dosu I don't understand: all mentioned PRs were merged already. All issues were fixed. Can I expect that in 6.0.1 won't have this problem ?
Or what is the ETA or plan?

[dosubot]

There is currently no official changelog, release branch, or tag for Superset 6.0.1, and no public ETA or release plan has been documented. The integer sorting fix is merged in master and will be included in the next release after 6.0.0, but there’s no confirmation yet about when 6.0.1 will be released or what it will contain. If you need the fix immediately, you’d need to use the latest master or apply the relevant PRs as a patch, but this isn’t officially documented or supported. For now, keep an eye on the Superset releases page for updates.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[rusackas]

@sadpandajoe this is a funky one... I added it to the board for 6.0.1 review.

[stasDomb]

still present in 6.0.1rc1

[stasDomb]

Unfortunately, it still present in 6.1.0rc1.

[stasDomb]

Still present in 6.1.0rc2. Could you please fix it? It's really important, I can't update from a really old version because of this problem