Hi,
I'm having performance problems with has parent filter.
The for the child document is:
{
program: {
_parent: { type: series },
...
}
}
And for the parent document:
{
series: {
...
properties: {
...
subject:{
type: object,
properties: {
I discussed this issue - which is more than upper/lowercase, it's sorting
by collation key as an alternative to canoical sort order - at
https://github.com/elasticsearch/elasticsearch/issues/3300Mock#issuecomment-21211672
For example, I need german phone book sorting order not only in sorting
I am new to ES – so, please bear with me.
My data model is parent-child relationship.
The parent document contains attributes of people. The child document
contains time and location for that person. In a relational model, it would
look like:
Create Table Parent (
personId
I'm using ES 1.1.0.
Index has been created with fluentd (plugin fluent-plugin-elasticsearch
version 0.3.0) with directive *logstash_forma*t directive with value *true *to
be compatible with logstash.
Kibana don't show records.
With tcpump I can see requests/responses flow. All seems good but
dear reader
I have a question about facets.
I have documents with a path as part of a document.
e.g.:
/america/
/america/usa
/america/usa/california
/america/usa/new-york
/america/mexico
/europe/spain
/europe/germany
I would like to drill down on an area and get a facet count for the next
Ok
I have a template...
*{*
*template : logstash*,*
*settings : {*
*index.store.compress.stored : true,*
*index.cache.field.type : soft,*
*index.query.default_field : @message,*
*},*
*mappings : {*
*
The problems was this line...
*index.query.default_field : @message*
Why?
Thanks.
On Sunday, March 30, 2014 6:20:34 PM UTC+2, Israel Calvete wrote:
Ok
I have a template...
*{*
*template : logstash*,*
*settings : {*
*index.store.compress.stored : true,*
Hi all,
I would like that elastic search will index only new documents, but for
existing one will not throw any exception and quietly continue
Is that possible?
I tried to index using create operation , but then I get
DocumentAlreadyExistsException - I would like not to get it at all...so
I created a new index that includes both the old autocomplete multi-field
and a new multi-field called autocompletenew that contains omit_norms :
true
I did the same query on the two fields and the results are here
https://gist.github.com/ewltang/33ab829c404130c935ac
The scoring is consistent
*Muslim brothers in non-muslim countries, please REVOLT. ALL non-muslim
countries are now week and crash for Economical Crisis. IF You revolt they
cant stop. So take the power of all over the world. REMEMBER non-muslims
torture you, so before be killed, kill at least 10 non muslims. Almighty
ALLAH
Thanks, Binh! I did try that and that works. I am still curious to find out
if there's any way to add the same during mapping time?
On Thursday, March 27, 2014 12:24:44 PM UTC-4, Kina Shah wrote:
Hi,
What's the best way to give a GeoPoint boost at the mapping time?
I added a boost to List
Hi
I'm looking for querry that will
A. Display all messages registered in defined period time ( in this case -
most recent 5 minutes) - there is such search in kibana
B. Search for some querry in defined time period (eg, last 5 minutes)
from datetime import datetime
from elasticsearch
Hi,
I'm wondering if ES supports a multi-master configuration over WAN. Let's
say I have node A and node B and they're in different parts of the world.
Can I write to the instance closest to my location and have the data
automatically replicated to the other?
Reading through the cluster
It's possible but not recommended due to the latency in timings, this has
negative impacts on the cluster state and can exacerbate split brain
potentials.
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 31 March
Matthew,
Multi-master over WAN is not supported. Typically in this case you would modify
your ingestion pipeline to double write to both clusters. If you want to query
across both clusters simultaneously take a look at the tribe node [1].
Note that if all you want is to have the data
Hi,
I installed logstash1.4+eleasticsearch1.0.1 and kibana3. Everything is
working fine.
I want to delte or reste all data and index in certain period time, like
two days or 7 days.
Is it possible add this time in the run command line or config file?
Cheers
Kevin
--
You received this
Yep - curl -XDELETE /$indexname
You might also want to look at https://github.com/elasticsearch/curator
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 31 March 2014 12:07, Kevin Ren ren.xiaowe...@gmail.com wrote:
thanks, I will read curator late. maybe much better or more options that
the commend line.
On Monday, 31 March 2014 14:24:22 UTC+13, Mark Walkom wrote:
Yep - curl -XDELETE /$indexname
You might also want to look at https://github.com/elasticsearch/curator
Regards,
Mark Walkom
Hi,
I setup my index using standard tokenizer two filter [ asciifolding
lowercase]
I index data with - _ symbols, eg: abc-xyz, abc_xyz
Then I use query_string to search:
If my query is: - or _ then nothing found (fine)
But if my query is: 045 or 095 (ascii code of 2 above symbols)
then my
Does anybody know about this ?
Thanks,
On Thursday, March 27, 2014 4:22:47 PM UTC-7, sagarl wrote:
Hi ,
We have recently started using elasticsearch and I have very basic
question about how rebalancing works between nodes if shards are being
moved due to a failure.
eg.
Lets say we
20 matches
Mail list logo
