First of all thank you for the repsonses/ideas.
The plain idea is to boost products that are sold more for a specific
customer.
I'll discuss this with my customer to see if we can start with limited
functionality as suggested by Walter.
Cheers,
Jan.
On 5 February 2016 at 17:33, Walter Und
This doesn't sound like a great use case for Solr - or any other search
engine for that matter. I'm not sure what you are really trying to
accomplish, but you are trying to put way too many balls in the air to
juggle efficiently. You really need to re-conceptualize your problem so
that it has far f
I would add a multiValued field for buying_customers. Add the customer ID for
each relevant customer to that field. Then use a boost query “bq”, to boost
those.
Try that first before using the hit rate. Always try on/off control before
going proportional. The simple approach will probably give
Hi,
We store 50K products stored in Solr. We have 10K customers and each customer
buys up to 10K of these products. Now we want to influence the results by
adding a field for every customer.
So we end up with 10K fields to influence the results on the buying behavior of
each customer (personal re
; on
> > > approx. 50 fields.
> > >
> > > We are planning to use SOLR 4.1. Following is the hardware
> configuration
> > of
> > > the web server that we plan to install SOLR on:-
> > >
> > > CPU: 2 x Dual Core (4 cores) | RAM: 12GB | Storage: 2
Following is the hardware configuration
> of
> > the web server that we plan to install SOLR on:-
> >
> > CPU: 2 x Dual Core (4 cores) | RAM: 12GB | Storage: 212 GB
> >
> > Questions :
> >
> > 1)What's the best approach when dealing with documents wi
; We are planning to use SOLR 4.1. Following is the hardware configuration of
> the web server that we plan to install SOLR on:-
>
> CPU: 2 x Dual Core (4 cores) | RAM: 12GB | Storage: 212 GB
>
> Questions :
>
> 1)What's the best approach when dealing with documents with lar
t approach when dealing with documents with large number of
> fields. What's the drawback of having a single document with a very large
> number of fields. Does SOLR support documents with large number of fields as
> in my case?
>
> 2)Will there be any performance issue if i def
hat's the best approach when dealing with documents with large number of
> fields. What's the drawback of having a single document with a very large
> number of fields. Does SOLR support documents with large number of fields
> as
> in my case?
>
> 2)Will there be any performanc
ssage-
From: kobe.free.wo...@gmail.com
Sent: Thursday, March 21, 2013 2:56 AM
To: solr-user@lucene.apache.org
Subject: SOLR - Documents with large number of fields ~ 450
Hello All,
Scenario:
My data model consist of approx. 450 fields with different types of data. We
want to include each fiel
with documents with large number of
fields. What's the drawback of having a single document with a very large
number of fields. Does SOLR support documents with large number of fields as
in my case?
2)Will there be any performance issue if i define all of the 450 fields for
indexing? Also if faceting
, roughly, but
depending on relative uniqueness of field values.
-- Jack Krupansky
-Original Message-
From: Keswani, Nitin - BLS CTR
Sent: Monday, May 14, 2012 10:27 AM
To: solr-user@lucene.apache.org
Subject: RE: Documents With large number of fields
Unfortunately I never got any
Performance Monitoring for Solr / ElasticSearch / HBase -
http://sematext.com/spm
>
> From: "Keswani, Nitin - BLS CTR"
>To: "solr-user@lucene.apache.org"
>Sent: Monday, May 14, 2012 10:27 AM
>Subject: RE: Documents With large number
any performance
issues.
Thanks.
Regards,
Nitin Keswani
-Original Message-
From: Jack Krupansky [mailto:j...@basetechnology.com]
Sent: Sunday, May 13, 2012 10:42 PM
To: solr-user@lucene.apache.org
Subject: Re: Documents With large number of fields
I didn't see any response. There
done, assuming a fair number of 64-bit sharded
machines.
-- Jack Krupansky
-Original Message-
From: Darren Govoni
Sent: Sunday, May 13, 2012 7:56 PM
To: solr-user@lucene.apache.org
Subject: Re: Documents With large number of fields
Was there a response to this?
On Fri, 2012-05-04 at 10:27
1) What's the best approach when dealing with documents with large number of
> fields .
> Should I keep a single document with large number of fields or split my
> document into a number of smaller documents where each document would
> consist of some fields
>
> 2) From
ions :
>
> 1) What's the best approach when dealing with documents with large number of
> fields .
> Should I keep a single document with large number of fields or split my
> document into a number of smaller documents where each document would
> consist of some field
faceting on
most of these fields so that I can drilldown to very small set of
Documents.
Here are some of the questions :
1) What's the best approach when dealing with documents with large number of
fields .
Should I keep a single document with large number of fields or split my
document
18 matches
Mail list logo