You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 03:06:33 UTC
Re: [D] RLS rule addition issue [superset]
GitHub user dosubot[bot] edited a comment on the discussion: RLS rule addition issue
<!-- Greeting -->
Hi @Vidyaranya-Gavai-TTPL! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
This is a known issue in Superset 4.1.2—dataset owners sometimes can't see their own datasets in the RLS rule dropdown, and the dropdown/API can be affected by pagination or backend limits, causing datasets or roles to appear inconsistently. This bug was still present in 4.1.2 as of late 2025 and is linked to both frontend and backend problems with dataset and role visibility in the RLS UI. Fatal errors when adding RLS rules are often related to backend exceptions or misconfigurations, especially with certain databases like PostgreSQL, or when API parameters are not handled as expected [[source](https://github.com/apache/superset/discussions/33308)] [[source](https://github.com/apache/superset/issues/31466)] [[source](https://github.com/apache/superset/issues/32394)].
Recent versions after 4.1.2 have merged several fixes for RLS rule management, dataset visibility, and error handling. For example, PRs like [#30490](https://github.com/apache/superset/pull/30490) and [#36061](https://github.com/apache/superset/pull/36061) address RLS application and dropdown/caching issues, and upgrading to a newer version should resolve most of these problems.
If you must stay on 4.1.2, a possible workaround for dropdown pagination issues is to increase the `DEFAULT_PAGE_SIZE` in the frontend code to fetch more roles or datasets, but this may not bypass backend limits. Also, double-check your deployment configuration if you're running Superset under a subpath (e.g., with `SUPERSET_APP_ROOT`), as misconfigurations there can break dropdowns and API endpoints [[source](https://github.com/apache/superset/issues/35027)].
In summary: upgrading to a newer Superset version is the most reliable fix. If that's not possible, try increasing frontend page size and review your deployment/proxy config. If you need more details on a specific workaround, let me know!
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=893c550b-560d-44f8-ac93-a712da32b696) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/36184#discussioncomment-15012462
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org