[PDB-announce] version 1.9.22 released

[Stefan Pratter]

version 1.9.22 has been released to beta.peeringdb.com
=====================================================================

PERFORMANCE OPTIMIZATIONS

   1) implementation of a cache layer for API GET listings

   Any request to GET that does not do any searches will now be served a 
cached result. Cache is updated approximately every 15 minutes. This 
interval will likely decrease after we release to production.

   Example: /api/net?depth=2 - will serve a cached result

   Example: /api/net?id__in=1,2 - will serve a live result

   2) implementation of a result limit for API GET listings that do not 
qualify for a cache load and have the depth parameter set

   Any request to GET that does search queries and has it's depth 
parameter specified will now have a result limit of 250 entries, any 
entries past this limit will be truncated, at which point you should be 
more specific with your search or use the skip and limit parameters to 
page through the result set.

   Example: /api/net?updated__gt=2011-01-01&depth=1 - will serve a live 
result and a maximum of 250 rows at a time.

   Example: /api/net?updated__gt=2011-01-01 - will serve a live result 
and will not be truncated

   Example: /api/net?depth=1 - will serve a cached result and will not 
be truncated

   3) serialization performance fixes

   We have tested these extensively, and there should be no changes in 
data structure anywhere, if you notice something regardless, please let 
us know as it is likely that it was unintended.

WEB UI

   * fix issue where password reset URL would redirect to front page if 
opened in a browser that was already authenticated
   * removed duplicate "Not Disclosed" choices from participant advanced 
search
   * removed "100+ Gbps" option from traffic info lists, networks that 
had this selected have been changed to the "100-200 Gbps" choice instead
   * fix issue where input validation error would sometimes render 
"parent entity pending" notification, even when this was not the case

API / DATA

   * filtering for exact dates should now work correctly - e.g 
/ix?created=2016-02-18 should return only exchanges created on that date
   * filtering for dates greater than provided date will now work 
correctly - it used to include the provided date in some instances
   * /ixlan net_set no longer contains pending objects
   * /poc fixed performance issue when doing a GET request while 
unauthenticated