Skip to content

Commit

Permalink
Include notes about required files in proto_path
Browse files Browse the repository at this point in the history
Not sure if this is just standard for most people, but personally I thought the library just wasn't working because I didn't have my proto_path set up right.  Props to this [Stack Overflow question on importing descriptor.proto](http://stackoverflow.com/questions/20069295/importing-google-protobuf-descriptor-proto-in-java-protocol-buffers) for helping me to see what needed to happen.
  • Loading branch information
jtratner committed Aug 30, 2014
1 parent cc90076 commit e2f7e30
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,12 @@ So you can reuse existing data definitions in .proto for BigQuery with this plug
The generated JSON schema files are suffixed with `.schema` and their base names are named
after their package names and `bq_table_name` options.

If you do not already have the standard google protobuf libraries in your `proto_path`, you'll need to specify them directly on the command line (and potentially need to copy `bq_schema.proto` into a proto_path directory as well), like this:

```sh
protc --bq-schema_out=path/to/out/dir foo.proto --proto_path=. --proto_path=<path_to_google_proto_folder>/src

This comment has been minimized.

Copy link
@gxy837

gxy837 Nov 13, 2014

protc
=>
protoc

```

### Example
Suppose that we have the following foo.proto.

Expand Down

0 comments on commit e2f7e30

Please sign in to comment.