Hi Hoss. Yes, the idea is indexing each document independently (in my scenario they are not translations, they are just documents with the same structure but different languages). So that considerations you did about queries in a range wouldn't be a problem in this case. The real issue I can see in this approach, is related to Analyzers... How to make them deal with different languages properly using one Solr instance with the same set of fields being used by documents in different languages....
Good, I just forgot that some fields don't need special treatment depending on language (like date or long)... Thanks for that. Looks like my best alternative then is using dynamic fields having then a set of fields for each language. But anyway I think I'll still need a way to apply different analyzers at query time so I can deal with each language details. Is it correct? Regards, Daniel On 16/6/07 04:31, "Chris Hostetter" <[EMAIL PROTECTED]> wrote: > > : One bad thing in having fields specific for your language (in my point of > : view) is that you will have to re-index your content when you add a new > : language (some will need to start with one language and in future will have > : others added). But OK, let's say the indexing is done. > > i don't see anyway you could possible avoid that, unless you index each > "langauge version" of your orriginl documents as seperate Solr Documents > (which would still work with the same type of schema) then if you add a > new translation for a "document" you only have to index the new text -- > but the trade off is you can't do queries for things like "all documents > written between 2004 and 2005" becuse you'll get every translation of > every document. > > : you are going to have a different "interface" as the system will receive and > : return a different set of fields in queries, wouldn't? > : It could be avoided transforming the request / response to a language aware > : / unaware format: > : requests: transforming fieldName => fieldName_language > : responses: transforming fieldName_language => fieldName > > sure ... the fields have the langauge in them, if you want a downstream > client ot be able to refer to them without the language in the name, > you'll need to strip it off. > > : And still you will not be able to search for all your documents... It may be > : interesting to search for the last published contents (no matter in which > : language this content is)... > > why wouldn't you be able to do that? "publish date" would be a field that > would be completley independent of the language, so you would just have it > as a regular field ing your schema (not dynamic, no langauge in the field > name) > > > > -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.
