go-elastic | Elasticsearch client with AWS sigv4 support | AWS library

It looks like you're using wrong endpoint for suggestions. Correct name is suggest.

Example: http://127.0.0.1:8000/search/publishers/suggest/?country_suggest__completion=Ar

Corresponding viewsets

As of your question about using two fields for suggestion at once, it's possible to get suggestions for multiple fields at once. For instance, if you have title and author, both properly indexed and configured, you could query it as follows:

http://127.0.0.1:8000/search/books/suggest/?title_suggest=wa&author_suggest=le

This will, however, return you the following result:

The problem was in my suggester configurations. First of all for term and phrase suggest we do not need completion fields (i.e. 'suggest': fields.CompletionField()) and we just need to declare our field in our Index, something like:

The StaticFiles as well as the tutorial linked are for Amazon Linux 1 (AL1). However, the current versions of EB use Amazon Linux 2 (AL2). AL2 is likely what you are using now.

In AL2, such option is invalid and new options for static files should be used as shown here and here.

Please not that the tutorial is for AL1, and other things may also not work. There are many differences between AL1 and AL2.

The Elasticsearch response which you've posted as JSON seems to not entirely correct (few brackets are missing and bad indentation) I've made an edit though, so no need to worry.

Coming to loop issue, this how your for-loop should like:

Based on the discussion in the comments, it was found that that the issue was caused by the fact eb was deploying an old version from git, rather then the local, corrected version of the application.

The solution was to push the changes to git so that new version get deployed.

You can add the fields in the Document class explicitly. Like following

Instead of defer wg.Wait, use wg.Wait at the end of the for-loop. You are using the data constructed by the goroutines in the for-loop right after for-loop completes, and you're not waiting for all the goroutines to complete before you use that data.

When you use defer wg.Wait, waiting happens at the end of the function. The for-loop using the data operates on incomplete data because the goroutines are still running.

When you use wg.Wait at the end of the for-loop, you first wait for all the goroutines to end, and then use the data generated by them.

I know this is late. But, I thought I should answer my own question, so that anyone face the same problem, can figure it out.

I created another App for Elastic search component.Yes, I created another App under the same project. And I followed this tutorial https://pypi.org/project/django-elasticsearch-dsl/ Then I called Elasticsearch view functions at views.py from the website App. It works perfectly now.

I am not a expert in Django or Elastic Search. So, I can not explain why it is not working as the previous attempt. I hope this helps to anyone who comes to this kind of situation.

I got the answer of my problem.

I set the RDS policy and create new custom_wsgi.config file on .ebextensions directory and write command :