fixed index creation on default field #6835
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(1) This fixed a bug where index creation with the schema update endpoint was not possible for default fields, because the index field names were not transformed to their internal names, e.g.
createdAt
->_created_at
.(2) However, this does not fix the issue that the schema still returns the internal index field names when being read. That means with this PR, a schema update request with index
{ createdAt: 1 }
creates an index{ _created_At: 1 }
and the call also returns the index as{ _created_At: 1 }
instead of as{ createdAt: 1 }
.This should probably be corrected as some point for consistency.This needs to be corrected because the test is failing for Postgres otherwise.closes #6834