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

[WIP] Elasticsearch upgrade #398

Closed
wants to merge 47 commits into
base: master
from

Conversation

Projects
None yet
3 participants
@oalders
Copy link
Member

oalders commented Mar 13, 2015

Making a PR so that review is a touch easier. Nicht mergen!

To use this branch you can do something like:

cd metacpan-api
git clone git@github.com:CPAN-API/p5-elasticsearch-model.git
cd lib
ln -s ../p5-elasticsearch-model/lib/ElasticSearchX .

Not the most elegant way to do things, but it works and it'll be available when you run ./bin/prove without requiring any additional flags. Make sure you do a carton install or vagrant provision after pulling in the changes.

In order to run this on your VM:

cd metacpan-puppet
git fetch
git co -b oalders/elasticsearch-upgrade origin/oalders/elasticsearch-upgrade
vagrant provision

To run the tests on your VM you'll (temporarily) need to use the "live" Elasticsearch instance. Keep in mind that doing this will blow away anything you may have previously indexed. We're still working on a fix for this.

vagrant ssh
cd metacpan-api
METACPAN_ES_TEST_PORT=9200 ./bin/prove

@oalders oalders force-pushed the andreeap/elasticsearch-upgrade branch from 6338ed7 to 98e79f3 Mar 13, 2015

@oalders oalders referenced this pull request Mar 13, 2015

Merged

[WIP]Elasticsearch Upgrade #393

@oalders oalders force-pushed the master branch from 31c1ae9 to 289dfa4 Mar 16, 2015

@andreeap

This comment has been minimized.

Copy link
Contributor

andreeap commented Mar 16, 2015

I was on the wrong repository and merged by accident this into the master, but I reverted the merge.

@oalders

This comment has been minimized.

Copy link
Member

oalders commented Mar 16, 2015

I've fixed it now. Don't click any more merge buttons or push to master. :) You'll need to delete your master and grab the current version as your history is out of sync.

@andreeap

This comment has been minimized.

Copy link
Contributor

andreeap commented Mar 16, 2015

Thank you, I was extremely scared for what I have done.

@rwstauner rwstauner force-pushed the master branch from 289dfa4 to be4d4d8 Mar 16, 2015

@oalders

This comment has been minimized.

Copy link
Member

oalders commented Apr 17, 2015

This has mostly been moved to #405

@ranguard ranguard added this to the Elasticsearch upgrade 1.5 milestone May 18, 2015

@oalders oalders closed this Jun 30, 2015

@ranguard ranguard deleted the andreeap/elasticsearch-upgrade branch Nov 22, 2016

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