-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Composite/unique SearchParameters indexes deleted resources and causes other SearchParameter's find them as well #1724
Comments
@jamesagnew any chance you might have time to take a look at this? |
@jamesagnew any insight on this problem? |
@jamesagnew any chance you could provide some information regarding this? |
@jamesagnew we would like to know if this is a bug or a feature? |
@jamesagnew I know you are very busy person but could you give some insight on this so we could better plan what we should do about this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello @jamesagnew,
Describe the bug
Normally when custom
SearchParameter
resource is created, for example with basePatient
and with codetest
which has expressionPatient.birthDate
this will find only resources that are not deleted. However if we create a composite unique index which refers to thatSearchParameter
, the queryPatient?test=...
will start to return also deleted resources (it won't return the full content of the resource, but will find them). This seems rather odd.I'm not sure if this is a bug, but I also noticed that the unique index contains values for the deleted resources as well. Is this by design or is this a bug as well? It seems like a bug to me.
To Reproduce
See unit test scenarios in #1723
Expected behavior
SearchParameter
should not behave differently when it's part of compositeSearchParameter
. AndSearchParameter
s shouldn't find deleted resources. And unique indices shouldn't index the deleted resources?Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: