13 - CSV or parquet
Choose the bundled sample format with data_source:
taxi-csv and taxi-parquet hold the same NYC taxi rows and register as MLTable data assets, so the pipeline code is identical.
For real parquet, set data_source: nyc-taxi-open. It is a 2,000-row sample of the public Azure Open Datasets yellow taxi data (January 2015) with its original column names such as tpepPickupDateTime and fareAmount. prep.py cleans it and maps it to the model features. To train on more rows, copy parquet files from https://azureopendatastorage.blob.core.windows.net/nyctlc/yellow/ (anonymous read) into your ADLS container and read them with the adls source.
Why parquet
- Typed columns. Parquet stores the data type of each column. CSV is plain text, so every reader has to guess types.
- Smaller and faster. Parquet is compressed and column based, so a job reads only the columns it needs. The same table is usually several times smaller than the CSV.
- The usual format for real data. Data lakes, Fabric, Synapse and Azure Open Datasets all use it.
CSV stays the default because everyone can open it in a text editor. Start there, then switch once you are comfortable.
Convert a CSV to parquet
Using your own parquet
The adls source registers one file as a uri_file, not an MLTable (see Known issues). prep.py reads parquet or CSV, and applies the Open Datasets mapping when it sees those column names.
Back to Options.