Replies: 3 comments 3 replies
-
|
@toiyabe not sure if you've gotten the same recommendation or not. |
Beta Was this translation helpful? Give feedback.
-
|
Hello Eric, I'm not an expert in Cosmos indexing by any means, so I'm interested in this as well. I did some readying on Cosmos Indexes (see link). By default Cosmos already indexes everything. I think that is what is referenced by the "default" indexing policy you have above. Having said that, I have seen YouTube videos where people set their own. I've seen either "*" or "?" added to the path, like this (see example): {
"indexingMode": "consistent",
"automatic": true,
"includedPaths": [
{
"path": "/Discriminator/*"
},
{
"path": "/UserName/*"
}
],
"excludedPaths": [
{
"path": "/*"
}
]
}If you add this, does it work? |
Beta Was this translation helpful? Give feedback.
-
|
That worked! I guess having the trailing /* made all the difference. Thank you! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Azure is recommending I create the following indexes:
I went into Cosmos DB data explorer, selected the Identity container and tried to add the following indexing policy.
{ "indexingMode": "consistent", "automatic": true, "includedPaths": [ { "path": "/Discriminator" }, { "path": "/UserName" } ], "excludedPaths": [ { "path": "/*" } ] }And got this error.
Has anyone else gotten the same recommendation? What'd you do to fix it?
For reference, the previous default index was the following.
{ "indexingMode": "consistent", "automatic": true, "includedPaths": [ { "path": "/*" } ], "excludedPaths": [ { "path": "/\"_etag\"/?" } ] }Beta Was this translation helpful? Give feedback.
All reactions