[
https://issues.apache.org/jira/browse/METRON-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242646#comment-16242646
]
ASF GitHub Bot commented on METRON-1301:
----------------------------------------
Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/metron/pull/832#discussion_r149471276
--- Diff:
metron-platform/metron-elasticsearch/src/main/java/org/apache/metron/elasticsearch/utils/ElasticsearchUtils.java
---
@@ -179,4 +186,46 @@ else if(ipObj instanceof List) {
}
throw new IllegalStateException("Unable to read the elasticsearch ips,
expected es.ip to be either a list of strings, a string hostname or a host:port
string");
}
+
+ /**
+ * Converts an Elasticsearch SearchRequest to JSON.
+ * @param esRequest The search request.
+ * @return The JSON representation of the SearchRequest.
+ */
+ public static String
toJSON(org.elasticsearch.action.search.SearchRequest esRequest) {
+ String json = "null";
--- End diff --
Yes, definitely this is kind of weird. This is taken care of in the latest
commit.
> Alerts UI - Sorting on Triage Score Unexpectedly Filters Some Records
> ---------------------------------------------------------------------
>
> Key: METRON-1301
> URL: https://issues.apache.org/jira/browse/METRON-1301
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.4.1
> Reporter: Nick Allen
> Assignee: Nick Allen
> Fix For: Next + 1
>
> Attachments: 01-Alerts-UI-default-view.png, 02-Sort-on-Score-field.png
>
>
> Sorting on a field like threat triage score in the Alerts UI removes any
> records that do not have a threat triage score defined from the search
> results.
> For example, I have 7 records when sorted by timestamp. All 7 records have a
> timestamp field.
> After sorting by score (threat triage score) there are only 5 records. The 2
> records missing a threat triage score are no longer included.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
