-
Notifications
You must be signed in to change notification settings - Fork 132
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
Sort not working on Cosmos DB #110
Comments
Hi team, I have the same error, any estimation about when it will be fixed? Thanks! |
Same here. I've been one week trying different things but didn't arrived to a solution. Did you found a way to solve it, Pingu(@carlesUdG )? |
I haven't found a way to solve it yet :( lets see if someone responds to this issue... |
I believe the problem is here: Sieve/Sieve/Extensions/OrderByDynamic.cs Line 57 in 8030550
|
This is also a problem for MongoDB. |
Hi Sieve,
I've found what I think is a new issue using the Sieve with Cosmos DB. When sorting, Sieve creates a query like the following:
SELECT VALUE root FROM root ORDER BY ((root[\"vulnId\"] = null) ? null : root[\"vulnId\"]) ASC OFFSET 0 LIMIT 100
.As you can see, the ORDER BY is using a derivative of a value, instead of a property of a document, as Cosmos requires, here is the doc: https://docs.microsoft.com/en-us/azure/cosmos-db/sql-query-order-by#remarks. Also here there is an example of this Cosmos limitation: https://stackoverflow.com/questions/56041767/cosmos-db-order-by-on-computed-field.
As a result, every time I sort, an error 500 is thrown by the cosmos library. Is there any way to support this Cosmos DB limitation?
Thank you!
The text was updated successfully, but these errors were encountered: