Re: geolocation search ignores distance parameter

On 11/22/2015 5:39 PM, PeterKerk wrote: > Why is the result below returned even though I'm filtering in a radius of 20 > from geocoordinates defined in pt parameter in the querystring? > As you can see the result in _dist_ in this result is is far larger than 20. > >

Re: Highlighting content field problem when using JiebaTokenizerFactory

I've tried to do some minor modification in the code under JiebaSegmenter.java, and the highlighting seems to be fine now. Basically, I created another int called offset2 under process() method. int offset2 = 0; Then I modified the offset to offset2 for this part of the code under process()

RptWithGeometrySpatialField

David, et al. 2 questions. Is this a good tradeoff for performance? Also, RptWithGeometrySpatialField improved performance on what type of searches? Does it support multivalued lat,lon fields? Does LatLonType support multivalued lat,lon fields or only RPT allows for this? -- Bill Bell

Re: geolocation search ignores distance parameter

@Erik: thanks, overlooked that...added fq= before geofilt and now it works :) -- View this message in context: http://lucene.472066.n3.nabble.com/geolocation-search-ignores-distance-parameter-tp4241564p4241571.html Sent from the Solr - User mailing list archive at Nabble.com.

geolocation search ignores distance parameter

Why is the result below returned even though I'm filtering in a radius of 20 from geocoordinates defined in pt parameter in the querystring? As you can see the result in _dist_ in this result is is far larger than 20.

Re: geolocation search ignores distance parameter

Looks like your query doesn't actually make geofilt be an actual fq parameter. > On Nov 22, 2015, at 19:39, PeterKerk wrote: > > Why is the result below returned even though I'm filtering in a radius of 20 > from geocoordinates defined in pt parameter in the

Re: Data Import Handler / Backup indexes

These are just Lucene indexes. There's the Cloud backup and restore that is being worked on. But if the index is static (i.e. not being indexed to), simply copying the data/index (well, actually the whole data index and subdirs) directory will backup and restore it. Copying the index directory

Re: Json Facet api on nested doc

Hello, I also played with json.facet, but couldn't achieve the desired result too. Yonik, Alessandro, Do you think it's a new feature or it can be achieved with the current implementation? On Thu, Nov 19, 2015 at 2:50 PM, xavi jmlucjav wrote: > Hi, > > I am trying to get

Re: Security Problems

Don, You seem to be suggesting that the UI be broken down into components that can be authorised independently. For example, a user who is allowed to query, but not to update, should not have access to UI elements (such as documents in its current incarnation) that allow updating. This is taking

Re: Security Problems

>You seem to be suggesting that the UI be broken down into components that can >be authorised independently. Yes, this is what I was mostly concerned of. It doesn’t apply much with today’s Admin UI though... >For myself, right now, I'm just keen to see that if authentication is required >for

Re: Json Facet api on nested doc

On Sun, Nov 22, 2015 at 3:10 PM, Mikhail Khludnev wrote: > Hello, > > I also played with json.facet, but couldn't achieve the desired result too. > > Yonik, Alessandro, > Do you think it's a new feature or it can be achieved with the current > implementation? Not sure