Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace angled single quotes with regular single quotes #6030

Merged
merged 2 commits into from
Sep 9, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 12 additions & 12 deletions website/docs/reference/resource-configs/databricks-configs.md
Original file line number Diff line number Diff line change
Expand Up @@ -410,43 +410,43 @@ To take advantage of this capability, you will need to add compute blocks to you

```yaml

<profile-name>:
target: <target-name> # this is the default target
profile-name:
target: target-name # this is the default target
outputs:
<target-name>:
target-name:
type: databricks
catalog: [optional catalog name if you are using Unity Catalog]
schema: [schema name] # Required
host: [yourorg.databrickshost.com] # Required
catalog: optional catalog name if you are using Unity Catalog
schema: schema name # Required
host: yourorg.databrickshost.com # Required

### This path is used as the default compute
http_path: [/sql/your/http/path] # Required
http_path: /sql/your/http/path # Required

### New compute section
compute:

### Name that you will use to refer to an alternate compute
Compute1:
http_path: [‘/sql/your/http/path’] # Required of each alternate compute
http_path: '/sql/your/http/path' # Required of each alternate compute

### A third named compute, use whatever name you like
Compute2:
http_path: [‘/some/other/path’] # Required of each alternate compute
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are square brackets needed? There should be just a single http_path per compute entry, not a list, correct?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you're right @johnson-jay-l ! the brackets were previously used to display code/fields that needed to be replaced with the user content. however, it can cause confusion for sure. I've removed them so it's clearer - thanks for flagging!

http_path: '/some/other/path' # Required of each alternate compute
...

<target-name>: # additional targets
target-name: # additional targets
...
### For each target, you need to define the same compute,
### but you can specify different paths
compute:

### Name that you will use to refer to an alternate compute
Compute1:
http_path: [‘/sql/your/http/path’] # Required of each alternate compute
http_path: '/sql/your/http/path' # Required of each alternate compute

### A third named compute, use whatever name you like
Compute2:
http_path: [‘/some/other/path’] # Required of each alternate compute
http_path: '/some/other/path' # Required of each alternate compute
...

```
Expand Down
Loading