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

VIVO-1587: Elasticsearch integration with VIVO #3177

Open
chenejac opened this issue Sep 17, 2018 · 7 comments · May be fixed by vivo-project/Vitro#469, #4023 or vivo-project/vivo-es#1
Open

VIVO-1587: Elasticsearch integration with VIVO #3177

chenejac opened this issue Sep 17, 2018 · 7 comments · May be fixed by vivo-project/Vitro#469, #4023 or vivo-project/vivo-es#1

Comments

@chenejac
Copy link
Contributor

Don Elsborg (Migrated from VIVO-1587) said:

Get branch from Jim Blake that he used to demo Elasticsearch integration with VIVO

@chenejac
Copy link
Contributor Author

@chenejac
Copy link
Contributor Author

chenejac commented Sep 17, 2018

Jim Blake said:

With some notes here:

Notes

@chenejac
Copy link
Contributor Author

Don Elsborg said:

[~accountid:557058:28b712ac-b117-4c3a-9e3c-2d97851d8fe6] What version of Elastic did you test with? The version we're using for our Facetview project was 1.7.3

This doesn't support the keyword type which I see you use for the mapping. 

[~accountid:5bb229e412ef2d4bf3a2233d] would you mind commenting on what you thought might need to be changed to upgrade Facetview to a newer ES, such as 5 or ideally 6?

Meanwhile, I will install a Version 6.4.1 on our system to move forward with this.

@chenejac
Copy link
Contributor Author

Don Elsborg said:

Installed ES 6.4.1 and the mapping worked.

Followed above instructions. Copied the 11 elastic files into my v.1.9.3 vitro directory

Modified applicationSetup.n3

compiled, restarted vivo.

Noticed the index wasn't initially rebuilt, but as soon as I clicked the 'index' page, the log showed a rebuild starting.

Also noticed the vivo index was receiving content as the index was being rebuilt.  I didn't think this was the case with embedded SOLR.

@chenejac
Copy link
Contributor Author

Benjamin Gross said:

[~accountid:5e347720a834270cb0997fb6] unfortunately I didn't get very far with experimenting with ES5, but you can see an example of the type of changes that will be necessary for the mappings here: gneissone/connect-unavco-elasticsearch@6b4bcf6

@chenejac
Copy link
Contributor Author

Don Elsborg said:

Index rebuild timings are equivalent for SOLR vs Elastic.

30 minutes for 100872 documents.

@chenejac
Copy link
Contributor Author

Andrew Woods said:

Resolved with: vivo-project/Vitro@45ddb56

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment