CMR-9268: Log Volume for Elasticsearch Index Search is Too High

[jmaeng72]

Overview

What is the feature/fix?

Log Volume for Elasticsearch Index Search is Too High

What is the Solution?

Switch log from info to debug

What areas of the application does this impact?

Elastic_utils

Checklist

• [ ] I have updated/added unit and integration tests that prove my fix is effective or that my feature works
• [x] New and existing unit and int tests pass locally and remotely with my changes
• [ ] I have removed unnecessary/dead code and imports in files I have changed
• [x] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] I have cleaned up integration tests by doing one or more of the following:
  • de-duped, consolidated, removed dead int tests
  • transformed applicable int tests into unit tests
  • refactored to reduce number of system state resets by updating fixtures (use-fixtures :each (ingest/reset-fixture {})) to be :once instead of :each

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 57.74%. Comparing base (6d12772) to head (f2a0673).

Files	Patch %	Lines
...tils-lib/src/cmr/elastic_utils/search/es_index.clj	0.00%	1 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #2122 +/- ## ========================================== - Coverage 57.74% 57.74% -0.01% ========================================== Files 1044 1044 Lines 70391 70391 Branches 1994 1987 -7 ========================================== - Hits 40649 40648 -1 Misses 27891 27891 - Partials 1851 1852 +1 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.