-
Notifications
You must be signed in to change notification settings - Fork 505
METRON-939 Elasticsearch ES5 with Xshield client support #619
Conversation
| .put("index.number_of_shards", 1) | ||
| .put("node.mode", "network") | ||
| .put("index.number_of_replicas", 1); | ||
| .put("transport.type", "netty4"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we parameterize this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry, nvm, I retract. This is in the integration test component.
cestella
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution!
|
|
||
| byte[] indexTemplate = new byte[0]; | ||
| try { | ||
| indexTemplate = Files.readAllBytes(Paths.get("/Users/wbekker/metron/metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/package/files/yaf_index.template")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This path should be relative.
| try { | ||
| indexTemplate = Files.readAllBytes(Paths.get("/Users/wbekker/metron/metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/package/files/yaf_index.template")); | ||
| } catch (IOException e) { | ||
| e.printStackTrace(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably want to throw back up a Runtime Exception
| try { | ||
| node.close(); | ||
| } catch (IOException e) { | ||
| e.printStackTrace(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We either want to throw up the exception or at least log it with a logger, rather than stdout.
|
Thanks for the review @cestella I've pushed a commit fixing the reported issues. (Again, not for merging) |
|
hey @cestella, @simonellistonball, see updated contributor notes. It's not ready for a official pull request, but this gives a good idea on the impact on the code for a working ES5.x implementation. |
|
@wardbekker Can you please merge master and deconflict? |
|
@JonZeolla done. |
|
Seems like this is failing on some un-related temporary test failures. Can we get Travis kicked, and see what's left to do on this? |
… transport client
|
As a note, this ticket is slightly impacted by the metaalerts backend ticket (#734). The alerts field in the various templates should be removed and the search queries for meta alerts updated according to https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-sort.html#_ignoring_unmapped_fields, in order to allow for searches against metaalerts without having to have an alert field in each template. |
|
This functionality was completed in #840. As mentioned in #840 this inspired much of that work. Is there anything else needed from this PR? If not, can you close this PR @wardbekker ? Thanks |
|
agreed @nickwallen |
Contributor Comments
This is a work-in-progress fix for Elasticsearch ES5 with Xshield client support. I'm opening a pull request to work through the remaining issues with the team. To be clear, the aim is discussion only for now, not for actually pulling in the code. @jasper-k verified the patch is working against a ES5.x Xpack enabled cluster.
Open issues in this pull request: