How to use facet filtering with nested documents on ElasticSearch
Hi!
I have the following mapping:
curl -XPUT 'http://localhost:9200/bookstore/user/_mapping' -d '
{
user: {
properties: {
user_id: { type: integer },
gender: { type: string, index : not_analyzed },
age: { type: integer },
age_bracket: { type: string, index : not_analyzed },
current_city: { type: string, index : not_analyzed },
relationship_status: { type: string, index : not_analyzed },
books : {
type: nested,
properties : {
b_oid: { type: string, index : not_analyzed },
b_name: { type: string, index : not_analyzed },
bc_id: { type: integer },
bc_name: { type: string, index : not_analyzed },
bcl_name: { type: string, index : not_analyzed },
b_id: { type: integer }
}
}
}
}
}'
Now, I'd like to run a query where I count the books.b_names for a certain
books.bcl_name (the books category name) and, for example, where the gender
is Male. I'm a little bit confused of how to get this to work. My query
is the following:
curl -XGET 'http://localhost:9200/bookstore/user/_search?pretty=1' -d '{
size: 0,
from: 0,
query: {
match_all: {}
},
facets: {
CategoryFacet: {
terms: {
field: books.b_name,
size: 5,
shard_size: 1000,
order: count
},
nested: books,
facet_filter: {
and: [
{
nested : {
path : books,
query : {
match : {
books.bcl_name : Trivia
}
},
join : false
}
},
{
term: {
gender: Male
}
}
]
}
}
}
}'
So, I'd like to facet_filter on both the nested document as well as the
parent. How can I achieve this, because apparantly it doesnt's work the way
I imagined. The result of my query is the following:
{
took : 320,
timed_out : false,
_shards : {
total : 5,
successful : 5,
failed : 0
},
hits : {
total : 50,
max_score : 1.0,
hits : [ ]
},
facets : {
CategoryFacet : {
_type : terms,
missing : 0,
total : 0,
other : 0,
terms : [ ]
}
}
}
Thanks!
--
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://groups.google.com/d/msgid/elasticsearch/59a95b77-a4d5-47dc-8095-d7124cb0d1ef%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: total.store.size_in_bytes measures what?
Hey, from a quick peek in the source, the StoreStats are generated in Store.stats(), which uses the Lucene Index Directory to get its size. Which again calls file.length() for each file in that directory in the end. So it is the size used by a lucene index in bytes. The indices stats API shows the data for total shards, for primaries only or for replicas and the same per index - so you can decide which data is important to you to count in your monitoring system. Does it make more sense now? --Alex On Wed, Jan 15, 2014 at 7:57 PM, Ryan Pedela rped...@datalanche.com wrote: What does total.store.size_in_bytes from the indices stats APIhttp://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-stats.htmlmeasure? Disk space for the Lucene index? Disk space for the _source data? Disk space for logs and other metadata? Does it count shards? Does it count replicas? Anything else? I know this question has been asked multiple times, but I have not been able to find a succinct breakdown of what is exactly involved in the calculation. The actual equation would be even better! -- 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://groups.google.com/d/msgid/elasticsearch/08534879-a398-4ebf-890a-09ba7bac52c8%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CAGCwEM-FyicftTP-gS2jG1e31ZLejkOxq%2BvmvtsNf%3D6L6qXWKg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Ann] Elasticsearch Windows MSI Installer updated to Java 7u51 (ES 0.90.10)
Hi, i'd like to announce a update of the Windows MSI Installer for Elasticsearch which now installs ES 0.90.10 with Oracle JRE 7 Update 51. It can be found here: https://github.com/salyh/elasticsearch-msi-installer/releases/tag/1.0.90.10 What is Windows MSI Installer for Elasticsearch? Create your own Elasticsearch MSI installer with a customized ES config that fit your needs. Or simply download the standard preconfigured installer that comes configured with: - 2G Heapsize - analysis-phonetic Plugin preinstalled - mapper-attachments Plugin preinstalled - dynamic scripting turned off (for more security) - embedded Java Runtime (Java 7 Update 51 x64 Server JRE) - Windows elasticsearch service will be automatically started by the installer and after OS boots - Uninstalling is supported Runs on x64 Win 7/Server 2008*/Win 2012 Its implemented as a set of non-interactive cmd and Powershell 2 scripts to build (on top of WIX Toolset) a MSI installer for installing Elasticsearch as a windows service. The scripts will fetch Elasticsearch and Java Server JRE (and WIX Toolset) directly from the internet and then they create a MSI installer with an embedded JRE. I hope it is useful for all of you who have to deal with ES and Windows. Suggestions, corrections, improvements are very welcome! Thanks and best regards Hendrik -- 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://groups.google.com/d/msgid/elasticsearch/19c58511-ec48-4a63-8507-7b6315c93a0a%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Retrieving information from elasticsearch, by the order of the input array
Hi everyone! Can't seem to find an answer to my doubt, so I decided to post the question and see if someone can help me. In my application, I have an array of ids which comes from the backend and which is ordered already as I want, for example: [0] = 23, [1] = 12, [2] = 45, [3] = 21 I then ask elasticsearch the information corresponding to each id present in this array, using a terms filter. The problem is the results don't come in the order of the ids I sent, so the results get mixed up, like: [0] = 21, [1] = 45, [2] = 23, [3] = 12 Note that I can't sort in elasticsearch by the sorting that orders the array in the backend. I also can't order them in php as I'm retrieving paginated results from elasticsearch, so if each page had 2 results, elasticsearch could give me the info only for [0] = 21, [1] = 45, so I can't even order them with php. How can I get the results ordered by the input array? Any ideas? Thanks in advance -- 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://groups.google.com/d/msgid/elasticsearch/033ddde5-dc22-43ff-aca2-45d451f28339%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
How to use ElasticSearch Custom Similarity provider classes ?
Hi,
I'm using the following two java files for overriding the Default
Similarity of ElasticSearch 0.90.3 but it's not working for me.
https://github.com/awnuxkjy/es-custom-similarity-provider/tree/master/src/main/java/org/elasticsearch/index/similarity
I have complied the two java files and added the corresponding class files
in my /lib/elasticsearc-0.90.3.jar file in the path
org/elasticsearch/index/similarity. Now, I'm trying to use those files in
my mapping like mentioned in:-
curl -XPOST 'http://host:port/tweeter/' -d '
{
settings: {
similarity: {
index: {
type: org.elasticsearch.index.similarity.CustomSimilarityProvider
},
search: {
type: org.elasticsearch.index.similarity.CustomSimilarityProvider
}
}
}
}'
But it's giving me following error:-
{error:IndexCreationException[[acqindex] failed to create index]; nested:
ElasticSearchIllegalArgumentException[SimilarityProvider [my_similarity] must
have an associated type]; ,status:400}
Can anyone please tell me how can I use these two files for overriding the
default similarity ?
Thanks
--
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://groups.google.com/d/msgid/elasticsearch/86099655-b887-42a8-92e4-92fa1f06ce48%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Ann] Elasticsearch plugins update for 1.0.0.RC1
Hi, after the release of Elasticsearch 1.0.0.RC1, I have updated my plugins: https://github.com/jprante/elasticsearch-analysis-baseform https://github.com/jprante/elasticsearch-analysis-decompound https://github.com/jprante/elasticsearch-analysis-german https://github.com/jprante/elasticsearch-analysis-skos https://github.com/jprante/elasticsearch-analysis-standardnumber https://github.com/jprante/elasticsearch-index-termlist https://github.com/jprante/elasticsearch-knapsack https://github.com/jprante/elasticsearch-langdetect https://github.com/jprante/elasticsearch-river-jdbc https://github.com/jprante/elasticsearch-skywalker https://github.com/jprante/elasticsearch-support All plugin version numbers have been uniformly reset to 1.0.0.RC1.1 so they reflect the Elasticsearch version they belong to. For more info about the plugins, see the Github pages. Feedback, comments, issues are most welcome. Best, Jörg -- 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://groups.google.com/d/msgid/elasticsearch/CAKdsXoFNiL_z8SsCAS7JYwc-pyLgwPiLP5RX-74u%3DuiwuQPrpg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Exact String maching problem
Hi Friends,
I have index on wiki data but when, I am trying to search with title
field. It has to written only these records/ result which title field is
exactly same as I have provided string in query
What I have to?
How will I change existing mapping to add
title: {type: string,index: not_analyzed}
--
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://groups.google.com/d/msgid/elasticsearch/89bc84d7-5e48-4a55-ab44-fe835e604427%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: How can we use elasticsearch custom similarity plugin in mapping ?
Using the function_score you could use a script. Since 0.90.10 you can access term statistics from a script (https://github.com/elasticsearch/elasticsearch/issues/3772), term frequency included. You could for instance emit your own score that takes into account only the term frequency but not the idf. On Thursday, January 16, 2014 9:18:57 AM UTC+1, Jörg Prante wrote: I don't know how to do this by function score, but have you looked at it? Jörg -- 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://groups.google.com/d/msgid/elasticsearch/1db8d628--4150-a2bd-64fcd7839cd0%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: How can we use elasticsearch custom similarity plugin in mapping ?
Is there any java api available for function_score ? On Thu, Jan 16, 2014 at 5:16 PM, Luca Cavanna cavannal...@gmail.com wrote: Using the function_score you could use a script. Since 0.90.10 you can access term statistics from a script ( https://github.com/elasticsearch/elasticsearch/issues/3772), term frequency included. You could for instance emit your own score that takes into account only the term frequency but not the idf. On Thursday, January 16, 2014 9:18:57 AM UTC+1, Jörg Prante wrote: I don't know how to do this by function score, but have you looked at it? Jörg -- 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://groups.google.com/d/msgid/elasticsearch/1db8d628--4150-a2bd-64fcd7839cd0%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CAAVTvp6rZ3yrTL8RMTpzS78-W_GKb7Oj2nED7jTiTfWEzw9amg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: How can we use elasticsearch custom similarity plugin in mapping ?
I tried using FunctionScoreQueryBuilders but there is no such thing available with me. Do I need to use any package for this ? On Thu, Jan 16, 2014 at 6:26 PM, Luca Cavanna cavannal...@gmail.com wrote: Not sure what you mean, the function score is a query that is part of the query DSL. If you are using the java API, you can find the usual query builder, called FunctionScoreQueryBuilder or even use the handy QueryBuilders static methods to create one. On Thu, Jan 16, 2014 at 1:43 PM, Mukul Gupta mukulnit...@gmail.comwrote: Is there any java api available for function_score ? On Thu, Jan 16, 2014 at 5:16 PM, Luca Cavanna cavannal...@gmail.comwrote: Using the function_score you could use a script. Since 0.90.10 you can access term statistics from a script ( https://github.com/elasticsearch/elasticsearch/issues/3772), term frequency included. You could for instance emit your own score that takes into account only the term frequency but not the idf. On Thursday, January 16, 2014 9:18:57 AM UTC+1, Jörg Prante wrote: I don't know how to do this by function score, but have you looked at it? Jörg -- 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://groups.google.com/d/msgid/elasticsearch/1db8d628--4150-a2bd-64fcd7839cd0%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/1tB6yB0m10o/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAAVTvp6rZ3yrTL8RMTpzS78-W_GKb7Oj2nED7jTiTfWEzw9amg%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CADdZ9MWh0f49t5ek9aaKA5AeEgaJEsfwc4XAqaqB5Cbibc0vig%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CAAVTvp7t6P16U0bb1DP0%2Bz%3DgS6dBjMfpCpbNw5WSmeXSHsYCHQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: How can we use elasticsearch custom similarity plugin in mapping ?
I guess you are using a not so recent version of elasticsearch then. Which version are you working on? On Thu, Jan 16, 2014 at 2:21 PM, Mukul Gupta mukulnit...@gmail.com wrote: I tried using FunctionScoreQueryBuilders but there is no such thing available with me. Do I need to use any package for this ? On Thu, Jan 16, 2014 at 6:26 PM, Luca Cavanna cavannal...@gmail.comwrote: Not sure what you mean, the function score is a query that is part of the query DSL. If you are using the java API, you can find the usual query builder, called FunctionScoreQueryBuilder or even use the handy QueryBuilders static methods to create one. On Thu, Jan 16, 2014 at 1:43 PM, Mukul Gupta mukulnit...@gmail.comwrote: Is there any java api available for function_score ? On Thu, Jan 16, 2014 at 5:16 PM, Luca Cavanna cavannal...@gmail.comwrote: Using the function_score you could use a script. Since 0.90.10 you can access term statistics from a script ( https://github.com/elasticsearch/elasticsearch/issues/3772), term frequency included. You could for instance emit your own score that takes into account only the term frequency but not the idf. On Thursday, January 16, 2014 9:18:57 AM UTC+1, Jörg Prante wrote: I don't know how to do this by function score, but have you looked at it? Jörg -- 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://groups.google.com/d/msgid/elasticsearch/1db8d628--4150-a2bd-64fcd7839cd0%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/1tB6yB0m10o/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAAVTvp6rZ3yrTL8RMTpzS78-W_GKb7Oj2nED7jTiTfWEzw9amg%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CADdZ9MWh0f49t5ek9aaKA5AeEgaJEsfwc4XAqaqB5Cbibc0vig%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/1tB6yB0m10o/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAAVTvp7t6P16U0bb1DP0%2Bz%3DgS6dBjMfpCpbNw5WSmeXSHsYCHQ%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CADdZ9MVNbuqDw%3DDHbvzprLvhM%2BT-UWFQwaLm1bX-qsgTzVzf4Q%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cluster state yellow
minimum_master_nodes is a dynamic cluster setting, that means, it can be set via cluster update API. Jörg -- 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://groups.google.com/d/msgid/elasticsearch/CAKdsXoHFgi5Wj%2Bz0P%2Bq3AJj55bTjaNhjGAzj_DHPmVfq6iRpBQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: How can we use elasticsearch custom similarity plugin in mapping ?
My bad. I'm using elasticsearch-0.90.3. I guess it's not available in this version. On Thu, Jan 16, 2014 at 6:56 PM, Luca Cavanna cavannal...@gmail.com wrote: I guess you are using a not so recent version of elasticsearch then. Which version are you working on? On Thu, Jan 16, 2014 at 2:21 PM, Mukul Gupta mukulnit...@gmail.comwrote: I tried using FunctionScoreQueryBuilders but there is no such thing available with me. Do I need to use any package for this ? On Thu, Jan 16, 2014 at 6:26 PM, Luca Cavanna cavannal...@gmail.comwrote: Not sure what you mean, the function score is a query that is part of the query DSL. If you are using the java API, you can find the usual query builder, called FunctionScoreQueryBuilder or even use the handy QueryBuilders static methods to create one. On Thu, Jan 16, 2014 at 1:43 PM, Mukul Gupta mukulnit...@gmail.comwrote: Is there any java api available for function_score ? On Thu, Jan 16, 2014 at 5:16 PM, Luca Cavanna cavannal...@gmail.comwrote: Using the function_score you could use a script. Since 0.90.10 you can access term statistics from a script ( https://github.com/elasticsearch/elasticsearch/issues/3772), term frequency included. You could for instance emit your own score that takes into account only the term frequency but not the idf. On Thursday, January 16, 2014 9:18:57 AM UTC+1, Jörg Prante wrote: I don't know how to do this by function score, but have you looked at it? Jörg -- 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://groups.google.com/d/msgid/elasticsearch/1db8d628--4150-a2bd-64fcd7839cd0%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/1tB6yB0m10o/unsubscribe . To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAAVTvp6rZ3yrTL8RMTpzS78-W_GKb7Oj2nED7jTiTfWEzw9amg%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CADdZ9MWh0f49t5ek9aaKA5AeEgaJEsfwc4XAqaqB5Cbibc0vig%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/1tB6yB0m10o/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAAVTvp7t6P16U0bb1DP0%2Bz%3DgS6dBjMfpCpbNw5WSmeXSHsYCHQ%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CADdZ9MVNbuqDw%3DDHbvzprLvhM%2BT-UWFQwaLm1bX-qsgTzVzf4Q%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CAAVTvp5BFRsSr30hDEjr%3DPb0bFXiL2_iOvMxaEShNU-dc7xV5g%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cluster state yellow
Gotcha, my bad. On 17/01/2014 12:43 AM, joergpra...@gmail.com joergpra...@gmail.com wrote: minimum_master_nodes is a dynamic cluster setting, that means, it can be set via cluster update API. Jörg -- 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://groups.google.com/d/msgid/elasticsearch/CAKdsXoHFgi5Wj%2Bz0P%2Bq3AJj55bTjaNhjGAzj_DHPmVfq6iRpBQ%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CACj2-4JfuGA4wAmTCjMdo2T%2B4cuY96EV1EN3Grc-pDMt%3D3xX%3DA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Match every token position in the field when using synonyms
In my Elasticsearch index I have documents that have multiple tokens at the
same position.
I want to get a document back when I match at least one token at every
position.
The order of the tokens is not important. How can I accomplish that?
I use Elasticsearch 0.90.5.
*Example:*
I index a document like this.
{
field:red car
}
I use a synonym token filter that adds synonyms at the same positions as
the original token.
So now in the field, there are 2 positions:
- Position 1: red
- Position 2: car, automobile
*My solution for now:*
To be able to ensure that all positions match, I index the maximum position
as well.
{
field:red car,
max_position: 2
}
I have a custom similarity that extends from DefaultSimilarity and returns
1 tf(), idf() and lengthNorm(). The resulting score is the number of
matching terms in the field.
Query:
{
custom_score: {
query: {
match: {
field: a car is an automobile
}
},
_script: _score*100/doc[\max_position\]+_score
},
min_score:100
}
Enter code here...
*Problem with my solution:*
The above search should not match the document, because there is no token
red in the query string. But it matches, because Elasticsearch counts the
matches for car and automobile as two matches and that gives a score of 2
which leads to a script score of 102, which satisfies the min_score.
--
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://groups.google.com/d/msgid/elasticsearch/77d52c69-8862-4e10-8036-470bf4ca8189%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: May I use ES as DB to replace MongoDB?
Note, there is a valuable snapshot/restore facility coming in ES 1.0.0, with incremental snapshots. http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/modules-snapshots.html Jörg On Thu, Jan 16, 2014 at 3:37 PM, Craig Lebowitz craiglebow...@gmail.comwrote: I was talking about using ES as a system of record with my friendly IT director today. We were brainstorming about how 'backup would work. The lucene index is immutable, so we can think about ES data as a transaction log. We can recreate from _source at a given time with a scan/scroll archive of docs at an interval, e.g 1h. This is exactly the same as backing up db transaction logs. -- 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://groups.google.com/d/msgid/elasticsearch/efa02928-b2f6-4c0e-a5ce-faf212c3e638%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CAKdsXoFO8GnHowQ5-p-yHCY8ytTkYXitXOgq%3DKu6gOohVcFGgg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: total.store.size_in_bytes measures what?
Yes, it makes more sense. Thanks. Thanks, Ryan Pedela Datalanche CEO, co-founder www.datalanche.com rped...@datalanche.com 513-571-6837 On Thu, Jan 16, 2014 at 2:38 AM, Alexander Reelsen a...@spinscale.de wrote: Hey, from a quick peek in the source, the StoreStats are generated in Store.stats(), which uses the Lucene Index Directory to get its size. Which again calls file.length() for each file in that directory in the end. So it is the size used by a lucene index in bytes. The indices stats API shows the data for total shards, for primaries only or for replicas and the same per index - so you can decide which data is important to you to count in your monitoring system. Does it make more sense now? --Alex On Wed, Jan 15, 2014 at 7:57 PM, Ryan Pedela rped...@datalanche.comwrote: What does total.store.size_in_bytes from the indices stats APIhttp://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-stats.htmlmeasure? Disk space for the Lucene index? Disk space for the _source data? Disk space for logs and other metadata? Does it count shards? Does it count replicas? Anything else? I know this question has been asked multiple times, but I have not been able to find a succinct breakdown of what is exactly involved in the calculation. The actual equation would be even better! -- 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://groups.google.com/d/msgid/elasticsearch/08534879-a398-4ebf-890a-09ba7bac52c8%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/ud9UAxFNMd0/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGCwEM-FyicftTP-gS2jG1e31ZLejkOxq%2BvmvtsNf%3D6L6qXWKg%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CACu89FQ5CCSMc8zR8nrKj%2BACLrkd-ikMM6td7D37NfLoUXf5bQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: 0.90.9 in elasticsearch - indexing with ngrams, search returns 0 results
Hey!
Just tested it with es 1.0.0.RC1 and it's working fine.
See https://gist.github.com/dadoonet/8456535
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 16 janvier 2014 at 14:25:02, thale jacobs (thalejac...@gmail.com) a écrit:
Hello - I am attempting to run a ngram test using elastics 0.90.9. I was able
to replicate the problem I am having in our production system by following the
example from here:
http://blog.rnf.me/2013/exact-substring-search-in-elasticsearch.html
The Mappings looks like this:
{
mappings: {
homes: {
properties: {
desc: {
type: string,
index_analyzer: index_ngram,
search_analyzer: search_ngram
}
}
}
},
settings: {
analysis: {
filter: {
desc_ngram: {
type: ngram,
min_gram: 3,
max_gram: 8
}
},
analyzer: {
index_ngram: {
type: custom,
tokenizer: keyword,
filter: [ desc_ngram, lowercase ]
},
search_ngram: {
type: custom,
tokenizer: keyword,
filter: lowercase
}
}
}
}
}
The mapping is set up as follows:
curl -s -XPUT 'localhost:9200/listings' -d @settings.json
Three records are inserted into the index as follows:
curl -s -XPUT 'localhost:9200/listings/homes/1' -d '{ desc: This is a lovely
home with a large yard. }'
curl -s -XPUT 'localhost:9200/listings/homes/2' -d '{ desc: This large
fixer-upper has a gravelly yard. }'
curl -s -XPUT 'localhost:9200/listings/homes/3' -d '{ desc: A colonial
mansion with a large yard and a pool. }'
The Search looks like this:
curl -s -XGET 'localhost:9200/listings/homes/_search?pretty=true' -d '{ query
: { bool : { must : [ { match : { desc : { query : large ya, type
: phrase } } }, { match : { desc : { query : arge yar, type :
phrase } } }, { match : { desc : { query : rge yard, type :
phrase } } } ] } } }';
The problem is no results are returned. Any input that can be given for a
solution would be appreciated.
Thank you!
--
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://groups.google.com/d/msgid/elasticsearch/4bee1be0-7ee4-4667-b4f7-b51371963928%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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://groups.google.com/d/msgid/elasticsearch/etPan.52d7f74c.2ae8944a.dc5%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/groups/opt_out.
Trouble with has_parent query containing scripted function_score
I have two document types, in a parent-child relationship:
myParent : {
properties : {
weight : {
type : double
}
}
}
myChild : {
_parent : {
type : myParent
},
_routing : {
required : true
}
}
The weight field is to be used for custom scoring/sorting. This query
directly against the parent documents works as intended:
{
query : {
function_score : {
script_score : {
script : _score * doc['weight'].value
}
}
}
}
However, when trying to do similar scoring for the child documents with a
has_parent query, I get an error:
{
query : {
has_parent : {
query : {
function_score : {
script_score : {
script : _score * doc['weight'].value
}
}
},
parent_type : myParent,
score_type : score
}
}
}
The error is:
QueryPhaseExecutionException[[myIndex][3]:
query[filtered(ParentQuery[myParent](filtered(function score
(ConstantScore(*:*),function=script[_score * doc['weight'].value], params
[null]))-cache(_type:myParent)))-cache(_type:myChild)],from[0],size[10]:
Query Failed [failed to execute context rewrite]]; nested:
ElasticSearchIllegalArgumentException[No field found for [weight] in
mapping with types [myChild]];
It seems like instead of taking the result of the scoring function and
applying it to the child, ES is taking the scoring *function* and applying
it to the child, hence the error.
If I don't use score for score_type, the error doesn't occur, although the
results scores are then all 1.0, as documented.
What am I missing here? How can I query these child documents with custom
scoring based on a parent field?
--
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://groups.google.com/d/msgid/elasticsearch/714f8a04-a88a-4a47-8baf-998992353f1f%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
cluster setup
Hi, I have 3 ubuntu VM's on a private network, each has 64GB ram. I started ES Beta2 (need it to use term vector feature) on each node with 30GB heap space and with the following changes in the configuration file: discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: [host1,host2,host3] bootstrap.mlockall: true gateway.type: local gateway.recover_after_nodes: 2 gateway.expected_nodes: 3 discovery.zen.minimum_master_nodes: 2 Sometimes es processes get killed by OOM killer and when I restart a node I ran into situation like host1,host2,host3 thinking all three nodes are connected and form a cluster, and the host3 thinks it is all by itself with status red (names are random) host1 and host2 form one cluster and host2 and host3 forms another cluster. Any idea about what I am doing wrong and any suggestions? I will need to index 20 million documents and have 3 separate indexes with 5 shards 1 replica. Thanks, T -- 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://groups.google.com/d/msgid/elasticsearch/62130b83-40aa-468e-9449-0046497d39ff%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
WARNING failed to prepare/warm after upgrading from 0.90.3 to 0.90.10
Hello, I'm making some test to upgrade from 0.90.3 to 0.90.10 Everything looks good except the following warning in log, below two examples. [2014-01-16 17:27:00,669][WARN ][index.engine.robin ] [integration] [m112][0] failed to prepare/warm java.lang.IllegalMonitorStateException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:485) at org.elasticsearch.search.SearchService$SearchWarmer$2.awaitTermination(SearchService.java:822) at org.elasticsearch.indices.warmer.InternalIndicesWarmer.warm(InternalIndicesWarmer.java:99) at org.elasticsearch.index.engine.robin.RobinEngine$RobinSearchFactory.newSearcher(RobinEngine.java:1652) at org.apache.lucene.search.SearcherManager.getSearcher(SearcherManager.java:155) at org.apache.lucene.search.SearcherManager.init(SearcherManager.java:89) at org.elasticsearch.index.engine.robin.RobinEngine.buildSearchManager(RobinEngine.java:1530) at org.elasticsearch.index.engine.robin.RobinEngine.start(RobinEngine.java:277) at org.elasticsearch.index.shard.service.InternalIndexShard.performRecoveryPrepareForTranslog(InternalIndexShard.java:660) at org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalIndexShardGateway.java:201) at org.elasticsearch.index.gateway.IndexShardGatewayService$1.run(IndexShardGatewayService.java:174) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) [2014-01-16 11:17:36,836][WARN ][index.engine.robin ] [sissor2-pp] [m105][0] failed to prepare/warm java.lang.IllegalMonitorStateException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:503) at org.elasticsearch.search.SearchService$SearchWarmer$2.awaitTermination(SearchService.java:822) at org.elasticsearch.indices.warmer.InternalIndicesWarmer.warm(InternalIndicesWarmer.java:99) at org.elasticsearch.index.engine.robin.RobinEngine$RobinSearchFactory.newSearcher(RobinEngine.java:1652) at org.apache.lucene.search.SearcherManager.getSearcher(SearcherManager.java:155) at org.apache.lucene.search.SearcherManager.init(SearcherManager.java:89) at org.elasticsearch.index.engine.robin.RobinEngine.buildSearchManager(RobinEngine.java:1530) at org.elasticsearch.index.engine.robin.RobinEngine.start(RobinEngine.java:277) at org.elasticsearch.index.shard.service.InternalIndexShard.performRecoveryPrepareForTranslog(InternalIndexShard.java:660) at org.elasticsearch.indices.recovery.RecoveryTarget$PrepareForTranslogOperationsRequestHandler.messageReceived(RecoveryTarget.java:389) at org.elasticsearch.indices.recovery.RecoveryTarget$PrepareForTranslogOperationsRequestHandler.messageReceived(RecoveryTarget.java:363) at org.elasticsearch.transport.netty.MessageChannelHandler$RequestHandler.run(MessageChannelHandler.java:270) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Anybody encounter this problem ? Thanks. Benoît -- 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://groups.google.com/d/msgid/elasticsearch/5f5c95bc-bee1-4cf1-8239-ee45d5f2a5e5%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: 0.90.9 in elasticsearch - indexing with ngrams, search returns 0 results
Hi David - Thanks for the reply. I just tried it on 90.5, 90.9, 90.10, and
1.0.0.RC1. No results were returned in my searches. I forgot to include
that I have ES running on ubuntu if that makes a difference.
Thale
On Thursday, January 16, 2014 10:14:20 AM UTC-5, David Pilato wrote:
Hey!
Just tested it with es 1.0.0.RC1 and it's working fine.
See https://gist.github.com/dadoonet/8456535
--
*David Pilato* | *Technical Advocate* | *Elasticsearch.com*
@dadoonet https://twitter.com/dadoonet |
@elasticsearchfrhttps://twitter.com/elasticsearchfr
Le 16 janvier 2014 at 14:25:02, thale jacobs
(thale...@gmail.comjavascript:)
a écrit:
Hello - I am attempting to run a ngram test using elastics 0.90.9. I was
able to replicate the problem I am having in our production system by
following the example from here:
http://blog.rnf.me/2013/exact-substring-search-in-elasticsearch.html
The Mappings looks like this:
{
mappings: {
homes: {
properties: {
desc: {
type: string,
index_analyzer: index_ngram,
search_analyzer: search_ngram
}
}
}
},
settings: {
analysis: {
filter: {
desc_ngram: {
type: ngram,
min_gram: 3,
max_gram: 8
}
},
analyzer: {
index_ngram: {
type: custom,
tokenizer: keyword,
filter: [ desc_ngram, lowercase ]
},
search_ngram: {
type: custom,
tokenizer: keyword,
filter: lowercase
}
}
}
}
}
The mapping is set up as follows:
curl -s -XPUT 'localhost:9200/listings' -d @settings.json
Three records are inserted into the index as follows:
curl -s -XPUT 'localhost:9200/listings/homes/1' -d '{ desc: This is a
lovely home with a large yard. }'
curl -s -XPUT 'localhost:9200/listings/homes/2' -d '{ desc: This large
fixer-upper has a gravelly yard. }'
curl -s -XPUT 'localhost:9200/listings/homes/3' -d '{ desc: A colonial
mansion with a large yard and a pool. }'
The Search looks like this:
curl -s -XGET 'localhost:9200/listings/homes/_search?pretty=true' -d '{
query : { bool : { must : [ { match : { desc : { query : large
ya, type : phrase } } }, { match : { desc : { query : arge
yar, type : phrase } } }, { match : { desc : { query : rge
yard, type : phrase } } } ] } } }';
The problem is no results are returned. Any input that can be given for a
solution would be appreciated.
Thank you!
--
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 elasticsearc...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/4bee1be0-7ee4-4667-b4f7-b51371963928%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
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://groups.google.com/d/msgid/elasticsearch/7bccf38a-eaa7-4e7b-9f82-a364a1d410df%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Adding _id to JSON instead of URL when adding doc
Excellent, thank you for the clarification. For some reason I was thinking that the bulk operation might put a different type of load on the service just to spin up that operation. Again, thanks for your time! On Wednesday, January 15, 2014 8:06:32 AM UTC-6, Jörg Prante wrote: Bulk request is in ES the same as single request, it is just concatenated so a bulk can be sent from a client over the network in a single step, saving a lot of roundtrips. So if you send a single request, for ES it does not matter if you choose single operation or bulk operation. Jörg -- 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://groups.google.com/d/msgid/elasticsearch/95d1d0fc-6521-4b7c-a05a-52ed4cba1de2%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: 0.90.9 in elasticsearch - indexing with ngrams, search returns 0 results
So you have specific settings in elasticsearch.yml file?
What result do you actually get?
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 16 janvier 2014 at 18:06:58, thale jacobs (thalejac...@gmail.com) a écrit:
Hi David - Thanks for the reply. I just tried it on 90.5, 90.9, 90.10, and
1.0.0.RC1. No results were returned in my searches. I forgot to include that
I have ES running on ubuntu if that makes a difference.
Thale
On Thursday, January 16, 2014 10:14:20 AM UTC-5, David Pilato wrote:
Hey!
Just tested it with es 1.0.0.RC1 and it's working fine.
See https://gist.github.com/dadoonet/8456535
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 16 janvier 2014 at 14:25:02, thale jacobs (thale...@gmail.com) a écrit:
Hello - I am attempting to run a ngram test using elastics 0.90.9. I was able
to replicate the problem I am having in our production system by following the
example from here:
http://blog.rnf.me/2013/exact-substring-search-in-elasticsearch.html
The Mappings looks like this:
{
mappings: {
homes: {
properties: {
desc: {
type: string,
index_analyzer: index_ngram,
search_analyzer: search_ngram
}
}
}
},
settings: {
analysis: {
filter: {
desc_ngram: {
type: ngram,
min_gram: 3,
max_gram: 8
}
},
analyzer: {
index_ngram: {
type: custom,
tokenizer: keyword,
filter: [ desc_ngram, lowercase ]
},
search_ngram: {
type: custom,
tokenizer: keyword,
filter: lowercase
}
}
}
}
}
The mapping is set up as follows:
curl -s -XPUT 'localhost:9200/listings' -d @settings.json
Three records are inserted into the index as follows:
curl -s -XPUT 'localhost:9200/listings/homes/1' -d '{ desc: This is a lovely
home with a large yard. }'
curl -s -XPUT 'localhost:9200/listings/homes/2' -d '{ desc: This large
fixer-upper has a gravelly yard. }'
curl -s -XPUT 'localhost:9200/listings/homes/3' -d '{ desc: A colonial
mansion with a large yard and a pool. }'
The Search looks like this:
curl -s -XGET 'localhost:9200/listings/homes/_search?pretty=true' -d '{ query
: { bool : { must : [ { match : { desc : { query : large ya, type
: phrase } } }, { match : { desc : { query : arge yar, type :
phrase } } }, { match : { desc : { query : rge yard, type :
phrase } } } ] } } }';
The problem is no results are returned. Any input that can be given for a
solution would be appreciated.
Thank you!
--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/4bee1be0-7ee4-4667-b4f7-b51371963928%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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://groups.google.com/d/msgid/elasticsearch/7bccf38a-eaa7-4e7b-9f82-a364a1d410df%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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://groups.google.com/d/msgid/elasticsearch/etPan.52d811f7.216231b.dc5%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/groups/opt_out.
No mapping found error for geo_distance sorting
Hello,
I've set up a mapping on myIndex as follows:
mappings : {
place : {
properties : {
location : {
type : geo_point,
fielddata : {
format : compressed,
precision : 3m
}
}
}
}
}
And indexed data like so:
{_index:myIndex,_type:place,_id:328,_version:2,exists:true,
_source : {location:{lat:42.02397,lon:-87.684965}}
When querying I get an error:
{
index: myIndex,
size: 10,
from: 1,
type: place,
filtered: {
query: {
query_string: test
},
bool: {
must: [
{
geo_distance: {
distance: 150mi,
place.location: {
lat: 41.8781136,
lon: -87.6297982
}
}
}
]
}
},
sort: [
{
geo_distance: {
location: {
lat: 41.8781136,
lon: -87.6297982
},
unit: mi,
order: ASC
}
}
]
}
The error is Parse Failure [No mapping found for [[object Object]] in order to
sort on
I've tried changing location to place.location in the sort.
Also, should I use _geo_distance or geo_distance? Why are they both used in
different documentation?
Thanks!
Travis
--
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://groups.google.com/d/msgid/elasticsearch/452ec200-001d-4347-b756-6350b281d59c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: No mapping found error for geo_distance sorting
Thanks, I already tried that with no luck.
On Thursday, January 16, 2014 11:31:32 AM UTC-6, David Pilato wrote:
See doc:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-sort.html#_geo_distance_sorting
Missing _ I guess
--
*David Pilato* | *Technical Advocate* | *Elasticsearch.com*
@dadoonet https://twitter.com/dadoonet |
@elasticsearchfrhttps://twitter.com/elasticsearchfr
Le 16 janvier 2014 at 18:21:24, Travis Bullock
(travisr...@gmail.comjavascript:)
a écrit:
Hello,
I've set up a mapping on myIndex as follows:
mappings : {
place : {
properties : {
location : {
type : geo_point,
fielddata : {
format : compressed,
precision : 3m
}
}
}
}
}
And indexed data like so:
{_index:myIndex,_type:place,_id:328,_version:2,exists:true,
_source : {location:{lat:42.02397,lon:-87.684965}}
When querying I get an error:
{
index: myIndex,
size: 10,
from: 1,
type: place,
filtered: {
query: {
query_string: test
},
bool: {
must: [
{
geo_distance: {
distance: 150mi,
place.location: {
lat: 41.8781136,
lon: -87.6297982
}
}
}
]
}
},
sort: [
{
geo_distance: {
location: {
lat: 41.8781136,
lon: -87.6297982
},
unit: mi,
order: ASC
}
}
]
}
The error is Parse Failure [No mapping found for [[object Object]] in order
to sort on
I've tried changing location to place.location in the sort.
Also, should I use _geo_distance or geo_distance? Why are they both used
in different documentation?
Thanks!
Travis
--
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 elasticsearc...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/452ec200-001d-4347-b756-6350b281d59c%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
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://groups.google.com/d/msgid/elasticsearch/31154fe7-e730-4147-946a-e8f8c2912949%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: total.store.size_in_bytes measures what?
I did more digging. Turns out that using version 0.90.9, the _source data is included in the calculation. In other words, the stats are the entire disk space used by an index including source data. And it is broken down by indices, primaries, etc as Alex said. I did not test to see if it takes into account source data compression, but it appears that it does. -- 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://groups.google.com/d/msgid/elasticsearch/5210cf67-4cf7-4695-89c3-0b3fb48a6290%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: No mapping found error for geo_distance sorting
Could you reproduce it with a curl recreation as explained here?
http://www.elasticsearch.org/help/
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 16 janvier 2014 at 18:40:12, Travis Bullock (travisrbull...@gmail.com) a
écrit:
Thanks, I already tried that with no luck.
On Thursday, January 16, 2014 11:31:32 AM UTC-6, David Pilato wrote:
See doc:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-sort.html#_geo_distance_sorting
Missing _ I guess
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 16 janvier 2014 at 18:21:24, Travis Bullock (travisr...@gmail.com) a écrit:
Hello,
I've set up a mapping on myIndex as follows:
mappings : {
place : {
properties : {
location : {
type : geo_point,
fielddata : {
format : compressed,
precision : 3m
}
}
}
}
}
And indexed data like so:
{_index:myIndex,_type:place,_id:328,_version:2,exists:true,
_source : {location:{lat:42.02397,lon:-87.684965}}
When querying I get an error:
{
index: myIndex,
size: 10,
from: 1,
type: place,
filtered: {
query: {
query_string: test
},
bool: {
must: [
{
geo_distance: {
distance: 150mi,
place.location: {
lat: 41.8781136,
lon: -87.6297982
}
}
}
]
}
},
sort: [
{
geo_distance: {
location: {
lat: 41.8781136,
lon: -87.6297982
},
unit: mi,
order: ASC
}
}
]
}
The error is Parse Failure [No mapping found for [[object Object]] in order to
sort on
I've tried changing location to place.location in the sort.
Also, should I use _geo_distance or geo_distance? Why are they both used in
different documentation?
Thanks!
Travis
--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/452ec200-001d-4347-b756-6350b281d59c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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://groups.google.com/d/msgid/elasticsearch/31154fe7-e730-4147-946a-e8f8c2912949%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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://groups.google.com/d/msgid/elasticsearch/etPan.52d81c45.3f2dba31.dc5%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/groups/opt_out.
Re: How to use ElasticSearch Custom Similarity provider classes ?
I am assuming that you packaged the two Java files into a jar file and
deploy it to the $ES_PATH lib directory. Elasticsearch will pick up any jar
files in that directory.
Similarities are either set to be the default for all the indices via the
index.similarity.default.type configuration parameter [1] or it must be
associated directly with a field [2]. Use the example from the website,
your mapping would look something like:
{
book : {
properties : {
title : { type : string, similarity : index }
}
}
As stated in the other thread, I believe the example provided in the plugin
is misleading since there is no individual index/search similarity. The
example creates two similarities types, index and search, which use the
same similarity type.
[1]
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-similarity.html
[2]
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#_configuring_similarity_per_field
Cheers,
Ivan
On Thu, Jan 16, 2014 at 8:13 AM, coder mukulnit...@gmail.com wrote:
I solved the error problem but still ElasticSearch is using its Default
Similariy. Can anyone tell me why is it not taking these new
CustomSimilarity files into consideration.
On Thursday, 16 January 2014 16:54:02 UTC+5:30, coder wrote:
Hi,
I'm using the following two java files for overriding the Default
Similarity of ElasticSearch 0.90.3 but it's not working for me.
https://github.com/awnuxkjy/es-custom-similarity-provider/
tree/master/src/main/java/org/elasticsearch/index/similarity
I have complied the two java files and added the corresponding class
files in my /lib/elasticsearc-0.90.3.jar file in the path
org/elasticsearch/index/similarity. Now, I'm trying to use those files
in my mapping like mentioned in:-
curl -XPOST 'http://host:port/tweeter/' -d '
{
settings: {
similarity: {
index: {
type: org.elasticsearch.index.similarity.CustomSimilarityProvider
},
search: {
type: org.elasticsearch.index.similarity.CustomSimilarityProvider
}
}
}
}'
But it's giving me following error:-
{error:IndexCreationException[[acqindex] failed to create index]; nested:
ElasticSearchIllegalArgumentException[SimilarityProvider [my_similarity]
must have an associated type]; ,status:400}
Can anyone please tell me how can I use these two files for overriding the
default similarity ?
Thanks
--
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://groups.google.com/d/msgid/elasticsearch/e082c7b9-9c7d-4b67-94e5-7194fcf2b114%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
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://groups.google.com/d/msgid/elasticsearch/CALY%3DcQA037LOhM2ipiTVj39mm84M1YipVyjAJSFrnrYH9tYb8w%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Exception in thread main java.lang.NoClassDefFoundError: Could not initialize class org.elasticsearch.Version classic Classic list List threaded Threaded 1 message Options Options Classic List
I had been running elasticsearch just fine under Mavericks until a few days ago and now it won't start up. Originally had used homebrew to install with launchctl to load the plist and everything was fine, however, launchctl status now shows 1 which indicates an error. So tried just downloading 0.90.10 and running directly and get this stack trace when trying to launch bin/elasticsearch -f: bin/elasticsearch Exception in thread main java.lang.NoClassDefFoundError: Could not initialize class org.elasticsearch.Version at org.elasticsearch.bootstrap.Bootstrap.buildErrorMessage(Bootstrap.java:252) at org.elasticsearch.bootstrap.Bootstrap.main(Bootstrap.java:236) at org.elasticsearch.bootstrap.ElasticSearch.main(ElasticSearch.java:32) java -version java version 1.7.0_51 Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode) echo $JAVA_HOME /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home There is nothing in the logs/elasticsearch.log. Am guessing a recent Apple update around 1/11/2014 messed something up, or something is fishy with my Java installation. Any tips or suggestions would be greatly appreciated! Thanks, Jeff -- 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://groups.google.com/d/msgid/elasticsearch/f3ce0d6a-969e-43bd-bfd0-4575fa6e78ad%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: having troubles parsing dates
Alex,
Thank-you very much for your reply. I've fixed my issue with your help.
For future reference I added the following to my logstash indexer for
apache;
date {
locale = en
timezone = Europe/Zurich
match = [ apachetime, dd/MMM/:HH:mm:ss Z ]
target = @timestamp
}
Thanks again for your reply.
Cheers,
Ben
On Thu, Dec 12, 2013 at 11:01 AM, Alexander Reelsen a...@spinscale.dewrote:
Hey,
judging from a quick peek at the problem: The value you are trying to
parse as the timestamp field (note: not the logstash @timestamp field) is
an unknown date format. This means it will only happen with apache access
logs. Somehow the timestamp field has already been configured to be of a
different format (from a past log entry most likely).
Two possibilites (note: maybe there are others, I am not a logstash wizard)
* Make the timestamp field a string and do not analyze it (which also
means, you cannot search for it, but usually you are using the @timestamp
field for that anyway)
* Have an own type for the apache access logs in your logstash config,
which uses a special timestamp based mapping format, that fits to CLF
timestamps
See
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping.htmland
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-put-mapping.htmland
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-templates.html
--Alex
On Thu, Dec 12, 2013 at 10:29 AM, Ben Morrice ben.morr...@gmail.comwrote:
Hi Phil,
Unfortunately i'm still seeing the same issue. Like your case this issue
comes and goes as well. I am running a 2 node cluster (ES 0.90.7) with
default configuration. I'm using logstash-1.2.2; however looking at the
debug logs within logstash the events are parsed correctly, they just die
when elasticsearch takes the floor.
Sorry I can't be of any more help... If you have any theories, please
share your thoughts.
Cheers,
Ben
On Wednesday, 11 December 2013 21:26:41 UTC+1, Phil Dougherty wrote:
I'm having the same exact issue. Running on a 4 node cluster and using
ES 0.90.3. Strangely this issue will randomly bite me, and it seems like it
happens when the index is living on a certain server. Were you able to
resolve this issue or could you provide some more information that may help
me resolve this?
On Monday, November 25, 2013 5:36:41 AM UTC-5, Ben Morrice wrote:
Hello,
I have a basic logstash - elasticsearch instance running to parse
apache logs; or at least I did. I don't know what has changed but
elasticsearch is now bailing on my timestamp field and is not able to
correctly parse it.
I'm using logstash standard grok patterns (COMBINEDAPACHELOG in this
case)
Is anyone able to assist me? I'm sure this is a simple fix?!
Please see below an example from my elasticsearch log
[2013-11-25 09:49:47,585][DEBUG][action.bulk ] [Slade,
Hamilton] [logstash-2013.11.25][3] failed to execute bulk item (index)
index {[logstash-2013.11.25][logs][CxGMkA9nSjej7jHdNfXh4g],
source[{message:10.80.5.30 - - [25/Nov/2013:09:49:45 +0100] \GET
/examplerequest HTTP/1.1\ 200 11415 \-\ \Jakarta
Commons-HttpClient/3.1\,@timestamp:2013-11-25T08:49:
47.548Z,@version:1,type:webfrontend,file:/var/
loghttpdssl_access_log,host:example.com,offset:
629386952,clientip:10.80.5.30,ident:-,auth:-,
timestamp:25/Nov/2013:09:49:45 +0100,verb:GET,request:
/examplerequest,httpversion:1.1,response:
200,bytes:11415,referrer:\-\,agent:\Jakarta
Commons-HttpClient/3.1\,tags:[apache]}]}
org.elasticsearch.index.mapper.MapperParsingException: failed to parse
[timestamp]
at org.elasticsearch.index.mapper.core.AbstractFieldMapper.parse(
AbstractFieldMapper.java:398)
at org.elasticsearch.index.mapper.object.ObjectMapper.
serializeValue(ObjectMapper.java:618)
at org.elasticsearch.index.mapper.object.ObjectMapper.
parse(ObjectMapper.java:471)
at org.elasticsearch.index.mapper.DocumentMapper.parse(
DocumentMapper.java:513)
at org.elasticsearch.index.mapper.DocumentMapper.parse(
DocumentMapper.java:457)
at org.elasticsearch.index.shard.service.InternalIndexShard.
prepareCreate(InternalIndexShard.java:342)
at org.elasticsearch.action.bulk.TransportShardBulkAction.
shardIndexOperation(TransportShardBulkAction.java:401)
at org.elasticsearch.action.bulk.TransportShardBulkAction.
shardOperationOnPrimary(TransportShardBulkAction.java:155)
at org.elasticsearch.action.support.replication.
TransportShardReplicationOperationAction$AsyncShardOperationAction.
performOnPrimary(TransportShardReplicationOperationAction.java:556)
at org.elasticsearch.action.support.replication.
TransportShardReplicationOperationAction$AsyncShardOperationAction$1.
run(TransportShardReplicationOperationAction.java:426)
at java.util.concurrent.ThreadPoolExecutor$Worker.
runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(
Re: RC1 - Create Index Exception
Whichever plugin you are using for the ComboAnalyzer is using the wrong class name. Caused by: java.lang.NoClassDefFoundError: org/elasticsearch/ElasticSearchIllegalArgumentException at org.elasticsearch.index.analysis.ComboAnalyzerProvider.get(ComboAnalyzerProvider.java:50) This class was renamed 10 days ago: https://github.com/elasticsearch/elasticsearch/commit/fa16969360ea43667ad11f827bbf86718c18fcc6 The plugin would need to be built against the current code. Cheers, Ivan On Thu, Jan 16, 2014 at 11:38 AM, davrob2 davirobe...@gmail.com wrote: Hi, I'm running through some test cases after upgrading to RC1, I'm getting an issue when I do this: CreateIndexResponse mapping = esNode.getClient() .admin().indices() .create(new CreateIndexRequest(indexName)) .actionGet(); The error I'm getting is this: org.elasticsearch.common.util.concurrent.UncategorizedExecutionException: Failed execution at org.elasticsearch.action.support.AdapterActionFuture.rethrowExecutionException(AdapterActionFuture.java:90) at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:50) at com.cs.cts.crm.elasticsearch.util.ESAdmin.createIndex(ESAdmin.java:347) Full stack trace here: https://gist.github.com/dav-rob/8461844 Any clues? Thanks. David. -- 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://groups.google.com/d/msgid/elasticsearch/d5777a87-f49a-4464-a596-d929b84cd7b8%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CALY%3DcQCTeA_4OCfrCkGxqgvJsJsDEYjTWJxWtm5N_x8s8RBTDw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Question on breaking change (boost) in 1.0.0.RC1 release
Hi all - I have been going through the list of breaking changes in 1.0.0.RC1 and have a question regarding boosting of documents. I see that *Support for document boosting via the _boost field has been removed from Lucene and is deprecated in Elasticsearch as of v1.0.0.RC1. * http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/mapping-boost-field.html#function-score-instead-of-boost Since I didnt really understand if there is a way one can still boost documents during indexing, I wanted to check with this group. So if I correctly understand there would be no mechanism to specify boost value of the documents during indexing time. Is that right? -Amit. -- 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://groups.google.com/d/msgid/elasticsearch/CAAOGaQJbeK0y%3DwzpKBQ7CMP2t_Et8j%3D4QXY6ggLisYLcKADZbQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problem searchingh after update
Hi Alex, It turns out that it was my fault. But this is a tricky one, I'd like to explain what happened for others to benefit. The issue was that I was not storing the field that I was updating. Therefore the getValue was returning empty from the Java API. The reason that I was able to see the updated document via REST api is that I was seeing the _source field. So I went back to my mappings, and corrected the store attribute on the field. Bottom line is _source field already contains the whole document, there's little point in storing individual fields in Lucene other than highlight purposes. Thanks for your answer. On Tue, Jan 14, 2014 at 1:41 PM, Alexander Reelsen a...@spinscale.de wrote: Hey, can you check the update response, if it was successful? Usually a refresh should be sufficient? You are testing the REST API while you are running this test and the REST works and this test doesnt? Also can you provide a complete snippet including indexation and all your calls? The above code doesnt compile and contains many placeholders, so we cannot a complete picture of what you are doing.. A gist would be great! Thanks! --Alex On Sat, Jan 11, 2014 at 1:07 PM, Ukyo Virgden ukyovirg...@gmail.comwrote: Hi, I've just updated to 0.90.10 from 0.90.5, and I'm having some issues with my unit tests. Here's the outline of the test TransportClient c = new TransportClient(settings).addTransportAddress(new InetSocketTransportAddress(localhost, 9300)); SearchResponse res = c.prepareSearch().setIndices(TEST_INDEX).addFields( LIST_OF_FIELDS).setQuery(QueryBuilders.matchQuery(id, SOME ID)). execute().actionGet(); // do the update UpdateResponse updateRes = prepareUpdateRequestForDocument(indexName,document ).setScript( UPDATE SCRIPT ).execute().actionGet(); // via REST API, I see the modified document hence the update is applied. // sleep for a while and repeat search SearchResponse res = c.prepareSearch().setIndices(TEST_INDEX).addFields( LIST_OF_FIELDS).setQuery(QueryBuilders.matchQuery(id, SOME ID)). execute().actionGet(); SearchHit hit = res.getHits().getAt(0); // the document returned in the second search is not the updated document. assert(check document) - fails even if I issue client.admin().indices().prepareRefresh(TEST_INDEX).execute().actionGet (); or client.admin().indices().prepareFlush(TEST_INDEX).execute().actionGet(); Why am I receiving the non-updated old document from the Java API where I immediately see the updated document via rest api? What am I missing? Thanks in advance, Ukyo -- 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://groups.google.com/d/msgid/elasticsearch/71df3e92-cc2d-4b03-acd1-73330e7df914%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/TmXih0KvEC0/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGCwEM_0jF9XA0%3DgRs3%2BCaqLKyed%2BBFX0-y_Ysj5Lh5UaQBZ-A%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CAHZHwzOXLVGQ2_ipduJbjj92MYknwazankhbzqjWacLEH5wjkg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Using a combined field as id mapping in ElasticSearch
I'm using ES 0.90.7.
Is there a way to do _id mapped to a custom value which is based on more
than one field?
http://stackoverflow.com/questions/21041952/using-a-combined-field-as-id-mapping-in-elasticsearch
Like i want _id to combine srId and closeDt as our document key?
this one doesnt work.
{
mappings: {
json: {
_id: {
path: srId.closeDt,
properties: {
srId: {
index: not_analyzed,
type: string
},
closeDt: {
index: not_analyzed,
type: long
}
}
}
}
}
}'
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Using-a-combined-field-as-id-mapping-in-ElasticSearch-tp4047728.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.
--
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://groups.google.com/d/msgid/elasticsearch/1389901947442-4047728.post%40n3.nabble.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Question on breaking change (boost) in 1.0.0.RC1 release
Judging by the commits, the functionality was only deprecated, not removed. https://github.com/elasticsearch/elasticsearch/issues/4664 I believe there are many use cases where it makes sense to boost a document at index time. The process only occurs once instead of every time during queries. That said, as the github issue says, document boosts are very confusing. What it basically does behind the scenes is changing the field norm for every field in the document. If you disable norms on a field, then that document cannot boost on that field. The scoring becomes erratic and hard to explain. You cannot disable length normalization on fields since that would require the field norms, which are needed by the document boosts. Overall it believe it is better to switch to custom scoring at query time. Cheers, Ivan On Thu, Jan 16, 2014 at 11:47 AM, Amit Soni amitson...@gmail.com wrote: Hi all - I have been going through the list of breaking changes in 1.0.0.RC1 and have a question regarding boosting of documents. I see that *Support for document boosting via the _boost field has been removed from Lucene and is deprecated in Elasticsearch as of v1.0.0.RC1. * http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/mapping-boost-field.html#function-score-instead-of-boost Since I didnt really understand if there is a way one can still boost documents during indexing, I wanted to check with this group. So if I correctly understand there would be no mechanism to specify boost value of the documents during indexing time. Is that right? -Amit. -- 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://groups.google.com/d/msgid/elasticsearch/CAAOGaQJbeK0y%3DwzpKBQ7CMP2t_Et8j%3D4QXY6ggLisYLcKADZbQ%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBHBCM7f%2BpZL7ZZ7d7HFzxqTr%3DO5begP%2BcK1JD7Rp3u2w%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Using a combined field as id mapping in ElasticSearch
You should do that on a client level and add a new attribute in your doc or
send the right _id.
My 2 cents.
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 16 janv. 2014 à 20:52, vinamar vina...@gmail.com a écrit :
I'm using ES 0.90.7.
Is there a way to do _id mapped to a custom value which is based on more
than one field?
http://stackoverflow.com/questions/21041952/using-a-combined-field-as-id-mapping-in-elasticsearch
Like i want _id to combine srId and closeDt as our document key?
this one doesnt work.
{
mappings: {
json: {
_id: {
path: srId.closeDt,
properties: {
srId: {
index: not_analyzed,
type: string
},
closeDt: {
index: not_analyzed,
type: long
}
}
}
}
}
}'
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Using-a-combined-field-as-id-mapping-in-ElasticSearch-tp4047728.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.
--
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://groups.google.com/d/msgid/elasticsearch/1389901947442-4047728.post%40n3.nabble.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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://groups.google.com/d/msgid/elasticsearch/22CD0FFA-DDF2-4D73-B96A-6AD75CA15CCF%40pilato.fr.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Tribe nodes
A tribe node is built into a usual Node, so there is no special tribe node class. If you pass parameter like tribe.t1.cluster.name etc. to the Node settings, a tribe service class is used and performs all the necessary work in the background. Basically the API stays the same but certain features will throw errors. In fact, the tribe mode opens one or more internal nodes that attach to different clusters, like specified. By listening to the cluster states, they can be merged. Because the client API does not change compared to a usual Java Node client, I think Kibana can make use of tribe mode right out of the box (but bare with me I am no Kibana expert). Jörg -- 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://groups.google.com/d/msgid/elasticsearch/CAKdsXoEGg1YuS8Lgom_XdLCx%3Dk%2BvscQcBGGMWdmUpwN%2BJye_zA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Indexing PDF and other binary formats
Thanks for the reply. the attachment plugin I understand encodes content before indexing it, this sounds like an expensive operation if we have lots of pdfs. I was thinking extracting text from pdf early on instead and deal with text instead. Does the plugin also work for binaries like images? On Thursday, January 16, 2014 4:12:47 PM UTC-5, David Pilato wrote: You can use Tika by yourself (recommended). See how I did it in fsriver project. You can use mapper attachment plugin which is using Tika behind the scene but gives you less control IMHO. About versions, elasticsearch does not keep old versions around. If you need that, you have to manage it yourself. HTH -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 16 janv. 2014 à 20:42, ZenMaster80 sabda...@gmail.com javascript: a écrit : - Is there any literature on how to index pdf documents and binary formats like images? - Versioning question: If I update an already indexed document, I believe ES will update the version number. I am wondering if it keeps the previous document, what if I needed access to the previous document? -- 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 elasticsearc...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a9e8f331-c4bd-4a4c-be5a-b91e4f2f0e26%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/94b706cf-c4de-4f94-87b7-48c9e6e814b0%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Indexing PDF and other binary formats
Yes. Some metadata are extracted with Tika. As you said, you should do that operation before indexation (means only index what you really need). -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 16 janv. 2014 à 22:51, ZenMaster80 sabdall...@gmail.com a écrit : Thanks for the reply. the attachment plugin I understand encodes content before indexing it, this sounds like an expensive operation if we have lots of pdfs. I was thinking extracting text from pdf early on instead and deal with text instead. Does the plugin also work for binaries like images? On Thursday, January 16, 2014 4:12:47 PM UTC-5, David Pilato wrote: You can use Tika by yourself (recommended). See how I did it in fsriver project. You can use mapper attachment plugin which is using Tika behind the scene but gives you less control IMHO. About versions, elasticsearch does not keep old versions around. If you need that, you have to manage it yourself. HTH -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 16 janv. 2014 à 20:42, ZenMaster80 sabda...@gmail.com a écrit : - Is there any literature on how to index pdf documents and binary formats like images? - Versioning question: If I update an already indexed document, I believe ES will update the version number. I am wondering if it keeps the previous document, what if I needed access to the previous document? -- 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 elasticsearc...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a9e8f331-c4bd-4a4c-be5a-b91e4f2f0e26%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/94b706cf-c4de-4f94-87b7-48c9e6e814b0%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/6CD3EB4F-93DD-48BD-98F7-D14E3FDA88CA%40pilato.fr. For more options, visit https://groups.google.com/groups/opt_out.
Re: Tribe nodes
I think it won't work. -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 16 janv. 2014 à 22:52, Mark Walkom ma...@campaignmonitor.com a écrit : Does anyone know if a tribe node can talk to v0.90.* clusters? ie the tribe functionality is only required on the designated tribe node and not all it's connected clusters. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: ma...@campaignmonitor.com web: www.campaignmonitor.com On 17 January 2014 08:48, joergpra...@gmail.com joergpra...@gmail.com wrote: A tribe node is built into a usual Node, so there is no special tribe node class. If you pass parameter like tribe.t1.cluster.name etc. to the Node settings, a tribe service class is used and performs all the necessary work in the background. Basically the API stays the same but certain features will throw errors. In fact, the tribe mode opens one or more internal nodes that attach to different clusters, like specified. By listening to the cluster states, they can be merged. Because the client API does not change compared to a usual Java Node client, I think Kibana can make use of tribe mode right out of the box (but bare with me I am no Kibana expert). Jörg -- 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://groups.google.com/d/msgid/elasticsearch/CAKdsXoEGg1YuS8Lgom_XdLCx%3Dk%2BvscQcBGGMWdmUpwN%2BJye_zA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CAEM624bYH-mxWAOpZD-6Wc-LtEaHrmOxF8RPTPirbtNA5EURpQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/38120DBB-C258-4A5F-A57D-8494FF76AA21%40pilato.fr. For more options, visit https://groups.google.com/groups/opt_out.
Re: Tribe nodes
0.90.* and 1.0.0.RC1 node clients can not talk to each other, discovery fails with errors like [2014-01-16 23:45:40,885][WARN ][discovery.zen.ping.multicast] [John Falsworth] failed to read requesting data from /192.168.1.113:54328 java.io.IOException: No transport address mapped to [17519] at org.elasticsearch.common.transport.TransportAddressSerializers.addressFromStream(TransportAddressSerializers.java:71) at org.elasticsearch.cluster.node.DiscoveryNode.readFrom(DiscoveryNode.java:267) at org.elasticsearch.cluster.node.DiscoveryNode.readNode(DiscoveryNode.java:257) at org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver.run(MulticastZenPing.java:410) at java.lang.Thread.run(Thread.java:724) and tribe mode will not magically overcome this situation. Jörg -- 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://groups.google.com/d/msgid/elasticsearch/CAKdsXoF-waXvHv-M6mTYFFa74bG8aBjTK%2Bg6TbPo5Z%3DkCWap4w%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Using a combined field as id mapping in ElasticSearch
Hi David,
I'm using fsriver plugin. Is there a way to specify a script to generate a
field like how couchDB river plugin is able to do.
http://stackoverflow.com/questions/15421720/how-do-i-index-all-the-revisions-of-a-couchdb-doc-using-elasticsearch-river-plug
{
couchdoc : {
_id : {
path : doc_rev_id
}
}
}
{
type : couchdb,
couchdb : {
script : ctx.doc.doc_rev_id = ctx.doc._id + '_' + ctx.doc._rev
}
}
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Using-a-combined-field-as-id-mapping-in-ElasticSearch-tp4047728p4047738.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.
--
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://groups.google.com/d/msgid/elasticsearch/1389912978917-4047738.post%40n3.nabble.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Exception in thread main java.lang.NoClassDefFoundError: Could not initialize class org.elasticsearch.Version classic Classic list List threaded Threaded 1 message Options Options Classic List s
I guess you try to run ES from a drive where no executables are permitted by the OS (e.g. a shared disk mount, or removable media). Jörg -- 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://groups.google.com/d/msgid/elasticsearch/CAKdsXoG4T7Lz50BR9gZ1o%3D52YdsJqakqX5MOkDmtUY3dC9d_5A%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Query score based on aggregated values
I am wondering if there is a way to use aggregated values inside a query.
Example:
Say our data contains items and their price:
{
id : string
name : string
price : float
}
I want to do a query that returns the top items that have a price far from
the average price of items with the same name.
Example Data:
*ID | Name |Price*
1| Chair | 5.99
2| Chair | 5.99
3| Chair | 59.99
4| Desk | 61.00
5| Desk | 60.00
6| Desk | 59.99
The top response would be ID 3, since 59.99 is way higher than the average
price for a chair.
I believe I need to write a custom score script, but I am not sure how I
can get a reference to the average of items with the same name.
Thank you,
Kevin
--
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://groups.google.com/d/msgid/elasticsearch/8069763d-9ce2-4dfc-afc5-6293c2171828%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Dynamic data into Name Suggester
Hi,
I am pretty new to Elastic Search, please help me find out how can I use
name_suggest on the data which I capture from ldap river.
I am trying to put the value of *first name* and *last name* fetched from
ldap river directly to *name_suggest* input so that these can be used in
suggestions.
*Step 1*. Created index with name_suggestor
curl -X PUT localhost:9200/ldapdata4 -d '
{
mappings: {
persons1 : {
properties : {
dsId : { type : string },
firstName : { type : string },
lastName : { type : string },
name_suggest : {
type : completion
}
}
}
}
}'
Checked the mapping created by running :
http://localhost:9200/ldapdata4/_mapping
{
ldapdata4: {
persons1: {
properties: {
dsId: {
type: string
},
firstName: {
type: string
},
lastName: {
type: string
},
name_suggest: {
type: completion,
analyzer: simple,
payloads: false,
preserve_separators: true,
preserve_position_increments: true,
max_input_len: 50
},
}
}
}
}
*Step 2: *Restarted the elastic search instance and it fetched the data
from ldap.
curl -XPUT 'localhost:9200/_river/my_ldap_river1/_meta' -d '{
type : ldap,
ldap : {
host : lookup-uat.mycomp.com,
userDn : ,
credentials : ,
baseDn : ou=people,o=mycomp,
filter : (objectClass=person),
poll : 86400s,
scope : subtree,
attributes : [
mycompDSID,
mycompDSID,
givenName,
mycompLastName,
],
fields : [
_id,
dsId,
firstName,
lastName
],
*name_suggest : {*
* input : [firstName,*
* lastName*
* ]*
* }*
},
index : {
index : ldapdata4,
type : persons1
}
}'
*Step 3: Checked the data inserted and found name_suggestor is not
populated*
http://localhost:9200/ldapdata4/_search?pretty=trueq=*:*
{
took : 3,
timed_out : false,
_shards : {
total : 5,
successful : 5,
failed : 0
},
hits : {
total : 4,
max_score : 1.0,
hits : [ {
_index : ldapdata4,
_type : persons1,
_id : 143,
_score : 1.0, _source :
{lastName:[babot,babbott],firstName:Aarun}
}, {
_index : ldapdata4,
_type : persons1,
_id : 93,
_score : 1.0, _source :
{lastName:sacskerson,firstName:test}
}
Please help me, how to put the dynamic data into name suggester.
--
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://groups.google.com/d/msgid/elasticsearch/d022942a-479b-43e9-83c0-8dbb9eeb8208%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Newbie question about analyzed vs not analyzed
I am just learning ES and would appreciate a quick explanation on analyzed vs not analyzed searches. My basic understanding is that unless indicated otherwise, fields are analyzed during indexing time but when it comes to search time, a term query matches documents for terms that are not analyzed, hence it must match exactly. I am not sure what that means exactly because for one, the fields are already analyzed and tokenized during indexing time, secondly, when I execute a term query, it only matches in lowercase but with match or query_string queries, they are case insensitive. Any insights will be much appreciated. Thanks, Bob -- 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://groups.google.com/d/msgid/elasticsearch/65638a99-eda4-4d90-8913-fb89380e63ae%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Newbie question about analyzed vs not analyzed
Oh I think I get it now, the analyzed value in the index is all lowercase
and hence the exact match must be lowercase for an exact match using term
query. When using match query, the term is first analyzed making it
lowercase before doing the search, hence case insensitive. Am I right?
On Thursday, January 16, 2014, Bob bob...@gmail.com wrote:
I am just learning ES and would appreciate a quick explanation on analyzed
vs not analyzed searches. My basic understanding is that unless indicated
otherwise, fields are analyzed during indexing time but when it comes to
search time, a term query matches documents for terms that are not
analyzed, hence it must match exactly. I am not sure what that means
exactly because for one, the fields are already analyzed and tokenized
during indexing time, secondly, when I execute a term query, it only
matches in lowercase but with match or query_string queries, they are case
insensitive. Any insights will be much appreciated.
Thanks,
Bob
--
You received this message because you are subscribed to a topic in the
Google Groups elasticsearch group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/Fs5ZN-JpCdo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscr...@googlegroups.com javascript:_e({}, 'cvml',
'elasticsearch%2bunsubscr...@googlegroups.com');.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/65638a99-eda4-4d90-8913-fb89380e63ae%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
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://groups.google.com/d/msgid/elasticsearch/CAFANT4%2BetJ%3DmQZA1nB29v%3D%2BCfK%3DAOXCLtd1gmE7VTx-X7VRpDA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Newbie question about analyzed vs not analyzed
Correction: meant to say use *term* queries on non-analyzed fields, not *text* queries. On Thu, Jan 16, 2014 at 6:22 PM, Ivan Brusic i...@brusic.com wrote: Correct. A term query does not analyze the terms, while a match query does. Generally, you should use text queries on non-analyzed fields, and match queries on analyzed ones. Analysis does not always mean lowercasing terms, but that is what the default (standard) analyzer does. All these concepts derive from Lucene. Cheers, Ivan On Thu, Jan 16, 2014 at 6:07 PM, Bob Ngu bob...@gmail.com wrote: Oh I think I get it now, the analyzed value in the index is all lowercase and hence the exact match must be lowercase for an exact match using term query. When using match query, the term is first analyzed making it lowercase before doing the search, hence case insensitive. Am I right? On Thursday, January 16, 2014, Bob bob...@gmail.com wrote: I am just learning ES and would appreciate a quick explanation on analyzed vs not analyzed searches. My basic understanding is that unless indicated otherwise, fields are analyzed during indexing time but when it comes to search time, a term query matches documents for terms that are not analyzed, hence it must match exactly. I am not sure what that means exactly because for one, the fields are already analyzed and tokenized during indexing time, secondly, when I execute a term query, it only matches in lowercase but with match or query_string queries, they are case insensitive. Any insights will be much appreciated. Thanks, Bob -- You received this message because you are subscribed to a topic in the Google Groups elasticsearch group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/Fs5ZN-JpCdo/unsubscribe. To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/65638a99-eda4-4d90-8913-fb89380e63ae%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CAFANT4%2BetJ%3DmQZA1nB29v%3D%2BCfK%3DAOXCLtd1gmE7VTx-X7VRpDA%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/CALY%3DcQC9dmr%2BsD_y%3DuuRYr_Am2sQ-svXBaVutphM61%2BD%3D_3%2Bgw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Query a document by field which is an array of strings?
Hi
My field relevancy_tags is index as an array of strings. A document is
indexed with relevancy_tags = [a, b,c,d]. I want to return the
document if the query is a. I've tried using the term and terms filter
but they don't return any results.
Help :( ?
Mapping:
relevancy_tags : {
type : string
},
--
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://groups.google.com/d/msgid/elasticsearch/fbb77163-246d-46b4-ba4d-25e98acdd308%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Newbie question about analyzed vs not analyzed
Yep, thanks for confirming my understanding, in the case of using term
queries on non-analyzed fields, the search value must match the exact case
of the original value if I understand this correctly.
Bob
On Jan 16, 2014, at 6:23 PM, Ivan Brusic
i...@brusic.comjavascript:_e({}, 'cvml', 'i...@brusic.com');
wrote:
Correction: meant to say use *term* queries on non-analyzed fields, not
*text* queries.
On Thu, Jan 16, 2014 at 6:22 PM, Ivan Brusic
i...@brusic.comjavascript:_e({}, 'cvml', 'i...@brusic.com');
wrote:
Correct. A term query does not analyze the terms, while a match query
does. Generally, you should use text queries on non-analyzed fields, and
match queries on analyzed ones. Analysis does not always mean lowercasing
terms, but that is what the default (standard) analyzer does. All these
concepts derive from Lucene.
Cheers,
Ivan
On Thu, Jan 16, 2014 at 6:07 PM, Bob Ngu bob...@gmail.comjavascript:_e({},
'cvml', 'bob...@gmail.com');
wrote:
Oh I think I get it now, the analyzed value in the index is all lowercase
and hence the exact match must be lowercase for an exact match using term
query. When using match query, the term is first analyzed making it
lowercase before doing the search, hence case insensitive. Am I right?
On Thursday, January 16, 2014, Bob bob...@gmail.com javascript:_e({},
'cvml', 'bob...@gmail.com'); wrote:
I am just learning ES and would appreciate a quick explanation on
analyzed vs not analyzed searches. My basic understanding is that unless
indicated otherwise, fields are analyzed during indexing time but when it
comes to search time, a term query matches documents for terms that are not
analyzed, hence it must match exactly. I am not sure what that means
exactly because for one, the fields are already analyzed and tokenized
during indexing time, secondly, when I execute a term query, it only
matches in lowercase but with match or query_string queries, they are case
insensitive. Any insights will be much appreciated.
Thanks,
Bob
--
You received this message because you are subscribed to a topic in the
Google Groups elasticsearch group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/Fs5ZN-JpCdo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/65638a99-eda4-4d90-8913-fb89380e63ae%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 javascript:_e({},
'cvml', 'elasticsearch%2bunsubscr...@googlegroups.com');.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAFANT4%2BetJ%3DmQZA1nB29v%3D%2BCfK%3DAOXCLtd1gmE7VTx-X7VRpDA%40mail.gmail.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to a topic in the
Google Groups elasticsearch group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/Fs5ZN-JpCdo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscr...@googlegroups.com javascript:_e({}, 'cvml',
'elasticsearch%2bunsubscr...@googlegroups.com');.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQC9dmr%2BsD_y%3DuuRYr_Am2sQ-svXBaVutphM61%2BD%3D_3%2Bgw%40mail.gmail.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
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://groups.google.com/d/msgid/elasticsearch/CAFANT4%2BF6hMvOZ1nYSM2thw2z15ENvff3Jo%3DzQAb1xp%2Bb1Exig%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Using a combined field as id mapping in ElasticSearch
No. Scripts are not supported in fsriver. What do you want to add with scripts?
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 16 janv. 2014 à 23:56, vinamar vina...@gmail.com a écrit :
Hi David,
I'm using fsriver plugin. Is there a way to specify a script to generate a
field like how couchDB river plugin is able to do.
http://stackoverflow.com/questions/15421720/how-do-i-index-all-the-revisions-of-a-couchdb-doc-using-elasticsearch-river-plug
{
couchdoc : {
_id : {
path : doc_rev_id
}
}
}
{
type : couchdb,
couchdb : {
script : ctx.doc.doc_rev_id = ctx.doc._id + '_' + ctx.doc._rev
}
}
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Using-a-combined-field-as-id-mapping-in-ElasticSearch-tp4047728p4047738.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.
--
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://groups.google.com/d/msgid/elasticsearch/1389912978917-4047738.post%40n3.nabble.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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://groups.google.com/d/msgid/elasticsearch/68BBAFDD-7AD7-47CD-BB9F-1B77886EC10F%40pilato.fr.
For more options, visit https://groups.google.com/groups/opt_out.
Store ES query output
I want to store ES query output back to ES. will it possible? -- 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://groups.google.com/d/msgid/elasticsearch/047e145b-b9ec-4cfa-ae91-826127e887b0%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Wrong function names documented for IndexResponse
http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/current/index_.html IndexResponse response = client.prepareIndex(twitter, tweet) .setSource(json) .execute() .actionGet(); IndexResponse object will give you report: // Index name String _index = response.index(); // Type name String _type = response.type(); // Document ID (generated or not) String _id = response.id(); // Version (if it's the first time you index this document, you will get: 1) long _version = response.version(); index() - getIndex() type() - getType() id() - getId() version() - getVersion() Please make the correction. -- 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://groups.google.com/d/msgid/elasticsearch/16c87c0d-0b9e-4b9f-b6f0-271dfa533bf9%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: How to use ElasticSearch Custom Similarity provider classes ?
Thanks a lot. It really solved my problem.
On Thu, Jan 16, 2014 at 11:22 PM, Ivan Brusic i...@brusic.com wrote:
I am assuming that you packaged the two Java files into a jar file and
deploy it to the $ES_PATH lib directory. Elasticsearch will pick up any jar
files in that directory.
Similarities are either set to be the default for all the indices via the
index.similarity.default.type configuration parameter [1] or it must be
associated directly with a field [2]. Use the example from the website,
your mapping would look something like:
{
book : {
properties : {
title : { type : string, similarity : index }
}
}
As stated in the other thread, I believe the example provided in the
plugin is misleading since there is no individual index/search similarity.
The example creates two similarities types, index and search, which use
the same similarity type.
[1]
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-similarity.html
[2]
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#_configuring_similarity_per_field
Cheers,
Ivan
On Thu, Jan 16, 2014 at 8:13 AM, coder mukulnit...@gmail.com wrote:
I solved the error problem but still ElasticSearch is using its Default
Similariy. Can anyone tell me why is it not taking these new
CustomSimilarity files into consideration.
On Thursday, 16 January 2014 16:54:02 UTC+5:30, coder wrote:
Hi,
I'm using the following two java files for overriding the Default
Similarity of ElasticSearch 0.90.3 but it's not working for me.
https://github.com/awnuxkjy/es-custom-similarity-provider/
tree/master/src/main/java/org/elasticsearch/index/similarity
I have complied the two java files and added the corresponding class
files in my /lib/elasticsearc-0.90.3.jar file in the path
org/elasticsearch/index/similarity. Now, I'm trying to use those files
in my mapping like mentioned in:-
curl -XPOST 'http://host:port/tweeter/' -d '
{
settings: {
similarity: {
index: {
type:
org.elasticsearch.index.similarity.CustomSimilarityProvider
},
search: {
type:
org.elasticsearch.index.similarity.CustomSimilarityProvider
}
}
}
}'
But it's giving me following error:-
{error:IndexCreationException[[acqindex] failed to create index];
nested: ElasticSearchIllegalArgumentException[SimilarityProvider
[my_similarity] must have an associated type]; ,status:400}
Can anyone please tell me how can I use these two files for overriding the
default similarity ?
Thanks
--
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://groups.google.com/d/msgid/elasticsearch/e082c7b9-9c7d-4b67-94e5-7194fcf2b114%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
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://groups.google.com/d/msgid/elasticsearch/CALY%3DcQA037LOhM2ipiTVj39mm84M1YipVyjAJSFrnrYH9tYb8w%40mail.gmail.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
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://groups.google.com/d/msgid/elasticsearch/CAAVTvp7USq9Z7j%2BcPVEmK3u%3DxUMfqkBMLx_-ZOuaJDy2YjnFGA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Store ES query output
On a client level. Not by elasticsearch on its own. -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 17 janv. 2014 à 07:18, abhi patel abhi...@gmail.com a écrit : I want to store ES query output back to ES. will it possible? -- 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://groups.google.com/d/msgid/elasticsearch/047e145b-b9ec-4cfa-ae91-826127e887b0%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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://groups.google.com/d/msgid/elasticsearch/25796A8C-6872-4034-ABEC-1474542B9EBC%40pilato.fr. For more options, visit https://groups.google.com/groups/opt_out.
