tenthe commented on issue #4140:
URL: https://github.com/apache/streampipes/issues/4140#issuecomment-3840824456
Hi,
thanks for the clarification. You’re right, the adapter does not start or
stop the broker; it simply connects to an already running one.
I had another look at the export you shared and noticed a potential issue:
the **configured event schema and the sample event do not fully match**.
Normally, the preview event should reflect the configured schema 1:1.
**Configured event schema (runtimeName fields):**
`area`, `asset_name`, `asset_path`, `company`, `created_date`,
`data_point_id`, `data_type`, `plant`, `quality`, `server_name`,
`source_system`, `tag_name`, `timestamp`, `value`, `value_string`
**Sample event from the export:**
```json
{
"server_name": "opc.tcp://milo.digitalpetri.com:62541/milo",
"source_system": "OPC_UA_DA",
"tag_name": "NodeId(Identifier=2258, NamespaceIndex=0,
NodeIdType=<NodeIdType.Numeric: 2>)",
"quality": "Good",
"asset_name": "Numeric: 2>)",
"value_string": "2026-02-01 11:23:07.380922+00:00",
"plant": "Numeric: 2>)",
"data_type": "datetime",
"company": "NodeId(Identifier=2258, NamespaceIndex=0,
NodeIdType=<NodeIdType",
"asset_path": "NodeId(Identifier=2258, NamespaceIndex=0,
NodeIdType=<NodeIdType.Numeric: 2>)",
"created_date": "2026-02-01T11:23:07.603782",
"data_point_id": 5.9391267199000282E17,
"timestamp": "2026-02-01T11:23:07.380922+00:00"
}
```
A question that might help clarify this further: what exactly does the Kafka
topic contain?
Does it include events for multiple OPC UA nodes, or only events for a
single node? Mixing events from different nodes (with slightly different
structures) on the same topic can easily lead to schema mismatches.
Did you create this adapter from scratch, or was it edited from an existing
one?
To help narrow this down, could you please:
* Provide a **raw JSON message** from the Kafka topic
* Share the **Kafka configuration** you are using
* Ensure the topic contains events with a **single, consistent schema**
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
