Solr 4.0 - Join performance

2012-08-02 Thread Eric Khoury
Hello all, I’m testing out the new join feature, hitting some perf issues, as described in Erick’s article (http://architects.dzone.com/articles/solr-experimenting-join). Basically, I’m using 2 objects in solr (this is a simplified view): Item - Id - Name Grant - ItemId - Av

Distributed Searching + unique Ids

2012-08-10 Thread Eric Khoury
hey guys, the spec mentions the following: The unique key field must be unique across all shards. If docs with duplicate unique keys are encountered, Solr will make an attempt to return valid results, but the behavior may be non-deterministic. I'm actually looking to dupli

RE: Distributed Searching + unique Ids

2012-08-14 Thread Eric Khoury
bits of sharding assume that a uniqueKey > exists on one and only one shard. Document counts may be > off. Faceting may be off. Etc. > > Why do you want to duplicate records across shards? What > benefit is this providing? > > This feels like an XY problem... > > Best

RE: Solr 4.0 - Join performance

2012-08-14 Thread Eric Khoury
e/attachment/12536717/SOLR-3076.patch> > 16/Jul/12 21:16 > > also can take it applied from > https://github.com/m-khl/solr-patches/tree/6611 . But the origin source > code might be a little bit old. > Regaining a nightly build, it's not so optimistic - I can't attrac

RE: Solr 4.0 - Join performance

2012-08-14 Thread Eric Khoury
dimension. It's taking a bit of time, but > when finished you should be able to use it for your use case ignoring the > 'y'. Eventually I'd like to develop such a Solr field type for a > numeric/time range to do it more natively but that's a ways off

RE: Solr 4.0 - Join performance

2012-08-14 Thread Eric Khoury
27; > (nor 'y') can't be the full range of a double, and it's not oriented towards > a 'long' time value. There's no JIRA issue for a one-dimensional spatial > field yet; that's pretty far down the priority list. You are certainly not > the

RE: Solr 4.0 - Join performance

2012-08-28 Thread Eric Khoury
David, Solr support for this will come in Solr-3304 I suppose?http://wiki.apache.org/solr/SolrAdaptersForLuceneSpatial4Any idea if this is going to make it into Solr 4.0? Thanks,Eric. > Date: Wed, 15 Aug 2012 07:07:21 -0700 > From: dsmi...@mitre.org > To: solr-user@lucene.apache.org > Subject:

RE: Solr 4.0 - Join performance

2012-08-29 Thread Eric Khoury
ngs this week. > ~ David > > On Aug 28, 2012, at 6:22 PM, Eric Khoury [via Lucene] wrote: > > > David, Solr support for this will come in Solr-3304 I > suppose?http://wiki.apache.org/solr/SolrAdaptersForLuceneSpatial4Any idea if > this is going to make it into Solr 4.0

RE: Solr 4.0 - Join performance

2012-08-29 Thread Eric Khoury
nce > > The solr.GeoHashFieldType is useless; I'd like to see it deprecated then > removed. You'll need to go with unreleased code and apply patches or wait > till Solr 4. > > ~ David > > On Aug 29, 2012, at 10:53 AM, Eric Khoury [via Lucene] wrote: > >

RE: Solr 4.0 - Join performance

2012-09-17 Thread Eric Khoury
To: solr-user@lucene.apache.org > Subject: Re: Solr 4.0 - Join performance > > The solr.GeoHashFieldType is useless; I'd like to see it deprecated then > removed. You'll need to go with unreleased code and apply patches or wait > till Solr 4. > > ~ David >

Using Solr-3304

2012-09-21 Thread Eric Khoury
Hi David, I've installed the latest nightly, and am trying to use the spacial queries.I've defined a field called Rectangle as such: Can you provide some guidance on how to index a field and how to query it? Indexing: X1,Y1,X2,Y2?Querying:? Thanks!Eric.

RE: Using Solr-3304

2012-09-21 Thread Eric Khoury
Thanks David, that's exactly what I needed. One thing, from my experiments, the order seems to be Xmin Ymin Xmax Ymax for both the indexing and the query. Eric.> Date: Fri, 21 Sep 2012 10:34:07 -0700 > From: dsmi...@mitre.org > To: solr-user@lucene.apache.org > Subject: Re: Using Solr-3304 > >

RE: Using Solr-3304

2012-09-21 Thread Eric Khoury
David, I tried increasing the maxDetailDist, as I need 9 decimal value precision. But when I do, I get the following error: Data "SEVERE: org.apache.solr.common.SolrException: ERROR: [doc=MV0005] Error adding field 'rectangle'='45.634801234 1.5 45.634805667 2.5' msg=Y values [-1.7

RE: Using Solr-3304

2012-09-21 Thread Eric Khoury
minutes?). The > boundary minX can be zero which will be your epoch, and the maxX will be the > farthest out in time you can go -- who knows. Set maxDetailDist to 1. > > On Sep 21, 2012, at 4:44 PM, Eric Khoury [via Lucene] wrote: > > >

RE: Using Solr-3304

2012-09-21 Thread Eric Khoury
pport 3d. If you have multi-value relationships > across all 3 parameters you mentioned, then you're a bit stuck. I thought > you had 1d (time) multi-value ranges without needing to correlate that to > other numeric ranges that are also multi-value. > > On Sep 21, 2012, at 5

RE: Using Solr-3304

2012-09-21 Thread Eric Khoury
Thanks David, I'll play around with it. I appreciate the help,Eric. > Date: Fri, 21 Sep 2012 14:47:36 -0700 > From: dsmi...@mitre.org > To: solr-user@lucene.apache.org > Subject: RE: Using Solr-3304 > > When I said "boundary" I meant worldBounds. > > Oh, and set distErrPct="0" to get precise s

Issue using SpatialRecursivePrefixTreeFieldType

2012-10-11 Thread Eric Khoury
Hi David, I'm defining my field as such: When I create a large rectangle, say "10 10 500 11", Solr seems to freeze for quite some time. I haven't looked at your code, but I can imagine the algorithm basically fills in some sort of indexing matrix, and that's what's taking so long for larg

RE: Issue using SpatialRecursivePrefixTreeFieldType

2012-10-16 Thread Eric Khoury
Thanks for the help David, makes sense. I found a workaround, creating much smaller rectangles and updating them more often.Glad to have this functionality, thanks again!Eric. > Date: Fri, 12 Oct 2012 21:06:52 -0700 > From: dsmi...@mitre.org > To: solr-user@lucene.apache.org > Subject: Re: Iss

RE: Issue using SpatialRecursivePrefixTreeFieldType

2012-10-17 Thread Eric Khoury
> > Eric, > Can you please elaborate on your workaround? I'm not sure I get your drift. > ~ David > On Oct 16, 2012, at 12:54 PM, Eric Khoury [via Lucene] wrote: > > > > > Thanks for the help David, makes sense. I found a workaround, creating > > much sm