-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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.
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
Multiple Widgets Error: OpenSearch exception type=null_pointer_exception #14386
Comments
Illuminate V3.1 is installed. |
@jivepig Hi, just for clarification can you confirm: in v4.3 this worked with OpenSearch 1.3? |
Yes It worked in my instance on V4.3 and it running Opensearch V1.3 |
thx. |
If there are no results from the query, the following in OpenSearch returns without "aggregations": Which creates the NPE further along in OpenSearch at: |
@jivepig Sorry to ask again: I could not reproduce the problem with GL5 and OpenSearch 1.3. Was this a combination that you had tested? |
Michael confirmed that it started with using 2.x |
The changes in aggregations made for 5.x were modified and backported to 5.0 so that the old logic is in place again. These errors should no longer occur. The new logic is still available for aggregations, but in a way that it's not "crashing" existing widgets. |
Currently Graylog V5.0.3 and OpenSearch V2.5, I do not see these errors now. |
Previously on V4.3 these widgets were loaded with empty widgets with no data. Some for the data captured worked. Now in V5 Multiple widgets are displaying an error:
While retrieving data for this widget, the following error(s) occurred:
OpenSearch exception [type=null_pointer_exception, reason=Cannot invoke "org.opensearch.search.aggregations.InternalAggregations.getSerializedSize()" because "reducePhase.aggregations" is null].
Expected Behavior
Graylog with no logs or Graylog with Logs should not have this error.
Current Behavior
Dashboards and widgets impacted:
Possible Solution
Unknown
Steps to Reproduce (for bugs)
As noted
Context
Failed widget load
Your Environment
The text was updated successfully, but these errors were encountered: