-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Add schema registry support to ProtoBufMessageDecoder #18221
Copy link
Copy link
Open
Labels
featureNew functionalityNew functionalityingestionRelated to data ingestion pipelineRelated to data ingestion pipelinejavaPull requests that update Java codePull requests that update Java codepluginsRelated to the plugin systemRelated to the plugin systempriority: lowNice to have, can waitNice to have, can waitserializationRelated to data serialization and deserializationRelated to data serialization and deserialization
Metadata
Metadata
Assignees
Labels
featureNew functionalityNew functionalityingestionRelated to data ingestion pipelineRelated to data ingestion pipelinejavaPull requests that update Java codePull requests that update Java codepluginsRelated to the plugin systemRelated to the plugin systempriority: lowNice to have, can waitNice to have, can waitserializationRelated to data serialization and deserializationRelated to data serialization and deserialization
Type
Fields
Give feedbackNo fields configured for issues without a type.
Motivation
pinot-plugins/pinot-input-format/pinot-protobuf/src/main/java/org/apache/pinot/plugin/inputformat/protobuf/ProtoBufMessageDecoder.javastill carries a top-level TODO for schema registry support.Pinot already has the Confluent-specific protobuf ingestion module, but the base protobuf decoder still requires descriptor files and class names. Supporting schema-registry-backed descriptor resolution here would close a long-standing gap, or clarify why the base decoder should stay file-based only.
Scope
Notes
Observed on
upstream/masteron April 15, 2026.