Copy Activity to Lakehouse Table creates bad table

[davidanhip]

I have a bunch of complex json files that I want to process and pull out some fields from each record into a table.  There are a bunch of files which are updated often, so I'm trying to get the most efficient pipeline I can for this process.  I'm trying to do a copy activity to move from a json file to a lakehouse table, which seems to work, but results in a table I can't query in a notebook.  The table schema looks fine in the lakehouse explorer, but the preview fails.  When I try to load it into a notebook using the generated code from right clicking on the table, the code fails with a 403 Forbidden error.  If I right click on the table in lakehouse explorer and view the files, I can see the parquet files and I can load an individual file, but I can't load the whole thing.  I'm trying a very simple test right now where I extract a simple text field at the root of the json document and write it to a string in the table and I still get the 403 Forbidden error.  Any suggestions or ways I might debug?

[Anonymous]

Hi @davidanhip ,

Generally, 403 Forbidden errors are caused by insufficient permissions. Verify that your user account has permission to access lakehouse and its files.

Best Regards,
Adamk Kong

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[davidanhip]

I debugged this forever.  After a while, I realized that somehow when this particular lakehouse was created, it was bogus.  I created a new one and migrated my data there and everything worked.