Skip to content

Upgrade Elasticsearch to 5.X #3787

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

Closed
wants to merge 9 commits into from
Closed

Conversation

xrmx
Copy link
Contributor

@xrmx xrmx commented Mar 13, 2018

This is a rebased and improved version of #3373. Tested with elastic search 5-alpine (ES 5.6.8) docker image. This has received limited testing but project and file search from the main search view and searching from inside the project page search works fine here.

@RichardLitt RichardLitt added Design Design or UX/UI related PR: work in progress Pull request is not ready for full review and removed Design Design or UX/UI related labels Mar 14, 2018
@xrmx
Copy link
Contributor Author

xrmx commented Mar 14, 2018

@RichardLitt from my point of view this is ready to review :)

@gaborbernat
Copy link
Contributor

Tested it myself with latest master, this on top of it with ES 5.6.8 and worked as expected.

@xrmx
Copy link
Contributor Author

xrmx commented Apr 10, 2018

Rebased to latest master and added tests courtesy of @paoloromolini

@xrmx xrmx force-pushed the elasticsearch5 branch 2 times, most recently from 4932508 to b9145ad Compare April 10, 2018 16:25
ericholscher and others added 5 commits April 17, 2018 10:17
As elasticsearch expects a long while we have an hash as string.
While at it remove references to _parent and _id as they are gone.
fields is now _source and filter should be inside the
query. aggs is the new facets and we can drop filtering on aggs
as they should be calculated on the query results so after filtering.
You got to start from somwhere
@xrmx
Copy link
Contributor Author

xrmx commented Apr 17, 2018

@berkerpeksag thanks for the review! updated branch

@xrmx
Copy link
Contributor Author

xrmx commented May 2, 2018

@ericholscher any chance you can take a look at this?

@ericholscher ericholscher self-assigned this May 3, 2018
'_source': source,
}
if parent:
doc['_parent'] = parent
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How the parent child relationship will be made?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was breaking in ES5 when I tested it. I think it will require a bit more thought when we move towards ES6, which is a fundamental change in how ES works, so it will require refactoring and thinking about architecture more.

@xrmx
Copy link
Contributor Author

xrmx commented Jun 7, 2018

@ericholscher you may want to close this too 😿 Still i think some of your preparatory changes can be cherry-picked and pushed separately.

@gaborbernat
Copy link
Contributor

So what will replace this? 😄

@xrmx
Copy link
Contributor Author

xrmx commented Jun 7, 2018

@gaborbernat #4183

@ericholscher
Copy link
Member

@xrmx agreed. I'm a little sad to not have this work be useful, but ES5->ES6 is a huge change in architecture, and I don't want to keep investing more time into the old code if we can use better abstractions and support ES6.

Thanks for the PR though! I'd love to have your help guiding Safwan & the GSOC work, so that we make sure it's useful for everyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants