Stream: hapi
Topic: JPA Support for "special" search parameters
Stephen MacVicar (Sep 20 2019 at 14:59):
Based on my investigations, it appears that the HAPI JPA server doesn't currently support search params of type special, is this correct? My use case involves some latitude/longitude based searches (such as the near parameter for Location).
I am guessing that this TODO refers to the near search.
Also, the JPA server currently serves an invalid CapabilityStatement related to special search parameters as described in this github issue.
James Agnew (Sep 20 2019 at 16:23):
Yup, special search parameters are not yet implemented.
Stephen MacVicar (Sep 20 2019 at 17:52):
Is adding support for special parameters something that could be done without losing all of the nice search features that come with the base JPA server (supporting multiple parameters, includes, etc.)? My impression from looking at the generated Location provider is that this is not something that could be done with something simple like an Interceptor, but would instead require messing around in the guts of HAPI.
Jake O'Donnell (Oct 07 2019 at 15:23):
Are there any potential workarounds for my HAPI JPA server to implement something that acts similarly to the special near search param (seeing as near is not supported)? I've been looking at trying to use a custom operation, would this be reasonable or discouraged?
James Agnew (Oct 07 2019 at 16:31):
That would absolutely be a reasonable thing to do as a workaround to near not being implemented.
What I really want to get done at some point soon is to take advantage of the spatial features in ElasticSearch to implement this one. Most of the precursor work is actually done now so it seems reasonable that we could do this.. Not yet sure about timing though.
Last updated: Apr 12 2022 at 19:14 UTC
