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

do not index large case property values #30009

Merged
merged 1 commit into from
Jul 7, 2021
Merged

do not index large case property values #30009

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 2 additions & 1 deletion corehq/pillows/mappings/case_search_mapping.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,8 @@
"exact": {
"index": "not_analyzed",
"type": "string",
"null_value": ""
"null_value": "",
"ignore_above": 8191
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you also need it on the main value field?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't believe so. Specifically the error message referenced this field, not case properties as a whole Document contains at least one immense term in field="case_properties.value.exact", which makes sense because each field is indexed separately rather than as a whole, so it's specifically this string one that is having the issue, but as with the other question above, I will make sure to confirm on staging.

},
"numeric": {
"type": "double",
Expand Down