We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
since 3.4 the log is flooded with this warning: 2018-01-25 14:43:59,889 WARN [geonetwork.search-logger] - unable to log query into database...
I guess it is related to the fact that this instance does not have elastic configured?
At least it doesn't make sense to log this if the feature is not activated
The text was updated successfully, but these errors were encountered:
Yes probably.
Then you should turn off search statistics in the admin no ?
Sorry, something went wrong.
What happens when it's activated and there is no elastisearch configured? If doesn't make sense, why it's activated by default?
Indeed. Turning it off by default.
Turn off search stats by default (#2502).
09f4d79
No branches or pull requests
since 3.4 the log is flooded with this warning:
2018-01-25 14:43:59,889 WARN [geonetwork.search-logger] - unable to log query into database...
I guess it is related to the fact that this instance does not have elastic configured?
At least it doesn't make sense to log this if the feature is not activated
The text was updated successfully, but these errors were encountered: