-
Notifications
You must be signed in to change notification settings - Fork 26
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
feature/#634 add Databricks Documentation #1281
base: develop
Are you sure you want to change the base?
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
…tion-documentation
#634
Temporarily deployed here: https://docs.taipy.io/en/feature634-databricks-integration-documentation/