Thank you Marc.
When I have leading dot, we are facing issues with schema confluent schema
registry integration.
1. We register schema without leading dot.
2. Confluent Schema registry uses the descriptor data to look up schema def
for a given protobuf message since descriptorData has extra
IIRC, the leading dot means that the name is absolute rather than relative.
I'm not sure it represents an error.
On Wed, 22 Dec 2021, 19:00 'Venkat Duddu' via Protocol Buffers, <
protobuf@googlegroups.com> wrote:
> We are seeing extra dot for external referenced variables in
> descriptorData in
We are seeing extra dot for external referenced variables in descriptorData
in the generated java class for a given Message.
*Message Definition*
syntax = "proto3";
package com.chegg;
import "google/protobuf/struct.proto";
message OneGraphRequest {
string operation_name = 1;
#1 for achieving "constants" the use of enums and default tag would give
you what you want, but this is only permitted in proto2
example: //Enums default to their zero value. By not using 0, you ensure a
message is always explicitly set.
enum MessageType {
MSG_TYPE_INVALID = 0;
MSG_TYPE_1 = 1;
