and I cant' use the _all field because of own scoring.
--
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 elasticsearch+unsubscr...@googlegroups.com.
To view this
Thank you - I thought may be there is another type like object-type which
would provide it.
Actually it should be a type like the array-type but with fields you could
analyse separately.
There would be different analysers for each language (especially because of
stemming).
--
You received
OK - I thought I could leave all my queries and add an additional filter if
the item is available in that language.
I'll watch your talk!
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails
ah wow - that's cool. I just came across your
http://jprante.github.io/lessons/2012/05/11/ISBN-search-with-Elasticsearch.html
which explains it in detail.
That's pretty close to what I want but I just found a new problem: There
should be a highlighting of the found results - so I guess I'll
:{}}
And the cluster has not been initialized
The following is also added to the log:
[WARN ][action.admin.cluster.settings] [elasticsearch-1] ignoring transient
setting [discovery.zen.ping.unicast.hosts], not dynamically updateable
Any help would be appreciated
Cheers
Martin Harris
--
You received
Thanks Itamar,
The tribe setup might work, but it may be easier if I can (at runtime)
simply give elasticsearch a new IP address to add to the cluster - this
will be accessible on port 9300 so the communication will not be over HTTP.
Is there any way to do this?
Cheers
Martin
On 2 June 2014
We recently upgraded three elasticsearch clusters from 0.20.2 to 1.1.1 in
one big step.
We did it without any downtime by setting up parallel clusters running
1.1.1. Since our data is changing all the time we created the parallel
clusters by first adding machines and shards to the existing
But be aware that there is a bug in Elasticsearch which can cause the
transport client to get the NoNodeAvailable exception of sniff is set to
false. It doesn't seem to have been the issue in this case but I thought I
should mention it.
--
You received this message because you are subscribed
I've tested it with ES 1.1 and the described behaviour is gone. So the Java
API does a correct interpretation of the JSON search result.
On Thursday, January 30, 2014 11:23:04 PM UTC+1, Martin Pape wrote:
Thanks for the information. I still have some months till production, so
might
)
The idea being that documents could be relatively big, and they should not
be indexed multiple times.
Does that make sense? Am I missing the right way to design such a
pattern? I am new to ES.
Thanks,
Martin
--
You received this message because you are subscribed to the Google Groups
I have also encountered this, did the debugging and created an issue:
https://github.com/elasticsearch/elasticsearch/issues/6325
--
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,
MB RAM free. That should be enough, should it not?
*elasticsearch.yml*
cluster.name: elasticsearch_martins
path.data: /usr/local/var/elasticsearch/
path.logs: /usr/local/var/log/elasticsearch/
path.plugins: /usr/local/var/lib/elasticsearch/plugins
network.host: 127.0.0.1
Cheers,
Martin
,
min_doc_count : 1
}
}
}
}'
I don't see how I can combine the documents to aggregate on to/from
combination.
Is this possible?
Thanks for any help,
Martin
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from
The Java API is said to have better performance (and I believe that). The
drawbacks are that you must use the exact same version of the java API
library on the client as the server runs, as well as the same version of
Java. So upgrades suck.
--
You received this message because you are
,
index_analyzer : ngram,
search_analyzer : ngram_search,
include_in_all : false
}
}
}
}
}
}
}
Cheers,
Martin Stabenfeldt
--
You received this message because you are subscribed to the Google Groups
elasticsearch
On Thu, Apr 3, 2014 at 11:49 PM, Binh Ly binhly...@yahoo.com wrote:
You should be able to do a multi-sort, like:
{
sort: [
{ your_geo_sort },
{ created_at: {} }
]
}
Perfect, thanks! :-)
--
Martin Stabenfeldt
--
You received this message because you are subscribed
If you use the Java client you probably also have to tell it to not sniff
out the other nodes in the cluster.
--
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
: {
filter : {
term : { state : active}
}
}
},
sort: [
{
created_at: {
order: asc
}
}
]
}
Cheers,
Martin
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group
Got it working! :-)
GET _search
{
query: {
match_all: {}
},
filter : {
term : { state : active}
},
sort: [
{
created_at: {
order: desc
}
}
]
}
On Friday, April 11, 2014 10:50:45 AM UTC+2, Martin Stabenfeldt wrote:
Hi,
I'm trying
On Tuesday, April 29, 2014 8:59:35 AM UTC+2, Mark Walkom wrote:
Yep, you can do this using
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html
Thanks, that's exactly what I was looking for.
/MaF
--
You received this message because you
On some further debugging I enabled debug logging on one of the nodes. Now
when I try to get the indices stats I get the following in the log on the
debugging node:
[2013-12-18 08:02:01,078][DEBUG][index.shard.service ] [NODE6]
[reference][10] Can not build 'completion stats' from engine
Hi,
I've decommissioned a node by it's IP.
curl -XPUT localhost:9200/_cluster/settings -d '{
transient : {
cluster.routing.allocation.exclude._ip : 10.0.0.1
}
}'
How can I remove that setting?
I tried the same command but as a DELETE request. Didn't work. :(
Cheers,
Martin
result. I just
wanted to stay inside the API and not
start to interpret the json of the search result myself. But if it has to
be...
BR - Martin
On Thursday, January 30, 2014 6:01:38 PM UTC+1, David Pilato wrote:
I guess you did not ask for specific fields in your query so only _source
* | *Technical Advocate* | *Elasticsearch.com*
@dadoonet https://twitter.com/dadoonet |
@elasticsearchfrhttps://twitter.com/elasticsearchfr
Le 30 janvier 2014 at 15:44:18, Martin Stabenfeldt (mar...@stabenfeldt.net)
a écrit:
Hi,
I've decommissioned a node by it's IP.
curl -XPUT localhost:9200
Hi Chris,
I'm in the same boat; looking to combine an or filter (so 1 or the other
filter matches) with a custom_filters_score in order to boost results which
meet a certain criteria.
Did you have any luck solving this?
On Friday, 3 May 2013 15:26:52 UTC+10, Chris wrote:
Of course, posting
to get the scoring filters to do the record filtering, which they don't.
On Thu, Feb 27, 2014 at 12:11 AM, James Martin jam...@gmail.com wrote:
Hi Chris,
I'm in the same boat; looking to combine an or filter (so 1 or the other
filter matches) with a custom_filters_score in order to boost
Thank you very much for answer.
I think that elasticsearch-jetty plugin handles only http request, am I
right? (REST API requests)
I have alrery disable http by *http.enabled: false* option and I want to
secure comunication amog the nodes.
For access to the cluster I use JAVA API. For me it´s
Hello,
We are running an es-cluster with 13 nodes, 10 data and 3 master, on Amazon
hi1.4xlarge machines. The cluster contains almost 10T of data (including
one replica). It is running Elasticsearch 1.1.1 on Oracle java 1.7.0_25.
Our problem is that every now and then the cpu load suddenly
Hi,
just wanted to announce a tiny project: estab, which helps to export
document fields as tab separated values (TSV). It's nothing curl + jq[1]
couldn't do, it's just a bit simpler to use. Hope you like it.
* https://github.com/miku/estab
Best,
Martin
[1] http://stedolan.github.io/jq
Hi Jörg,
Thanks, didn't know about that plugin! I installed it on Elasticsearch
1.3.2, it registers fine, but the URL is not available; maybe I am doing[1]
it wrong?
Cheers,
Martin
[1] https://gist.github.com/miku/da3e1641174c38a7a4ce
On Friday, 22 August 2014 14:38:44 UTC+2, Jörg Prante
Thanks for the quick fix, it works now. Just a minor issue with nested
field values (e.g. institution.address.street or the like), but I'll
probably open a issue on GH for that.
Cheers,
Martin
On Friday, 22 August 2014 17:46:30 UTC+2, Jörg Prante wrote:
My fault. I forgot to push out
I see the same problem. We are running 1.1.1 on a 13-node cluster (3 master
and 5+5 data). I see stuck threads on most of the data nodes, I had a look
around on one of them. Top in thread mode shows:
top - 08:08:20 up 62 days, 18:49, 1 user, load average: 9.18, 13.21, 12.67
Threads: 528 total,
I did report it https://github.com/elasticsearch/elasticsearch/issues/7478
--
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
FYI, this turned out to be a real bug. A fix has been committed and will be
included in the next release.
On Wednesday, August 27, 2014 11:36:03 AM UTC+2, Martin Forssen wrote:
I did report it https://github.com/elasticsearch/elasticsearch/issues/7478
--
You received this message because
does not create a
compile error...
How can I make this work? :O
best regards,
Martin
--
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 elasticsearch+unsubscr
Hello,
I wonder if it is possible to put a limit on the from parameter in
pagination requests. For example refuse any paginating searches where the
from is above X? This would be good to protect clusters which otherwise are
easy to bring down.
--
You received this message because you are
Hi,
I can't figure out why Elasticsearch still can't be reached from the public
ip of the ec2 instance. This is my config file
cloud.aws.access_key: AKIAXPWEW2A
cloud.aws.secret_key: EvU0I5Xx+b+FlRXXXSSDFfM2Z
plugin.mandatory: cloud-aws
cluster.name: escluster
node.name:
me.
*There will be no re-lo provided and no sponsorship at this time.
Traci Martin
512-640-3656
tmar...@intersysconsulting.com
*Data Engineer*
*Who we are: *
*Intersys Consulting* is a leading Business Intelligence, Data Management,
and Application Development professional services
/guide/en/elasticsearch/guide/current/using-stopwords.html
And there is no error or warning telling me that my stopwords:
[www, fr, com]
line got ignored.
Gist :
script
src=https://gist.github.com/Alix-Martin/7186e38459e88a474e13.js;/script
Alix Martin
--
You received this message
Gist link is https://gist.github.com/Alix-Martin/7186e38459e88a474e13
--
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 elasticsearch+unsubscr...@googlegroups.com
have
had the pleasure of working with.
It is a permanent position offering great benefits, a laid back atmosphere,
and very competitive salary with options. If you are interested please feel
free to contact me.
*There will be no re-lo provided and no sponsorship at this time.
Traci Martin
I've a this mapping for indexing GeoJSON MultiPolygons:
{
mappings: {
my_type : {
properties : {
geometry: {
type: object,
properties: {
coordinates: {
type: geo_shape,
tree: quadtree,
precision: 1m
Can I use Newtonsoft.Json 4.5.0.0 instead of 6.0.0.0 with NEST?
How?
Thanks for your advice.
Martin
--
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
.
On Wednesday, February 11, 2015 at 11:38:19 AM UTC+1, Martin Widmer wrote:
Can I use Newtonsoft.Json 4.5.0.0 instead of 6.0.0.0 with NEST?
How?
Thanks for your advice.
Martin
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe
Hello,
I'm experimenting with snapshots to S3, but I'm having no luck. The cluster
consists of 8 nodes (i2.2xlarge). The index I'm trying to snapshot is
2.91T, has 16 shards and 1 replica. I shoudl perhaps also mention that this
is running Elasticsearch version 1.1.1.
Initially when I
We just encountered some mysterious problems when upgrading from 1.1.1 to
1.5.0.
The cluster consists of three machines, two data nodes and one master-only
node. It hosts 86 indices which each has one replica.
I stopped writes, did a snapshot and stopped the entire cluster before I
upgraded
}
}
}
}
}'
If we populate new documents, then the exists filter works just fine.
Regards,
Mads Martin
--
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 elasticsearch
They're similar. The 1.5.0 cluster has created : 1000199, and the 1.4.1
cluster also has created : 1000199
On Wednesday, March 25, 2015 at 4:45:30 PM UTC+1, Igor Motov wrote:
Hi Mads Martin,
Could you check the version that is returned when you run curl
localhost:9200/my_own_index
Thanks for fixing!
On Thursday, March 26, 2015 at 3:29:17 PM UTC+1, Igor Motov wrote:
Thanks for checking. It's a bug, which should be fixed in 1.5.1
https://github.com/elastic/elasticsearch/pull/10268
On Wednesday, 25 March 2015 13:43:28 UTC-4, Mads Martin Jørgensen wrote:
They're
49 matches
Mail list logo
