for all your responses so far!
>
> -Original Message-
> From: kenf_nc [mailto:ken.fos...@realestate.com]
> Sent: Wednesday, April 13, 2011 1:15 PM
> To: solr-user@lucene.apache.org
> Subject: RE: Indexing Question for large dataset
>
> Is NAME a product name? W
Message-
From: kenf_nc [mailto:ken.fos...@realestate.com]
Sent: Wednesday, April 13, 2011 1:15 PM
To: solr-user@lucene.apache.org
Subject: RE: Indexing Question for large dataset
Is NAME a product name? Why would it be multivalue? And why would it appear
on more than one document? Is each
Is NAME a product name? Why would it be multivalue? And why would it appear
on more than one document? Is each 'document' a package of products? And
the pricing tiers are on the package, not individual pieces?
So sounds like you could, potentially, have a PriceListX column for each
user. As your
r all those
columns)?
Example Query:
q=name&fl=NAME,ID&facet=true&facet.field=PRICELIST500
Thanks,
Josh B.
-Original Message-
From: kenf_nc [mailto:ken.fos...@realestate.com]
Sent: Wednesday, April 13, 2011 10:47 AM
To: solr-user@lucene.apache.org
Subject: Re: Indexing Ques
Indexing isn't a problem, it's just disk space and space is cheap. But, if
you do facets on all those price columns, that gets put into RAM which isn't
as cheap or plentiful. Your cache buffers may get overloaded a lot and
performance will suffer.
2000 price columns seems like a lot, could the doc
