What if you just change the Elasticsearch version in your setup
(attributes, role overrides, etc)? There is no patch/commit needed to
install 1.x versions with the cookbook. (There are just special cases where
overriding attributes doesn't work as expected.)
Is there anything printed to the
Hi,
what you're looking for is a proxy which can communicate with an OAuth
provider, with an OAuth provider (such as Google+ Sign-In, Sign in with
Twitter, etc), verify the cookies, and pass requests between the browser
and Elasticsearch. (See this
diagram:
There's an Elasticsearch User Group in Czech Republic (please register
here, http://www.meetup.com/Elasticsearch-User-Group-CZ/), also two of the
Elasticsearch employees (me and Honza Kral) are based in Prague. You can
meet us frequently at Ruby and Python meetups and other developer events.
So, are you actually passing the `c` URL parameter to the search method?
Notice the code: `if options[:categories]` in your search method.
But you don't seem to be passing just `params[:query]` in your controller:
Company.search
params[:query]
Karel
What I mean by facets aren't working, that
I'm getting results but facets aren't working
Can you specify in a bit more detail how facet's aren't working (i.e.
what do you want to achieve, what is expected, etc)? Since you base your
code on the provided Rails templates, the code should be easily
translatable to your use case.
This is actually a change in Lucene -- previously, the long term was
silently dropped, now it raises an exception, see Lucene
ticket https://issues.apache.org/jira/browse/LUCENE-5710
You might want to add a `length` filter to your analyzer
Can you try using an AWS key with full permissions to your account? I don't
know if somebody has a concrete list of permissions to use here, it
definitely needs also permissions for listing volumes, etc. It also applies
to using IAM roles -- I've never sucessfully discovered which concrete
With the first command, you *update* the mapping for an existing index --
when that index doesn't exist, you'll get, predictably, an
error: {error:IndexMissingException[[twitter] missing],status:404}
With the second, command, you're creating an index called twitter (hence
PUT with name, as per
The `elasticsearch-ruby` library is what we call a low level client,
closely matching the semantics and notation of the REST API.
So, you pass in exactly the same query as you would into Curl. The only
exception here are e.g. names of document types, which are part of the URL,
and are
I use the 1.0.0.RC1 this is what I get. ES still not working. What is
missing? I installed elasticsearch-cloud-aws.
I would double check, that you're using the matching versions of
Elasticsearch and the Cloud AWS plugin. Check the files actually installed,
you should see
Okproblem solvedwas not discovery., I was the attachment of the
volume. This brings up another issue.why did I not get an error?
What do you mean by attachment of the volume? The volume was not attached,
was attached somewhere else, there was a permissions problem? When
The EC2 plugin doesn't mess with networking settings, so the behaviour
you're describing is weird.
After ES starts, can you connect to it via `curl localhost:9200`?
Also, don't use the now deprecated S3 gateway, apart maybe from strictly
testing purposes -- it's unsupported and unpredictable.
12 matches
Mail list logo
