It appears as if you are defining title and name as types, not as fields.
Both types have the en field, and for a query that doesn't restrict based
on types it searches the en field in both of the types.
What you really want is the title and name fields defined as multi_fieldmappings within some type. And then the sub-mapping of the same name is the
default. For example, here is an excerpt of one of my own field mappings
from an exploratory schema. It is for the cn (common name, in LDAP
parlance) field:
Then, a Lucene query string for cn: chooses the english_stemming_analyzer,
while cn.finnish chooses the finnish_stemming_analyzer. And so on. Of
course, the actual specifications of these analyzers is not shown here.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.