Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

fix concatenate field docs #5370

Merged
merged 3 commits into from
Sep 4, 2024
Merged

fix concatenate field docs #5370

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
eea8d6d
fix concatenate field docs
tontinton Aug 30, 2024
c29a481
Merge branch 'main' into fix-concat-docs
fmassot Sep 3, 2024
721f934
Merge branch 'main' into fix-concat-docs
fmassot Sep 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/configuration/index-config.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -424,7 +424,7 @@ to the field being searched.
```yaml
name: my_default_field
type: concatenate
concatenated_fields:
concatenate_fields:
- text # things inside text, tokenized with the `default` tokenizer
- resource.author # all fields in resource.author, assuming resource is an `object` field.
include_dynamic_fields: true
Expand All @@ -435,7 +435,7 @@ record: basic
Concatenate fields don't support fast fields, and are never stored. They uses their own tokenizer, independently of the
tokenizer configured on the individual fields.
At query time, concatenate fields don't support range queries.
Only the following types are supported inside a concatenate field: text, bool, i64, u64, json. Other types are rejected
Only the following types are supported inside a concatenate field: text, bool, i64, u64, f64, json. Other types are rejected
at index creation, or silently discarded during indexation if they are found inside a json field.
Adding an object field to a concatenate field doesn't automatically add its subfields (yet).
<!-- typing is made so it wouldn't be too hard do add, as well as things like params_* matching all fields which starts name with params_ , but the feature isn't implemented yet -->
Expand Down
Loading