dosubot[bot] commented on issue #37551:
URL: https://github.com/apache/superset/issues/37551#issuecomment-3858301468

   <!-- Answer -->
   Here's the current status: your issue is a known regression in Superset 6, 
where guest RLS (Row Level Security) filters are applied twice to virtual 
datasets in embedded dashboards. This double application causes SQL alias 
mismatches and "unknown column" errors, even if the column exists in your 
dataset. This did not happen in Superset 5 and is tracked in [GitHub issue 
#37359](https://github.com/apache/superset/issues/37359).
   
   A fix is proposed in [PR 
#37395](https://github.com/apache/superset/pull/37395), which is open and under 
review. The PR author (@YuriyKrasilnikov) is actively working on it, but there 
is no explicit assignment to a specific maintainer yet. There is no 
configuration workaround except using physical datasets instead of virtual 
ones, which may not be practical for your use case.
   
   You can follow progress or add context directly on the PR. If you have 
further technical questions or need more details about the workaround or the 
fix, let me know.
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   <sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/fc4bc4ae-b992-4e41-881b-ce3885ff3e5a?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/fc4bc4ae-b992-4e41-881b-ce3885ff3e5a?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/fc4bc4ae-b992-4e41-881b-ce3885ff3e5a?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/fc4bc4ae-b992-4e41-881b-ce3885ff3e5a?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/fc4bc4ae-b992-4e41-881b-ce3885ff3e5a?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/fc4bc4ae-b992-4e41-881b-ce3885ff3e5a?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/fc4bc4ae-b992-4e41-881b-ce3885ff3e5a?feedback_type=other)</sup>
   
   [![Chat with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&nbsp;[![Open
 in 
Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Here%27s%20the%20current%20status%3A%20your%20issue%20is%20a%20known%20regression%20in%20Superset%206%2C%20where%20guest%20RLS%20%28Row%20Level%20Security%29%20filters%20are%20applied%20twice%20to%20virtual%20datasets%20in%20embedded%20dashboards.%20This%20double%20application%20causes%20SQL%20alias%20mismatches%20and%20%22unknown%20column%22%20errors%2C%20even%20if%20the%20column%20exists%20in%20your%20dataset.%20This%20did%20not%20happen%20in%20Superset%205%20and%20is%20tracked%20in%20%5BGitHub%20issue%20%2337359%5D%28https%3A//github.com/apache/superset/issues/37359%29.%0A%0AA%20fix%20is%20proposed%20in%20%5BPR%20%2337395%5D%28https%3A//github.com/apache/superset/pull/37395%29%2C%20which%20is%20open%20and%20under%20review.%20The%20PR%20author%20
 
%28%40YuriyKrasilnikov%29%20is%20actively%20working%20on%20it%2C%20but%20there%20is%20no%20explicit%20assignment%20to%20a%20specific%20maintainer%20yet.%20There%20is%20no%20configuration%20workaround%20except%20using%20physical%20datasets%20instead%20of%20virtual%20ones%2C%20which%20may%20not%20be%20practical%20for%20your%20use%20case.%0A%0AYou%20can%20follow%20progress%20or%20add%20context%20directly%20on%20the%20PR.%20If%20you%20have%20further%20technical%20questions%20or%20need%20more%20details%20about%20the%20workaround%20or%20the%20fix%2C%20let%20me%20know.)&nbsp;[![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/37551)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to