feature/#634 add Databricks Documentation#1281
Conversation
docs/userman/advanced_features/3rd party integration/databricks.md
Outdated
Show resolved
Hide resolved
docs/userman/advanced_features/3rd party integration/databricks.md
Outdated
Show resolved
Hide resolved
docs/userman/advanced_features/3rd party integration/databricks.md
Outdated
Show resolved
Hide resolved
docs/userman/advanced_features/3rd party integration/databricks.md
Outdated
Show resolved
Hide resolved
| It uses the default `SCENARIO` scope again. The Databricks table name is "hist_log". The profile | ||
| and cluster id are similar to the previous Databricks Table data node config. The *exposed_type* | ||
| provided is "polars". | ||
|
|
There was a problem hiding this comment.
Can we add one or two lines explaining the usage is the same as a normal data node.
read/write/append, etc... Why not a short example.
What do you think?
| to build the write and append queries to write and append data to Databricks database. | ||
| Its *scope* is by default `SCENARIO`. The profile to be used is "default" profile with the cluster id is | ||
| "0123-456789-dbscluster2". The exposed type of this data node will be the default value "polars". | ||
|
|
There was a problem hiding this comment.
Can we add one or two lines explaining the usage is the same as a normal data node.
read/write/append, etc... Why not a short example.
What do you think?
docs/userman/advanced_features/3rd party integration/databricks.md
Outdated
Show resolved
Hide resolved
docs/userman/advanced_features/3rd party integration/databricks.md
Outdated
Show resolved
Hide resolved
jrobinAV
added
Core
…tion-documentation
…ntation # Conflicts: # docs/userman/scenario_features/data-integration/data-node-usage.md
|
This PR has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this PR, then please add new commit or another comment, otherwise this PR will be closed in 14 days. For more information please refer to the contributing guidelines. |
github-actions
bot
added
the
🥶Waiting for contributor
trgiangdo
removed
the
🥶Waiting for contributor
|
This is on hold for now but should not be closed. |
|
This PR has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this PR, then please add new commit or another comment, otherwise this PR will be closed in 14 days. For more information please refer to the contributing guidelines. |
github-actions
bot
added
the
🥶Waiting for contributor
trgiangdo
removed
the
🥶Waiting for contributor
|
This PR has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this PR, then please add new commit or another comment, otherwise this PR will be closed in 14 days. For more information please refer to the contributing guidelines. |
github-actions
bot
added
the
🥶Waiting for contributor
|
This PR has been closed because it has been marked as "🥶Waiting for contributor" for more than 14 days with no activity. |
trgiangdo
removed
the
🥶Waiting for contributor
3 participants
#634
Temporarily deployed here: https://docs.taipy.io/en/feature634-databricks-integration-documentation/