This sounds OK. I can create a field name mapping structure to change the requests / responses in a way my client doesn't need to be aware of different fields.
Thanks for this directions, Daniel On 8/6/07 21:32, "Chris Hostetter" <[EMAIL PROTECTED]> wrote: > > : Can't I have the same index, using one single core, same field names being > : processed by language specific components based on a field/parameter? > > yes, but you don't really need the complexity you describe below ... you > don't need seperate request handlers per language, just seperate fields > per language. asusming you care about 3 concepts: title, author, body .. > in a single language index those might corrispond ot three fields, in your > index they corrispond to 3*N fields where N is the number of languages you > wnat to support... > > title_french > title_english > title_german > ... > author_french > author_english > ... > > documents which are in english only get values for th english fields, > documents in french etc... ... unless perhaps you want to support > "translations" of the documents in which case you can have values > fields for multiple langagues, it's up to you. When a user wants to query > in french, you take their input and query against the body_french field > and display the title_french field, etc... > > -Hoss > http://www.bbc.co.uk/ This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this.
