Skip to content

Conversation

@christophstrobl
Copy link
Member

Index creation failed for @Indexed and @CompoundIndex as the resolved dotPath was not used for creation.

We now not only resolve the dotPath but also use it within the key for index definition. In case of a nested compound index the key definition is enhanced by the provided path.

When leaving the key definition empty for nested compound index we'll create an index for the whole nested document.

Trying to create a compound index on root level not providing key information leads to InvalidDataApiUsageException.

Prepare issue branch.
Index creation failed for @indexed and @CompoundIndex as the resolved dotPath was not used for creation. We now not only resolve the dotPath but also use it within the key for index definition. In case of a nested compound index the key definition is enhanced by the provided path. When leaving the key definition empty for nested compound index we'll create an index for the whole nested document. Trying to create a compound index on root level not providing key information leads to InvalidDataApiUsageException
christophstrobl added a commit that referenced this pull request May 19, 2014
Index creation failed for @indexed and @CompoundIndex as the resolved dotPath was not used for creation. We now not only resolve the dotPath but also use it within the key for index definition. In case of a nested compound index the key definition is enhanced by the provided path. When leaving the key definition empty for nested compound index we'll create an index for the whole nested document. Trying to create a compound index on root level not providing key information leads to InvalidDataApiUsageException. Original pull request: #179.
@odrotbohm odrotbohm closed this May 19, 2014
@odrotbohm odrotbohm deleted the issue/DATAMONGO-929 branch May 19, 2014 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants