Integrations

OPC UA to Databricks, without a script.

Read the OPC UA nodes with MaestroHub on the plant network, turn them into named values with units and quality, and write them to a Unity Catalog Volume or a table through a Databricks SQL warehouse. Writes are buffered on disk through network outages.

The flow

One value, from the machine to Databricks. Illustrative.

OPC UAindustrial protocolns=3;s=Press7.Temp

MaestroHub

Press 7 temperature · 75.9 °C · Good

named, unit, quality
origin stamped
buffered on disk

Databrickslakehouse/Volumes/plant/raw/press7/

Why do it with MaestroHub

More than a pipe from OPC UA to Databricks.

Bronze data that is already clean

Values arrive named, typed and with quality, so the first lakehouse layer is usable instead of a raw dump to reverse-engineer.

One edge, many tables

The same OPC UA values can feed Databricks, a historian and dashboards at once, each destination with its own buffer.

Every number traceable

Origin is stamped on every value, so a feature in a model can be walked back to the machine and node it came from.

What lands in Databricks

An example. You choose the fields in the pipeline.

ts	asset	signal	value	unit	quality
2026-10-03 06:00:01	press-shop/press7	temperature	75.9	°C	good

Set it up in three steps

1
Connect OPC UA
Add the OPC UA server, browse its address space and pick the nodes, or add hundreds at once with bulk creation.
2
Give the values meaning
Map each value to a topic in the namespace with its name, unit and schema. Quality and origin are stamped on every value.
3
Deliver to Databricks
Add a Databricks output: write files to a Unity Catalog Volume, or insert rows through a SQL warehouse.

Before you start

What each side needs, from the connector documentation.

OPC UA

The server address, built as opc.tcp://host:port/path. The standard OPC UA port is 4840.
For any Security Policy other than None, a client certificate: paste your own (RSA keys only) or let MaestroHub generate a self-signed one.
If you use the auto-generated certificate, the OPC UA server administrator must trust it on the server.
A username and password when the server does not allow Anonymous access.

Example settings

Server Hostname: opcua.example.com
Port: 4840
Security Policy: Basic256Sha256
Security Mode: SignAndEncrypt
Certificate Mode: Auto-generate (self-signed)
Authentication Type: UsernamePassword

OPC UA connector documentation

Databricks

A Databricks workspace URL starting with https://, for example https://myworkspace.cloud.databricks.com.
A personal access token, or an OAuth M2M client ID and client secret.
Unity Catalog enabled in the workspace, with the target volumes already created.
For Databricks SQL: the SQL warehouse ID, found under Connection Details on the warehouse page.

Example settings

Workspace URL: https://<your-workspace>.cloud.databricks.com
Auth Type: OAuth M2M
Client ID: <your-client-id>
Default Volume Path: /Volumes/my_catalog/my_schema/my_volume/
Max File Size (MB): 25
Overwrite (Write function): false

Databricks connector documentation

Things to know

Pitfalls and limits the documentation calls out, so they don't surprise you on site.

OPC UA

Security Policy and Security Mode must agree. Policy None requires Mode None. Any other policy requires Sign or SignAndEncrypt.
Node identifiers need a namespace index and a type prefix (i=, s=, g=, b=). Namespace 0 is typically standard nodes, 2 and up custom nodes. Browse a small scope first to find the exact IDs.
On Monitor functions, set the sampling interval equal to or faster than the publishing interval, or changes can be missed. Subscriptions are recreated automatically after a lost connection or a session timeout.

Limits

Manual client certificates support RSA keys only. Auto-generated certificates are RSA 2048-bit and valid for 365 days.
Monitor functions cannot be created through Quick Add. Use the full Function Builder.

Databricks

Volume paths must follow /Volumes/<catalog>/<schema>/<volume>/. Set a Default Volume Path to use relative paths in functions.
Write overwrites an existing file by default. Set Overwrite to false to make the call fail instead.
In Databricks SQL, the connection's Query Timeout caps every statement. A function's Timeout can shorten it but not extend it.

Limits

File reads and writes are limited by Max File Size: 25 MB by default, 124 MB at most.
Databricks Storage works only on Unity Catalog Volumes.

What teams use it for

Predictive maintenance models

Vibration and temperature history with quality flags for feature engineering.

Quality analytics

Process parameters joined with inspection results per part or batch.

Cross-plant benchmarking

The same namespace structure from every site, so plants compare like for like.

Ways to connect OPC UA to Databricks

In general terms. Check any specific product for its own details.

Compare a custom script, a flow tool, a cloud vendor's edge service and MaestroHub

Swipe sideways to see every column

	A custom script	A flow tool	A cloud vendor's edge service	MaestroHub
Talks OPC UA	A library you choose	Community plug-ins	Depends on the vendor	Built in, one of 90+ connectors
Names, units and schema	You write it	You build it	Partly, in the vendor's model	One governed namespace
Quality on every value	You write it	You build it	Depends on the vendor	Built in, carried through calculations
Where each value came from	You write it	You build it	Depends on the vendor	Stamped on every value
Survives a network outage	You build it	You build it	Usually, to that vendor's cloud	On disk, per destination, in order
Several destinations at once	One script each	Yes, flow by flow	Mostly that vendor's cloud	Any mix, each with its own buffer
Permissions and audit	You build it	You build it	Cloud account permissions	Roles, single sign-on, audit trail
AI agents can use the data	You build it	You build it	Depends on the vendor	Through the MCP server

Questions

How do I get OPC UA data into Databricks?

Do I need to write code to connect OPC UA to Databricks?

No. You configure the OPC UA connection and the Databricks output in MaestroHub and join them with a pipeline. Transformations can be added where you need them.

Where does MaestroHub run for this?

On your own infrastructure next to the machines: an edge box, a virtual machine or Kubernetes. Only the rows you choose leave the plant for Databricks.

Why not just write a script for OPC UA to Databricks?

A script works on day one. The cost comes later: decoding and naming values, handling bad quality, buffering through outages, keeping credentials safe, and doing it again for the next machine and the next destination. MaestroHub does those once, for every connector.

What else can OPC UA data go to?

More than 90 connectors are included in every edition, among them historians, databases, cloud warehouses, message brokers and business systems, so the same values can feed several destinations at once.

Other integrations

All integrations