Great, I'm glad that worked. Note that you will get more readable results if you use your original --decode command instead of --decode_raw, since --decode_raw interprets the data without having access to the schema.
If this other 186 MB file is failing to parse then I would guess it's not actually a binary protocol buffer. I don't know if a general utility program exists for converting binary to JSON, but it's fairly easy to write a simple program to do that. On Sun, Mar 31, 2019 at 1:36 AM tausif.elahi via Protocol Buffers < [email protected]> wrote: > Thanks Adam *IT WORKED !* > Like you said, I used protoc 3.7.1, and I got an output on the command > line interface. > I have attached a text file which shows, my output results. > Yet, on the other hand, I have a file size of approx. 186MB, but after > running the command I get this output: > > *Failed to parse input.* > > > By the way, is there any command where I can get the output in a text/json > file ? > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/protobuf. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
