Hi,
I was wondering what is the quickest way to delete all documents associated
with a specified alias or set of aliases.
Referring to the users data flow. Suppose some users unsubscribed and I
want to remove their data to free up unwanted used space, what is the
fastest way of doing this?
Hi David,
Thanks but I'm struggling getting this done. I tried different things. For
example:
csv {
columns = [NAME,DATE,LAT,LONG]
separator = ;
add_tag = [csv_parse_successfull]
}
date {
match = [DATE, dd-MM- HH:mm:ss]
}
It's not an issue IMO but just a default configuration.
FYI here is a sample config file I just used to parse some CSV data:
input {
stdin {}
}
filter {
csv {
separator = ;
columns = [
id,name,slug,uic,uic8_sncf,longitude,latitude,
parent_station_id,is_city,country,
Hello,
I have the following object in my index:
{
user : {
info : {
fname : John,
lname : Stark
},
settings : {
hide_menu : true,
time_offset : 3
}
},
views : [
]
}
And I'd like to create a filter to find all the users whose first name is
John and have time_offset=3
So I need to build a must
Dear All,
I am using elasticsearch 1.4.X. Suppose I have below document indexed, lets
say if i search for priority=2 will it search in entire document as
free-text search?
or it will search only for attribute priority?
{
date_gmt: 2015-04-15,
plugin_id: 1001,
signature: DELETED SERVER-OTHER HP
Thanks for a quick reply David!! Really appreciate it.
Regards.
On 26-Apr-2015 5:57 pm, David Pilato da...@pilato.fr wrote:
If you use a query string or simple query string, searching for priority:2
will search in priority field only.
Using a query dsl with filters will make this more obvious
Yes David, the issue is not related to it.
I changed my code, but annoying can't find the root problem.
client.prepareUpdate(index, type, documentID).setDoc(updateObject).get();
On Saturday, April 25, 2015 at 4:52:48 PM UTC+3, David Pilato wrote:
Not sure it’s your issue but elasticsearch
If you use a query string or simple query string, searching for priority:2 will
search in priority field only.
Using a query dsl with filters will make this more obvious and more efficient
performance wise.
HTH
David
Le 26 avr. 2015 à 14:23, jigish thakar jigishptha...@gmail.com a écrit :
Hi all,
I'm sure I'm not the first one with this idea, but couldn't find anything
on the net which resembles a solution.
My goal is to have a horizontal line expressing a threshold level.
The scenario in questions is a Kibana 4 visualization of NginX request
duration average. I want to set a
Not an exact answer but you could use a filter and stacked lines. Have one
color for above threshold and a different color and under threshold.
Thanks
Ruvi
-Original Message-
From: Yarden Bar ayash.jor...@gmail.com
Sent: 4/26/2015 2:38 PM
To: elasticsearch@googlegroups.com
Hi,
I'm installing Kibana 4.0.0 on Linux x86, using ES 1.5.0 as a back end.
All data in ES is fed through logstash but there is no common prefix like
logstash-*.
All indices are daily based, e.g. analytics-2015.04.25.
On Kibana's initia settings page I do:
1. Check on the Index contains
Hello,
What is the correct syntax of using _primary_first in search and search
template queries?
GET myindex/_search/template?preference=_primary_first
or
GET myindex/_search/template?routing=_primary_first
Is there any verbose mode that can log the list of shards that were
actually
You cannot use wild card prefixes.
There is functionally no difference between * and *-something, as each
index has to be checked to see if it matches, so you might as well just use
*.
On 27 April 2015 at 12:19, Amos S amos.shap...@gmail.com wrote:
Hi,
I'm installing Kibana 4.0.0 on Linux
13 matches
Mail list logo
