Warehouse Parquet Format

[andyemiller]

I utilized a data pipeline to copy a lakehouse into a warehouse. Everything transferred properly, but within 30 minutes, the transferred tables were converted into a Parquet format. 

When you view the cloud-based warehouse, you see standard tables from the lakehouse. See the first image. 

I can also see the stored procedures and views that were created within the warehouse. However, PowerBI and any SQL endpoint is not able to reference the aforementioned tables. Here are the tables on the SQL endpoint. 

Even the earlier pipeline cannot find the stored procedures, tables, and views that are available in the warehouse. Here is the error message on the copy activity. 

Would someone be able to assist me with this issue? I need to retain the original file structure, views, and stored procedures within the view.

[andyemiller]

Once again, the issue noted above has reemerged. 

The cloud-based warehouse has the correct table structure. 

However, the SQL endpoint has the Parquet file structure. 

Once again, this breaks the reporting tools. Is anyone able to assist me? 

[Anonymous]

Hi @andyemiller ,

Thanks for using Fabric Community.

Apologies for the issue you have been facing. I would like to check are you still facing this issue?
As we know currently Fabric is in preview it is difficult to tell what could be the reason for this performance. I would request you to wait for sometime and try again as it may be due to some outage issue.

If the issue still persists, please reach out to our support team so they can do a more thorough investigation on why this it is happening: Link

After creating a Support ticket please provide the ticket number as it would help us to track for more information.

Hope this helps. Please let us know if you have any other queries.

[andyemiller]

@Anonymous, yes, I am still experiencing the issue. The timing is intermittent and inconsistent.  I have submitted a ticket (2311160040010477) with the related information. 

[andyemiller]

I cannot explain it, but the issue was corrected this morning within minutes of posting this message. There was, however, a real issue between 12:00 pm EST yesterday and 5:00 am EST today.