GrpcClientProperties.Channel.Inbound.Message.maxSize and GrpcClientProperties.Channel.Inbound.Metadata.maxSize are missing the @DataSizeUnit(DataUnit.BYTES) annotation that their server-side equivalents in GrpcServerProperties have.
Server (annotated):
// GrpcServerProperties.Inbound.Message
@DataSizeUnit(DataUnit.BYTES)
private DataSize maxSize = DataSize.ofBytes(4194304);
// GrpcServerProperties.Inbound.Metadata
@DataSizeUnit(DataUnit.BYTES)
private DataSize maxSize = DataSize.ofBytes(8192);
Client (missing):
// GrpcClientProperties.Channel.Inbound.Message
private DataSize maxSize = DataSize.ofBytes(4194304);
// GrpcClientProperties.Channel.Inbound.Metadata
private DataSize maxSize = DataSize.ofBytes(8192);
The server-side Javadoc also documents "If a data size suffix is not specified, bytes will be used" while the client-side does not.
This is similar to gh-49722 where the @DurationUnit annotations were added consistently across gRPC properties. The commit 5b7a6a9 for that issue updated the Duration fields in GrpcClientProperties but the DataSize fields in the same class were not addressed.
GrpcClientProperties.Channel.Inbound.Message.maxSizeandGrpcClientProperties.Channel.Inbound.Metadata.maxSizeare missing the@DataSizeUnit(DataUnit.BYTES)annotation that their server-side equivalents inGrpcServerPropertieshave.Server (annotated):
Client (missing):
The server-side Javadoc also documents "If a data size suffix is not specified, bytes will be used" while the client-side does not.
This is similar to gh-49722 where the
@DurationUnitannotations were added consistently across gRPC properties. The commit 5b7a6a9 for that issue updated the Duration fields inGrpcClientPropertiesbut the DataSize fields in the same class were not addressed.