Everything is working great now.
Thanks David
On Wed, Jun 5, 2013 at 12:07 AM, David Smiley (@MITRE.org) <
dsmi...@mitre.org> wrote:
> maxDistErr should be like 0.3 based on earlier parts of this discussion
> since
> your data is to one of a couple hours of the day, not whole days. If it
> was
maxDistErr should be like 0.3 based on earlier parts of this discussion since
your data is to one of a couple hours of the day, not whole days. If it was
whole days, you would use 1. Changing this requires a re-index. So does
changing worldBounds if you do so.
distErrPct should be 0. Changing i
Hi David,
Thanks for your continued help.
I think that you have nailed it on the head for me. I'm 100% sure that I
had previously tried that query without success. I'm not sure if perhaps I
had wrong distErrPct or maxDistErr values...
It's getting late, so I'm going to call it a night (I'm on GM
So "availability" is the absence of any other document's indexed time
duration overlapping with your availability query duration. So I think
you should negate an overlaps query. The overlaps query looks like:
Intersects(-Inf start end Inf). And remember the slight buffering needed
as described o
Here is an example I have tried.
So let's assume that I want to checkIn on the 30th day, and leave on the
115th day.
My query would be:
-availability_spatial:"Intersects( 30 0 3650 115 )"
However, that wouldn't match anything. Here is an example document below so
you can see. (I've not negat
Thanks David.
Query times are really quick and my index is only 20Mb now which is about
what I would expect.
I'm having some problems figuring out what type of query I want to find
*Available* properties with this new points system.
I'm storing bookings against each document. So I have X Y coordi
Hi Chris:
Have you read: http://wiki.apache.org/solr/SpatialForTimeDurations
You're modeling your data sub-optimally. Full precision rectangles
(distErrPct=0) doesn't scale well and you're seeing that. You should
represent your durations as a point and it will take up a fraction of the
space (se
Also, here is a sample query, and the debugQuery output
fq={!cost=200}*:* -availability_spatial:"Intersects(182.6 0 199.4 1)"
Incase the formatting is bad, here is a raw past of the debugQuery:
http://pastie.org/pastes/872/text?key=ksjyboect4imrha0rck8sa
0 8171 true true *:* 1370259235
