: 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
