We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
default-spec.toml
cargo build
cargo build --release
cargo run
cargo run --release
./target/release/parquet-gen
./target/release/parquet-gen -s default-spec.toml
It panics with following error.
parse spec file: Error { inner: Error { inner: TomlError { message: "invalid inline table\nexpected `}`"
I think the issue is with default-spec.toml. Particularly bloom_filter config.
bloom_filter
# write with a bloom filter on this column bloom_filter = { fpp = 0.1, ndv = 100000 }
Looks like we cannot use multi-line as show above. If I change it to following single-line, then it's able to parse default-spec.toml just fine.
Change bloom_filter config used in default-spec.toml to use single-line inline table like explained above.
The text was updated successfully, but these errors were encountered:
fix(config): Fix default-spec.toml parse error
9693f2e
fixes: influxdata#1 Signed-off-by: Kaviraj <kavirajkanagaraj@gmail.com>
de024f3
Successfully merging a pull request may close this issue.
Steps to reproduce
cargo build
orcargo build --release
cargo run
orcargo run --release
or./target/release/parquet-gen
or./target/release/parquet-gen -s default-spec.toml
It panics with following error.
Problem.
I think the issue is with
default-spec.toml
. Particularlybloom_filter
config.Looks like we cannot use multi-line as show above. If I change it to following single-line, then it's able to parse
default-spec.toml
just fine.Potential solution
Change
bloom_filter
config used indefault-spec.toml
to use single-line inline table like explained above.Reference
The text was updated successfully, but these errors were encountered: