Skip to content
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

Open
tuomoa opened this issue Feb 20, 2020 · 5 comments

Comments

@tuomoa
Copy link
Contributor

tuomoa commented Feb 20, 2020

Hello @jamesagnew,

Describe the bug
Normally when custom SearchParameter resource is created, for example with base Patient and with code test which has expression Patient.birthDate this will find only resources that are not deleted. However if we create a composite unique index which refers to that SearchParameter, the query Patient?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 composite SearchParameter. And SearchParameters shouldn't find deleted resources. And unique indices shouldn't index the deleted resources?

Environment (please complete the following information):

  • HAPI FHIR 4.1.0
@tuomoa
Copy link
Contributor Author

tuomoa commented May 13, 2020

@jamesagnew any chance you might have time to take a look at this?

@tuomoa
Copy link
Contributor Author

tuomoa commented Dec 10, 2020

@jamesagnew any insight on this problem?

@tuomoa
Copy link
Contributor Author

tuomoa commented Jun 21, 2021

@jamesagnew any chance you could provide some information regarding this?

@ruoat
Copy link
Contributor

ruoat commented Aug 25, 2021

@jamesagnew we would like to know if this is a bug or a feature?

@ruoat
Copy link
Contributor

ruoat commented Oct 7, 2021

@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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants