This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
The following commit(s) were added to refs/heads/main by this push:
new e87a652ec chore: protobuf-message-action says which imports the schema
can have: the well-known types of Google except field_mask.proto (CAMEL-27377)
(#3355)
e87a652ec is described below
commit e87a652ec796eba1ce5e13388e3a7c411ae964af
Author: Claus Ibsen <[email protected]>
AuthorDate: Sun Nov 22 17:24:00 2026 +0100
chore: protobuf-message-action says which imports the schema can have: the
well-known types of Google except field_mask.proto (CAMEL-27377) (#3355)
Claude-Session: https://claude.ai/code/session_016Y4dDmBDsSWV117kccuNf9
Co-authored-by: Claude Opus 5.5 <[email protected]>
---
kamelets/protobuf-message-action.kamelet.yaml | 2 +-
library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json | 2 +-
.../src/main/resources/kamelets/protobuf-message-action.kamelet.yaml | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/kamelets/protobuf-message-action.kamelet.yaml
b/kamelets/protobuf-message-action.kamelet.yaml
index 0488e02eb..26243d10c 100644
--- a/kamelets/protobuf-message-action.kamelet.yaml
+++ b/kamelets/protobuf-message-action.kamelet.yaml
@@ -40,7 +40,7 @@ spec:
Output: the body is a `com.google.protobuf.DynamicMessage` of the
message type `messageName`. The headers are kept.
- Good to know: a field of the JSON that the schema does not have is left
out, and a value of the wrong type fails the message. The schema is read once,
when the Kamelet starts, so a syntax error, an unknown `messageName` or an
import other than the well-known types of Google (such as
`google/protobuf/timestamp.proto`) fails at startup. This Kamelet brings the
`.proto` parser `camel-protobuf-schema`, with Kotlin and Guava (about 6 MB).
+ Good to know: a field of the JSON that the schema does not have is left
out, and a value of the wrong type fails the message. The schema is read once,
when the Kamelet starts, so a syntax error or an unknown `messageName` fails at
startup. The schema is one file: it can import only the well-known types of
Google that the parser ships, which are `any.proto`, `descriptor.proto`,
`duration.proto`, `empty.proto`, `struct.proto`, `timestamp.proto` and
`wrappers.proto` under `google/prot [...]
required:
- schema
type: object
diff --git
a/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
b/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
index dc95dbcd5..d7861c523 100644
--- a/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
+++ b/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
@@ -1765,7 +1765,7 @@
"supportLevel" : "Stable",
"title" : "Protobuf Message Action",
"summary" : "Turns each message, JSON text, into a Protobuf message object
that follows the `.proto` schema you give, with no classes generated by the
Protobuf compiler.",
- "description" : "Turns each message, JSON text, into a Protobuf message
object that follows the `.proto` schema you give, with no classes generated by
the Protobuf compiler.\n\nUse it before `kafka-sink` with
`schemaRegistryVendor` and `schemaFormat` `protobuf`, which needs a Protobuf
message object as the body and fails on JSON text. It also suits any other step
that takes a Protobuf message (a `com.google.protobuf.Message`). To get
Protobuf binary data instead, use `protobuf-serial [...]
+ "description" : "Turns each message, JSON text, into a Protobuf message
object that follows the `.proto` schema you give, with no classes generated by
the Protobuf compiler.\n\nUse it before `kafka-sink` with
`schemaRegistryVendor` and `schemaFormat` `protobuf`, which needs a Protobuf
message object as the body and fails on JSON text. It also suits any other step
that takes a Protobuf message (a `com.google.protobuf.Message`). To get
Protobuf binary data instead, use `protobuf-serial [...]
"group" : "Actions",
"namespace" : "Transformation",
"provider" : "Apache Software Foundation"
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/protobuf-message-action.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/protobuf-message-action.kamelet.yaml
index 0488e02eb..26243d10c 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/protobuf-message-action.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/protobuf-message-action.kamelet.yaml
@@ -40,7 +40,7 @@ spec:
Output: the body is a `com.google.protobuf.DynamicMessage` of the
message type `messageName`. The headers are kept.
- Good to know: a field of the JSON that the schema does not have is left
out, and a value of the wrong type fails the message. The schema is read once,
when the Kamelet starts, so a syntax error, an unknown `messageName` or an
import other than the well-known types of Google (such as
`google/protobuf/timestamp.proto`) fails at startup. This Kamelet brings the
`.proto` parser `camel-protobuf-schema`, with Kotlin and Guava (about 6 MB).
+ Good to know: a field of the JSON that the schema does not have is left
out, and a value of the wrong type fails the message. The schema is read once,
when the Kamelet starts, so a syntax error or an unknown `messageName` fails at
startup. The schema is one file: it can import only the well-known types of
Google that the parser ships, which are `any.proto`, `descriptor.proto`,
`duration.proto`, `empty.proto`, `struct.proto`, `timestamp.proto` and
`wrappers.proto` under `google/prot [...]
required:
- schema
type: object