When using the storage_gcs_key_file option, ensure that the JSON key file is physically located on the server where the SAS Compute session is running (or accessible via a shared network path), not just on your local client machine; additionally, the Service Account associated with that key must have the "Storage Object Admin" role (or at least write permissions) on the target bucket to successfully create new Parquet files.
Type : CREATION_INTERNE
The example uses the internal SASHELP.BASEBALL dataset. The code provides the complete context for creating the Parquet table and displaying the data.
| 1 | LIBNAME mylib parquet "" |
| 2 | storage_platform = "GCS" |
| 3 | storage_bucket_name = "my-bucket" |
| 4 | storage_gcs_key_file = "/user/myfiles/my-project-5123b3a258a1.json" |
| 5 | ; |
| 6 | PROC COPY in=sashelp out=mylib; |
| 7 | select baseball; |
| 8 | RUN; |
| 9 | PROC PRINT DATA=mylib.baseball (obs=3); |
| 10 | var name team; |
| 11 | RUN; |
FedSQL is a proprietary SAS implementation of the ANSI SQL:1999 standard, offering scalable, mult...
This document describes the default SAS libraries (Work, User, Sashelp, Sasuser) provided by SAS,...
This document explains how SAS engines manage access and processing of data files in the SAS Comp...
This document describes the characteristics of SAS engines, including a summary of commonly used ...
This document defines what a SAS data set is, its components (data and metadata), and how it is s...