Skip to content
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

Figure out what version of ES we can move to without needing to refactor stuff #9065

Closed
jtesser opened this issue May 9, 2016 · 2 comments
Closed

Comments

@jtesser
Copy link
Contributor

jtesser commented May 9, 2016

Don't do it lets look at the change log and upgrade path

https://www.elastic.co/support/eol

@jtesser jtesser added this to the 3.6 milestone May 9, 2016
@chrismccracken
Copy link
Contributor

Re: #9041, an argument could be made to get to a new ES version in order to use native mappings for ipv6 addrs. elastic/elasticsearch#17746

@maurizo maurizo self-assigned this Jun 20, 2016
maurizo added a commit to dotCMS/dotcms-libs that referenced this issue Jun 29, 2016
Includes ES 1.7.3 and Lucene 4.10.2
@maurizo
Copy link
Contributor

maurizo commented Jun 29, 2016

PR on core: #9288

@maurizo maurizo removed their assignment Jun 29, 2016
dsilvam added a commit that referenced this issue Jun 29, 2016
…e-1.7.3

#9065 support for ES 1.7.3 includes lucene 4.10.4
@dsilvam dsilvam added the Merged label Jun 29, 2016
@erickgonzalez erickgonzalez self-assigned this Jul 7, 2016
@erickgonzalez erickgonzalez removed their assignment Jul 8, 2016
@dsilvam dsilvam closed this as completed Jul 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants