I agree that it is a worthwhile contribution.
Some suggestions... allow the configuration to specify field boost values, and analyzer(s). If analyzers are specified per-field, then wrap then automatically with a PerFieldAnalyzerWrapper. Also, having a facility to aggregate fields into a "contents"-like field would be nice - though maybe this would be covered implicitly as part of the SQL mapping with one of the columns being an aggregate column.
Perhaps the configuration aspect of it (XML mapping of expressions to field details) could be generalized to work with an object graph as well as SQL result sets. OGNL (www.ognl.org) makes expression language glue and I can see it being used for mappings - for example the "name" field could be mapped to "company.president.name", where "company" is an object (or Map) with a "president" property, and so on.
Erik
On Feb 8, 2005, at 2:42 AM, Aad Nales wrote:
If that is a general thought then I will plan for some time to put this in action.
Cheers, Aad
David Spencer wrote:
Nice, very similar to what I was thinking of, where the most significant difference is probably just that I was thinking of a batch indexer, not one embedded in a web container. Probably a worthwhile contribution to the sandbox.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
