azure-sdk-for-java
azure-sdk-for-java copied to clipboard
[FEATURE REQ] Cosmos Criteria API: add support for IS_DEFINED function
Describe the solution you'd like Please add support for IS_DEFINED function for Cosmos Criteria API.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @kushagraThapar, @anfeldma-ms
@mbhaskar - please take a look at this issue.
Considering this for next semester planning.
@TheovanKraay can you please take a look at this, thanks!
Hi, are there any updates on this?
@Blackbaud-AliRashed this is currently in our backlog and has not been picked up.
I am wondering if you are stuck because of this or is there a workaround which can unblock you while we support this in its original form?
I'm blocked by this.
I have documents where i added fields and i need to provide backward compatiblity. So i would like to add to the query where X = false or IS NOT_DEFINED(X). I don't immediatly see how i can create a workaround for this.
@Blackbaud-AliRashed this is currently in our backlog and has not been picked up.
I am wondering if you are stuck because of this or is there a workaround which can unblock you while we support this in its original form?
For my use-case, I was able to implement a workaround, so I'm not currently blocked.
@OverbodigeZever are you able to post your use case so that I can see if there is a work around until this is addressed? Are you able to use @Query definition with a repository in the meantime like below?
we are building our queries dynamically using the Criteria API due to the business logic we need. I can not use the example as above. At the moment we skipped this, since it's not supported. It would however be very interesting to support this. This first message dates from 2020.. and people do use your sdk for good reasons. Thanks for the fast reply @trande4884
Understood @OverbodigeZever, this is now in our plan to accomplish and I will update here once it's done!
Hi @siarheiburliayeu, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.