### BigSchema
This library is meant as a simple way to generate the big query boilerplate
given a simple yaml based schema.
#### CLI Tool
The library comes with a simple command line tool that takes a source file,
an optional destination directory default is ```./schema/``` and an output
format and transforms the given yaml specifications to BigQuery compliant
schema in the desired output format.
```bash
$ bigschema --help
Usage: bigschema [OPTIONS] SOURCE [DESTINATION]
Options:
-f, --output-format [java|json]
Which format to output the data in? Default
is JSON
-o, --overwrite BOOLEAN Should we overwrite the data in existing
file? Default is FALSE
--help Show this message and exit.
```
#### File Specification
```yaml
spec-mode: "compact" | "verbose"
---------------------------------------------------------------------------------
spec-mode: "verbose"
--------------------
table:
type: "table"
fields:
- name:
type: "integer" | "float" | "string" | "timestamp" | "boolean" | "bytes" | "record_name"
mode: "nullable" | "repeated" | "required"
record:
type: "record"
fields:
- name:
type: "integer" | "float" | "string" | "timestamp" | "boolean" | "bytes" | "record_name"
mode: "nullable" | "repeated" | "required"
----------------------------------------------------------------------------------
spec-mode: "compact"
--------------------
table:
type: table
fields:
- name_of_column, type_of_column, mode_of_column
record:
type: record
fields:
- name_of_column, type_of_column, mode_of_column
```
This library is meant as a simple way to generate the big query boilerplate
given a simple yaml based schema.
#### CLI Tool
The library comes with a simple command line tool that takes a source file,
an optional destination directory default is ```./schema/``` and an output
format and transforms the given yaml specifications to BigQuery compliant
schema in the desired output format.
```bash
$ bigschema --help
Usage: bigschema [OPTIONS] SOURCE [DESTINATION]
Options:
-f, --output-format [java|json]
Which format to output the data in? Default
is JSON
-o, --overwrite BOOLEAN Should we overwrite the data in existing
file? Default is FALSE
--help Show this message and exit.
```
#### File Specification
```yaml
spec-mode: "compact" | "verbose"
---------------------------------------------------------------------------------
spec-mode: "verbose"
--------------------
table:
type: "table"
fields:
- name:
type: "integer" | "float" | "string" | "timestamp" | "boolean" | "bytes" | "record_name"
mode: "nullable" | "repeated" | "required"
record:
type: "record"
fields:
- name:
type: "integer" | "float" | "string" | "timestamp" | "boolean" | "bytes" | "record_name"
mode: "nullable" | "repeated" | "required"
----------------------------------------------------------------------------------
spec-mode: "compact"
--------------------
table:
type: table
fields:
- name_of_column, type_of_column, mode_of_column
record:
type: record
fields:
- name_of_column, type_of_column, mode_of_column
```
Metadata
Release files for bigschema 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bigschema-1.0.3.tar.gz | 6.6 kB | Details |
Release files / bigschema-1.0.3.tar.gz
| Download URL | bigschema-1.0.3.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3b364aeb647894c84e01bd8256d48550d302f9d3120bd59ff0473e2cecb711da
|
|
BLAKE2b-256 checksum How to use checksums |
fed4b4fbe8d8b8990a805170b7fd175b8f1913e811cacbaec1e508563c0c72e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |