Interesting. Will give it a shot!
Thanks for the help and have a great weekend.
-joel
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
UTC-4, Joel Potischman wrote:
Hi Boaz. I know this is an old thread but I can't find anything newer and
it seems very related to this issue.
Is there documentation anywhere on how to script installation of the
license initially? We have not yet run Marvel in production and we do not
allow
We have a license for Marvel and while the documentation just says to enter
it through the Marvel UI when prompted, we script 100% of our
infrastructure creation and deployments (Ansible). My goal is to be able to
start with a bare VM, run our deployment, and when the dust settles, our
Oh well. At least I now have a definitive answer. Thanks!
-joel
On Thursday, April 30, 2015 at 5:37:40 PM UTC-4, Mark Walkom wrote:
Unfortunately there isn't a way to do this, but I've raised a feature
request to get this added.
On 30 April 2015 at 23:39, Joel Potischman joel.po
You could use a boosting query
http://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-boosting-query.html,
or you could use a multi-match query
http://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-multi-match-query.html
and
add a boost directly to the
Hi Boaz. I know this is an old thread but I can't find anything newer and
it seems very related to this issue.
Is there documentation anywhere on how to script installation of the
license initially? We have not yet run Marvel in production and we do not
allow manual steps in our deployment
One thing you might want to consider is whether or not you need your index
to stay perfectly in synch with your database. If a topic is viewed 1000
times over the course of 2 minutes, is it important that Elasticsearch
update after every one? Maybe after each update you queue a reindexing, but
Hi Yogesh. I am not 100% sure of this, so if someone else posts a reply
that differs from mine you should probably go with theirs, but I think this
is correct behavior.
Unless there is another process demanding memory from the OS, there is no
harm whatsoever in having the JVM consume all
We currently monitor our app by having a monitoring tool (Pingdom) retrieve
a health page from our app that retrieves and displays the Elasticsearch
cluster info, e.g.
{
status: 200,
name: whatever,
cluster_name: whatever_dev,
version: {
number: 1.4.4,
/issues/7411
Thanks
Vineeth Mohan,
Elasticsearch consultant,
qbox.io ( Elasticsearch service provider http://qbox.io/)
On Sat, Mar 14, 2015 at 1:48 AM, Joel Potischman joel.po...@beatport.com
javascript: wrote:
I ran into the following today in Elasticsearch
I ran into the following today in Elasticsearch 1.4.4 and am trying to
determine if this is a bug in Elasticsearch or a bug in my understanding of
Elasticsearch. I'm more than willing to believe it is the latter. It should
be very reproducible with the commands I've pasted.
Let's say I have
.
Jörg
On Tue, Mar 3, 2015 at 2:26 AM, Joel Potischman joel.po...@beatport.com
javascript: wrote:
Thanks Jörg, that makes sense.
I've made that change and it works but I'm still struggling to have
scoring behave the way I want. I simplified the query in my original post
for clarity
words,
penalize all docs that match the condition some_flag=true.
Jörg
On Mon, Mar 2, 2015 at 7:03 PM, Joel Potischman joel.po...@beatport.com
javascript: wrote:
I have a query template that currently returns results exactly as
desired. I've been given a requirement to very slightly
I have a query template that currently returns results exactly as desired.
I've been given a requirement to very slightly downrank results that have
an optional boolean field set to True. The intent is to ensure that we
return everything that matches the query, but if multiple records match,
14 matches
Mail list logo
