Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File Format "NativeParquet" is never used in SampleDB.sql #28

Open
casperlehmann opened this issue Jun 24, 2020 · 2 comments
Open

File Format "NativeParquet" is never used in SampleDB.sql #28

casperlehmann opened this issue Jun 24, 2020 · 2 comments

Comments

@casperlehmann
Copy link

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'?

@asears
Copy link

asears commented Jul 2, 2020

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.

Also See: https://docs.microsoft.com/en-us/sql/t-sql/statements/create-external-table-transact-sql?view=sql-server-ver15
https://docs.microsoft.com/en-us/azure/synapse-analytics/sql/develop-openrowset

@casperlehmann
Copy link
Author

Could the NativeParquet custom file format simply be used in one of the examples to make its use more apparent?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants