> > Your question appears to be an "XY Problem" ... that is: you are dealing > with "X", you are assuming "Y" will help you, and you are asking about "Y" > without giving more details about the "X" so that we can understand the full > issue. Perhaps the best solution doesn't involve "Y" at all? See Also: > http://www.perlmonks.org/index.pl?node_id=542341 > Hahaha, thats classic Hoss! Thanks for introducing me to the XY problem. Had I known the two completely, I wouldn't have posted it on the mailing list. And I wasn't looking for a "solution" either. Anyways, as I replied back earlier, I'll get back with questions once I get more clarity.
Cheers Avlesh On Wed, Jan 6, 2010 at 2:02 AM, Chris Hostetter <hossman_luc...@fucit.org>wrote: > > : I am planning to build a rules engine on top search. The rules are > database > : driven and can't be stored inside solr indexes. These rules would > ultimately > : two do things - > : > : 1. Change the order of Lucene hits. > : 2. Add/remove some results to/from the Lucene hits. > : > : What should be my starting point? Custom search handler? > > This smells like an XY problem ... can you elaborate on the types of > rules/conditions/situations when you want #1 and #2 listed above to > happen? > > http://people.apache.org/~hossman/#xyproblem<http://people.apache.org/%7Ehossman/#xyproblem> > XY Problem > > Your question appears to be an "XY Problem" ... that is: you are dealing > with "X", you are assuming "Y" will help you, and you are asking about "Y" > without giving more details about the "X" so that we can understand the > full issue. Perhaps the best solution doesn't involve "Y" at all? > See Also: http://www.perlmonks.org/index.pl?node_id=542341 > > > > > > -Hoss > >