[
https://issues.apache.org/jira/browse/NIFI-6840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otto Fowler updated NIFI-6840:
------------------------------
Description:
Instead of creating a protobuf converter processor, if PROTOBUF was supported
as a valid deserializer in nifi, with the corresponding support underneath,
then all the existing record processors would just work and there would be a
lot of functionality.
The first pass of this would not necessarily have to infer schema.
I *think* that a schema can only be avro however, I'm not sure how that is
overcome.
was:
Instead of creating a protobuf converter processor, if PROTOBUF was supported
as a valid schema in nifi, with the corresponding support underneath, then all
the existing record processors would just work and there would be a lot of
functionality.
The first pass of this would not necessarily have to infer schema.
This would include support in the schema registry/registries.
Summary: Support PROTOBUF Record Serialization/deserialization (was:
Support PROTOBUF as a valid schema type in NIFI)
> Support PROTOBUF Record Serialization/deserialization
> -----------------------------------------------------
>
> Key: NIFI-6840
> URL: https://issues.apache.org/jira/browse/NIFI-6840
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Otto Fowler
> Priority: Major
>
> Instead of creating a protobuf converter processor, if PROTOBUF was supported
> as a valid deserializer in nifi, with the corresponding support underneath,
> then all the existing record processors would just work and there would be a
> lot of functionality.
> The first pass of this would not necessarily have to infer schema.
> I *think* that a schema can only be avro however, I'm not sure how that is
> overcome.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
