In the recent weeks, we have made several updates on LOCGS and LOCRICH to improve data accuracy and service reliability
LOCRICH GeoMapping Sort by Level (Available Since V1.7.1)
By default, our geomapping process will sort the geo based on the geo boundary size with assumption that more specific geos should always be smaller than less specific geo
While the case is quite rare, in case of children geo have bigger boundary than its parents due then the response order would be wrong even if the parent-child relationship is defined correctly on Geo Tools
Therefore if your use case requires getting geoIds from a location with higher accuracy from locrich, you should update the jar to v1.7.1 and utilize LEVEL sort method to ensure the order of geoId are based on structure you see in Geo Tools rather than order by its size
However if you are getting the geoIds by location from locgs, then you won't need to do anything since LEVEL sort method would automatically used since 8 June 2021
LOCGS & LOCRICH Client Service Circuit Breaker
Recently we have added Circuit Breaker between LOCGS and LOCRICH to prevent cascading failure that happened few weeks ago.
In case you haven't setup your own circuit breaker to both LOCGS and LOCRICH, updating your jar depending on service you are using would automatically setup the circuit breaker
LOCRICH: Starting v1.8.0
LOCGS: Starting v2.9.0
By default you won't need to add any config on the client config, however if you want to set the circuit breaker config explicitly you can refer to this config