# RunParameters ## Properties | Name | Type | Description | Notes | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | **jar\_params** | Option<**Vec**> | A list of parameters for jobs with Spark JAR tasks, for example `\"jar_params\": [\"john doe\", \"35\"]`. The parameters are used to invoke the main function of the main class specified in the Spark JAR task. If not specified upon `run-now`, it defaults to an empty list. jar\_params cannot be specified in conjunction with notebook\_params. The JSON representation of this field (for example `{\"jar_params\":[\"john doe\",\"35\"]}`) cannot exceed 10,000 bytes. Use [Task parameter variables](https://docs.databricks.com/jobs.html#parameter-variables) to set parameters containing information about job runs. | \[optional] | | **notebook\_params** | Option<[**::std::collections::HashMap\**](https://github.com/mach-kernel/databricks-kube-operator/blob/master/databricks-rust-jobs/docs/serde_json::Value.md)> | A map from keys to values for jobs with notebook task, for example `\"notebook_params\": {\"name\": \"john doe\", \"age\": \"35\"}`. The map is passed to the notebook and is accessible through the [dbutils.widgets.get](https://docs.databricks.com/dev-tools/databricks-utils.html#dbutils-widgets) function. If not specified upon `run-now`, the triggered run uses the job’s base parameters. notebook\_params cannot be specified in conjunction with jar\_params. Use [Task parameter variables](https://docs.databricks.com/jobs.html#parameter-variables) to set parameters containing information about job runs. The JSON representation of this field (for example `{\"notebook_params\":{\"name\":\"john doe\",\"age\":\"35\"}}`) cannot exceed 10,000 bytes. | \[optional] | | **python\_params** | Option<**Vec**> | A list of parameters for jobs with Python tasks, for example `\"python_params\": [\"john doe\", \"35\"]`. The parameters are passed to Python file as command-line parameters. If specified upon `run-now`, it would overwrite the parameters specified in job setting. The JSON representation of this field (for example `{\"python_params\":[\"john doe\",\"35\"]}`) cannot exceed 10,000 bytes. Use [Task parameter variables](https://docs.databricks.com/jobs.html#parameter-variables) to set parameters containing information about job runs. Important These parameters accept only Latin characters (ASCII character set). Using non-ASCII characters returns an error. Examples of invalid, non-ASCII characters are Chinese, Japanese kanjis, and emojis. | \[optional] | | **spark\_submit\_params** | Option<**Vec**> | A list of parameters for jobs with spark submit task, for example `\"spark_submit_params\": [\"--class\", \"org.apache.spark.examples.SparkPi\"]`. The parameters are passed to spark-submit script as command-line parameters. If specified upon `run-now`, it would overwrite the parameters specified in job setting. The JSON representation of this field (for example `{\"python_params\":[\"john doe\",\"35\"]}`) cannot exceed 10,000 bytes. Use [Task parameter variables](https://docs.databricks.com/jobs.html#parameter-variables) to set parameters containing information about job runs. Important These parameters accept only Latin characters (ASCII character set). Using non-ASCII characters returns an error. Examples of invalid, non-ASCII characters are Chinese, Japanese kanjis, and emojis. | \[optional] | | **python\_named\_params** | Option<[**::std::collections::HashMap\**](https://github.com/mach-kernel/databricks-kube-operator/blob/master/databricks-rust-jobs/docs/serde_json::Value.md)> | A map from keys to values for jobs with Python wheel task, for example `\"python_named_params\": {\"name\": \"task\", \"data\": \"dbfs:/path/to/data.json\"}`. | \[optional] | | **pipeline\_params** | Option<[**crate::models::RunParametersPipelineParams**](https://github.com/mach-kernel/databricks-kube-operator/blob/master/databricks-rust-jobs/docs/RunParameters_pipeline_params.md)> | | \[optional] | | **sql\_params** | Option<[**::std::collections::HashMap\**](https://github.com/mach-kernel/databricks-kube-operator/blob/master/databricks-rust-jobs/docs/serde_json::Value.md)> | A map from keys to values for SQL tasks, for example `\"sql_params\": {\"name\": \"john doe\", \"age\": \"35\"}`. The SQL alert task does not support custom parameters. | \[optional] | | **dbt\_commands** | Option<**Vec**> | An array of commands to execute for jobs with the dbt task, for example `\"dbt_commands\": [\"dbt deps\", \"dbt seed\", \"dbt run\"]` | \[optional] | [\[Back to Model list\]](/doc/databricks-rust-jobs.md#documentation-for-models) [\[Back to API list\]](/doc/databricks-rust-jobs.md#documentation-for-api-endpoints) [\[Back to README\]](/doc/databricks-rust-jobs.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://databricks-kube-operator.gitbook.io/doc/databricks-rust-jobs/docs/runparameters.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.