-
Notifications
You must be signed in to change notification settings - Fork 802
Elasticsearch::Persistence index is overwritten by newly instantiated classes #385
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
Comments
@JonathanKolnik Hey, I see you've closed the issue -- how did you solve it? It looks like incorrect instructions or a bug in the library indeed. |
@karmi I chickened out and thought I hadn't explored it enough.
I think this might be related. Note, @gateway matches. When I use this example https://github.com/elastic/elasticsearch-rails/tree/master/elasticsearch-persistence#the-default-class I don't see the issue. |
@JonathanKolnik Yeah, I tried it briefly and I think it's a bug, labelling appropriately... |
+1 |
@karmi I started to look into this and I am not quite sure how you would want to proceed with this bug. The problem seems to stem from the gateway being made a class method: |
same issue as this one: #811 |
@MMartyn @JonathanKolnik @dimroc |
I'm closing this as 6.0.0 is released and it includes a fix for this. |
split_test_repository.rb
rails console
Is index a class variable? That seems weird. I don't understand why by instantiating repo_2, repo_1.index now points to repo_2's index
I followed this example https://github.com/elastic/elasticsearch-rails/blob/master/elasticsearch-persistence/README.md#a-custom-class
The text was updated successfully, but these errors were encountered: