Putting selling rate in the index is OK for me, I also think that is a good
idea.
The problem is: I don't know how to store the sell rate of the product that
depends on a specific query
Can you please give me your idea about how to store it in the Lucene
document ? (field/value)
Thank you very
: I don't know what is the best way:
that depends on your needs ... if Selling rate changes very infrequently,
or if you are dealing with teh sell rate for lots of books per
query then i'd put it in your index ... if it's constantly in flux and you
only care about the sell rate of one or two book
Yes, that is exactly what I want to do !
My external system gives me sell rate/Top N Selling books matching the user
terms (query)
I don't know what is the best way:
Storing sell rate into lucene Fields of the documents... (multiple
combination) and sort by this field,
or doing something like
: Ok, for the sort object, but my problem is I don't know haox to retrieve (or
: store) information of the sell rate of the products (the sell rate deponds
: on the QUERY ! The sort is different for each queries.)
:
: I imagine to connect to the DB and get sell rate of products for this
: specific
Hello,
Ok, for the sort object, but my problem is I don't know haox to retrieve (or
store) information of the sell rate of the products (the sell rate deponds
on the QUERY ! The sort is different for each queries.)
I imagine to connect to the DB and get sell rate of products for this
specific qu
Sorting on an integer field can be done using any of the Searcher.search
methods which take a "Sort" object.
-Hoss
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
(excuse the semi-appropriate forum to make this comment in - but it is very
brief and may actually help improve the final Lucene-based app)
You may also like to import popularity data from Amazon using their open
APIs and mix the relevancy between your own popularity score and theirs.
Dejan (affi
