Forum Discussion
Lakehouse Grant Read Permission Problem
- 9 months ago
After some tests, I got the exactly same error message. The cause could be the third to last limitation of schemas in this list: https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-schemas#public-preview-limitations .
There could be two solutions though they aren't perfect.
1. Stop using schema.
2. Use Pyspark instead like following, the address is an ABFS address.
df = spark.read.load("abfss://[email protected]/0558838e7/Tables/dbo/sales") display(df)
Hello tayloramy ,
We can not do this just using onelake security roles, as far as I tested user needs to have viewer role in workspace of lakehouse at least. Otherwise user can not see the table data.
Hi,
We can achieve this without granting the user a view role in workspace. I changed the setting "Data access mode" in my test and I got it done. But this could be a big change to the security settings, I would suggest doing it with cautions. Please refer to the following.
1. Change the setting "Data access mode". This is in the "Settings" of SQL Endpotint only.
2. Create a role.
3. Done, use it in a notebook with Spark.
- ismail_ozturk9 months agoHelper I
Hello DaleT ,
You are absolutely right I changed the "Data access mode" setting as "User's identity access mode" and the user sees only the tables which he has right to see. But if the same user tries to read these tables via spark, it gives an error "Artifact not found". I could not understand why 😞
- tayloramy9 months agoSuper User
Hi ismail_ozturk,
I recommend opening a ticket with Microsoft. I see similar things in my tenant with OneLake Security. I guess this is why it is still in preview.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
- DaleT9 months agoResolver II
Hi,
The error message is a little strange. But I still find something. It seems you enabled the schema in the lakehouse. The table isn't under the default schema either. So, try query the table with schema, please. Please also try Pyspark for debug purpose.
select * from gensenta.eban limit 10;
- ismail_ozturk9 months agoHelper I
Hello DaleT ,
I tried the path as you said and also the full path but nothing changed, I got the same error.