Forum Discussion
Unexpected parquet exception occurred. Class: 'ParquetStatusException'
Hi
Thanks for your reply. The strange thing is that when I first create the flow it all works fine. Then if I re-run the Dataflow I get the issue. I have found that if I then 'drop' the table, go back to the flow and get it to recreate the table and rerun the import it all works again. The only difference is that on the first run it creates the table, on the second run it is replacing the data.
Hope that makes sense.
Regards
Toby
Advocate IIIHi Toby,
this is exactly what I found out yesterday. (Drop the tables in Lakehouse / Warehouse) and rerun the dataflow solves the report for again only the 1st refresh.
But This is clearly a bug IMO. Replacing a table shouldt break the lineage (table names and so on didnt change..).
Maybe for now we could try something like this:
1. using pipeline to schedule the DFs
2. adding a step (for warehouses it can be a stored procedure) before running the DF, which says - not drop the table - but delete all rows in the table
3. changing the DF from replace to append
maybe this works but clearly this should be a top issue to solve for the fabric team..
I had a support call with MS yesterday and they confirmed it is not linked to my subscription model and they are looking into it.
- webchris
I am facing the same issue... I hope that support will come back with a solution quick...
SnoekLHelper II
Any news on this issue. I'm experiencing the same problem.
Having similar issue. Please keep us posted of the solution
- Tom_CA
Helper I
sgrewalAdvocate I
Getting same error , is there a resolution for this issue.
