hi,
is there any way to indicate that field name path used in the query
represents absolute path ?
looks like elasticsearch is recognizing that field path starts with type
name and removes it before executing query
consider example below:
1. insert two test documents:
POST test/sublocality/1
/guide/en/elasticsearch/reference/current/docs-update.html
Regards,
Karol Gwaj
On Sunday, March 30, 2014 8:28:33 AM UTC+1, Lauri wrote:
Hi,
I'm having performance problems with has parent filter.
The for the child document is:
{
program: {
_parent: { type: series
Hi,
is it possible, with current elasticsearch extensibility model, to create
custom filter handlers ?
so i could do something like this:
{
query :
{
filtered :
{
filter :
{
*my_custom_filter : *
* {*
*
BTW, i will suggest you to avoid using parent/child relationships if your
index contains more than million documents per shard
besides the obvious problems with maintaining parent/child/grandchild
relationships, parent/child queries tend to be quite slow and id_cache
(used to store parent/child
any idea why query below is executing in around 5s:
POST INDEX/PARENT/_search
{
query: {
has_child: {
type: CHILD,
query: {
has_child: {
type: CHILD_SCORE,
query: {
range: {
the results.
search_type = query_then_fetch
But still i am getting different score for same keyword.
On Monday, February 17, 2014 4:50:51 PM UTC+5:30, Karol Gwaj wrote:
your query runs in parallel on multiple shards and score you seeing is
computed independently on every shard
the default
granular scoring:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-function-score-query.html
Cheers,
Karol Gwaj
On Monday, February 17, 2014 11:00:47 AM UTC, Vallabh Bothre wrote:
Dear Friends,
I am using phonetic analysis in elasticsearch to search best
too many question marks :)
try this one:
GET /_analyze?analyzer=standard**text='This is a test'
On Monday, February 17, 2014 10:42:02 AM UTC, rakesh goyal wrote:
How do I run this in chrome sense plugin:
GET /_analyze?analyzer=standard?text='This is a test'
I am getting following
hi,
can elasticsearch sort by rounded date ?
i want to sort by document creation date but rounded to 1 day, something
like that:
sort: [
CreationDate*/1d*
]
solr supports this type of sorting, so i expect elasticsearch is supporting
it too, but i cant find any
Hi,
i run *.../_cache/clear* command on some of my indexes and after that i
started seeing a lot of warnings:
[2014-01-21 11:19:28,706][WARN ][transport.netty ] [node name]
Message not fully read (response) for [9917139] handler
actually the setting is: *index.cache.id.simple.reuse: true*
(just in case if you still having problem with heap memory)
On Friday, December 27, 2013 2:01:57 PM UTC, Jörg Prante wrote:
All parent IDs are loaded into cache by default. Try the setting
index.cache.id.reuse: true
It should
did you tried any of elasticseach health monitoring plugins
for example 'ElasticSearch HQ' have 'Node Diagnostics' option that will
point weak points of your cluster and will suggest possible solution (very
useful if you just starting your adventure with elasticsearch)
also 'bigdesk' is very
Hi,
im doing crash test of small elasticsearch cluster):
- 3 ubuntu micro instance (EC2, 3 zones)
- 2 replicas (one per zone)
- 10 indexes (with 10 shards per index)
- 30k documents indexed in bulks (100 per batch) in parallel on every node
- swap disabled
im using micro instances to simulate a
yep it sounds great, cant wait to see some beta version to play with
i gave a quick look into logstash, but it is not exactly what i want
and feels too 'resources heavy' for me to install additional framework on
every node (or have dedicated nodes for it)
will be nice if elasticsearch team
) and yours
which of course is a DEB build unless you built from source. I'm using the
RPM downloaded directly through the Elasticsearch website.
Tony
On Monday, December 23, 2013 6:16:45 PM UTC-8, Karol Gwaj wrote:
Im using elasticsearch version 0.90.7
by live request, do you mean the situation that user hits elasticsearch
with query, and then waits for elasticsearch river to pull data from some
API (before responding back to user)?
is so then i dont think the river is the way to go here
if in other hand you can populate your index a little
Take a look at default elasticsearch.yml:
https://github.com/elasticsearch/elasticsearch/blob/master/config/elasticsearch.yml
especially this part:
# Any element in the configuration can be replaced with environment variables
# by placing them in ${...} notation. For example:
#
# node.rack:
to work with the mapping above your indexed document will have to look
something like that:
{
id : 1234,
*location : *
*{*
*lat : 53.1,*
*lon : -6.1*
*}*
}
if for some reason your document have to have flat structure, then you can
try computed fields plugin:
Hi,
is there any build-in way to ensure that rivers are equally distributed
across nodes in the elasticsearch cluster ?
(i have like 100 rivers pulling data from different sources and i will like
to avoid situation when they all run on this same node (i want to
distribute the load across
elasticsearch config file supports environment variables (and java system
properties) substitution
for example (elasticsearch.yml):
*node.name: ${name}*
*${name}* will be replaced with environment variable (export
name=hostname) or system property (ES_JAVA_OPTS=-Dname=hostname)
On
20 matches
Mail list logo
