Forum Discussion
V-Order Functionality in Fabric Notebook
DennesTorres to me it seems like a bug , when tables are not optimized at session level while they are at dataframe write level ( by adding "parquet.vorder.enabled ","true") even after that there seems no signs that it has been optimized in metadata/ logs not even at the time of its first creation
After doing checks at _delta logs and in the metadata and even table properties
There is no v order which has been present after checking by all three methods , i
am not sure if any other method is also availiable, if not then to me it sounds more like a bug
Hi,
I tried your script. It will help me a lot in other purposes, but I confirm your result: If the optmization doesn't happen on session level there is no sign of any metadata pointing to the optmization.
To be absolutely sure about the result, I completed a test on the file level as well. The original article mentions only the parquet files affected by the write operation would be optmized.
But even on file level, there is no metadata pointing to any optmization.
The script I tried, a variation from yours, is located below. What's the link to the issue you registered?