You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am thinking of using this library for my ES integration.
I am going to cluster my indexes as posts-{region} to scope them and search within those scopes.
ie
posts-americas -> would host and be searchable for Americas region
posts-europe -> similary just for europe posts
and then I could delete the whole index to get rid of sort of a dynamic region.
Looking at the documentation I see this
# You should configure each index which you maintain in Elasticsearch here.
# This configuration will be read by the `mix elasticsearch.build` task,
# described below.
indexes: %{
# This is the base name of the Elasticsearch index. Each index will be
# built with a timestamp included in the name, like "posts-5902341238".
# It will then be aliased to "posts" for easy querying.
posts: %{
First: is this possible from the usage of this library or would I have to modify the task itself?
Second: Would the following return an %MyApp.Post{} struct or a raw ES response with the meta-information about the results too?
Hi, I am thinking of using this library for my ES integration.
I am going to cluster my indexes as
posts-{region}
to scope them and search within those scopes.ie
and then I could delete the whole index to get rid of sort of a dynamic region.
Looking at the documentation I see this
First: is this possible from the usage of this library or would I have to modify the task itself?
Second: Would the following return an
%MyApp.Post{}
struct or a raw ES response with the meta-information about the results too?Thank you in advance for the library!
The text was updated successfully, but these errors were encountered: