Possible - giving higher score based on "views"

Hi, First let me explain the logic behind here :) We have a list of "images" in a mySQL DB, which we are indexing (fine) We have the following fields: 1) description - a text field, separated by whitespace 2) keywords - a text field, separated by whitespace 3) download_count (a "sint", i.e sorta

Custom request handler/plugin

I have a requirement to filter solr results, based on my application entitlement rules,before they are returned from Solr to the application. In order to do this, I have to implement a custom plugin, which gets entire solr results and apply my application rules (which will be exposed via web servic

Results driving me nuts!

Hi, Ok, I'm really really trying to get my head around this, but I just can't :/ Here are 2 example records, both using the query "st patricks" to search on (matches for the keywords are in **stars** like so, to make a point of what SHOULD be matching); keywords: animations mini alphabets **st**

Re: Possible - giving higher score based on "views"

> First let me explain the logic behind here :) We have a > list of "images" in > a mySQL DB, which we are indexing (fine) > > We have the following fields: > > 1) description - a text field, separated by whitespace > 2) keywords - a text field, separated by whitespace > 3) download_count (a "sin

Re: Custom request handler/plugin

Your approach is problematic. It probably doesn't factor in things like faceting, highlighting, ... Can you say why it is that the original search can't include a filter query to filter out results the user shouldn't have access to? That's the standard approach to implement access control. ~ Davi

Re: Results driving me nuts!

--- On Sun, 3/13/11, Andy Newby wrote: > From: Andy Newby > Subject: Results driving me nuts! > To: solr-user@lucene.apache.org > Date: Sunday, March 13, 2011, 10:38 PM > Hi, > > Ok, I'm really really trying to get my head around this, > but I just can't :/ > > Here are 2 example records, bot

Problem with field collapsing of patched Solr 1.4

Hello. I just tried to patch Solr 1.4 with the field collapsing patch of https://issues.apache.org/jira/browse/SOLR-236. The patching and build process seemed to be ok (below are the steps I did), but the field collapsing feature doesn't seem to work. When I go to `http://localhost:8982/solr/selec

Re: Custom request handler/plugin

*If* you decide to check each result found in your search results against some 3rd party so-called "entitlement service" which is essentially a black box for this discussion, then your search results are going to be disastrously slow; no? Especially if it's a SOAP one ;-) (I'm looking at your use

Version Incompatibility(Invalid version (expected 2, but 1) or the data in not in 'javabin' format)

Hi All, I am using Solr 4.0 api to search from index (made using solr1.4 version). I am getting error Invalid version (expected 2, but 1) or the data in not in 'javabin' format. Can anyone help me to fix problem. Thanks! Isha

Different options for autocomplete/autosuggestion

Hi. There seems to be several options for implementing an autocomplete/autosuggestions feature with Solr. I am trying to summarize those possibilities together with their advantages and disadvantages. It would be really nice to read some of your opinions. * Using N-Gram filter + text field query

Re: Custom request handler/plugin

Below are the reasons why I thought it wouldn't be feasible to have pre-filtered results with filter queries. please comment. Since can't pen down direct business reqs due to confidentially contact with the client, I'll mock out scenario using an example. - There is a parent entity called "Quiz",