Any ideas?
On Friday, December 19, 2014 11:40:37 AM UTC+1, Georgeta Boanea wrote:
Hi All,
After upgrading from ES 0.20.6 to 1.3.4 the following messages occurred:
[2014-12-19 10:02:06.714 GMT] WARN ||
elasticsearch[es-node-name][generic][T#14]
org.elasticsearch.cluster.action.shard
Hi,
Does the individual boost factor get honoured for fields getting copied
into a custom _all field via copy_to option?
I am facing issues with the behavior. Have a look at the example below
PUT localhost:9200/investigations/TestCustom/_mapping
{
TestCustom: {
properties: {
I want to configure Kibana in such a way that my different panels have
different indexes. For example, histogram panel uses index 'X'' and table
panel uses index 'Y'.
Is there any way to do this in Kibana 3. As far as I checked, we can set
Index only at Dashboard level and not at Panel level.
Boosting is not supported in copy_to, see
https://github.com/elasticsearch/elasticsearch/pull/4972
Alternative, as quoted from the commit message
Instead, users should either (1) query the common field AND the field that
requires boosting, or (2) the multi_match query will soon be able to
Thanks Jörg.
On Tuesday, December 30, 2014 2:43:20 PM UTC+5:30, Jörg Prante wrote:
Boosting is not supported in copy_to, see
https://github.com/elasticsearch/elasticsearch/pull/4972
Alternative, as quoted from the commit message
Instead, users should either (1) query the common field AND
I would first try without any script.
If it still does not work, you should may be open an issue in the project.
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 30 déc. 2014 à 11:00, Vinay H M vi...@paqs.biz a écrit :
ya shell script can be used ... but this error is
I'm starting working with Elastic and Kibana.
I have indexed some JSON but I think that there're something that I'm
missing.
My JSONs have some simple fields and another field that it's an array, the
schema is:
This bug occurs because you are upgrading to an old version of
elasticsearch (1.3.4). Try the latest version where the bug is fixed:
https://issues.apache.org/jira/browse/LUCENE-5975
On Fri, Dec 19, 2014 at 5:40 AM, Georgeta Boanea gio...@gmail.com wrote:
Hi All,
After upgrading from ES 0.20.6
This is a Cygwin setup problem. Although off-topic, I recommend to run
cygcheck -s -v -r -h cygcheck_output.txt
and post the result text somewhere so Cygwin experts can examine it.
See also https://cygwin.com/cygwin-ug-net/using-utils.html
Jörg
On Mon, Dec 29, 2014 at 11:25 PM, Vilas Reddy
On Monday, 29 December 2014 22:26:24 UTC+1, Vilas Reddy wrote:
Hi,
I am trying to use Perl API for retrieving data from Elasticsearch.
I am using Elasticsearch in windows cygwin.
I need help with installing perl api and using it. I tried the following:
*1. Installed cpan in cygwin and
The Lucene bug is referring to 3.0-3.3 versions, Elasticsearch 0.20.6 is
using Lucene 3.6, is it the same bug?
On Tuesday, December 30, 2014 2:08:48 PM UTC+1, Robert Muir wrote:
This bug occurs because you are upgrading to an old version of
elasticsearch (1.3.4). Try the latest version
Hello,
I have a 3-node ES (v1.2.1) cluster with 1 replica. When there is a node
failure, the cluster rebalances and allocates primary shards(6 per index)
and replicas among the remaining 2 nodes which is fine. But we had an issue
where the disk space filled up and brought the whole cluster
Yes. again, use the latest version (1.4.x). its very simple.
On Tue, Dec 30, 2014 at 8:53 AM, Georgeta Boanea gio...@gmail.com wrote:
The Lucene bug is referring to 3.0-3.3 versions, Elasticsearch 0.20.6 is
using Lucene 3.6, is it the same bug?
On Tuesday, December 30, 2014 2:08:48 PM UTC+1,
I was reading documentation about Kibana and ES and I think that Elastic
doesn't type the nested properties to indicate that some of my fields are
nested. Anyway, I created another index to try it with nested properties
and I can't see them on the field panel from Kibana.
On Tuesday, December
Hi,
I'm currently working on a project that visualizes geospatial data in
Elasticsearch. One of the things I am doing is generating heatmaps with
the geohash grid aggregation. I would like to take this to the extreme
case of gridding down to the individual pixel level to display raster
Is there any way to see the fields of an array in a pretty way in Kibana or
it isn't supported?? Now, I just see them like just one field.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving
Hi Eliott,
The overhead of computing the doc counts is actually low, I don't think you
should worry about it.
On Tue, Dec 30, 2014 at 5:12 PM, Elliott Bradshaw ebradsh...@gmail.com
wrote:
Hi,
I'm currently working on a project that visualizes geospatial data in
Elasticsearch. One of the
This will be possible in Kibana4 with scripted fields
On Monday, December 29, 2014 9:22:51 PM UTC, Ramakrishna N wrote:
Hi,
I have a question regarding the ElasticSearch and Kibana.
My goal is I have to compare two different dates of data by hour/min/sec.
All my data is indexed and
I have about 50 GB of data (1 mil docs) in a single node--8 cores with 32
GB (24 GB heap). I just upgraded from 1.2.4 to 1.4.2, and I noticed that a
few commands take a long time to return, and marvel doesn't work as well as
it used to.
Some of the commands that are slow for me are
I've just installed Elasticsearch 1.4.2 using the RHEL RPM. I noticed that
it didn't create a new user elasticsearch nor did it create a new group
elasticsearch. Nor are any of the directories I'd expect the default
user to be able to read and write owned by anything other than root.
This
Hello Abhimanyu,
Below is a simple example for creating a geo_shape mapping and inserting a
MultiPoint document. For further detail on inserting different geometry
types be sure to have a look at
On Wednesday, December 10, 2014 4:33:12 PM UTC-3, thomas@beatport.com
wrote:
On Monday, August 11, 2014 1:29:56 PM UTC-4, Mike Topper wrote:
Hello,
I'm having trouble coming up with how to supply a field within a nested
object in the multi_match fields list. I'm using the
As you have found so far, you cannot do this.
On 30 December 2014 at 19:44, Ashutosh Parab ashush...@gmail.com wrote:
I want to configure Kibana in such a way that my different panels have
different indexes. For example, histogram panel uses index 'X'' and table
panel uses index 'Y'.
Is
How slow?
Is the load on your system high?
On 31 December 2014 at 05:04, psk...@gmail.com wrote:
I have about 50 GB of data (1 mil docs) in a single node--8 cores with 32
GB (24 GB heap). I just upgraded from 1.2.4 to 1.4.2, and I noticed that a
few commands take a long time to return, and
I am keeping document counts on Y-Axis and Hour of Day(0-23) on X-Axis.
Now in the graph, I need to show hourly data for Dec 10 2014 and Dec 15
2014.
Appreciate your help!
Regards,
Rama
On Tuesday, December 30, 2014 2:46:54 PM UTC-8, Ramakrishna N wrote:
I am started using Kibana4, still I
I just installed ES 1.4.2 from repos on CentOS and it created both user and
group;
[root@vagrant-centos65 ~]# getent passwd|grep elasticsearch
elasticsearch:x:497:497:elasticsearch
user:/usr/share/elasticsearch:/sbin/nologin
It also set the directories it needs to write to to the correct
Thanks for the response Mark!
However, I am trying to understand how massive index can be a problem if
everytime I know which type to query ? Any explanation or link to some
documentation regarding this ?
On Tuesday, December 30, 2014 3:42:20 AM UTC+5:30, Mark Walkom wrote:
Ideally you want
27 matches
Mail list logo
