lastic.co/ . This email
> list has been deprecated in favor of using that. There are settings that
> make it function almost the same way the mailing list functioned.
>
> On Thu, Aug 27, 2015 at 3:39 AM, Ron Sher <ron.s...@gmail.com> wrote:
>
>> Hi,
>>
>> I'
Hi,
I'm using the query below in my search to find all users without parents.
The search works as expected, but delete by query fails with has_parent]
query and filter unsupported in delete_by_query api
I've searched and it seems that it should be supported.
Anything that I'm missing?
{
Nope. Didn't find anything
בתאריך 8 במאי 2015 12:06 לפנה״צ, Richard Eyre dicke...@gmail.com כתב:
Hi Ron,
Did you ever make any progress on rolling upgrades?
Thanks,
Richard
On Sunday, July 27, 2014 at 11:04:31 PM UTC-6, Ron Sher wrote:
Hi,
I know there's a guide on installing
We have child documents and we suspect that some of them don't have their
parents. Can someone suggest a query I can use to find child documents without
parents?
Thanks,
Ron
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from
So I also looked at logstash, but you have to define the field names for each
file. Same as the others.
Logstash is almost worse because you need a restart of the service when you
update the config file.
--
You received this message because you are subscribed to the Google Groups
)
Jörg
On Sun, Jan 25, 2015 at 7:55 AM, Ron rulk...@gmail.com javascript:
wrote:
Yup.. I'm one of the guys posting in that Issue log..
On Sunday, January 25, 2015 at 12:26:04 AM UTC-5, David Pilato wrote:
I think you are looking for this?
https://github.com/elasticsearch/logstash
for this as well, it has a CSV filter.
On 24 January 2015 at 01:21, Ron rulk...@gmail.com javascript: wrote:
Hello all,
So I'm trying to import a large number of CSV files into Elasticsearch.
All the files have different content in them, with different headers.
My goal is to have a directory we
25 janv. 2015 à 03:40, Ron rulk...@gmail.com javascript: a écrit :
The same issue exists with the Logstash plugin. You have to define the
field names in the Logstash config file.
Almost worse, each time you update field names, you have to restart
logstash.
On Friday, January 23, 2015 at 5
.
Thanks
Ron
--
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
#scroll-scan
--
*David Pilato* | *Technical Advocate* | *Elasticsearch.com
http://Elasticsearch.com*
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr
https://twitter.com/elasticsearchfr | @scrutmydocs
https://twitter.com/scrutmydocs
Le 10 déc. 2014 à 21:16, Ron Sher ron
?
Thanks,
Ron
On Wednesday, December 10, 2014 10:53:50 PM UTC+2, David Pilato wrote:
No I did not say that. Or I did not mean that. Sorry if it was unclear.
I said: don’t use large sizes:
Never use size:1000 or from:1000.
You should read this:
http://www.elasticsearch.org/guide/en
not for realtime use); again not clear which size is recommended.
So you see - many options and not clear which path to take.
What do you think?
Thanks,
Ron
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving
We had poor experience with has_parent queries and we ended up implementing
it ourselves using 2 steps:
1. Filter the parent documents to get a list of IDs.
2. Filter the child documents and look only for IDs in the list of IDs
from 1
On Wednesday, December 10, 2014 7:48:55 PM UTC+2,
results.
About size, I'd would try and test. It depends on your docs size I believe.
Try with 1 and see how it goes when you increase it. You will may be
discover that getting 10*1 docs is the same as 1*10. :)
Best
David
Le 10 déc. 2014 à 19:09, Ron Sher ron@gmail.com
we have 24 data nodes, 3 master nodes and 3 client nodes.
We use m3.4xlarge for the data nodes
On Tue, Dec 9, 2014 at 4:37 PM, Mark Walkom markwal...@gmail.com wrote:
How many servers are in this cluster?
On 9 December 2014 at 14:36, Ron Sher ron.s...@gmail.com wrote:
Hi,
We have a multi
count to 24 brings you
under this level and also gives you room for growth on an index level.
Having a higher shard count also spreads the query load, and reduces the
amount of thrashing (ie data transfer) if/when a node goes down.
On 9 December 2014 at 15:50, Ron Sher ron@gmail.com
about the effect of
not limiting the count since we're thinking of making a breaking change and
limit this to 100.
Thanks for your help
Ron
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails
for your help,
Ron
--
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
to
lower than the client side timeout.
The server side timeout should return partial results if possible.
On Nov 30, 2014 10:41 AM, Ron Sher ron@gmail.com javascript:
wrote:
Hi all,
I want to make sure the search query doesn't exceed some limit.
I've seen the option to use a setTimeout vs
],
publish_address : inet[/ipaddress:9300]
},
http : {
bound_address : inet[/0:0:0:0:0:0:0:0:9200],
publish_address : inet[/ipaddress:9200],
max_content_length_in_bytes : 104857600
},
plugins : [ ]
}
}
}
Any help would be greatly appreciated.
ron
On Tue
starting to run queries in a loop that may suggest that facets are
actually (a bit) faster.
Thanks for your feedback,
Ron
--
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
Thanks for the answer and sorry for the duplicate (posted from a different
source by mistake)
On Monday, August 18, 2014 11:02:47 AM UTC+3, Adrien Grand wrote:
Hi Ron,
The cause of this issue is that Elasticsearch uses Lucene's internal doc
IDs as tie-breakers. Internal doc IDs might
such behavior? Any suggestions on resolving this?
We're using version 1.3.1.
Thanks,
Ron
--
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
-with-chef-solo/
here
http://www.elasticsearch.org/tutorials/deploying-elasticsearch-with-chef-solo/
but it looks like it's suitable for first installation or a complete
cluster shutdown.
I'm looking for an automated rolling upgrade of elasticsearch.
Any suggestion?
Thanks,
Ron
--
You received
(one is enough)
On Sunday, February 2, 2014 8:50:47 AM UTC+1, Ron Sher wrote:
again, using 0.90.10.
This is what I did:
bin/plugin -i elasticsearch/marvel/latest
/etc/init.d/elasticsearch restart
Did the same on a different cluster - still doesn't work.
On Sun, Feb 2, 2014 at 9:45 AM
)
at java.lang.Thread.run(Thread.java:724)
What now?
On Sun, Feb 2, 2014 at 11:29 AM, Ron Sher ron.s...@gmail.com wrote:
This is what I see in the log after the restart:
STATUS | wrapper | 2014/02/02 11:26:54 | Copyright (C) 1999-2011 Tanuki
Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2014/02
)
On Sun, Feb 2, 2014 at 3:43 PM, Ron Sher ron.s...@gmail.com wrote:
I've noticed that I didn't have a logging.yml (was called logging.xml
instead).
Changed that and then I see:
[2014-02-02 15:42:19,824][ERROR][marvel.agent.exporter] error sending
data
java.io.FileNotFoundException: http
marvel where sends data
to. See
http://www.elasticsearch.org/guide/en/marvel/current/index.html#stats-export
On Sun, Feb 2, 2014 at 3:23 PM, Ron Sher ron.s...@gmail.com wrote:
The beginning of the log looks like:
[2014-02-02 15:38:56,003][INFO ][node ] [hades3]
version
I don't see any indices of marve:
ron@ron-VirtualBox:~$ curl -XGET http://hades3:1/.marvel*/_stats?
clearstore
curl: (7) couldn't connect to host
ron@ron-VirtualBox:~$ curl -XGET http://hades3:9200/.marvel*/_stats?
clearstore
{error:IndexMissingException[[.marvel*] missing],status:404
Tony,
What do you mean by activity?
Indeed I've added marvel to an already running cluster and no data is shown
in the dashboard and I don't see any marvel index
Ron
On Fri, Jan 31, 2014 at 12:47 AM, Tony Su tonysu...@gmail.com wrote:
Just a FYI
I just installed Marvel and I noticed you
again, using 0.90.10.
This is what I did:
bin/plugin -i elasticsearch/marvel/latest
/etc/init.d/elasticsearch restart
Did the same on a different cluster - still doesn't work.
On Sun, Feb 2, 2014 at 9:45 AM, Boaz Leskes b.les...@gmail.com wrote:
Hi Ron,
It looks like no data is sent. What
Hey,
Just tried installing the plugin.
Installation was easy (bin/plugin -i elasticsearch/marvel/latest followed
by a restart) by then the plugin shows an empty dashboard.
Am I missing something?\
Thanks,
Ron
--
You received this message because you are subscribed to the Google Groups
We have 0.90.10
On Thu, Jan 30, 2014 at 2:41 PM, DH ciddp...@gmail.com wrote:
Hello,
I had the same problem.
For me, It was because I didn't pay attention enough.
What is your version of ES? You need to have a 90.9 or higher. On my
former 0.90.5, the pugin was detected but showed nothing.
33 matches
Mail list logo
