-
Notifications
You must be signed in to change notification settings - Fork 1k
Correct handling of __name__ in firestore indexes #8862
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
Changes from all commits
f127fba
5290d41
fce1b90
7a21aaa
bd6fadc
42fdcff
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
- Fixed issue where `__name__` fields with DESCENDING order were incorrectly filtered from index listings, causing duplicate index issues (#7629) and deployment conflicts (#8859). The fix now preserves `__name__` fields with explicit DESCENDING order while filtering out implicit ASCENDING `__name__` fields. |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18,9 +18,34 @@ | |
apiClient = new Client({ urlPrefix: firestoreOrigin(), apiVersion: "v1" }); | ||
printer = new PrettyPrint(); | ||
|
||
/** | ||
* Process indexes by filtering out implicit __name__ fields with ASCENDING order. | ||
* Keeps explicit __name__ fields with DESCENDING order. | ||
* @param indexes Array of indexes to process | ||
* @returns Processed array of indexes with filtered fields | ||
*/ | ||
public static processIndexes(indexes: types.Index[]): types.Index[] { | ||
return indexes.map((index: types.Index): types.Index => { | ||
// Per https://firebase.google.com/docs/firestore/query-data/index-overview#default_ordering_and_the_name_field | ||
// this matches the direction of the last non-name field in the index. | ||
let fields = index.fields; | ||
const lastField = index.fields?.[index.fields.length - 1]; | ||
if (lastField?.fieldPath === "__name__") { | ||
const defaultDirection = index.fields?.[index.fields.length - 2]?.order; | ||
if (lastField?.order === defaultDirection) { | ||
fields = fields.slice(0, -1); | ||
} | ||
} | ||
return { | ||
...index, | ||
fields, | ||
}; | ||
}); | ||
} | ||
|
||
/** | ||
* Deploy an index specification to the specified project. | ||
* @param options the CLI options. | ||
Check warning on line 48 in src/firestore/api.ts
|
||
* @param indexes an array of objects, each will be validated and then converted | ||
* to an {@link Spec.Index}. | ||
* @param fieldOverrides an array of objects, each will be validated and then | ||
|
@@ -28,11 +53,11 @@ | |
*/ | ||
async deploy( | ||
options: { project: string; nonInteractive: boolean; force: boolean }, | ||
indexes: any[], | ||
fieldOverrides: any[], | ||
databaseId = "(default)", | ||
): Promise<void> { | ||
const spec = this.upgradeOldSpec({ | ||
indexes, | ||
fieldOverrides, | ||
}); | ||
|
@@ -40,8 +65,8 @@ | |
this.validateSpec(spec); | ||
|
||
// Now that the spec is validated we can safely assert these types. | ||
const indexesToDeploy: Spec.Index[] = spec.indexes; | ||
Check warning on line 68 in src/firestore/api.ts
|
||
const fieldOverridesToDeploy: Spec.FieldOverride[] = spec.fieldOverrides; | ||
|
||
const existingIndexes: types.Index[] = await this.listIndexes(options.project, databaseId); | ||
const existingFieldOverrides: types.Field[] = await this.listFieldOverrides( | ||
|
@@ -183,7 +208,7 @@ | |
return []; | ||
} | ||
|
||
return indexes; | ||
return FirestoreApi.processIndexes(indexes); | ||
} | ||
|
||
/** | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new tests cover composite indexes well, but they miss an important edge case: an index that only contains the
__name__
field. Add test cases to verify the behavior for single-field__name__
indexes.