-
Notifications
You must be signed in to change notification settings - Fork 41
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
Changes required to install Elasticsearch 6 on staging #6421
Merged
Merged
Changes from 1 commit
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
56c8188
update elasticsearch version on public.yml on staging
AmitPhulera 6015334
add task to download es 6
AmitPhulera 8d371ff
create misc settings for es6
AmitPhulera f493e31
include es5 related changes in main task
AmitPhulera 05a2c0d
update es config file and service file
AmitPhulera 88141e9
update elasticsearch_major_version to get right es client on staging
AmitPhulera a491b1b
update config file based on docs
AmitPhulera eb11aa5
fix jvm options thats were misconfigured
AmitPhulera fda8d7f
DRY up es version based config
AmitPhulera 086eba4
fix typo
AmitPhulera 56def3d
cleanup es 2 related settings
AmitPhulera a939217
fix download hash for es
AmitPhulera 6acafad
don't use deprecated syntax to check checksum
AmitPhulera 9621345
remove path.conf from setting
AmitPhulera f9a79f7
also create tmp dir
AmitPhulera 98c2f9d
check if es directories exist and then create the one which are not p…
AmitPhulera 01b369c
Merge remote-tracking branch 'origin/master' into ap/es6-install
AmitPhulera 390dc72
Merge branch 'master' into ap/es6-install
AmitPhulera 9f6f712
Merge branch 'master' into ap/es6-install
AmitPhulera File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Just going off of this, these settings seemed to also apply to ES5 and therefore aren't strictly an ES2 setting? Are they still safe to remove?
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.
Yes this is safe to remove and is intentionally removed. This was there to in ES 5 to support if someone was using groovy scripts which are deprecated.
If someone installs commcare now they will not need es5 with groovy scripts so it is safe to remove for ES5 as well.