Hi,
I have a requirement where we need to sort the prices present for products
from all the user stores.
Let us assume if a product is present in 3 stores(store1001,1002,1003) ,i
have created the following fields in my schema.xml
*
*
In my case price range
Hey Peter,
Now I understood your requirement :-).
I come across this http://wiki.apache.org/solr/StatsComponent
have a look if it helps you :-).
--
View this message in context:
http://lucene.472066.n3.nabble.com/get-min-max-prices-as-facets-tp4099501p4099737.html
Sent from the Solr - User
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/get-min-max-prices-as-facets-tp4099501p4099613.html
> Sent from the Solr - User mailing list archive at Nabble.com.
Hi Raymond,
Thanks.
This caching of the main query you mention, is that done automatically or do
I have to do something for that?
--
View this message in context:
http://lucene.472066.n3.nabble.com/get-min-max-prices-as-facets-tp4099501p4099613.html
Sent from the Solr - User mailing list
hen the user filters on brand Audi.
>
> The cheapest Audi is 40,000 and the most expensive 80,000
> In this case I the price range filter changes, and holds a minimum value of
> 40,000 and a max of 80,000. This will a) give the user an indication of all
> Audi prices and b) prevent h
minimum value of
40,000 and a max of 80,000. This will a) give the user an indication of all
Audi prices and b) prevent him from selecting a price for which there is no
car available.
I believe this is different then what you are suggesting right?
--
View this message in context:
http://lucene
I'm not sure if my answer would help you :-).
Usually we do not need to know the min and max prices that our current
database or solr is holding for all the products. Even if you were to that,
would be complex and just make your business logic bigger and tedious.
Instead, we would know wh
values of all products in my data-config.xml.How can I get these lowest
and highest price for the current query?Thanks!
--
View this message in context:
http://lucene.472066.n3.nabble.com/get-min-max-prices-as-facets-tp4099501.html
Sent from the Solr - User mailing list archive at Nabble.com.
q= the spatial query then you simply do score
sorting.
~ David
-
Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
--
View this message in context:
http://lucene.472066.n3.nabble.com/modeling-prices-based-on-daterange-using-multipoints-tp4026011p4026456.html
Sent from the Solr - User mailing list archive at Nabble.com.
eSource, being a
valueSource, would enable me to expose it by name to the frontend?
What I'm saying is: let's say I want to call this implementation
'pricesort' and chain it with other sorts, like: 'sort=pricesort asc,
popularity desc, name asc'. Or use it by name in a functionquery. That
would be possible right?
Geert-Jan
>
> -
> Author:
> http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/modeling-prices-based-on-daterange-using-multipoints-tp4026011p4026256.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
e. You'd have to get back all the values, or maybe write a
DocTransformer to find the specific one.
~ David
-
Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
--
View this message in context:
http://lucene.472066.n3.nabble.com/modeling-prices-based-on-daterange-using-multipoints-tp4026011p4026256.html
Sent from the Solr - User mailing list archive at Nabble.com.
g) [via Lucene] <
ml-node+s472066n4026151...@n3.nabble.com>
> Hi Britske,
> This is a very interesting question!
>
> britske wrote
> ...
> I realize the new spatial-stuff in Solr 4 is no magic bullet, but I'm
> wondering if I could model multiple prices per day as mul
Hi Britske,
This is a very interesting question!
britske wrote
> ...
> I realize the new spatial-stuff in Solr 4 is no magic bullet, but I'm
> wondering if I could model multiple prices per day as multipoints,
> whereas:
>
> - date*duration*nr of persons*roomtyp
t really the point of this
question)
I realize the new spatial-stuff in Solr 4 is no magic bullet, but I'm
wondering if I could model multiple prices per day as multipoints, whereas:
- date*duration*nr of persons*roomtype is modeled as point.x (discretized
in some 20.000 values)
- price mo
On Wed, Mar 2, 2011 at 4:19 PM, Scott K wrote:
> On Wed, Mar 2, 2011 at 12:21, Chris Hostetter
> wrote:
>> historicly it has been because of a fundemental limitation in how the
>> Lucene FieldCache has historicly worked where the array backed FieldCaches
>> use the default numeric value (ie: 0)
On Wed, Mar 2, 2011 at 12:21, Chris Hostetter wrote:
> historicly it has been because of a fundemental limitation in how the
> Lucene FieldCache has historicly worked where the array backed FieldCaches
> use the default numeric value (ie: 0) when docs have no value (but in the
> case of Strings, t
: When I sort by price ascending, documents with no price are listed
: first. I would like them listed last. I tried adding the
: sortMissingLast flag, even though it says it is only for strings, but
it works for any field type *backed* by a string, including the
SortableIntField (and it's breat
issue, but I couldn't find any solutions when
I searched this group and on google.
The map function almost works, but if I use this, then prices of 0 are
treated as null, which is not what I want.
sort=map(price,0,0,99)+asc
schema.xml:
Thanks, Scott
Jonathan- right in one!
Using floats for prices will lead to madness. My mortgage UI kept
changing the loan's interest rate.
On Fri, Feb 4, 2011 at 12:13 PM, Dennis Gearon wrote:
> That's a good idea, Yonik. So, fields that aren't stored don't get displayed,
> s
pache.org
Sent: Fri, February 4, 2011 10:49:42 AM
Subject: Re: prices
On Fri, Feb 4, 2011 at 12:56 PM, Dennis Gearon wrote:
> Using solr 1.4.
>
> I have a price in my schema. Currently it's a tfloat. Somewhere along the way
> from php, json, solr, and back, extra zeroes are gettin
Your prices are just dollars and cents? For actual queries, you might consider
an int type rather than a float type. Multiple by a hundred to put it in the
index, then multiply your values in queries by a hundred before putting them in
the query. Same for range facetting, just divide by 100
s.
>
> So I have two questions, neither of which seemed to be findable with google.
>
> A/ Any way to keep both zeroes going inito a float field? (In the analyzer,
> with
> XML output, the values are shown with 1 zero)
> B/ Can strings be used in range queries like a float
e.
A/ Any way to keep both zeroes going inito a float field? (In the analyzer,
with
XML output, the values are shown with 1 zero)
B/ Can strings be used in range queries like a float and work well for prices?
Dennis Gearon
Signature Warning
It is always a good idea to learn
23 matches
Mail list logo