duplicates for each "Product," and all, facet counts, paging and sorting is
then inaccurate; so it appears I need do this myself, with multiple Solr
requests.
Is this really the best approach; and if so, should I use the Solr
Deduplication update processor when indexing and queryin
quot; entities having
> purchasable "SKU" entities. But this also means I now have documents
> which are mostly duplicates for each "Product," and all, facet counts,
> paging and sorting is then inaccurate; so it appears I need do this
> myself, with multi
s, if i
> understood your question well enough, answers it.
>
> [1] http://wiki.apache.org/solr/SolrQuerySyntax
> [2] http://wiki.apache.org/solr/FunctionQuery
>
>
> Cheers,
>
>
--
View this message in context:
http://old.nabble.com/Encountering-a-roadblock-with-my-Solr-schema-design...use-dedupe--tp27118977p27120031.html
Sent from the Solr - User mailing list archive at Nabble.com.
M]
>> price = 5
>>
>> Using the data above you can answer your question using a basic Solr
>> query [1] like the following: q=color:green AND price:[0 TO 9,99] AND
>> size:M
>>
>> Of course, you would make this a function query [2] but this, if i
>> understood your
99 or less?" can be easily
>>> answered using a schema like yours.
>>>
>>> id = 1
>>> color = [green, blue]
>>> size = [M, S]
>>> price = 6
>>>
>>> id = 2
>>> color = [red, blue]
>>> size = [L, S]
>>
blem correctly. But i
> >>> believe your first approach is the right one.
> >>>
> >>> Your question: "Which products are available that contain skus with
> >>> color Green, size M, and a price of $9.99 or less?" can be easily
> >>>
:[0 TO 9,99] AND
size:M
Of course, you would make this a function query [2] but this, if i
understood your question well enough, answers it.
[1] http://wiki.apache.org/solr/SolrQuerySyntax
[2] http://wiki.apache.org/solr/FunctionQuery
Cheers,
--
View this message in context:
http://old.nab
"Product," and all, facet counts, paging and sorting is
> then inaccurate; so it appears I need do this myself, with multiple Solr
> requests.
>
> Is this really the best approach; and if so, should I use the Solr
> Deduplication update processor when indexing and querying?
>
> Thanks in advance,
> Kelly
> --
> View this message in context:
> http://old.nabble.com/Encountering-a-roadblock-with-my-Solr-schema-design...use-dedupe--tp27118977p27118977.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
> ~ David Smiley
> Author: http://www.packtpub.com/solr-1-4-enterprise-search-server/
>
--
View this message in context:
http://old.nabble.com/Encountering-a-roadblock-with-my-Solr-schema-design...use-dedupe--tp27118977p27131969.html
Sent from the Solr - User mailing list archive at Nabble.com.
mponent as it existed when I wrote it but it has been updated since
>> then.
>>
>> A recent separate question by you on this list suggests you're going down
>> this path. I would grab the attached SOLR-236.patch file and attempt to
>> apply it to the 1.4 source.
: Dedupe is completely the wrong word. Deduping is something else
: entirely - it is about trying not to index the same document twice.
Dedup can also certainly be used with field collapsing -- that was one of
the initial use cases identified for the SignatureUpdateProcessorFactory
... you can
inct documents ... so use cases
> where people only "distinct" URLs work using field collapse but by default
> all matching documents can still be returned and searches on text in the
> boilerplate markup also still work.
>
>
> -Hoss
>
>
>
--
View thi
same" but still index
> > all of the URLs and their content as distinct documents ... so use cases
> > where people only "distinct" URLs work using field collapse but by
> default
> > all matching documents can still be returned and searches on text in the
> > b
tent as distinct documents ... so use
> cases
> > > where people only "distinct" URLs work using field collapse but by
> > default
> > > all matching documents can still be returned and searches on text in
> the
> > > boilerplate markup also still work.
> > >
> > >
> > > -Hoss
> > >
> > >
> > >
> >
> > --
> > View this message in context:
> >
> http://old.nabble.com/Encountering-a-roadblock-with-my-Solr-schema-design...use-dedupe--tp27118977p27155115.html
> > Sent from the Solr - User mailing list archive at Nabble.com.
> >
> >
>
14 matches
Mail list logo
