Re: Advice for implementing a secure graph index with ElasticSearch
And i also want to ask you, are you from altamira? i found you on lumify. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e8f576c8-5d3f-4402-915d-8d0e9eaf8c10%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Is it possible to get the name of the field above an element?
You currently can only get all of the original document (minus the
excludes) when using inner/nested documents. There is currently an open
issue, but I do not think there has been any progress until the search
refactor is completed:
https://github.com/elasticsearch/elasticsearch/issues/3022 (no need for
more +1s, the team knows about the issue)
--
Ivan
On Thu, May 15, 2014 at 7:54 AM, maximilian.brod...@googlemail.com wrote:
Additional:
At the beginning I had all entries in an array. But By searching for the
strings I got also back the wohle array.
The document looks in this way:
{
project :
[
{
title : A,
id : 1234,
fulltext : Some Text
},
{
title: Believe,
id: 5678,
fulltext: inside the fied
},
{
title: imagination,
id: 9,
fulltext: makes trouble
}
]
}
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/0e2a1f79-712b-4012-ab95-0eac36f70399%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/0e2a1f79-712b-4012-ab95-0eac36f70399%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBvJAYTdGTAKSq9FMHKiUphO9-hCotd%3DvUAR-dEfx9B2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
unassigned primary shards
Good morning: We had to restart our elasticsearch cluster v0.90.5 and 3 primary shards have been 2 days trying unsuccessfully assigned. Is there any solution to recover without having to refresh the index? Regards -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/ca1dc3fb-15fb-4563-94e6-bf8303ac635b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: running out of memory indexing on linux
Are you using the SUN jvm 1.7 or above? I had similar issues with standard Linux openJDk. Hi, Alberto Paro Inviato da iPad Il giorno 15/mag/2014, alle ore 17:28, Vince Wadhwani vinc...@gmail.com ha scritto: I recently switched from a mac to using debian linux. Same data set, indexing method, and elastic version. On OS X I can index my records (about 1 million) but on linux I can see memory usage increasing over time until I finally run out and the process is killed. I've got 8GB of RAM and 16GB of Swap but I still can't get through the records I could with half that RAM on OSX. Is there a config option somewhere I can toggle? (I've already tried enabling bootstrap.mlockall: true) Or is there something else going on? -Vince -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e0268477-5cc2-49a9-ad95-f90960884578%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/AA2390DC-7AD0-4D50-8B3F-73000459F999%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Coukd someone have this link backup? Elasticsearch-Storage-Optimization
Coukd someone have this link backup? https://github.com/logstash/logstash/wiki/Elasticsearch-Storage-Optimizationhttps://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Flogstash%2Flogstash%2Fwiki%2FElasticsearch-Storage-Optimizationsa=Dsntz=1usg=AFQjCNFI5g4_kE6yBQ57LBMR8JI3QWJmgw -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/afb5ddea-ae79-4b22-b20f-e6dfd3a9a687%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Coukd someone have this link backup? Elasticsearch-Storage-Optimization
What are you trying/wanting to do? If you want the Logstash team to re-instate it you can try raising a Jira or posting to the logstash mailing list :) Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: ma...@campaignmonitor.com web: www.campaignmonitor.com On 16 May 2014 18:02, hengyunabc chen hengyun...@gmail.com wrote: Coukd someone have this link backup? https://github.com/logstash/ logstash/wiki/Elasticsearch-Storage-Optimizationhttps://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Flogstash%2Flogstash%2Fwiki%2FElasticsearch-Storage-Optimizationsa=Dsntz=1usg=AFQjCNFI5g4_kE6yBQ57LBMR8JI3QWJmgw -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/afb5ddea-ae79-4b22-b20f-e6dfd3a9a687%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/afb5ddea-ae79-4b22-b20f-e6dfd3a9a687%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624Zo4FQFhn9z_-qY9T4Qecpbb50mP%2BeegZSQND6MobZoTw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Disk-based shard allocation per node settings
It's a cluster level setting, so all nodes use the same one. As far as I know, there is no node level setting. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: ma...@campaignmonitor.com web: www.campaignmonitor.com On 16 May 2014 17:43, Michel Conrad michel.con...@trendiction.com wrote: Is it possible to specify different thresholds for different nodes in the cluster? I could not find it in the documentation, when updating the setting through the cluster settings as described on http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html#disk the threshold is applied to every node. When specifing the thresholds through the configuration file, will it then be only applied to the node reading the configuration? In this case how to I prevent the cluster settings being applied and overwriting the configuration file (remove a setting). Thanks for any thoughts, Michel -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAH0sEYgM4%3DmH2cA3wJoBQAmx82ddrz6N%3D8u3XE0EFoKoOwTUUQ%40mail.gmail.com . For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624a6tk9jqGkh_ED%3Dx_bpJPxpiydP9_KxTugrBVZuX5yaCw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
How can I find out which date/number field matched?
If the user does a complex search (lots of ORs and ANDs in their query), it's useful to be able to show them results, highlighting the bits in each one that matched. The highlighting feature does this fine for string fields, but it does not appear to work for dates and numbers. Is there any way of finding out which fields matched? Thanks, Tim. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e0b19706-1c43-4ddd-89bc-5c9e06c3508d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Coukd someone have this link backup? Elasticsearch-Storage-Optimization
Sorry, I thought they merged. 在 2014年5月16日星期五UTC+8下午4时35分08秒，Mark Walkom写道： What are you trying/wanting to do? If you want the Logstash team to re-instate it you can try raising a Jira or posting to the logstash mailing list :) Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: ma...@campaignmonitor.com javascript: web: www.campaignmonitor.com On 16 May 2014 18:02, hengyunabc chen hengy...@gmail.com javascript:wrote: Coukd someone have this link backup? https://github.com/logstash/ logstash/wiki/Elasticsearch-Storage-Optimizationhttps://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Flogstash%2Flogstash%2Fwiki%2FElasticsearch-Storage-Optimizationsa=Dsntz=1usg=AFQjCNFI5g4_kE6yBQ57LBMR8JI3QWJmgw -- 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 elasticsearc...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/afb5ddea-ae79-4b22-b20f-e6dfd3a9a687%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/afb5ddea-ae79-4b22-b20f-e6dfd3a9a687%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f195ac1d-af90-4441-8d61-d2c2f9fa91e9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Coukd someone have this link backup? Elasticsearch-Storage-Optimization
They are under the Elasticsearch banner but they are they are still handled by their original dev teams. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: ma...@campaignmonitor.com web: www.campaignmonitor.com On 16 May 2014 18:41, hengyunabc chen hengyun...@gmail.com wrote: Sorry, I thought they merged. 在 2014年5月16日星期五UTC+8下午4时35分08秒，Mark Walkom写道： What are you trying/wanting to do? If you want the Logstash team to re-instate it you can try raising a Jira or posting to the logstash mailing list :) Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: ma...@campaignmonitor.com web: www.campaignmonitor.com On 16 May 2014 18:02, hengyunabc chen hengy...@gmail.com wrote: Coukd someone have this link backup? https://github.com/logstash/ logstash/wiki/Elasticsearch-Storage-Optimizationhttps://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Flogstash%2Flogstash%2Fwiki%2FElasticsearch-Storage-Optimizationsa=Dsntz=1usg=AFQjCNFI5g4_kE6yBQ57LBMR8JI3QWJmgw -- 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 elasticsearc...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/elasticsearch/afb5ddea-ae79-4b22-b20f-e6dfd3a9a687% 40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/afb5ddea-ae79-4b22-b20f-e6dfd3a9a687%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f195ac1d-af90-4441-8d61-d2c2f9fa91e9%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/f195ac1d-af90-4441-8d61-d2c2f9fa91e9%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624Y725083NqBHE_zq1-vroKHR92gprrGBC4v0dRrz5BsGQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [hadoop] Extra Documents in Elastic Search
Hi,
I strongly recommend using the latest release (es-hadoop 2.0 RC1) which
handles document rejections (which can and will happen when ES is
overloaded). Simply replace the jar and start adding more tasks until you
get the desired performance. Know that es-hadoop also records stats about
the job (docs rejected, sent, accepted, etc...) which are displayed at the
end of the job so you can use that information as well to double-check the
number of docs added.
Cheers,
On Thu, May 15, 2014 at 10:37 PM, Napoleon T. napoleon...@gmail.com wrote:
I did not entirely solve this issue. But it looks like ES is dropping some
requests when it's overloaded. As my hadoop cluster can handle 42 mappers,
I had 42 tasks trying to send write requests to only 1 ES node (I believe
all the requests only go to one node is ES). Most of the time, many tasks
will fail and my hadoop job will fail. But sometimes, hadoop returns a
success and not all the data has been successfully written.
Reducing the number of mappers should have helped, but for some reasons
running pig with the property -Dmapred.tasktracker.map.tasks.maximum=1 did
not do the trick.
Limiting the number of mappers directly in the cluster conf files seems to
have solved the problem.
On Wednesday, April 23, 2014 4:15:19 PM UTC-5, Napoleon T. wrote:
Hi,
I'm trying to store a lot of documents into ES using pig. The pig job
ends successfully but I end up with more documents in Elasticsearch than
the number of rows in my input.
My pig script is 3 lines:
REGISTER 'local/path/to/m2.jar'
data = load 'path/to/hdfs/file.tsv' as (field1: chararray, field2: long,
field3: long, field4: long)
store data into 'index/type' using org.elasticsearch.hadoop.pig.
EsStorage('es.nodes=node2.domain.com', 'es.rersource=index/type');
I have speculative execution disabled for map and reduce when running
this pig script.
Hadoop states that 54,723,557 records were written (console output and
job tracker UI).
ES head plugin claims that I have docs: 57,344,987 (57,344,987).
My environment:
hadoop: 1.2.1 with 6 nodes cluster
elasticsearch: 1.0.0. 6 node cluster. Different than hadoop nodes.
elasticsearch-hadoop version M2.
Pig version: 0.12.0
Any ideas of what is going on here?
Thanks.
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/b819e576-f0ef-41d4-854a-63bab811951a%40googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAJogdmc5NOAmsjhVca2c%2B%3D5pCdHPPfyZPDPgagD5PWM3%3Da09Pg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
panels blank out with newly released kibana 3.1.0
panels are not showing when i look at dashboards with the new kibana release. it all works fine when i open the dashboard as a file, but not when i point the browser to the url... anyone else? any likely cause? https://lh4.googleusercontent.com/-vFnyX4IdIK4/U3XeOHqSM0I/AAc/Shyz78ins20/s1600/guided+dashboard+from+url.png https://lh5.googleusercontent.com/-jeGtBfbPhFo/U3Xdq02Ej-I/AAU/BVo755XDvAI/s1600/guided+dashboard+from+file.png -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/16349b24-07a8-4f75-b1c7-51fd004a92b4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Official .NET client
Hi Paige, Sorry for the late reply. Many thanks about it, I will have a look at Elasticsearch.Net (I already had a look at NEST some month ago, but it wasn't all I need) and see if it can help me :) Regards, Loïc Le vendredi 9 mai 2014 04:06:47 UTC+2, Paige Cook a écrit : Elasticsearch.Net and NEST are the official .NET Clients for Elasticsearch. You can read about them in the recent blog post - introducing elasticsearch.net and nest 1.0.0-beta1http://www.elasticsearch.org/blog/introducing-elasticsearch-net-nest-1-0-0-beta1/ Both aggregations and integrated failover are supported in Elasticsearch.Net and NEST. On Tuesday, May 6, 2014 5:51:25 AM UTC-4, Loïc Wenkin wrote: Hello everybody, I watched a video 2 or 3 months ago (Facebook and Elasticsearch), and in this video, it was said that it was planned to develop an official .NET client. Do you have some news about it ? Is there a roadmap (or at least, an idea about a release date (2014, 2015 ...)) for this client ? Currently, I am using PlainElastic.Net which is a great client (I like the idea to work with strings directly accessible to user, allowing us to easily debug queries), but some features are missing (I think to aggregations, for example, or a kind of integrated failover system). Any news about it would be appreciated :) Regards, Loïc -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d65bad34-b911-433a-bd67-37f1d623222c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: ElasticSearch not seen in JPS
Fixed, permission issue in /tmp
Regards,
Greg
On Thursday, May 15, 2014 5:41:41 PM UTC+2, Greg Bui wrote:
Hello,
I encounter a weird problem, jps is not returning elasticsearch whereas it
is running and (seems) working fine. I remember that was the case before.
jstat is not working as well...
# jps
243157 jruby-complete-1.7.11.jar
50184 Jps
# ps aux | grep elasti
494 48931 54.3 13.0 383893516 4303840 ? Sl 17:29 3:07
/usr/java/default/bin/java -Xms16g -Xmx16g -Xss256k
-Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
-XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly
-XX:+HeapDumpOnOutOfMemoryError -XX:MaxPermSize=256m -Delasticsearch
-Des.pidfile=/var/run/elasticsearch/elasticsearch.pid
-Des.path.home=/usr/share/elasticsearch -cp
:/usr/share/elasticsearch/lib/elasticsearch-1.1.1.jar:/usr/share/elasticsearch/lib/*:/usr/share/elasticsearch/lib/sigar/*
-Des.default.path.home=/usr/share/elasticsearch
-Des.default.path.logs=/var/log/elasticsearch -Des.default.path.data=/data
-Des.default.path.work=/tmp/elasticsearch
-Des.default.path.conf=/etc/elasticsearch
org.elasticsearch.bootstrap.Elasticsearch
# jstat -gc 48931
48931 not found
jmap -heap PID is working though.
Any ideas how to fix this ? I'm using JPS for one of my monitoring probe.
I'm using CentOS 6.5 with ES 1.1.1 from RPM and java 1.7
# java -version
java version 1.7.0_55
Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.55-b03, mixed mode)
$ curl http://localhost:9200/
{
status : 200,
name : logstash_master,
version : {
number : 1.1.1,
build_hash : f1585f096d3f3985e73456debdc1a0745f512bbc,
build_timestamp : 2014-04-16T14:27:12Z,
build_snapshot : false,
lucene_version : 4.7
},
tagline : You Know, for Search
}
Thanks a lot in advance,
Greg
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a27f4dd9-d2a6-4c5f-9c15-e1f9b0f2aee4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: panels blank out with newly released kibana 3.1.0
Well... just needed to clear the browser caches as proposedhttps://github.com/elasticsearch/kibana/issues/533#issuecomment-25254331byRashid Khan . On Friday, May 16, 2014 11:46:04 AM UTC+2, oz.sh...@gmail.com wrote: panels are not showing when i look at dashboards with the new kibana release. it all works fine when i open the dashboard as a file, but not when i point the browser to the url... anyone else? any likely cause? https://lh4.googleusercontent.com/-vFnyX4IdIK4/U3XeOHqSM0I/AAc/Shyz78ins20/s1600/guided+dashboard+from+url.png https://lh5.googleusercontent.com/-jeGtBfbPhFo/U3Xdq02Ej-I/AAU/BVo755XDvAI/s1600/guided+dashboard+from+file.png -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/04348239-a0ea-49e2-8b73-7e1ef79dc10b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
snowball analyzer not working
Hi All, I want to search document in following order -- 1. men's foil shaver 2. men's foils shaver 3. men's foil advanced shaver I tried multi-field option while mapping the field and mapped it with different filters and analyzers like one index with not_analyzed,one with snow ball analyzer, one with stemmer -- minimul english, standard, whitespace analyzer and one with ngram having min ngram 3 and max nagram 10. None of them works for me. Major part of the problem is if I search for men's foil shaver then all of them have same score of I CANNOT re-sequence them. I'm getting: 1. men's foil shaver 3. men's foil advanced shaver 2. men's foils shaver expected result: 1. men's foil shaver 2. men's foils shaver -- zero word distance with 1 plural foil -- foils 3. men's foil advanced shaver --1 word distance with no plural. Please suggest. Any help? I have posted kind of same questionhttps://groups.google.com/forum/#!topic/elasticsearch/ui9OR7JARs4 before but I did not reach to answer. I'm still waiting on my answers for that. one more question I have posted before few weeks: https://groups.google.com/forum/#!searchin/elasticsearch/plural/elasticsearch/ET-S3SCD22I/zFyErGO4SRcJ . Suggestion did improve my problem but it is not solved yet. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/fa97ad24-c5e1-40a4-9962-15b98bdcbe01%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
How to upgrade ES from 0.90.2 to 1.1.1
Hi everyone:
I used ES-0.90.2 as my index server.I have three pcs and each pc
has a ES instance.They run as a cluster.And they worked well,but now I want
upgrade my ES from 0.90.2 to 1.1.1.
At first,I read the document on the elasticsearch.org.I shutdown
my ES0.90.2，and unzip the ES1.1.1 in each pc. Then I copy the 'data' folder
in the ES0.90.2 to the same dictionary in ES1.1.1.At last,i run the three
ES1.1.1.But the shards became unassigned.Why,and how could i upgrade
rightly.
In my ES0.90.2,there is one index and more more than 30 types.I
creat 20 shards and 2 replica in my index.So there are 60 shards in total
and there are 20 shards in each pc.
When I start ES1.1.1,it seemed can find the meta infomation of the
old index data.Because，ES1.1.1 could know the name of old index data and
know how many shards the old index data has.
the status of my ES1.1.1 is：
{
cluster_name : test,
status : red,
timed_out : false,
number_of_nodes : 1,
number_of_data_nodes : 1,
active_primary_shards : 0,
active_shards : 0,
relocating_shards : 0,
initializing_shards : 0,
unassigned_shards : 60
}
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/d0e14772-3076-4130-8d49-66ba02a1aea0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Is it possible to get the name of the field above an element?
Thanks for the answer! Hope they make it soon.
But I searched a while and found this plugin.
https://github.com/wikimedia/search-highlighter
It doesn't solute the problem at all, but till the team make it, it will
work!
With this query I get want I want:
{
_source: false,
query: {
term: {
project.fulltext: so
}
},
highlight: {
fields: {
project.fulltext: {
type: experimental,
options: {
fetch_fields: [ project.id, project.title ]
}
}
}
}
}
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Is-it-possible-to-get-the-name-of-the-field-above-an-element-tp4055941p4055983.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/1400239369061-4055983.post%40n3.nabble.com.
For more options, visit https://groups.google.com/d/optout.
Re: Looking for good tutorial on setting up a basic index template to allow faceting of syslog files
Thanks Binh, let me read up on that API. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/67ab2276-404b-4de8-aad6-a6b28d89dbae%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Update on synonyms file requires full index recreation?
Hi, ES 1.1.1 when i use the synonyms filter with a synonyms_path file i have to create whole index again to take new synonyms in effect. It is not enough to update the index data, in need to remove, create and update whole index. Is that expected behaviour? If so what is ur strategy to get this done on a productive system? Thx regards Tom -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/0d8448bb-92e2-4748-a624-29fd95ea4ba1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
customize field name in dynamic template
Hi All,
Can I customize filed name in dynamic template? For example, I have
fields like twitter_title, twitter_body,blog_title,blog_body , and
there could be more fields with format xxx_title,xxx_body which are
added from front-end, then I want mapping twitter_title and
twitter_bodyto field “twitter”, mapping xxx_title and xxx_body to
xxx, are there any way for this kind of mapping?
I find there are some sample dynamic templates which append string to field
name, but I request to truncate field name..., here is sample to append
string to field name.
dynamic_templates : [
{
string_template : {
match : *,
match_mapping_type : string,
mapping : {
type : multi_field,
fields : {
{name}: {type: string, index :
analyzed, analyzer : default, store : false},
untouched : {type: string, index :
analyzed, analyzer : default, store : false}
}
}
}
}
]
Thanks!
Jun
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/fb065b1b-b923-436f-8392-cf9bae6529bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Copy_To an customize field
Hi All,
Can I customize filed name in dynamic template? For example, I have
fields like twitter_title, twitter_body,blog_title,blog_body , and
there could be more fields with format xxx_title,xxx_body which are
added from front-end, then I want to map xxx_title and xxx_body to
xxx, for example twitter_title to twitter, are there any way for
this kind of mapping?
dynamic_templates : [
{
string_template : {
match : *_title,
match_mapping_type : string,
mapping : {
type : string,
copy_to : target field name # how
could I calculate target field name from {name}?
}
}
}
]
Thanks!
Jun
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/0ab472ee-bac1-4dd0-bbcd-83cd013f0e7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Looking for good tutorial on setting up a basic index template to allow faceting of syslog files
Thanks Binh, let me read up on that API. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f9b26f0f-37fc-462e-8b41-caeb076f38a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
copy_to a field data to another customized filed
Hi All,
Can I customize filed name in dynamic template? For example, I have
fields like twitter_title, twitter_body,blog_title,blog_body , and
there could be more fields with format xxx_title,xxx_body which are
added from front-end, then I want to map xxx_title and xxx_body to
xxx, for example twitter_title to twitter, are there any way for
this kind of mapping?
dynamic_templates : [
{
string_template : {
match : *_title,
match_mapping_type : string,
mapping : {
type : string,
copy_to : target field name # how
could I calculate target field name from {name}?
}
}
}
]
Thanks!
Jun
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/b3e1bfd8-3878-4e7c-ad25-850fcdcc8ee6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Advice for implementing a secure graph index with ElasticSearch
Hi Mohit, Can you please ask your Lumify questions over on the Lumify google group at https://groups.google.com/d/forum/lumify? I'd rather not pollute the ElasticSearch group with unrelated messages. Thanks, Jeff On Friday, May 16, 2014 1:26:28 AM UTC-4, mohit kaushik wrote: Hi! jeff You said, you are using lumify. And lumify user secure-graph which implicitly implements cell level security that you all need. You can easily have access controls on your user and query returns the vertices in the way you want. I recently started working with secure-graph and want to implement the class /securegraph-core/src/main/java/org/securegraph/query/GraphQuery.java wchich is provided in the package and as it has been much days to your post so hope you might have figured out it. If you have please notify me. Thanks Mohit kaushik On Wednesday, March 5, 2014 10:40:11 PM UTC+5:30, Jeff Kunkle wrote: I've been trying to figure out how I can index a graph data structure using ElasticSearch and could really use some advice from someone more knowledgeable than me. First, let me explain the challenge. The graph model has individual access controls at the vertex (node), edge (relationship), and property level. I'd like my users to be able to search the graph for vertices or edges containing matching properties, with two caveats: 1. They should not get vertex or edge results they don't have permission to see. 2. Properties a user does not have access to see should not be evaluated in the query. My first thought was to index properties as either nested or child documents of a vertex/edge and use a custom filter to remove properties a user didn't have access to. The first problem I run into is when I try a boolean query across properties. For example, assume I want to query a person vertex by first name and date of birth. Since these properties are indexed as separate documents there is never a match. What I essentially need is the ability to query across nested or child documents and return the parent only when there are matches across the child documents. For example, assume a parent vertex with one property document called full_name set to Barak Obama and another property document named political_party set to Democrat. Is there any way for me to query for the parent document of these two properties by asking for one property with full_name=Barak Obama and another property with political_party=Democrat? -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3527e622-cba3-4e5e-8ed3-49df8acf53b8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
cluster failure
I just had an incident where my entire cluster (all nodes) ended up using
100% cpu on each nod at the same time and become completely unresponsive
even to /_cluster/health. This happened while I was using Kibana, which was
working fine up to that point. I was running a few simple queries (nothing
fancy, see log below). Even the shutdown call failed. After restarting, the
cluster seems fine again (green state after a few minutes) but I'd like to
prevent similar incidents in the future. This is the second time I've seen
elasticsearch die in this way. Last time, I got some helpful suggestions to
put some limits on the field data cache, which I did but obviously that
wasn't the (only) problem.
I'm running a three node cluster with elasticsearch 1.1.1, java 1.7.0_55
I'm using logstash and kibana. I have about three months worth of indices
(5 shards, 2 replicas) and a fresh index every day. 210G in total. Kibana
loads quite slowly but runs fine once loaded.
I don't see evidence of out of memory errors in the logs but it seems
garbage collects are very slow (5s). So obviously something is leaking
memory over time. Uptime of the cluster must have been around three weeks
(since last time it died).
Here's the log just before one of the nodes died. You can see the query I
ran actually failed for valid reasons because the (small) index I was
trying to query from kibana does not actually have the timestamp field.
[2014-05-16 14:28:54,880][INFO ][monitor.jvm ] [192.168.1.13]
[gc][old][1562124][155961] duration [6.6s], collections [1]/[12.3s], total
[6.6s]/[9.3h], memory [4.9gb]-[4.9gb]/[4.9gb], all_pools {[young]
[532.5mb]-[532.5mb]/[532.5mb]}{[survivor]
[43.3mb]-[38.2mb]/[66.5mb]}{[old] [4.3gb]-[4.3gb]/[4.3gb]}
[2014-05-16 14:28:54,880][DEBUG][action.search.type ] [192.168.1.13]
[deals_v5][4], node[ObP5F1ZSQKWOJrAb6T1T0g], [P], s[STARTED]: Failed to
execute [org.elasticsearch.action.search.SearchRequest@4e2d22c8] lastShard
[true]
org.elasticsearch.search.SearchParseException: [deals_v5][4]:
from[-1],size[-1]: Parse Failure [Failed to parse source
[{facets:{0:{date_histogram:{field:@timestamp,interval:30s},global:true,facet_filter:{fquery:{query:{filtered:{query:{query_string:{query:type:deal}},filter:{bool:{must:[{range:{@timestamp:{from:1400239478674,to:now}}}],size:0}]]
at
org.elasticsearch.search.SearchService.parseSource(SearchService.java:634)
at
org.elasticsearch.search.SearchService.createContext(SearchService.java:507)
at
org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:480)
at
org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:252)
at
org.elasticsearch.search.action.SearchServiceTransportAction.sendExecuteQuery(SearchServiceTransportAction.java:202)
at
org.elasticsearch.action.search.type.TransportSearchCountAction$AsyncAction.sendExecuteFirstPhase(TransportSearchCountAction.java:70)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:216)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$4.run(TransportSearchTypeAction.java:296)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.elasticsearch.search.facet.FacetPhaseExecutionException:
Facet [0]: (key) field [@timestamp] not found
at
org.elasticsearch.search.facet.datehistogram.DateHistogramFacetParser.parse(DateHistogramFacetParser.java:160)
at
org.elasticsearch.search.facet.FacetParseElement.parse(FacetParseElement.java:93)
at
org.elasticsearch.search.SearchService.parseSource(SearchService.java:622)
... 10 more
[2014-05-16 14:28:54,935][DEBUG][action.search.type ] [192.168.1.13]
[deals_v5][0], node[ObP5F1ZSQKWOJrAb6T1T0g], [P], s[STARTED]: Failed to
execute [org.elasticsearch.action.search.SearchRequest@4622b34d] lastShard
[true]
org.elasticsearch.search.SearchParseException: [deals_v5][0]:
from[-1],size[-1]: Parse Failure [Failed to parse source
[{facets:{0:{date_histogram:{field:@timestamp,interval:30s},global:true,facet_filter:{fquery:{query:{filtered:{query:{query_string:{query:type:deal}},filter:{bool:{must:[{range:{@timestamp:{from:1400239468981,to:now}}}],size:0}]]
at
org.elasticsearch.search.SearchService.parseSource(SearchService.java:634)
at
org.elasticsearch.search.SearchService.createContext(SearchService.java:507)
at
org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:480)
at
org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:252)
at
Complex query
Hello community,
First, I apologize for my English.
I can not find a complex query.
I have thes columns :
*Id : String*
*Name : String*
*FirstName : String*
*ZipCode : String*
If a user perfoms a query : *word1 * *wordn*
I need to make a query, something like this :
Name contains word1 *OR*
FirstName contains word1 *OR*
ZipCode starts with word1
*AND*
*AND*
Name contains wordn *OR*
FirstName contains wordn *OR*
ZipCode starts with wordn
i make this query but it's not my real need :
*{*
* query: {*
*bool: {*
* must: [*
*{*
* query_string: {*
*fields: [*
* name,*
* firstname,*
* zipcode*
*],*
*query: *word1**
* }*
*},*
*{*
* query_string: {*
*fields: [*
* name,*
* firstname,*
* zipcode*
*],*
*query: *wordn**
* }*
*}*
* ],*
* must_not: [],*
* should: []*
*}*
* },*
* from: 0,*
* size: 10,*
* sort: [],*
* facets: {}*
*} *
This query is not good because I don't have my condition zipcode start
with but zipcode contains.
Can someone help me build the right query ?
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/882034da-08c4-4573-ac1a-c3d929ca1154%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Disk-based shard allocation per node settings
What if I set the option in the configuration file, will it then only be applied to the node reading the configuration file? On Fri, May 16, 2014 at 10:36 AM, Mark Walkom ma...@campaignmonitor.com wrote: It's a cluster level setting, so all nodes use the same one. As far as I know, there is no node level setting. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: ma...@campaignmonitor.com web: www.campaignmonitor.com On 16 May 2014 17:43, Michel Conrad michel.con...@trendiction.com wrote: Is it possible to specify different thresholds for different nodes in the cluster? I could not find it in the documentation, when updating the setting through the cluster settings as described on http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html#disk the threshold is applied to every node. When specifing the thresholds through the configuration file, will it then be only applied to the node reading the configuration? In this case how to I prevent the cluster settings being applied and overwriting the configuration file (remove a setting). Thanks for any thoughts, Michel -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAH0sEYgM4%3DmH2cA3wJoBQAmx82ddrz6N%3D8u3XE0EFoKoOwTUUQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624a6tk9jqGkh_ED%3Dx_bpJPxpiydP9_KxTugrBVZuX5yaCw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAH0sEYjc5DAO4mW%2B%3DnrgDfxbEd%2BYxwcn1vZ9jXxBNm1N%2BH9%3D1Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Disk-based shard allocation per node settings
The link you provided is for transient settings, meaning they will reset once the cluster restarts. Doing this via the configurations file ensures the settings are loaded back. As Mark said, this is cluster level settings. If you have nodes with different HD characteristics you probably want to use percentages for the watermark values. -- Itamar Syn-Hershko http://code972.com | @synhershko https://twitter.com/synhershko Freelance Developer Consultant Author of RavenDB in Action http://manning.com/synhershko/ On Fri, May 16, 2014 at 3:26 PM, Michel Conrad michel.con...@trendiction.com wrote: What if I set the option in the configuration file, will it then only be applied to the node reading the configuration file? On Fri, May 16, 2014 at 10:36 AM, Mark Walkom ma...@campaignmonitor.com wrote: It's a cluster level setting, so all nodes use the same one. As far as I know, there is no node level setting. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: ma...@campaignmonitor.com web: www.campaignmonitor.com On 16 May 2014 17:43, Michel Conrad michel.con...@trendiction.com wrote: Is it possible to specify different thresholds for different nodes in the cluster? I could not find it in the documentation, when updating the setting through the cluster settings as described on http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html#disk the threshold is applied to every node. When specifing the thresholds through the configuration file, will it then be only applied to the node reading the configuration? In this case how to I prevent the cluster settings being applied and overwriting the configuration file (remove a setting). Thanks for any thoughts, Michel -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAH0sEYgM4%3DmH2cA3wJoBQAmx82ddrz6N%3D8u3XE0EFoKoOwTUUQ%40mail.gmail.com . For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624a6tk9jqGkh_ED%3Dx_bpJPxpiydP9_KxTugrBVZuX5yaCw%40mail.gmail.com . For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAH0sEYjc5DAO4mW%2B%3DnrgDfxbEd%2BYxwcn1vZ9jXxBNm1N%2BH9%3D1Q%40mail.gmail.com . For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZtTZfb%2B0uJSxohd685pCAcEgxZXSg_SYeu9izq%3D4_1zjQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Debugging scripts
I'm trying to debug an MVEL script that's failing in production but working
locally, and I've tried to do logging a couple different ways, but I can
only get logging to work locally.
Both local and production are running 1.1.1, same exact build. Both are
running with java 1.7._55.
I've tried the logger approach based
on
https://github.com/imotov/elasticsearch-test-scripts/blob/master/logging_from_script.sh,
but that only works when the server is running under java 1.6. Under 1.7,
both local and production fail.
I've tried using System.out.println, but that only works locally even under
java 1.7. In production I just get error:
ElasticsearchIllegalArgumentException[failed to execute script]; nested:
PropertyAccessException[[Error: unresolvable property or identifier:
]\n[Near : {... System.out.println(\SCRIPT: }]\n ^\n[Line: 12, Column:
1]];
Does anyone have any pointers as to how to debug MVEL or get log output
from MVEL scripts in ES?
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/c6914ca7-a4da-4bb5-97c6-4a299d68d2c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: running out of memory indexing on linux
On Friday, May 16, 2014 3:43:22 AM UTC-4, Alberto Paro wrote: Are you using the SUN jvm 1.7 or above? I had similar issues with standard Linux openJDk Yes, I am. I've got 1.7.0_55 via Debian Sid. How did you solve your issue? -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1d768b6b-b333-4d3a-bb3e-591536f91dc7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Complex query
Please, I really need help for this query.
I just created this query but it's a very heavy query
{
query: {
match_all: {}
},
filter: {
and: [
{
or: [
{
query: {
query_string: {
query: *Word1*,
default_field: name
}
}
},
{
query: {
query_string: {
query: *Word1*,
default_field: firstname
}
}
},
{
query: {
query_string: {
query: Word1*,
default_field: zipcode
}
}
}
]
},
{
or: [
{
query: {
query_string: {
query: *Wordn*,
default_field: name
}
}
},
{
query: {
query_string: {
query: *Wordn*,
default_field: firstname
}
}
},
{
query: {
query_string: {
query: Wordn*,
default_field: zipcode
}
}
}
]
}
]
}
}
If i have ten word, i think the query will be very very very long to be
execute
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/29359521-cada-41de-beac-1b6d786abbdd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
index update performance
Hi, We are exploring the Lucene/ES as an embedded search engine inside our product offering and while analysis following concerns come up. Could you share your thoughts on how serious/genuine these are :- 1.Read Dominant - Data in Lucene Index is intended to be read predominantly and not to be frequently updated. Although, it supports NEAR Real-time Searches. We might have scenarios where one or multiple users are updating/deleting few documents (concurrently) in a large index repository (250 million documents). 2.While Lucene Index facilitates insert, delete and update of documents, single field update capabilities aren't good especially if that field is text indexed. Whenever a new field is added or the contents of an existing field is changed, every single document in Lucene Index must be reprocessed in its entirety before the data is populated for the new field in all documents. Thanks Gaurav -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/93d7c25f-e8c3-4078-9f8c-f2158e26752c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Cross Fields w/ Fuzziness
+1 fuzziness would be great when using cross_fields Am Mittwoch, 7. Mai 2014 22:00:25 UTC+2 schrieb Ryan Tanner: Any update to this? On Monday, April 7, 2014 7:59:54 AM UTC-6, Elliott Bradshaw wrote: Hi Elasticsearch, I've been playing with the new cross_fields multi match type, and I've got to say that I love it. It's a great way to search complex data without doing a lot of memory killing denormalization. That said, is there any plan to implement a fuzziness option with this type? That would certainly be very valuable. - Elliott -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/119435db-2635-4866-90de-762685e22d41%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Plain Highlighter using document-defined analyzer
Any thoughts on this? On Tuesday, 13 May 2014 16:22:13 UTC, Mateusz Kaczynski wrote: We have recently encountered a problem with item highlighting when we changed the way we define analysers. In short, the problem boiled down to PlainHighlighter using analyser for the document type. while we specify analyser on per-document basis. '_analyzer' field is not used (or, from my debugging, even visible) in the highlighter context. As a temporary solution, I made highlighter use the field to which '_analyzer' points to(via path) in the mappings we use, My attempt at it is over here: https://github.com/arachnys/elasticsearch/commit/8082fcab5e22f783536f226eb544da7c27ceabba There are a couple of issues that I am seeking help with: 1) Does this seem like an about - right approach to dealing with the situation? 2) Analyzer field name is hardcoded, as I was unable to figure out how to get it from the document in the correct way (again, the right field is pointed to in '_analyzer' via path). Any suggestions how to do it properly? Regards, Mateusz Kaczyński -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d2962d64-26d6-4984-835a-e6b3bee7731c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Official .NET client
If it has been a couple of months since you last looked at NEST, I would suggest looking at it again as the 1.0.0-beta1 release of NEST has also added more of the functionality you mentioned below, since NEST is now built on top of Elasticsearch.Net. On Friday, May 16, 2014 5:56:12 AM UTC-4, Loïc Wenkin wrote: Hi Paige, Sorry for the late reply. Many thanks about it, I will have a look at Elasticsearch.Net (I already had a look at NEST some month ago, but it wasn't all I need) and see if it can help me :) Regards, Loïc Le vendredi 9 mai 2014 04:06:47 UTC+2, Paige Cook a écrit : Elasticsearch.Net and NEST are the official .NET Clients for Elasticsearch. You can read about them in the recent blog post - introducing elasticsearch.net and nest 1.0.0-beta1http://www.elasticsearch.org/blog/introducing-elasticsearch-net-nest-1-0-0-beta1/ Both aggregations and integrated failover are supported in Elasticsearch.Net and NEST. On Tuesday, May 6, 2014 5:51:25 AM UTC-4, Loïc Wenkin wrote: Hello everybody, I watched a video 2 or 3 months ago (Facebook and Elasticsearch), and in this video, it was said that it was planned to develop an official .NET client. Do you have some news about it ? Is there a roadmap (or at least, an idea about a release date (2014, 2015 ...)) for this client ? Currently, I am using PlainElastic.Net which is a great client (I like the idea to work with strings directly accessible to user, allowing us to easily debug queries), but some features are missing (I think to aggregations, for example, or a kind of integrated failover system). Any news about it would be appreciated :) Regards, Loïc -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/85581f6c-078a-4211-b944-69e75cffc17b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Debugging scripts
Someone should can answer this issue, I'm having the same problem logging
scripts. Maybe Imovot can.
El viernes, 16 de mayo de 2014 10:33:12 UTC-3, Mike Snare escribió:
I'm trying to debug an MVEL script that's failing in production but
working locally, and I've tried to do logging a couple different ways, but
I can only get logging to work locally.
Both local and production are running 1.1.1, same exact build. Both are
running with java 1.7._55.
I've tried the logger approach based on
https://github.com/imotov/elasticsearch-test-scripts/blob/master/logging_from_script.sh,
but that only works when the server is running under java 1.6. Under 1.7,
both local and production fail.
I've tried using System.out.println, but that only works locally even
under java 1.7. In production I just get error:
ElasticsearchIllegalArgumentException[failed to execute script]; nested:
PropertyAccessException[[Error: unresolvable property or identifier:
]\n[Near : {... System.out.println(\SCRIPT: }]\n ^\n[Line: 12, Column:
1]];
Does anyone have any pointers as to how to debug MVEL or get log output
from MVEL scripts in ES?
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/d8bc37f2-b3ea-4711-8bcd-eb65af9b61f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: java 8, elasticsearch, and MVEL
It's a little hard to tell between the mvel es commit histories and the github issue. It looks like this isn't fixed, and isn't going to get fixed in MVEL? Am I misreading something? --paul On Monday, April 21, 2014 8:39:43 AM UTC-4, Alexander Reelsen wrote: Hey, this commits upgrades mvel, that seems to have fixed the java8 issues (still requires more testing on our side though): https://github.com/elasticsearch/elasticsearch/commit/21a36678883c159e50a03b76309d3da2a8e5d7b4 IIRC this bug has also been fixed in the new MVEL version: https://github.com/elasticsearch/elasticsearch/issues/5483 --Alex On Tue, Apr 15, 2014 at 11:40 AM, Bernhard Berger bernhardb...@gmail.comjavascript: wrote: Is there an open issue so that I can watch the progress for this bug? I cannot find any issue for this on GitHub. Am 07.04.2014 01:12, schrieb Shay Banon: We will report back with findings and progress. -- 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 elasticsearc...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/534CFEA8.9060100%40gmail.comhttps://groups.google.com/d/msgid/elasticsearch/534CFEA8.9060100%40gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- *Important Notice:* The information contained in or attached to this email message is confidential and proprietary information of RedOwl Analytics, Inc., and by opening this email or any attachment the recipient agrees to keep such information strictly confidential and not to use or disclose the information other than as expressly authorized by RedOwl Analytics, Inc. If you are not the intended recipient, please be aware that any use, printing, copying, disclosure, dissemination, or the taking of any act in reliance on this communication or the information contained herein is strictly prohibited. If you think that you have received this email message in error, please delete it and notify the sender. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e4717341-fc95-4ca0-badf-50b38e6df5d2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Cannot register snapshot repository in Elasticsearch
Hello ES community,
I am trying to create a snapshot for ES and I am following the steps at:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-snapshots.html
.
Unfortunately the repository creation fails in our environment: Debian 6.0.9
This is what I run:
curl -XPUT 'http://localhost:9200/_snapshot/my_backup' -d '{
type: fs,
settings: {
location: /mount/backups/my_backup,
compress: true
}
}'
The Error I get every time: (for info, just in case i restarted ES...)
{error:RepositoryException[[my_backup] failed to create repository];
nested: CreationException[Guice creation errors:\n\n1) Error injecting
constructor, org.elasticsearch.common.blobstore.BlobStoreException: Failed
to create directory at [/mount/backups/my_backup]\n at
org.elasticsearch.repositories.fs.FsRepository.init(Unknown Source)\n
while locating org.elasticsearch.repositories.fs.FsRepository\n while
locating org.elasticsearch.repositories.Repository\n\n1 error]; nested:
BlobStoreException[Failed to create directory at
[/mount/backups/my_backup]]; ,status:500}
Here is our version of ES:
{
status : 200,
name : Slither,
version : {
number : 1.0.1,
build_hash : 5c03844e1978e5cc924dab2a423dc63ce881c42b,
build_timestamp : 2014-02-25T15:52:53Z,
build_snapshot : false,
lucene_version : 4.6
},
I spent quite a long time trying to find something on the web in all the ES
threads but without any luckAm I missing something obvious???
Many thanks in advance for your help.
Kind regards
Fred
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/25e30d61-6148-452a-975c-0a04d992ebb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Inconsistent Search Results with 2 Node Cluster
We are using elastic search. We have a 2 Node Cluster with 2 shards and 1 replica and are indexing around 4 million documents. We started noticing that the search results that we are getting back from the cluster are inconsistent in the total number of counts for the results, as well as the results that are being brought back. Here is an example: I search for a document with a very unique name using a DSF_QUERY_THEN_FETCH search. I know there is only one of this document on this server so when I search for the unique name, I should get only one document back but when I search it multiple times here is what happens (I excited the same search 5 times in a row) Search “uniqueTerm” Results - 1 Search “uniqueTerm” Results - 1 Search “uniqueTerm” Results - 0 Search “uniqueTerm” Results - 0 Search “uniqueTerm” Results - 0 And then it repeats the exact same pattern. It’s like it’s not finding the data part of the time. The weird thing is that it doesn’t matter have fast or how slow the I excite the searches, it finds it the first 2 times and for the next three it doesn’t. HOWEVER: If I modify the cluster to have 1 node, 1 shard, no replicas, and repeat the same test the results are such: Search “uniqueTerm” Results - 1 Search “uniqueTerm” Results - 1 Search “uniqueTerm” Results - 1 Search “uniqueTerm” Results - 1 Search “uniqueTerm” Results - 1 We are running elasticsearch 1.1.0 and using the Java API to excute our searches. Does anyone know if there is a setting or something that we are missing in our cluster? Thanks again -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Inconsistent-Search-Results-with-2-Node-Cluster-tp4056008.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1400256193906-4056008.post%40n3.nabble.com. For more options, visit https://groups.google.com/d/optout.
Re: Cannot register snapshot repository in Elasticsearch
Did you check your read/write settings for /mount/backups dir?
They should be writable by the user which runs elasticsearch.
If still not working, could you try create /mount/backups/my_backup and gives
privileges to elasticsearch user?
HTH
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 16 mai 2014 à 17:55:28, Fred Ducrot (ducrot.frede...@gmail.com) a écrit:
Hello ES community,
I am trying to create a snapshot for ES and I am following the steps at:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-snapshots.html.
Unfortunately the repository creation fails in our environment: Debian 6.0.9
This is what I run:
curl -XPUT 'http://localhost:9200/_snapshot/my_backup' -d '{
type: fs,
settings: {
location: /mount/backups/my_backup,
compress: true
}
}'
The Error I get every time: (for info, just in case i restarted ES...)
{error:RepositoryException[[my_backup] failed to create repository]; nested:
CreationException[Guice creation errors:\n\n1) Error injecting constructor,
org.elasticsearch.common.blobstore.BlobStoreException: Failed to create
directory at [/mount/backups/my_backup]\n at
org.elasticsearch.repositories.fs.FsRepository.init(Unknown Source)\n while
locating org.elasticsearch.repositories.fs.FsRepository\n while locating
org.elasticsearch.repositories.Repository\n\n1 error]; nested:
BlobStoreException[Failed to create directory at [/mount/backups/my_backup]];
,status:500}
Here is our version of ES:
{
status : 200,
name : Slither,
version : {
number : 1.0.1,
build_hash : 5c03844e1978e5cc924dab2a423dc63ce881c42b,
build_timestamp : 2014-02-25T15:52:53Z,
build_snapshot : false,
lucene_version : 4.6
},
I spent quite a long time trying to find something on the web in all the ES
threads but without any luckAm I missing something obvious???
Many thanks in advance for your help.
Kind regards
Fred
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/25e30d61-6148-452a-975c-0a04d992ebb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/etPan.5376357b.7644a45c.f868%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.
slow indexing and large index
For this environment i'm using ES + Logstash + GrayLog2 I've manually ( and stupidly ) deleted the elasticsearch indices in /var/lib/elasticsearch/ Then i've cleaned mongodb to reset the GL2 config Logstash is reading logfiles and sending GELF output In GL2 i created Inputs for UDP GELF All is working fine BUT the indexing is now very slow, on average 50 messages per second. I saw frequent numbers of over 2000 messages per second What can i do to analyze, troubleshoot, fix this issue ? Best Regards, Joris -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4dbaa503-d794-4b95-b924-13709ec11ee9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Cannot register snapshot repository in Elasticsearch
Hi David,
Thanks for your prompt reply. It was a rights issue as you suspected. So it
was VERY obvious!
Mental note: Don't try to do things on a Friday afternoon after an awfully
tiring week! ;-)
Thanks again for your help.
Fred
On Friday, 16 May 2014 17:57:46 UTC+2, David Pilato wrote:
Did you check your read/write settings for /mount/backups dir?
They should be writable by the user which runs elasticsearch.
If still not working, could you try create /mount/backups/my_backup and
gives privileges to elasticsearch user?
HTH
--
*David Pilato* | *Technical Advocate* | *Elasticsearch.com*
@dadoonet https://twitter.com/dadoonet |
@elasticsearchfrhttps://twitter.com/elasticsearchfr
Le 16 mai 2014 à 17:55:28, Fred Ducrot (ducrot@gmail.com javascript:)
a écrit:
Hello ES community,
I am trying to create a snapshot for ES and I am following the steps at:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-snapshots.html
.
Unfortunately the repository creation fails in our environment: Debian
6.0.9
This is what I run:
curl -XPUT 'http://localhost:9200/_snapshot/my_backup' -d '{
type: fs,
settings: {
location: /mount/backups/my_backup,
compress: true
}
}'
The Error I get every time: (for info, just in case i restarted ES...)
{error:RepositoryException[[my_backup] failed to create repository];
nested: CreationException[Guice creation errors:\n\n1) Error injecting
constructor, org.elasticsearch.common.blobstore.BlobStoreException: Failed
to create directory at [/mount/backups/my_backup]\n at
org.elasticsearch.repositories.fs.FsRepository.init(Unknown Source)\n
while locating org.elasticsearch.repositories.fs.FsRepository\n while
locating org.elasticsearch.repositories.Repository\n\n1 error]; nested:
BlobStoreException[Failed to create directory at
[/mount/backups/my_backup]]; ,status:500}
Here is our version of ES:
{
status : 200,
name : Slither,
version : {
number : 1.0.1,
build_hash : 5c03844e1978e5cc924dab2a423dc63ce881c42b,
build_timestamp : 2014-02-25T15:52:53Z,
build_snapshot : false,
lucene_version : 4.6
},
I spent quite a long time trying to find something on the web in all the
ES threads but without any luckAm I missing something obvious???
Many thanks in advance for your help.
Kind regards
Fred
--
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 elasticsearc...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/25e30d61-6148-452a-975c-0a04d992ebb4%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/25e30d61-6148-452a-975c-0a04d992ebb4%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/d4a73011-fd6e-437d-84e0-387cd771bc43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
ElasticSearch Version problem
Hi, I need to index documents from mysql to ES. I read about jdbc river but it is compatible for ES 1.1.0. My problem is I'm using mongodb also for indexing some documents and that too with ES version 0.90.3. I know it's bit of a older version but that why I want to upgrade to newer version but my problem is I'm not able to find any suitable mongo river plugin for ES 1.1.0. Can anyone give me pointer to where I can get river mongo plugin for ES 1.1.0 or jdbc river plugin for ES 0.90.3. Thanks, -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/feff43d5-e0fe-400c-b9d1-40ebcc535422%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: geo_shape type
Hi everyone. I have got exactly the same error
org.elasticsearch.index.mapper.MapperParsingException: No handler for type
[geo_shape] declared on field [full_geometry]
This is a part of mapping
center_point: {
type: geo_point,
index: not_analyzed
},
full_geometry: {
type: geo_shape
}
center points works, but full_geometry failed.
ES version 1.1.1
I use ES via maven dependency
dependency
groupIdorg.elasticsearch/groupId
artifactIdelasticsearch/artifactId
version1.1.1/version
/dependency
Maybe I should add some additional dependencies or anything else.
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/19e830a4-f924-4f27-9208-4829045c5e65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: geo_shape type
Got it. I was miss JTS dependency. dependency groupIdcom.vividsolutions/groupId artifactIdjts/artifactId version1.13/version /dependency -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/87676788-f953-4d19-8262-247a3ad17da2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Return only the YYYY-MM-DDD from date field - can I do that with a script?
I have some date type data coming back from a query, like the example below
field signupDate. Can I query and have the date only return the calendar
date and drop the hours, minutes, etc. Would I do that with a script
field? This signup date is entered as system time and i can't change that,
but when I query it I just wan to see the signup date as a normal date.
hits: [
{
_index: index1,
_type: type1,
_id: 6ctRoz-0RI24Lu2FRZXwOQ,
_score: 1,
fields: {
signupDate: [
2014-01-03T04:22:43.502586
],
accountNumber: [
358666
]
}
},
...
Here's the query I'm using:
{ query: {filtered: {
query: {match_all: {}},
filter: {range: {
signupDate: {
from: 2014-01-01,
to: 2014-01-15
}
}
}
}
},
fields: [
accountNumber,signupDate]
}
The signupDate field is defined as:
signupDate: {
type: date,
format: dateOptionalTime
},
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/ab61156a-c405-48f0-9b1b-95d47155960f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
warmers vs eager field data loading
I noticed the warmers documentation mentioned that it's often used for fields involved in sorting/faceting. My understanding is this is because those operations require the entire field loaded in the field data cache. In this case why not set the fielddata.loading property to eager in the field mapping? Wouldn't this accomplish the same thing? Also in what situation does eager_global_ordinals loading option provide benefits? Thanks! http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/fielddata-formats.html#_fielddata_loading -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/2afc2ade-dbbc-40e8-bf4c-9143f5de0f54%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: java 8, elasticsearch, and MVEL
MVEL 2.2.0 fixes Java 8 compilation issue http://jira.codehaus.org/browse/MVEL-299 Jörg On Fri, May 16, 2014 at 5:45 PM, Paul Sanwald p...@redowlanalytics.comwrote: It's a little hard to tell between the mvel es commit histories and the github issue. It looks like this isn't fixed, and isn't going to get fixed in MVEL? Am I misreading something? -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoETutbGnKOT72psnAsZiUrMNomGyNmtwKLzVrmYcNF1XA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: modify explain string in elasticsearch plugin
I looked into the same issue when I first switched over to using custom scoring. I did not see a simple solution, so I did not investigate it further. Hopefully you will be able to find something. -- Ivan On Thu, May 15, 2014 at 10:14 AM, Srinivasan Ramaswamy ursva...@gmail.comwrote: Does the current explain gives details about the function/script in function score query ? If so how is it achieved ? I would like to add explanation for my custom scoring so that its easy to investigate. How do people achieve this typically using elasticsearch ? Thanks Srini On Wed, May 14, 2014 at 4:28 PM, Ivan Brusic i...@brusic.com wrote: The explain string is basically a JSON formatted string of Lucene's explain object. I doubt this formatter is pluggable or that you can change the Explain object. -- Ivan On Tue, May 13, 2014 at 11:36 PM, Srinivasan Ramaswamy ursva...@gmail.com wrote: Hi I am overriding the scoring function using a plugin as described in https://github.com/imotov/elasticsearch-native-script-example I would like to know how to override the explain string, so that i can add explanation for all my custom scoring. Thanks Srini -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b4485fa8-39f0-40f3-b614-9842c200a0e2%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/b4485fa8-39f0-40f3-b614-9842c200a0e2%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/7e2Xe_mpJYU/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQAmU3cKM%3Ddw2NyV_7BZfZn6MnBJ8zy7SX0Ri45epZUPcA%40mail.gmail.comhttps://groups.google.com/d/msgid/elasticsearch/CALY%3DcQAmU3cKM%3Ddw2NyV_7BZfZn6MnBJ8zy7SX0Ri45epZUPcA%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAL1MvVzRZ%2B5eSn85uNFi8BX963Q_QojcYp72m6unTrmm5SdLUw%40mail.gmail.comhttps://groups.google.com/d/msgid/elasticsearch/CAL1MvVzRZ%2B5eSn85uNFi8BX963Q_QojcYp72m6unTrmm5SdLUw%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBR2is9JFammnnh%3D4RYa--zOw6bdEsJneX_ahw673MGXA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: ElasticSearch Version problem
Rivers did not change since ES 1.0.0 so I'm quite confident that https://github.com/richardwilly98/elasticsearch-river-mongodb 2.0.0 will run with ES 1.1.0 Jörg On Fri, May 16, 2014 at 6:57 PM, coder mukulnit...@gmail.com wrote: Hi, I need to index documents from mysql to ES. I read about jdbc river but it is compatible for ES 1.1.0. My problem is I'm using mongodb also for indexing some documents and that too with ES version 0.90.3. I know it's bit of a older version but that why I want to upgrade to newer version but my problem is I'm not able to find any suitable mongo river plugin for ES 1.1.0. Can anyone give me pointer to where I can get river mongo plugin for ES 1.1.0 or jdbc river plugin for ES 0.90.3. Thanks, -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/feff43d5-e0fe-400c-b9d1-40ebcc535422%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/feff43d5-e0fe-400c-b9d1-40ebcc535422%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEgtmg2pd1-b5U219tL3JY6DEZmC-g6Vb5iom7wyO8f0g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Update on synonyms file requires full index recreation?
Read about file wathcer service here https://github.com/elasticsearch/elasticsearch/issues/4063 Anything happening according this or am i monitoring the wrong path? Am Freitag, 16. Mai 2014 13:42:19 UTC+2 schrieb Tom: Hi, ES 1.1.1 when i use the synonyms filter with a synonyms_path file i have to create whole index again to take new synonyms in effect. It is not enough to update the index data, in need to remove, create and update whole index. Is that expected behaviour? If so what is ur strategy to get this done on a productive system? Thx regards Tom -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c9eb7ca7-328b-4829-b636-3a69f714f226%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to upgrade ES from 0.90.2 to 1.1.1
How many nodes do you have? You mentioned that you unzip the distribution
on each PC, but you status only shows 1 node. Can you output the status for
each node? Did you copy the configs as well?
First of all, there is no need to copy the data unless you want a backup.
You can maintain the same configs and data by pointing elasticsearch to the
some directory that lives outside of the installation directory:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-dir-layout.html
Cheers,
Ivan
On Fri, May 16, 2014 at 4:01 AM, nie...@126.com wrote:
Hi everyone:
I used ES-0.90.2 as my index server.I have three pcs and each pc
has a ES instance.They run as a cluster.And they worked well,but now I want
upgrade my ES from 0.90.2 to 1.1.1.
At first,I read the document on the elasticsearch.org.I shutdown
my ES0.90.2，and unzip the ES1.1.1 in each pc. Then I copy the 'data' folder
in the ES0.90.2 to the same dictionary in ES1.1.1.At last,i run the three
ES1.1.1.But the shards became unassigned.Why,and how could i upgrade
rightly.
In my ES0.90.2,there is one index and more more than 30 types.I
creat 20 shards and 2 replica in my index.So there are 60 shards in total
and there are 20 shards in each pc.
When I start ES1.1.1,it seemed can find the meta infomation of the
old index data.Because，ES1.1.1 could know the name of old index data and
know how many shards the old index data has.
the status of my ES1.1.1 is：
{
cluster_name : test,
status : red,
timed_out : false,
number_of_nodes : 1,
number_of_data_nodes : 1,
active_primary_shards : 0,
active_shards : 0,
relocating_shards : 0,
initializing_shards : 0,
unassigned_shards : 60
}
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/d0e14772-3076-4130-8d49-66ba02a1aea0%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/d0e14772-3076-4130-8d49-66ba02a1aea0%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
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 discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQB1HPpx2Om%2BHvW-%2B65ytZJ1jdvoDzyZsPogXpE4v2jm1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: Update on synonyms file requires full index recreation?
The synonym file will be read whenever a new index is created or if an index is re-opened. Closing and opening an index is not the cleanest solution, so I created a plugin to help solve the problem: https://github.com/brusic/refresh-token-filters However, this version of the plugin does not seem to be working 100%. Unfortunately, I do not have time to test. I have a different version of the plugin working at my company for over a year without any issues. It has more bells and whistles (connects to a database for the term lists, timed refreshes), but I wanted my public version to be simpler. The most important change is that I moved from tracking the filter Java objects directly to using the IndicesService. However, I found that some analyzers can be cached and therefore there internal filters do not change. Like I said, I don't have time to test, but I am assuming that is the issue. Cheers, Ivan On Fri, May 16, 2014 at 3:19 PM, Tom t.opp...@superreal.de wrote: Read about file wathcer service here https://github.com/elasticsearch/elasticsearch/issues/4063 Anything happening according this or am i monitoring the wrong path? Am Freitag, 16. Mai 2014 13:42:19 UTC+2 schrieb Tom: Hi, ES 1.1.1 when i use the synonyms filter with a synonyms_path file i have to create whole index again to take new synonyms in effect. It is not enough to update the index data, in need to remove, create and update whole index. Is that expected behaviour? If so what is ur strategy to get this done on a productive system? Thx regards Tom -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c9eb7ca7-328b-4829-b636-3a69f714f226%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/c9eb7ca7-328b-4829-b636-3a69f714f226%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDub2OH1CKS1phM286gC7808vqGVXyJDtf7D%3DfoyBb5%2BA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
my elastic search is not returning any data since 12 hr now
although the inserts are going fine but i am not able to query them back also my marvel show blank dashboard since 12 hr now but i have data prior to that and also able to fetch them from query. Refer to the attached screenshot which describes the series of events after which my ES has started behaving absurdly as described above. -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/8f64ec77-c0ff-413c-a171-705a5b201204%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
about fielddata cache and filter cache expire
*My Cluster Specification* node : 7 Memory : 24G JVM : 12G, OS : 12G *elasticsearch version : 1.1.1* *set elasticsearch.yml* indices.cache.filter.size: 30% indices.fielddata.cache.size: 50% I saw the head plug-in. cache was about fitler cache and fielddata cache 200mb. all cache expires after about 10 minutes. I have enough memory. What options do I need? -- 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 discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/ea7127ef-af02-498e-b4a0-2eb0634c6470%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
