-
Notifications
You must be signed in to change notification settings - Fork 793
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
Associations not bringing back results #33
Comments
Can you gist/pastie the full recreation with Curl commands (
|
@karmi - Not sure the best way to do that...is that provided in the gem |
@railsdevmatt Of course. I assume you've set aside enough time to study the resources such as https://github.com/elasticsearch/elasticsearch-rails/tree/master/elasticsearch-model#the-elasticsearch-client and https://github.com/elasticsearch/elasticsearch-ruby/tree/master/elasticsearch-transport#logging? |
@karmi - the only problem I see is that |
@railsdevmatt I'm getting more and more confused. Have you actually checked https://github.com/elasticsearch/elasticsearch-rails/tree/master/elasticsearch-model#the-elasticsearch-client, have you tried it? It will print to STDERR by default. The other link has a very specific advice on how to put the log/trace output into a file. |
@karmi - my bad. I misread that the settings needed to go in an initializer here is the curl
and here is the log
|
@karmi - just realized the import Discussion.import fixed the issue |
HI @karmi
I have the following relationship
We also have multiple indexes which you gave use a solution from #30
It appears we have it set up right
but searching for Apples or Oranges gives us no results.
The text was updated successfully, but these errors were encountered: