his means we just can't use stopwords out of the box. In terms of what's
in the index, "food" and "cats" and "horse" are present. I use the stemming
to also get "cat" and "horses" although i have to really get into testing
tha
Hi,
We have users typing stuff like "food for dogs" and we've indexed the data
with "dogfood". What is the best strategy to get a match with
elasticsearch's filters and or analyzers?
Thanks,
Maarten
--
You received this message because you are subscribed to the Google Groups
"elasticsearch"
Hi,
I'm looking into elasticsearch to replace our current engine. The most
challenging feature is the 'free text search' and finding relevant hits.
For our catalogue wide search we currently use *48 fields* to search
through like producttitle, author, brand, synonyms, keywords, color,
platform
Hi,
I'm trying to figure out the correct mapping for searching for exact values
but lowercased. I thought this would work:
"exact_lowercase": {
"filter": [
"lowercase"
],
"type": "custom",
"tokenizer": "keyword"
}
...
Hi,
I have the following (json) query i use:
{
"fields": ["ID","ID2"],
"query": {
"filtered": {
"query": {
"multi_match": {
"query": "",
"fields": ["FIELD1.not_analyzed","FIELD2.partial"]
}
t;
> On Sun, Sep 28, 2014 at 1:17 PM, Maarten Roosendaal > wrote:
>
>> Hi,
>>
>> I'm trying to solve the following use case with elasticsearch: we want to
>> provide users with autocomplete functionality but the results of a typed
>> term shoul
Hi,
I'm trying to solve the following use case with elasticsearch: we want to
provide users with autocomplete functionality but the results of a typed
term should be aggregated by type of entity in the index, like brand and
creator.
For example, i have this in the index (name, type, score)
br
Hi,
What you can do is include the 'parent' in the sql and give it the value of
the parentId. I think you have to do this in 2 runs, first all the parents,
second all the children.
see
http://elasticsearch-users.115913.n3.nabble.com/JDBC-River-amp-amp-parent-td4029976.html
for
another discus
},
"from": 0,
"size": 50,
"sort": [],
"facets": {}
}
the like_text contains product_id's from a wishlist for which i want to
find similair lists
Op woensdag 8 januari 2014 16:50:53 UTC+1 schreef Maarten Roosendaal:
>
> Hi,
>
> Th
cuments are
> being scored higher than others. MoreLikeThis using the same fulltext
> scoring as far as I know, so term position would affect score.
>
>
> http://lucene.apache.org/core/3_0_3/api/contrib-queries/org/apache/lucene/search/similar/MoreLikeThis.html
>
> Ju
Hi,
I have a question about why the 'more like this' algorithm scores documents
higher than others, while they are (at first glance) the same.
What i've done is index wishlist-documents which contain 1 property:
product_id, this property contains an array of product_id's (e.g. [1234,
, 555
Hi Jörg,
How do i proved the user's wishlist when using the mlt query?
i've tried:
GET http://localhost:9200/wishlists/list/*[id user's wishlist*]/_search/
{
"more_like_this" : {
"fields" : ["product_id"],
"min_term_freq" : 1,
"max_query_terms" : 12
}
}
but it do
Hi,
Not yet, what i did was:
* flatten the data to 1 property (productIds) so it is an array of
productId's
* use the API
and it worked quite nicely, but i have no control over other things like,
only compare to lists with more than 5 productId's.
What i'm not certain of if i could use nested
as a side note: i've modelled a product as a nested document inside the
list-entity
Op maandag 6 januari 2014 12:15:57 UTC+1 schreef Maarten Roosendaal:
>
> Hi,
>
> We want to be able to suggest entities to customers that are similair to
> their entity. For example, i cre
Hi,
We want to be able to suggest entities to customers that are similair to
their entity. For example, i create a *wishlist *and add 10 products to
that list. Another customer also created a wishlist with 20 products on it
and there are *6 *products that are the *same *on both lists. We want t
ription=ccc it
> will match although item 123 has desc=aaa.
>
> Just think carefully how you will search & filter then choose your right
> type.
>
> On Tuesday, December 17, 2013 4:03:07 AM UTC-8, Maarten Roosendaal wrote:
>>
>> Hi,
>>
>> We are looki
nested documents then on an update you will have
> as a result reindexing the parent with all of its children, on the other
> hand parent/child does not have such a behavior
>
> On Tuesday, December 17, 2013 2:03:07 PM UTC+2, Maarten Roosendaal wrote:
>>
>> Hi,
&
e afaik actually
> child documents ensuring to be in the same block of data with the parent.
> If you do changes in the list then you should probably choose to go with
> the parent/child association. Hope that helps
>
> Thomas
>
> Τη Τρίτη, 17 Δεκεμβρίου 2013 2:03:07 μ.μ.
Hi,
We are looking into using elasticsearch and one of the use cases is
customerlists, for example a wishlist. So i can create a list (X-mas
shopping list) with a description, tags and some other metainformation. I
can then add items (with an identifier) to that list and also a custom
descript
19 matches
Mail list logo
