Skip to content

Conversation

@christophstrobl
Copy link
Member

We now check for an explicitly declared language field for setting langugae_override within a text index. Therefore the attribute (even if named with the reserved keyword language) has to be explicitly marked with @Language. Prior to this change having:

@Language String lang; String language;

would have caused trouble when trying to resolve index structures as one cannot set language override to more than one property.

We now check for an explicitly declared language field for setting ‘langugae_override’ within a text index. Therefore the attribute (even if named with the reserved keyword ‘language’) has to be explicitly marked with @language. Prior to this change having: @language String lang; String language; would have caused trouble when trying to resolve index structures as one cannot set language override to more than one property.
christophstrobl added a commit that referenced this pull request Sep 25, 2014
We now check for an explicitly declared language field for setting language_override within a text index. Therefore the attribute (even if named with the reserved keyword language) has to be explicitly marked with @language. Prior to this change having: @language String lang; String language; would have caused trouble when trying to resolve index structures as one cannot set language override to more than one property. Original pull request: #224.
christophstrobl added a commit that referenced this pull request Sep 25, 2014
We now check for an explicitly declared language field for setting language_override within a text index. Therefore the attribute (even if named with the reserved keyword language) has to be explicitly marked with @language. Prior to this change having: @language String lang; String language; would have caused trouble when trying to resolve index structures as one cannot set language override to more than one property. Original pull request: #224.
@odrotbohm odrotbohm closed this Sep 25, 2014
@odrotbohm odrotbohm deleted the issue/DATAMONGO-1049 branch September 25, 2014 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants