AWS databrew permissions does not respect lakeformation data filter permissions

Dear AWS Support Team,

I am are currently implementing a data governance tool utilizing AWS Lake Formation and AWS Glue Databrew for data transformations. i've encountered an issue: Glue Databrew does not seem to respect AWS Lake Formation data filter permission rules. Databrew throws an error when opening a dataset that has lakefomation data filter permission that disallow user to view certain columns. By right, users should still be able to open the dataset but not able to see the columns based on the dataset filters.

Lake Formation is a central part of AWS data governance, and it's crucial that data permissions are consistently enforced across AWS services. However, we've found that Glue Databrew is not adhering to Lake Formation data permissions, potentially causing security and compliance concerns.

I am seeking clarification on whether Glue Databrew should align with Lake Formation data permissions. We also need guidance on best practices to ensure compliance.