Data Import
`read_parquet` Function
| Function | Description | Example |
|:--|:--|:-----|
| `read_parquet(path_or_list_of_paths)` | Read Parquet file(s)     | `SELECT * FROM read_parquet('test.parquet');` |
| `parquet_scan(path_or_list_of_paths)` | Alias for `read_parquet` | `SELECT * FROM parquet_scan('test.parquet');` |  
If your file ends in `.parquet`, the function syntax is optional. The system will automatically infer that you are reading a Parquet file:  
```sql
SELECT * FROM 'test.parquet';
```  
Multiple files can be read at once by providing a glob or a list of files. Refer to the [multiple files section](#docs:data:multiple_files:overview) for more information.  
#### Parameters {#docs:data:parquet:overview::parameters}  
There are a number of options exposed that can be passed to the `read_parquet` function or the [`COPY` statement](#docs:sql:statements:copy).  
| Name | Description | Type | Default |
|:--|:-----|:-|:-|
| `binary_as_string` | Parquet files generated by legacy writers do not correctly set the `UTF8` flag for strings, causing string columns to be loaded as `BLOB` instead. Set this to true to load binary columns as strings. | `BOOL` | `false` |
| `encryption_config` | Configuration for [Parquet encryption](#docs:data:parquet:encryption). | `STRUCT` | - |
| `filename` | Whether or not an extra `filename` column should be included in the result. | `BOOL` | `false` |
| `file_row_number` | Whether or not to include the `file_row_number` column. | `BOOL` | `false` |
| `hive_partitioning` | Whether or not to interpret the path as a [Hive partitioned path](#docs:data:partitioning:hive_partitioning). | `BOOL` | `true` |
| `union_by_name` | Whether the columns of multiple schemas should be [unified by name](#docs:data:multiple_files:combining_schemas), rather than by position. | `BOOL` | `false` |