Skip to content

DATAMONGO-1049 - Check for explicitly declared language field. #224

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants