Configuration#
Setting the Runner#
Control the execution backend that Daft will run on by calling these functions once at the start of your application.
Set the runner for executing Daft dataframes to your local Python interpreter - this is the default behavior. |
|
Set the runner for executing Daft dataframes to a Ray cluster |
Setting configurations#
Configure Daft in various ways during execution.
Globally sets various configuration parameters which control Daft plan construction behavior. |
|
Context manager that wraps set_planning_config to reset the config to its original setting afternwards |
|
Globally sets various configuration parameters which control various aspects of Daft execution. |
|
Context manager that wraps set_execution_config to reset the config to its original setting afternwards |
I/O Configurations#
Configure behavior when Daft interacts with storage (e.g. credentials, retry policies and various other knobs to control performance/resource usage)
These configurations are most often used as inputs to Daft DataFrame reading I/O functions such as in Dataframe Creation.
Create configurations to be used when accessing storage |
|
Create configurations to be used when accessing an S3-compatible system |
|
Create credentials to be used when accessing an S3-compatible system |
|
Create configurations to be used when accessing Google Cloud Storage. |
|
Create configurations to be used when accessing Azure Blob Storage. |