Forum Discussion
Lakehouse Grant Read Permission Problem
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 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 😞
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;
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 DaleT ,
I tried the path as you said and also the full path but nothing changed, I got the same error.
Hello DaleT ,
You are completely right. I have tested this same scenario without using onelake schema and it worked. I wont use this option. Thank you so much
Best regards