You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NativeParquet is implemented as a file format, but when the view parquet.YellowTaxi is created, it refers to FORMAT='PARQUET'.
There does not seem to be a reason for it to exist, and it confuses the reader, when they are trying to get up to speed with using the platform.
Is there any benefit to creating a custom file format rather than refering to 'PARQUET'?
The text was updated successfully, but these errors were encountered:
External File Format is required with an External Table, though it is not used in this view example. The OpenRowSet syntax uses a built-in formatter.
Agree, it would be beneficial if this example either removed the unused object or better implemented it and identified where to use a view containing OpenRowSet vs. External Table.
NativeParquet is implemented as a file format, but when the view parquet.YellowTaxi is created, it refers to FORMAT='PARQUET'.
There does not seem to be a reason for it to exist, and it confuses the reader, when they are trying to get up to speed with using the platform.
Is there any benefit to creating a custom file format rather than refering to 'PARQUET'?
The text was updated successfully, but these errors were encountered: