To eliminate the possibility of errors, you need to buffer the query as
indicated in the wiki. If you don't and you use a super-small maxDistErr
as you tell me you are doing, then you are merely making the probability
of hitting an error small (perhaps even very very small), but not
nonexistent.
I tried reducing the maxDistErr to "0.01", just to test making it smaller.
I got maxLevels down to 45, and slightly better query times (Indexing time
was about the same). However, my queries are not accurate anymore. I need
to pad by 2 or 3 whole numbers to get a hit now, which won't work in real
u
Kevin,
Those are some good query response times but they could be better. You've
configured the field type sub-optimally. Look again at
http://wiki.apache.org/solr/SpatialForTimeDurations and note in particular
maxDistErr. You've left it at the value that comes pre-configured with
Solr, 0.0
Sorry for the late response. I needed to find the time to load a lot of
extra data (closer to what we're anticipating). I have an index with close
to 220,000 documents, each with at least two coordinate regions anywhere
between -10 billion to +10 billion, but could potentially have up to maybe
half
Oh cool! I'm glad it at least seemed to work. Can you post your
configuration of the field type and report from Solr's logs what the
"maxLevels" is used for this field, which is logged the first time you use
the field type?
Maybe there isn't a limit under 10B after all. Some quick'n'dirty
calcu
What are the dangers of trying to use a range of 10 billion? Simply a
slower index time? Or will I get inaccurate results?
I have tried it on a very small sample of documents, and it seemed to
work. I could spend some time this week trying to get a more robust (and
accurate) dataset loaded to play
Like Hoss said, you're going to have to solve this using
http://wiki.apache.org/solr/SpatialForTimeDurations
Using PointType is *not* going to work because your durations are
multi-valued per document.
It would be useful to create a custom field type that wraps the capability
outlined on the wiki
.loadClass(ClassLoader.java:423)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
... 57 more
Here is my ant build.xml for building the CustomPlugins jar file:
From: Chris Hostetter [hossman_luc...@fucit.org]
Sent: Friday, July 19, 2
}
____________
From: Kevin Stone
Sent: Saturday, July 20, 2013 8:24 AM
To: solr-user@lucene.apache.org
Subject: RE: custom field type plugin
Thank you for the links, they really helped me understand. I see how the
spatial solution works now. I think this could
: I can try again this weekend to get a clean environment. However, the
: order I did things in was the reverse of what you suggest. I got the
Hmmm... then i'm kind of at a loss to explain what you're describing.
need to see more details of the configs, dir structure, jar
structure, etc...
From: Chris Hostetter [hossman_luc...@fucit.org]
Sent: Friday, July 19, 2013 3:15 PM
To: solr-user@lucene.apache.org
Subject: Re: custom field type plugin
: a chromosome (or gene, or other object types). All that really boils
: down to is being able to give a number
: a chromosome (or gene, or other object types). All that really boils
: down to is being able to give a number, e.g. 10234, and return documents
: that have regions containing the number. So you'd have a document with a
: list like ["1:16090","400:8000","40123:43564"], and it should come
12 matches
Mail list logo
