I have a similar need but haven't looked into a solution. However, would
using "bytes" instead of "string" prevent the output? Or does the debug
logging also output the contents of the bytes?

-- TJ

You can always write custom code that formats messages any way you want for
your logs.  The TextFormat class is based purely on public interfaces, so
you can copy it and modify it.  You can define a custom option for flagging
fields that you want removed from the logs and use that custom option in
your modified TextFormat.

I don't think we want to implement this feature directly in the base
implementation.  There are too many little feature requests like this, and
if we implemented them all the library would get quite bloated.

Anyway, thanks for considering it. And thanks for keeping protobuf
bloat-free!

Kenton,

I have a message that contains fields that should never be logged. It would
be great if there was a way that the Message.toString() did not
automatically convert everything to a text representation. I'd love it if it
were an opt-in for the TextFormat instead of trying never to use toString()
on those messages.

Since AbstractMessage.toString() currently calls the static method for
TextFormat, would it be too much bloat to have an SPI layer there to attach
a custom formatter? Or maybe just not have a toString() at all where
everyone must explicitly use TextFormat.

The extra conditional isn't a problem--it's the fact that somewhere in the
code there may be a string cast where the field may be converted is bad or
in new code from a developer that isn't aware that toString() will behave
that way.

Message myMessage;
log.debug("message={}", myMessage); // TextFormat.printToString()
if(log.isDebugEnabled()) {
  log.debug("message={}", MyTextFormat.printToString(myMessage));