quickwit-oss / quickwit-oss/quickwit

Tutorials are failing on index creation

Open
#3,984 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Rust
Stars
11.7k
Forks
597
Avg merge
2d 22h
Merged PRs (30d)
37

Description

Describe the bug
Running:

curl -o hdfs_logs_index_config.yaml https://raw.githubusercontent.com/quickwit-oss/quickwit/main/config/tutorials/hdfs-logs/index-config.yaml
./quickwit index create --index-config hdfs_logs_index_config.yaml

as described in the S3 tutorial fails with

❯ Creating index...
✘ Command failed: Api error: (code=400 Bad Request, message=Invalid config: Failed to read YAML file.: Error while parsing field `timestamp`: unknown field `fast_precision`, expected one of `description`, `input_formats`, `output_format`, `precision`, `indexed`, `stored`, `fast`.)

Caused by:
    (code=400 Bad Request, message=Invalid config: Failed to read YAML file.: Error while parsing field `timestamp`: unknown field `fast_precision`, expected one of `description`, `input_formats`, `output_format`, `precision`, `indexed`, `stored`, `fast`.)

I haven't tested it but this probably occurs elsewhere (everywhere?) in the docs.

Steps to reproduce (if applicable)
See above

Configuration:
The configuration described in the turorial.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with config/tutorials/hdfs-logs/index-config.yaml and the linked S3 tutorial, then run the documented curl and ./quickwit index create commands to reproduce the YAML validation error. Check the related tutorial configuration for the reported timestamp field and confirm the tutorial's index creation succeeds without the unknown-field error.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
documentation
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.