alpancs / protoc-gen-pubsub-schema Goto Github PK

I got error plugin killed by signal 9 when execute this plugin. Kindly help with this issue :)

How to reproduce:
protoc wartek/core/event/nlp_job_update/v1/event.proto --pubsub-schema_out=OUT_DIR --pubsub-schema_opt=message-encoding=json

--pubsub-schema_out: protoc-gen-pubsub-schema: Plugin killed by signal 9.

"Protobuf release 3.12 adds experimental support for optional fields in proto3".

foo.proto:

syntax = "proto3";

message Foo {
    optional string id = 1;
}

But:

protoc \
--proto_path=${PWD} \
--pubsub-schema_out=${PWD} \
--pubsub-schema_opt=message-encoding-json \
--pubsub-schema_opt=schema-syntax=proto3 \
${PWD}/foo.proto

Yields:

foo.proto: is a proto3 file that contains optional fields, but code generator protoc-gen-pubsub-schema hasn't been updated to support optional fields in proto3. Please ask the owner of this code generator to support proto3 optional.

If a protocol buffer file includes multiple top-level messages, the plugin rejects the file.

Solutions:

1. Extract top-level message into a separate file and use that
2. Permit the specification of one top-level message type using e.g. --pubsub-schema_opt=top-level-message=Foo

foo.proto:

syntax = "proto3";

message Foo {
}
message Bar {
}

But:

protoc \
--proto_path=${PWD} \
--pubsub-schema_out=${PWD} \
--pubsub-schema_opt=message-encoding-json \
--pubsub-schema_opt=schema-syntax=proto3 \
${PWD}/foo.proto

Yields:

--pubsub-schema_out: test/foo.proto: only one top-level type may be defined in a file (see https://cloud.google.com/pubsub/docs/schemas#schema_types). use nested types or imports (see https://developers.google.com/protocol-buffers/docs/proto)

If not, it would be great if we could move it under:
https://github.com/GoogleCloudPlatform

Similar to this plugin:
https://github.com/GoogleCloudPlatform/protoc-gen-bq-schema