I agree with Otis's suggestion.
I don't think that the preference table/matrix ( 1)product_id, 2)user_id,
3)score_value) should be indexed in Lucene/Solr. Any key-value/RDBMS/iMDG
updateable storage is fair enough to store preferences lists:
user/sessionID -> { (product, weight), (product, weight)
Message -
| From: "Otis Gospodnetic"
| To: solr-user@lucene.apache.org
| Sent: Saturday, November 24, 2012 7:39:04 PM
| Subject: Re: User context based search in apache solr
|
| On the other hand, people have successfully built recommendation
| engines on
| top of Lucene or Solr before, a
http://manning.com/owen/
>
>
>
> - Original Message -
> | From: "Otis Gospodnetic"
> | To: solr-user@lucene.apache.org
> | Sent: Saturday, November 24, 2012 5:05:53 PM
> | Subject: Re: User context based search in apache solr
> |
> | Hi,
> |
> | I don&#
:
Mahout In Action
http://manning.com/owen/
- Original Message -
| From: "Otis Gospodnetic"
| To: solr-user@lucene.apache.org
| Sent: Saturday, November 24, 2012 5:05:53 PM
| Subject: Re: User context based search in apache solr
|
| Hi,
|
| I don't have a full picture he
Let me re-phrase. In our application de-normalizing "Will" result in to
1. required more amount of memory.
2. degrade search performance (cpu and response time)
Let me give example - Our application has product table with 1 million
entries and users are increasing exponentially.
Hi Erick
Thanks for reply.
In our application having product table with many fields and we are
providing these all fields during search. If we made de-normalized structure
then there is having lots of redundant data and that may result in to
1. required more amount of memory.
2. d
