François Massot

> Unfortunately, publishing the docs from our main repo to our website repo is not automated (yet) It is... but it was broken as one page had a broken link....

@zamazan4ik I opened a dedicated issue for the indexer monitoring #2160

So here is an example of a hit: ```json { "document": { "created_at": "2022-09-28T14:20:49Z", "id": 24276723600 } } ``` I see one problem coming: the json structure depending on snippet...

@geek-frio did you try such a config? ```yaml doc_mapping: field_mappings: - name: data_binary type: text indexed: false stored: true ``` With such a config, it should be stored but not...

> 2. Quickwit return an error, says: "doc_mapping.field_mappings: Error while parsing field data_binary: record, tokenizer, and fieldnorms parameters are allowed only if indexed is true. at line 11 column 5"...

Ok, sorry, that's probably a bug, let me reproduce that and push a fix.

@geek-frio we have merged PR #2075, and it should be fixed your issue, closing this one for now. Thanks for your feedback.

@demangejeremy I'm on M1, and you can build it with cargo. If you need to build it with all features (kafka, azure, postgresql...), you can launch `cargo build --features release-feature-vendored-set`

All endpoints are not idempotent, we need to work on that too.

Ideally I would see the retry at the tonic level. We need also to take into account that some gRPC clients use a tower balance service.