-
Notifications
You must be signed in to change notification settings - Fork 802
The "refresh", and "index" options of Model.import don't work well together #506
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
ganta
added a commit
to ganta/elasticsearch-rails
that referenced
this issue
Apr 1, 2017
ganta
added a commit
to ganta/elasticsearch-rails
that referenced
this issue
Apr 9, 2017
estolfo
pushed a commit
that referenced
this issue
Sep 5, 2018
estolfo
pushed a commit
that referenced
this issue
Sep 5, 2018
Closing this as the pull request #692 was merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey,
tl;dr: in
Model.import
,self.refresh_index!
is called without specifying the index to refresh, which I think is an issue if you specify theindex
option.I have a rake task that goes something like...
If I run
rake map:reindex[map_index]
, then newmap_index
index will be created properly, and the maps will be imported in the right index, but the wrong index will be refreshed.alias_maps_development
being the actual index of my model (well, it's an alias).Is this behavior intended? Shouldn't
refresh
refresh the index that's being passed as an option? (lib/elasticsearch/model/importing.rb:130
)Thanks
The text was updated successfully, but these errors were encountered: