Elasticsearch log flooded with 'Deprecated field [lowercase_expanded_terms] used'
Open
Nobody has claimed this yet.
Component: opscode-erchef
Status: move to jira
Type: Chore
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
Chef Server Version
chef-server-core 14.10.23-1
Platform Details
Ubuntu 18.04
Configuration
Pretty standard standalone setup
Scenario
The log in /var/log/opscode/elasticsearch is constantly being flooded with the following line:
2021-11-29_09:45:59.73218 [2021-11-29T09:45:59,732][WARN ][o.e.d.c.ParseField ] [chef.example.com] Deprecated field [lowercase_expanded_terms] used, replaced by [Decision is now made by the analyzer]
2021-11-29_09:45:59.77185 [2021-11-29T09:45:59,771][WARN ][o.e.d.c.ParseField ] [chef.example.com] Deprecated field [lowercase_expanded_terms] used, replaced by [Decision is now made by the analyzer]
2021-11-29_09:45:59.77188 [2021-11-29T09:45:59,771][WARN ][o.e.d.c.ParseField ] [chef.example.com] Deprecated field [lowercase_expanded_terms] used, replaced by [Decision is now made by the analyzer]
2021-11-29_09:46:00.16032 [2021-11-29T09:46:00,160][WARN ][o.e.d.c.ParseField ] [chef.example.com] Deprecated field [lowercase_expanded_terms] used, replaced by [Decision is now made by the analyzer]
2021-11-29_09:46:00.16035 [2021-11-29T09:46:00,160][WARN ][o.e.d.c.ParseField ] [chef.example.com] Deprecated field [lowercase_expanded_terms] used, replaced by [Decision is now made by the analyzer]
2021-11-29_09:46:00.16258 [2021-11-29T09:46:00,162][WARN ][o.e.d.c.ParseField ] [chef.example.com] Deprecated field [lowercase_expanded_terms] used, replaced by [Decision is now made by the analyzer]
2021-11-29_09:46:00.16260 [2021-11-29T09:46:00,162][WARN ][o.e.d.c.ParseField ] [chef.example.com] Deprecated field [lowercase_expanded_terms] used, replaced by [Decision is now made by the analyzer]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with /var/log/opscode/elasticsearch and reproduce or inspect the repeated deprecated-field warnings. Trace which Chef Server search request emits lowercase_expanded_terms, then verify that the warning is no longer produced while the affected search behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch
- Domain
- search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100