MinusOneDB logoMinusOneDB
MinusOneDB Docs

Appearance

Release Notes ​

TimestampComponentDescription
2026-03-30 10:38ops
  • No user facing changes
2026-03-30 10:38svc
  • Improve error messages when there is a failure to connect to data or session store
  • Improve error messages when there is a failure to connect to internal db
  • Add % progress to geo loading status in /health; percentCompleted and count are always available as keys in the geo status
2026-03-30 10:38session
  • No user facing changes
2026-03-30 10:38store
  • No user facing changes
2026-03-23 17:29ops
  • No user facing changes
2026-03-23 17:29svc
  • No user facing changes
2026-03-23 17:29session
  • No user facing changes
2026-03-23 17:29store
  • No user facing changes
2026-03-17 14:51ops
  • Add /env/outbound endpoint with param enable (true/false); this either enables or disables outbound access to the public internet for environment servers. If you are loading data from a gcs bucket you must enable outbound connectivity
  • env/get now returns an additional outbound attribute indicating whether the environment has outbound access to the public internet
2026-03-17 14:51svc
  • Support /publish for files in gcs buckets; use gs://yourgcsbucket/file.csv
  • the s3file param to /publish is now deprecated in favor of file; it will continue to be supported but clients should migrate to file, as it may be removed in a future release
2026-03-15 14:49ops
  • No user facing changes
2026-03-15 14:49svc
  • No user facing changes
2026-03-15 14:49session
  • No user facing changes
2026-03-15 14:49store
  • No user facing changes
2026-03-11 11:55svc
  • Fix regression introduced in 2026-03-08 release where enabling geo would cause an infinite loop of loading geo data
2026-03-08 20:33ops
  • Address CVE-2026-2006
  • Address CVE-2026-2007
2026-03-08 20:33svc
  • Address CVE-2026-2006
  • Address CVE-2026-2007
2026-03-08 20:33session
  • No user facing changes
2026-03-08 20:33store
  • No user facing changes
2026-02-27 16:46ops
  • No user facing changes
2026-02-27 16:46svc
  • Add store/backup/rename endpoint: rename a backup in an environment
  • Fix theoretical sql injection issue with name param of store/backup/create
2026-02-27 16:46session
  • No user facing changes
2026-02-27 16:46store
  • No user facing changes
2026-02-20 15:04ops
  • No user facing changes
2026-02-20 15:04svc
  • Fix behavior of /query when sorting by a field that is unpopulated; now documents with null values will always sort to the end. This will be a breaking change if the previous buggy behavior was relied upon Note that to see this change on existing store, you must readd all properties via /schema/add after running /schema/wipe
2026-02-20 15:04session
  • No user facing changes
2026-02-20 15:04store
  • No user facing changes
2026-02-13 13:44ops
  • Address CVE-2026-2003
  • Address CVE-2026-2004
  • Address CVE-2026-2005
  • Address CVE-2026-2006
  • Address CVE-2026-2007
2026-02-13 13:44svc
  • Address CVE-2026-2003
  • Address CVE-2026-2004
  • Address CVE-2026-2005
  • Address CVE-2026-2006
  • Address CVE-2026-2007
2026-02-13 13:44session
  • No user facing changes
2026-02-13 13:44store
  • No user facing changes
2026-02-06 17:08ops
  • Address CVE-2025-43368
  • Address CVE-2025-7425
  • Address CVE-2026-21945
  • Address CVE-2026-21932
  • Address CVE-2026-21933
  • Address CVE-2025-6021
  • Address CVE-2025-12183
  • Address CVE-2026-21925
  • Address CVE-2025-6052
  • Address CVE-2026-21947
  • Address CVE-2025-47219
2026-02-06 17:08svc
  • Any successful call to /schema/add now will always sync schemas of underlying data stores; this allows one to run m1 env-yours schema/add -properties '[]' after adding a store to sync its schema
  • Address CVE-2025-43368
  • Address CVE-2025-7425
  • Address CVE-2026-21945
  • Address CVE-2026-21932
  • Address CVE-2026-21933
  • Address CVE-2025-6021
  • Address CVE-2025-12183
  • Address CVE-2026-21925
  • Address CVE-2025-6052
  • Address CVE-2026-21947
  • Address CVE-2025-47219
2026-02-06 17:08session
  • Address CVE-2025-43368
  • Address CVE-2025-7425
  • Address CVE-2026-21945
  • Address CVE-2026-21932
  • Address CVE-2026-21933
  • Address CVE-2025-6021
  • Address CVE-2025-12183
  • Address CVE-2026-21925
  • Address CVE-2025-6052
  • Address CVE-2026-21947
  • Address CVE-2025-47219
2026-02-06 17:08store
  • No user facing changes
2026-01-30 11:54ops
  • No user facing changes
2026-01-30 11:54svc
  • Fix bug where store/backup/create would not properly set status of backup to "failed" if an error occured during the backup; the status would have remained in the "working" state indefinitely.
2026-01-30 11:54session
  • No user facing changes
2026-01-30 11:54store
  • No user facing changes
2026-01-23 12:06ops
  • No user facing changes
2026-01-23 12:06svc
  • No user facing changes
2026-01-23 12:06store
  • No user facing changes
2026-01-23 12:06session
  • No user facing changes
2026-01-16 15:26ops
  • No user facing changes
2026-01-16 15:26svc
  • No user facing changes
2026-01-16 15:26session
  • No user facing changes
2026-01-16 15:26store
  • No user facing changes
2026-01-09 16:10ops
  • No user facing changes
2026-01-09 16:10svc
  • No user facing changes
2026-01-09 16:10session
  • No user facing changes
2026-01-09 16:10store
  • No user facing changes
2026-01-02 12:25ops
  • No user facing changes
2026-01-02 12:25svc
  • No user facing changes
2026-01-02 12:25session
  • No user facing changes
2026-01-02 12:25store
  • No user facing changes
2025-12-26 16:29ops
  • No user facing changes
2025-12-26 16:29svc
  • No user facing changes
2025-12-26 16:29session
  • No user facing changes
2025-12-26 16:29store
  • No user facing changes
2025-12-19 17:14ops
  • No user facing changes
2025-12-19 17:14svc
  • No user facing changes
2025-12-19 17:14store
  • No user facing changes
2025-12-19 17:14session
  • No user facing changes
2025-12-12 15:46ops
  • No user facing changes
2025-12-12 15:46svc
  • No user facing changes
2025-12-12 15:46session
  • No user facing changes
2025-12-12 15:46store
  • No user facing changes
2025-12-05 14:39ops
  • No user facing changes
2025-12-05 14:39svc
  • No user facing changes
2025-12-05 14:39session
  • No user facing changes
2025-12-05 14:39store
  • No user facing changes
2025-11-28 16:57ops
  • No user facing changes
2025-11-28 16:57svc
  • No user facing changes
2025-11-28 16:57session
  • No user facing changes
2025-11-28 16:57store
  • No user facing changes
2025-11-21 16:30ops
  • No user facing changes
2025-11-21 16:30svc
  • No user facing changes
2025-11-21 16:30session
  • No user facing changes
2025-11-21 16:30store
  • No user facing changes
2025-11-14 14:19ops
  • Address CVE-2025-12817
  • Address CVE-2025-12818
2025-11-14 14:19svc
  • Address CVE-2025-12817
  • Address CVE-2025-12818
2025-11-14 14:19session
  • No user facing changes
2025-11-14 14:19store
  • No user facing changes
2025-11-07 14:53ops
  • No user facing changes
2025-11-07 14:53svc
  • No user facing changes
2025-11-07 14:53session
  • No user facing changes
2025-11-07 14:53store
  • No user facing changes
2025-10-31 20:54svc
  • Add store/backup/drop endpoint: deletes a backup from an environment
2025-10-31 19:55ops
  • No user facing changes
2025-10-31 19:55svc
  • No user facing changes
2025-10-31 19:55session
  • No user facing changes
2025-10-31 19:55store
  • No user facing changes
2025-10-2416:10ops
  • No user facing changes
2025-10-2416:10svc
  • No user facing changes
2025-10-2416:10session
  • No user facing changes
2025-10-2416:10store
  • No user facing changes
2025-10-17 21:59ops
  • No user facing changes
2025-10-17 21:59svc
  • No user facing changes
2025-10-17 21:59session
  • No user facing changes
2025-10-17 21:59store
  • No user facing changes
2025-10-10 14:20ops
  • No user facing changes
2025-10-10 14:20svc
  • No user facing changes
2025-10-10 14:20session
  • No user facing changes
2025-10-10 14:20store
  • No user facing changes
2025-10-03 14:11ops
  • No user facing changes
2025-10-03 14:11svc
  • No user facing changes
2025-10-03 14:11session
  • No user facing changes
2025-10-03 14:11store
  • No user facing changes
2025-09-26 14:40ops
  • No user facing changes
2025-09-26 14:40svc
  • Breaking change: /query endpoint can be used to request documents or facets but not both in 1 query
  • Dramatically improve performance of certain types of queries in multishard environments; previously the more shards one had, responses with very large /query outputs would become linearly slower with the number of shards.
2025-09-26 14:40session
  • No user facing changes
2025-09-26 14:40store
  • No user facing changes
2025-09-19 14:44ops
  • No user facing changes
2025-09-19 14:44svc
  • No user facing changes
2025-09-19 14:44session
  • No user facing changes
2025-09-19 14:44store
  • No user facing changes
2025-09-12 20:57ops
  • No user facing changes
2025-09-12 20:57svc
  • No user facing changes
2025-09-12 20:57session
  • No user facing changes
2025-09-12 20:57store
  • No user facing changes
2025-09-05 22:31ops
  • No user facing changes
2025-09-05 22:31svc
  • Fix bug where in an environment where publish-permissive is set to false and a transform rule set is used, a /publish of data will incorrectly "succeed" even when there is a mismatch between schema and data (the output data will simply be null, like when publish-permissive is set to true, rather than throwing an error as it should in this mode).
2025-09-05 22:31session
  • No user facing changes
2025-09-05 22:31store
  • No user facing changes
2025-08-29 17:02ops
  • No user facing changes
2025-08-29 17:02svc
  • No user facing changes
2025-08-29 17:02session
  • No user facing changes
2025-08-29 17:02store
  • No user facing changes
2025-08-22 19:15ops
  • Fix http status of various environment modifying related operations; service calls that should return a 400 (for example, referencing a non existent store) would return a 500 rather than 400
2025-08-22 19:15svc
  • Make proper error message and http status code if one calls env/store/backup with an invalid backup id
2025-08-22 19:15session
  • No user facing changes
2025-08-22 19:15store
  • No user facing changes
2025-08-15 18:15ops
  • Address CVE-2025-8713
  • Address CVE-2025-8714
  • Address CVE-2025-8715
2025-08-15 18:15svc
  • Address CVE-2025-8713
  • Address CVE-2025-8714
  • Address CVE-2025-8715
2025-08-15 18:15session
  • No user facing changes
2025-08-15 18:15store
  • No user facing changes
2025-08-08 17:18vdops
  • Fix bug where env/reboot would return a 500 with ugly error message when trying to reboot a non existent store; now returns a proper 400 with "No such store" error message
  • Remove any 409 or 404 error codes returned by ops methods in favor of a 400; this is technically a breaking change but the 400 status code in this case is more of an industry standard
2025-08-08 17:18vdsvc
  • No user facing changes
2025-08-08 17:18vdsession
  • No user facing changes
2025-08-08 17:18vdstore
  • No user facing changes
2025-08-01 12:57ops
  • No user facing changes
2025-08-01 12:57svc
  • No user facing changes
2025-08-01 12:57session
  • No user facing changes
2025-08-01 12:57store
  • No user facing changes
2025-07-27 20:39reports
  • Fix security issue where html/javascript content stored in an m1db environment could potentially be executed; this would typically result in errors but would generally be blocked by Content-Security-Policy settings and would not result in any sort of data leakage.
2025-07-25 20:27ops
  • No user facing changes
2025-07-25 20:27svc
  • No user facing changes
2025-07-25 20:27session
  • No user facing changes
2025-07-25 20:27store
  • No user facing changes
2025-07-18 13:24ops
  • No user facing changes
2025-07-18 13:24svc
  • No user facing changes
2025-07-18 13:24session
  • No user facing changes
2025-07-18 13:24store
  • No user facing changes
2025-07-11 13:16ops
  • No user facing changes
2025-07-11 13:16svc
  • No user facing changes
2025-07-11 13:16session
  • No user facing changes
2025-07-11 13:16store
  • No user facing changes
2025-07-06 18:07ops
  • No user facing changes
2025-07-06 18:07svc
  • No user facing changes
2025-07-06 18:07session
  • No user facing changes
2025-07-06 18:07store
  • No user facing changes
2025-06-28 14:09ops
  • Fix bug where env/store/deploy would fail if trying to rename a store with more than 1 shard; one would get the error "Unable to rename store. java.util.ConcurrentModificationException",
2025-06-27 21:08ops
  • Fix regression introduced in 2025-03-14 release that broke env/store/rename and /env/session/rename endpoints; any use of these endpoints would return an error like "Unable to rename store. 400 BAD_REQUEST \"No null `index` exists."
2025-06-27 15:50ops
  • No user facing changes
2025-06-27 15:50svc
  • No user facing changes
2025-06-27 15:50session
  • No user facing changes
2025-06-27 15:50store
  • No user facing changes
2025-06-20 13:05ops
  • No user facing changes
2025-06-20 13:05svc
  • No user facing changes
2025-06-20 13:05session
  • No user facing changes
2025-06-20 13:05store
  • No user facing changes
2025-06-13 18:24ops
  • No user facing changes
2025-06-13 18:24svc
  • No user facing changes
2025-06-13 18:24session
  • No user facing changes
2025-06-13 18:24store
  • No user facing changes
2025-06-06 14:29ops
  • No user facing changes
2025-06-06 14:29svc
  • No user facing changes
2025-06-06 14:29session
  • No user facing changes
2025-06-06 14:29store
  • No user facing changes
2025-05-30 13:49ops
  • No user facing changes
2025-05-30 13:49svc
  • No user facing changes
2025-05-30 13:49session
  • No user facing changes
2025-05-30 13:49store
  • No user facing changes
2025-05-23 11:38ops
  • No user facing changes
2025-05-23 11:38svc
  • No user facing changes
2025-05-23 11:38session
  • No user facing changes
2025-05-23 11:38store
  • No user facing changes
2025-05-16 9:50ops
  • No user facing changes
2025-05-16 9:50svc
  • No user facing changes
2025-05-16 9:50session
  • No user facing changes
2025-05-16 9:50store
  • No user facing changes
2025-05-09 12:30ops
  • Address CVE-2025-4207
2025-05-09 12:30svc
  • Address CVE-2025-4207
2025-05-09 12:30session
  • No user facing changes
2025-05-09 12:30store
  • No user facing changes
2025-05-02 10:35ops
  • No user facing changes
2025-05-02 10:35svc
  • No user facing changes
2025-05-02 10:35session
  • No user facing changes
2025-05-02 10:35store
  • No user facing changes
2025-04-26 14:29ops
  • No user facing changes
2025-04-26 14:29svc
  • No user facing changes
2025-04-26 14:29session
  • No user facing changes
2025-04-26 14:29store
  • No user facing changes
2025-04-18 9:36ops
  • Address CVE-2025-23083
  • Address CVE-2024-54534
  • Address CVE-2024-47606
  • Address CVE-2025-21587
  • Address CVE-2025-30698
  • Address CVE-2025-30691
2025-04-18 9:36svc
  • Address CVE-2025-23083
  • Address CVE-2024-54534
  • Address CVE-2024-47606
  • Address CVE-2025-21587
  • Address CVE-2025-30698
  • Address CVE-2025-30691
2025-04-18 9:36session
  • Address CVE-2025-23083
  • Address CVE-2024-54534
  • Address CVE-2024-47606
  • Address CVE-2025-21587
  • Address CVE-2025-30698
  • Address CVE-2025-30691
2025-04-18 9:36store
  • Address CVE-2025-23083
  • Address CVE-2024-54534
  • Address CVE-2024-47606
  • Address CVE-2025-21587
  • Address CVE-2025-30698
  • Address CVE-2025-30691
2025-04-11 11:16ops
  • No user facing changes
2025-04-11 11:16svc
  • No user facing changes
2025-04-11 11:16session
  • No user facing changes
2025-04-11 11:16store
  • No user facing changes
2025-04-04 18:26ops
  • No user facing changes
2025-04-04 18:26svc
  • No user facing changes
2025-04-04 18:26session
  • No user facing changes
2025-04-04 18:26store
  • No user facing changes
2025-03-28 10:26ops
  • No user facing changes
2025-03-28 10:26svc
  • No user facing changes
2025-03-28 10:26session
  • No user facing changes
2025-03-28 10:26store
  • No user facing changes
2025-03-21 10:17ops
  • No user facing changes
2025-03-21 10:17svc
  • No user facing changes
2025-03-21 10:17session
  • No user facing changes
2025-03-21 10:17store
  • No user facing changes
2025-03-14 11:01ops
  • system properties are now gettable and settable via /system/properties rather than /system/. All properties may still be retrieved via a call to /system but this may be deprecated in the future.
  • A number of changes to authentication:
  • Authentication tokens are no longer stateful and may not be listed or invalidated individually.
  • Given that tokens are no longer stateful, we recommend a shorter ttl on tokens. The default for newly created environments is now 10 minutes; you can get the same behavior on your existing environment by running something like "m1 your-env system/properties/token-expire-ms -value 600000"
  • Adds support for JWTs to be used for authentication (authn) and authorization (authz) by peer applications.
  • JWTs follow the standard spec in all regards with the exception of using longer keylengths for JWT signing.
  • Remote applications may validate keys and retrieve claims either by service call or by validating signature remotely using an available public key.
  • JWTs are not encrypted by default but may be encrypted by provding a secret to be used to encrypt using symmetric encryption via the encryption-secret property in /system/properties.
  • Fix status code for authentication failures -- was previously 500 but should be 401
2025-03-14 11:01svc
  • A number of changes to authentication:
  • Authentication tokens are no longer stateful and may not be listed or invalidated individually.
  • Given that tokens are no longer stateful, we recommend a shorter ttl on tokens. The default for newly created environments is now 10 minutes; you can get the same behavior on your existing environment by running something like "m1 your-env system/properties/token-expire-ms -value 600000"
  • Adds support for JWTs to be used for authentication (authn) and authorization (authz) by peer applications.
  • JWTs follow the standard spec in all regards with the exception of using longer keylengths for JWT signing.
  • Remote applications may validate keys and retrieve claims either by service call or by validating signature remotely using an available public key.
  • JWTs are not encrypted by default but may be encrypted by provding a secret to be used to encrypt using symmetric encryption via the encryption-secret property in /system/properties.
  • Fix status code for authentication failures -- was previously 500 but should be 401
2025-03-14 11:01session
  • No user facing changes
2025-03-14 11:01store
  • No user facing changes
2025-03-07 11:16ops
  • Improve error message in the event that an env/rescale call fails
2025-03-07 11:16svc
  • No user facing changes
2025-03-07 11:16session
  • No user facing changes
2025-03-07 11:16store
  • No user facing changes
2025-02-28 10:06ops
  • No user facing changes
2025-02-28 10:06svc
  • No user facing changes
2025-02-28 10:06session
  • No user facing changes
2025-02-28 10:06store
  • No user facing changes
2025-02-21 13:15ops
  • Address CVE-2004-56337
  • Address CVE-2025-1094
2025-02-21 13:15svc
  • Address CVE-2004-56337
  • Address CVE-2025-1094
2025-02-21 13:15session
  • Address CVE-2004-56337
2025-02-21 13:15store
  • No user facing changes
2025-02-14 10:56ops
  • No user facing changes
2025-02-14 10:56svc
  • No user facing changes
2025-02-14 10:56session
  • No user facing changes
2025-02-14 10:56store
  • No user facing changes
2025-02-07 11:06ops
  • No user facing changes
2025-02-07 11:06svc
  • No user facing changes
2025-02-07 11:06session
  • No user facing changes
2025-02-07 11:06store
  • No user facing changes
2025-01-31 15:29ops
  • Address CVE-2025-0509
  • Address CVE-2025-21502
2025-01-31 15:29svc
  • Address CVE-2025-0509
  • Address CVE-2025-21502
2025-01-31 15:29session
  • Address CVE-2025-0509
  • Address CVE-2025-21502
2025-01-31 15:29store
  • Address CVE-2025-0509
  • Address CVE-2025-21502
2025-01-24 9:52ops
  • No user facing changes
2025-01-24 9:52svc
  • No user facing changes
2025-01-24 9:52session
  • No user facing changes
2025-01-24 9:52store
  • No user facing changes
2025-01-17 14:36ops
  • No user facing changes
2025-01-17 14:36svc
  • No user facing changes
2025-01-17 14:36session
  • No user facing changes
2025-01-17 14:36store
  • No user facing changes
2025-01-10 17:11ops
  • No user facing changes
2025-01-10 17:11svc
  • No user facing changes
2025-01-10 17:11session
  • No user facing changes
2025-01-10 17:11store
  • No user facing changes
2025-01-03 14:36ops
  • No user facing changes
2025-01-03 14:36svc
  • No user facing changes
2025-01-03 14:36session
  • No user facing changes
2025-01-03 14:36store
  • No user facing changes
2024-12-27 16:30ops
  • No user facing changes
2024-12-27 16:30svc
  • No user facing changes
2024-12-27 16:30session
  • No user facing changes
2024-12-27 16:30store
  • No user facing changes
2024-12-20 11:06ops
  • No user facing changes
2024-12-20 11:06svc
  • No user facing changes
2024-12-20 11:06session
  • No user facing changes
2024-12-20 11:06store
  • No user facing changes
2024-12-13 14:07ops
  • No user facing changes
2024-12-13 14:07svc
  • No user facing changes
2024-12-13 14:07session
  • No user facing changes
2024-12-13 14:07store
  • No user facing changes
2024-12-06 17:14ops
  • No user facing changes
2024-12-06 17:14svc
  • No user facing changes
2024-12-06 17:14session
  • No user facing changes
2024-12-06 17:14store
  • No user facing changes
2024-11-29 10:27ops
  • No user facing changes
2024-11-29 10:27svc
  • No user facing changes
2024-11-29 10:27session
  • No user facing changes
2024-11-29 10:27store
  • No user facing changes
2024-11-22 12:07ops
  • No user facing changes
2024-11-22 12:07svc
  • No user facing changes
2024-11-22 12:07session
  • No user facing changes
2024-11-22 12:07store
  • No user facing changes
2024-11-15 14:21ops
  • Address CVE-2024-10976
  • Address CVE-2024-10977
  • Address CVE-2024-10978
  • Address CVE-2024-10979
2024-11-15 14:21svc
  • Address CVE-2024-10976
  • Address CVE-2024-10977
  • Address CVE-2024-10978
  • Address CVE-2024-10979
2024-11-15 14:21session
  • No user facing changes
2024-11-15 14:21store
  • No user facing changes
2024-11-08 15:47ops
  • No user facing changes
2024-11-08 15:47svc
  • No user facing changes
2024-11-08 15:47session
  • No user facing changes
2024-11-08 15:47store
  • No user facing changes
2024-11-02 18:29ops
  • No user facing changes
2024-11-02 18:29svc
  • No user facing changes
2024-11-02 18:29session
  • No user facing changes
2024-11-02 18:29store
  • No user facing changes
2024-10-25 10:38ops
  • Address CVE-2024-21235
  • Address CVE-2024-21208
  • Address CVE-2024-21210
  • Address CVE-2024-21217
  • Address CVE-2023-42950
  • Address CVE-2024-25062
2024-10-25 10:38svc
  • Address CVE-2024-21235
  • Address CVE-2024-21208
  • Address CVE-2024-21210
  • Address CVE-2024-21217
  • Address CVE-2023-42950
  • Address CVE-2024-25062
2024-10-25 10:38session
  • Address CVE-2024-21235
  • Address CVE-2024-21208
  • Address CVE-2024-21210
  • Address CVE-2024-21217
  • Address CVE-2023-42950
  • Address CVE-2024-25062
2024-10-25 10:38store
  • Address CVE-2024-21235
  • Address CVE-2024-21208
  • Address CVE-2024-21210
  • Address CVE-2024-21217
  • Address CVE-2023-42950
  • Address CVE-2024-25062
2024-10-23 22:06ops
  • Add new /env/bucket/grant and /env/bucket/revoke endpoints; These let one grant read rights to an environment's data bucket to an AWS role in one's one account required params: env = environment, arn = AWS entity that will be granted read rights
  • /env/get will have a new key "bucketGrantees" describing roles that have been granted access to the data bucket
2024-10-18 14:59ops
  • No user facing changes
2024-10-18 14:59svc
  • No user facing changes
2024-10-18 14:59session
  • No user facing changes
2024-10-18 14:59store
  • No user facing changes
2024-10-11 17:53ops
  • No user facing changes
2024-10-11 17:53svc
  • No user facing changes
2024-10-11 17:53session
  • No user facing changes
2024-10-11 17:53store
  • No user facing changes
2024-10-04 09:57ops
  • No user facing changes
2024-10-04 09:57svc
  • No user facing changes
2024-10-04 09:57session
  • No user facing changes
2024-10-04 09:57store
  • No user facing changes
2024-09-27 13:18ops
  • No user facing changes
2024-09-27 13:18svc
  • No user facing changes
2024-09-27 13:18session
  • No user facing changes
2024-09-27 13:18store
  • No user facing changes
2024-09-20 10:48ops
  • No user facing changes
2024-09-20 10:48svc
  • No user facing changes
2024-09-20 10:48session
  • No user facing changes
2024-09-20 10:48store
  • No user facing changes
2024-09-13 11:34ops
  • No user facing changes
2024-09-13 11:34svc
  • No user facing changes
2024-09-13 11:34session
  • No user facing changes
2024-09-13 11:34store
  • No user facing changes
2024-09-06 10:23ops
  • No user facing changes
2024-09-06 10:23svc
  • No user facing changes
2024-09-06 10:23session
  • No user facing changes
2024-09-06 10:23store
  • No user facing changes
2024-08-30 18:01ops
  • No user facing changes
2024-08-30 18:01svc
  • No user facing changes
2024-08-30 18:01session
  • No user facing changes
2024-08-30 18:01store
  • Fix bug that could cause some long running queries to fail with an "Unknown error while returning streamed response" message.
    This would typically only occur for stores with more than 1 shard.
    Older stores should be backed up and restored to a new store in order to take advantage of this fix.
2024-08-23 20:25ops
  • No user facing changes
2024-08-23 20:25svc
  • No user facing changes
2024-08-23 20:25session
  • No user facing changes
2024-08-23 20:25store
  • No user facing changes
2024-08-16 15:23ops
  • No user facing changes
2024-08-16 15:23svc
  • No user facing changes
2024-08-16 15:23session
  • No user facing changes
2024-08-16 15:23store
  • No user facing changes
2024-08-09 14:15ops
  • Address CVE-2024-7348
  • Address CVE-2023-5869
2024-08-09 14:15svc
  • Address CVE-2024-7348
  • Address CVE-2023-5869
2024-08-09 14:15session
  • No user facing changes
2024-08-09 14:15store
  • No user facing changes
2024-08-02 16:08ops
  • No user facing changes
2024-08-02 16:08svc
  • No user facing changes
2024-08-02 16:08session
  • No user facing changes
2024-08-02 16:08store
  • No user facing changes
2024-07-26 11:52ops
  • No user facing changes
2024-07-26 11:52svc
  • No user facing changes
2024-07-26 11:52session
  • No user facing changes
2024-07-26 11:52store
  • No user facing changes
2024-07-19 12:59ops
  • Address CVE-2024-27983
  • Address CVE-2024-21147
  • Address CVE-2024-21145
  • Address CVE-2024-21140
  • Address CVE-2024-21144
  • Address CVE-2024-21131
  • Address CVE-2024-21138
  • Address CVE-2024-27980
  • Address CVE-2024-27982
2024-07-19 12:59svc
  • Fix bug where a 500 (rather than a 400) http status code was returned for invalid calls to /schema/add (missing name, invalid type, etc.)
  • Address CVE-2024-27983
  • Address CVE-2024-21147
  • Address CVE-2024-21145
  • Address CVE-2024-21140
  • Address CVE-2024-21144
  • Address CVE-2024-21131
  • Address CVE-2024-21138
  • Address CVE-2024-27980
  • Address CVE-2024-27982
2024-07-19 12:59session
  • Address CVE-2024-27983
  • Address CVE-2024-21147
  • Address CVE-2024-21145
  • Address CVE-2024-21140
  • Address CVE-2024-21144
  • Address CVE-2024-21131
  • Address CVE-2024-21138
  • Address CVE-2024-27980
  • Address CVE-2024-27982
2024-07-19 12:59store
  • Address CVE-2024-27983
  • Address CVE-2024-21147
  • Address CVE-2024-21145
  • Address CVE-2024-21140
  • Address CVE-2024-21144
  • Address CVE-2024-21131
  • Address CVE-2024-21138
  • Address CVE-2024-27980
  • Address CVE-2024-27982
2024-07-17 15:53svc
  • Fix issue where a sufficiently high enough number of concurrent /publish calls could cause 500s with an exception containing "Unable to load credentials from any of the providers in the chain AwsCredentialsProviderChain(credentialsProviders"
2024-07-12 13:10ops
  • No user facing changes
2024-07-12 13:10svc
  • No user facing changes
2024-07-12 13:10session
  • No user facing changes
2024-07-12 13:10store
  • No user facing changes
2024-07-05 11:05ops
  • No user facing changes
2024-07-05 11:05svc
  • No user facing changes
2024-07-05 11:05session
  • No user facing changes
2024-07-05 11:05store
  • No user facing changes
2024-06-28 09:43ops
  • No user facing changes
2024-06-28 09:43svc
  • No user facing changes
2024-06-28 09:43session
  • No user facing changes
2024-06-28 09:43store
  • No user facing changes
2024-06-21 14:39ops
  • No user facing changes
2024-06-21 14:39svc
  • No user facing changes
2024-06-21 14:39session
  • No user facing changes
2024-06-21 14:39store
  • No user facing changes
2024-06-14 09:41ops
  • No user facing changes
2024-06-14 09:41svc
  • No user facing changes
2024-06-14 09:41session
  • No user facing changes
2024-06-14 09:41store
  • No user facing changes
2024-06-07 16:03ops
  • No user facing changes
2024-06-07 16:03svc
  • No user facing changes
2024-06-07 16:03session
  • No user facing changes
2024-06-07 16:03store
  • No user facing changes
2024-05-31 20:39ops
  • No user facing changes
2024-05-31 20:39svc
  • No user facing changes
2024-05-31 20:39session
  • No user facing changes
2024-05-31 20:39store
  • No user facing changes
2024-05-24 15:53ops
  • No user facing changes
2024-05-24 15:53svc
  • No user facing changes
2024-05-24 15:53session
  • No user facing changes
2024-05-24 15:53store
  • No user facing changes
2024-05-17 14:45ops
  • No user facing changes
2024-05-17 14:45svc
  • No user facing changes
2024-05-17 14:45session
  • No user facing changes
2024-05-17 14:45store
  • No user facing changes
2024-05-10 09:53ops
  • Address CVE-2024-4317
2024-05-10 09:53svc
  • Address CVE-2024-4317
2024-05-10 09:53session
  • No user facing changes
2024-05-10 09:53store
  • No user facing changes
2024-05-03 10:43ops
  • No user facing changes
2024-05-03 10:43svc
  • No user facing changes
2024-05-03 10:43session
  • No user facing changes
2024-05-03 10:43store
  • No user facing changes
2024-04-26 13:19ops
  • No user facing changes
2024-04-26 13:19svc
  • No user facing changes
2024-04-26 13:19session
  • No user facing changes
2024-04-26 13:19store
  • No user facing changes
2024-04-26 10:18reports
  • No user facing changes
2024-04-19 10:14ops
  • Address CVE-2023-22043
  • Address CVE-2023-22041
  • Address CVE-2023-22051
  • Address CVE-2023-25193
  • Address CVE-2023-22044
  • Address CVE-2023-22045
  • Address CVE-2023-22049
  • Address CVE-2023-22036
  • Address CVE-2023-22006
2024-04-19 10:14svc
  • Address CVE-2023-22043
  • Address CVE-2023-22041
  • Address CVE-2023-22051
  • Address CVE-2023-25193
  • Address CVE-2023-22044
  • Address CVE-2023-22045
  • Address CVE-2023-22049
  • Address CVE-2023-22036
  • Address CVE-2023-22006
2024-04-19 10:14session
  • Address CVE-2023-22043
  • Address CVE-2023-22041
  • Address CVE-2023-22051
  • Address CVE-2023-25193
  • Address CVE-2023-22044
  • Address CVE-2023-22045
  • Address CVE-2023-22049
  • Address CVE-2023-22036
  • Address CVE-2023-22006
2024-04-19 10:14store
  • No user facing changes
2024-04-12 10:26ops
  • No user facing changes
2024-04-12 10:26svc
  • No user facing changes
2024-04-12 10:26session
  • No user facing changes
2024-04-12 10:26store
  • No user facing changes
2024-04-05 16:57ops
  • No user facing changes
2024-04-05 16:57svc
  • No user facing changes
2024-04-05 16:57session
  • No user facing changes
2024-04-05 16:57store
  • No user facing changes
2024-03-29 10:39ops
  • No user facing changes
2024-03-29 10:39svc
  • No user facing changes
2024-03-29 10:39session
  • No user facing changes
2024-03-29 10:39store
  • No user facing changes
2024-03-22 10:55ops
  • No user facing changes
2024-03-22 10:55svc
  • No user facing changes
2024-03-22 10:55session
  • No user facing changes
2024-03-22 10:55store
  • No user facing changes
2024-03-15 09:42ops
  • No user facing changes
2024-03-15 09:42svc
  • No user facing changes
2024-03-15 09:42session
  • No user facing changes
2024-03-15 09:42store
  • No user facing changes
2024-03-08 09:23ops
  • No user facing changes
2024-03-08 09:23svc
  • No user facing changes
2024-03-08 09:23session
  • No user facing changes
2024-03-08 09:23store
  • No user facing changes
2024-03-01 10:35ops
  • Address CVE-2024-1597
2024-03-01 10:35svc
  • Address CVE-2024-1597
2024-03-01 10:35session
  • No user facing changes
2024-03-01 10:35store
  • No user facing changes
2024-02-23 15:25ops
  • Address CVE-2024-0985
2024-02-23 15:25svc
  • Address CVE-2024-0985
2024-02-23 15:25session
  • No user facing changes
2024-02-23 15:25store
  • No user facing changes
2023-02-16 10:30ops
  • No user facing changes
2023-02-16 10:30svc
  • No user facing changes
2023-02-16 10:30session
  • No user facing changes
2023-02-16 10:30store
  • No user facing changes
2023-02-09 9:40ops
  • No user facing changes
2023-02-09 9:40svc
  • No user facing changes
2023-02-09 9:40session
  • No user facing changes
2023-02-09 9:40store
  • No user facing changes
2023-02-02 14:30ops
  • No user facing changes
2023-02-02 14:30svc
  • No user facing changes
2023-02-02 14:30session
  • No user facing changes
2023-02-02 14:30store
  • No user facing changes
2023-01-26 16:35ops
  • No user facing changes
2023-01-26 16:35svc
  • No user facing changes
2023-01-26 16:35session
  • No user facing changes
2023-01-26 16:35store
  • No user facing changes
2024-01-19 15:00ops
  • Address CVE-2023-5072
  • Address CVE-2024-20932
  • Address CVE-2024-20918
  • Address CVE-2024-20952
  • Address CVE-2024-20919
  • Address CVE-2024-20921
  • Address CVE-2024-20926
  • Address CVE-2024-20945
  • Address CVE-2024-20955
2024-01-19 15:00svc
  • Address CVE-2023-5072
  • Address CVE-2024-20932
  • Address CVE-2024-20918
  • Address CVE-2024-20952
  • Address CVE-2024-20919
  • Address CVE-2024-20921
  • Address CVE-2024-20926
  • Address CVE-2024-20945
  • Address CVE-2024-20955
2024-01-19 15:00session
  • Address CVE-2023-5072
  • Address CVE-2024-20932
  • Address CVE-2024-20918
  • Address CVE-2024-20952
  • Address CVE-2024-20919
  • Address CVE-2024-20921
  • Address CVE-2024-20926
  • Address CVE-2024-20945
  • Address CVE-2024-20955
2024-01-19 15:00store
  • Address CVE-2023-5072
  • Address CVE-2024-20932
  • Address CVE-2024-20918
  • Address CVE-2024-20952
  • Address CVE-2024-20919
  • Address CVE-2024-20921
  • Address CVE-2024-20926
  • Address CVE-2024-20945
  • Address CVE-2024-20955
2024-01-12 16:10ops
  • No user facing changes
2024-01-12 16:10svc
  • No user facing changes
2024-01-12 16:10session
  • No user facing changes
2024-01-12 16:10store
  • No user facing changes
2024-01-05 10:20ops
  • No user facing changes
2024-01-05 10:20svc
  • No user facing changes
2024-01-05 10:20session
  • No user facing changes
2024-01-05 10:20store
  • No user facing changes
2023-12-29 12:55ops
  • No user facing changes
2023-12-29 12:55svc
  • No user facing changes
2023-12-29 12:55session
  • No user facing changes
2023-12-29 12:55store
  • No user facing changes
2023-12-22 17:30ops
  • No user facing changes
2023-12-22 17:30svc
  • No user facing changes
2023-12-22 17:30session
  • No user facing changes
2023-12-22 17:30store
  • No user facing changes
2023-12-15 10:10ops
  • No user facing changes
2023-12-15 10:10svc
  • No user facing changes
2023-12-15 10:10session
  • No user facing changes
2023-12-15 10:10store
  • No user facing changes
2023-12-08 10:10ops
  • No user facing changes
2023-12-08 10:10svc
  • No user facing changes
2023-12-08 10:10session
  • No user facing changes
2023-12-08 10:10store
  • No user facing changes
2023-12-01 18:45ops
  • Address CVE-2023-45648
2023-12-01 18:45svc
  • Address CVE-2023-45648
2023-12-01 18:45session
  • Address CVE-2023-45648
2023-12-01 18:45store
  • No user facing changes
2023-11-25 14:50ops
  • No user facing changes
2023-11-25 14:50svc
  • No user facing changes
2023-11-25 14:50session
  • No user facing changes
2023-11-25 14:50store
  • No user facing changes
2023-11-17 14:30ops
  • Address CVE-2023-5868
  • Address CVE-2023-5869
  • Address CVE-2023-5870
2023-11-17 14:30svc
  • Address CVE-2023-5868
  • Address CVE-2023-5869
  • Address CVE-2023-5870
2023-11-17 14:30session
  • No user facing changes
2023-11-17 14:30store
  • No user facing changes
2023-11-10 09:15ops
  • No user facing changes
2023-11-10 09:15svc
  • No user facing changes
2023-11-10 09:15session
  • No user facing changes
2023-11-10 09:15store
  • No user facing changes
2023-11-03 12:45ops
  • No user facing changes
2023-11-03 12:45svc
  • No user facing changes
2023-11-03 12:45session
  • No user facing changes
2023-11-03 12:45store
  • No user facing changes
2023-10-27 14:45ops
  • No user facing changes
2023-10-27 14:45svc
  • No user facing changes
2023-10-27 14:45session
  • No user facing changes
2023-10-27 14:45store
  • No user facing changes
2023-10-20 23:00ops
  • No user facing changes
2023-10-20 23:00svc
  • No user facing changes
2023-10-20 23:00session
  • No user facing changes
2023-10-20 23:00store
  • No user facing changes
2023-10-14 10:10ops
  • No user facing changes
2023-10-14 10:10svc
  • No user facing changes
2023-10-14 10:10session
  • No user facing changes
2023-10-14 10:10store
  • No user facing changes
2023-10-09 21:00ops
  • No user facing changes
2023-10-09 21:00svc
  • No user facing changes
2023-10-09 21:00session
  • No user facing changes
2023-10-09 21:00store
  • No user facing changes
2023-09-29 15:18ops
  • No user facing changes
2023-09-29 15:18svc
  • Behavior change: remove _version_ attribute from all /query output (this field was an internal implementation detail and had no practical use to end users)
2023-09-29 15:18session
  • No user facing changes
2023-09-29 15:18store
  • No user facing changes
2023-09-26 15:40ops
  • No user facing changes
2023-09-22 22:28svc
  • Fix bug where /modify was not properly doing typical schema related transformations that /publish performs
  • Fix bug where /get could return the wrong doc in some cases (this was a regression from the release prior in the day)
2023-09-22 12:30ops
  • Address CVE-2023-41080
2023-09-22 12:30svc
  • Address CVE-2023-41080
  • Add new /modify endpoint for direct lake modification Rights: Requires publish right for inserts/updates and the delete right for deletes Parameters: "e" a list of entities to be persisted ot the datalake; entities with an _m1key will be updated entities without an _m1key will be inserted "deleted" a list of _m1key values whose entities will be deleted Returns: A map containing the # of documents updated, deleted, and the lowest _m1key of inserted docs
2023-09-22 12:30session
  • Address CVE-2023-41080
2023-09-22 12:30store
  • No user facing changes
2023-09-15 16:30ops
  • No user facing changes
2023-09-15 16:30svc
  • No user facing changes
2023-09-15 16:30session
  • No user facing changes
2023-09-15 16:30store
  • No user facing changes
2023-09-08 12:40ops
  • No user facing changes
2023-09-08 12:40svc
  • No user facing changes
2023-09-08 12:40session
  • No user facing changes
2023-09-08 12:40store
  • No user facing changes
2023-09-01 11:10ops
  • No user facing changes
2023-09-01 11:10svc
  • No user facing changes
2023-09-01 11:10session
  • No user facing changes
2023-09-01 11:10store
  • No user facing changes
2023-08-25 16:05ops
  • Address CVE-2023-39417
  • Address CVE-2023-39418
2023-08-25 16:05svc
  • Address CVE-2023-39417
  • Address CVE-2023-39418
  • Add cpu utilization in health check
2023-08-25 16:05session
  • Add cpu utilization in health check
2023-08-25 16:05store
  • Add cpu utilization in health check
2023-08-18 12:25ops
  • No user facing changes
2023-08-18 12:25svc
  • No user facing changes
2023-08-18 12:25session
  • No user facing changes
2023-08-18 12:25store
  • No user facing changes
2023-08-11 16:05ops
  • No user facing changes
2023-08-11 16:05svc
  • No user facing changes
2023-08-11 16:05session
  • No user facing changes
2023-08-11 16:05store
  • No user facing changes
2023-08-06 15:40ops
  • No user facing changes
2023-08-06 15:40svc
  • No user facing changes
2023-08-06 15:40session
  • No user facing changes
2023-08-06 15:40store
  • No user facing changes
2023-07-30 13:40ops
  • No user facing changes
2023-07-30 13:40svc
  • No user facing changes
2023-07-30 13:40session
  • No user facing changes
2023-07-30 13:40store
  • No user facing changes
2023-07-28 21:00svc
  • Enhancement to /query jsonl behavior -- the first line returned will not only include the information from the responseHeader node available in the json response but will also now additionally include all metadata fields from the response node
2023-07-28 17:45svc
  • Change in behavior to /query when using the jsonl format -- the first line will now be the responseHeader normally returned with the json format.
2023-07-24 19:20ops
  • Address CVE-2023-22043
  • Address CVE-2023-22041
  • Address CVE-2023-22051
  • Address CVE-2023-25193
  • Address CVE-2023-22044
  • Address CVE-2023-22045
  • Address CVE-2023-22049
  • Address CVE-2023-22036
  • Address CVE-2023-22006
2023-07-24 19:20svc
  • Truncate query in error messages that echo query; makes error messages involving large queries much more readable
  • Address CVE-2023-22043
  • Address CVE-2023-22041
  • Address CVE-2023-22051
  • Address CVE-2023-25193
  • Address CVE-2023-22044
  • Address CVE-2023-22045
  • Address CVE-2023-22049
  • Address CVE-2023-22036
  • Address CVE-2023-22006
2023-07-24 19:20session
  • Address CVE-2023-22043
  • Address CVE-2023-22041
  • Address CVE-2023-22051
  • Address CVE-2023-25193
  • Address CVE-2023-22044
  • Address CVE-2023-22045
  • Address CVE-2023-22049
  • Address CVE-2023-22036
  • Address CVE-2023-22006
2023-07-24 19:20store
  • Address CVE-2023-22043
  • Address CVE-2023-22041
  • Address CVE-2023-22051
  • Address CVE-2023-25193
  • Address CVE-2023-22044
  • Address CVE-2023-22045
  • Address CVE-2023-22049
  • Address CVE-2023-22036
  • Address CVE-2023-22006
2023-07-18 19:15ops
  • Fix bug where large POST payloads (>2MB) would fail
2023-07-18 19:15svc
  • Fix bug where large POST payloads (>2MB) would fail
2023-07-18 19:15session
  • Fix bug where large POST payloads (>2MB) would fail
2023-07-18 19:15store
  • No user facing changes
2023-07-16 16:15ops
  • Address CVE-2023-34981
2023-07-16 16:15svc
  • Address CVE-2023-34981
2023-07-16 16:15session
  • Address CVE-2023-34981
2023-07-16 16:15store
  • No user facing changes
2023-07-13 15:00svc
  • Fix regression in 2023-07-12 release that would cause svc servers to be unable to connect to store servers.
2023-07-12 19:34svc
  • /query format parameter now supports jsonl in addition to csv (and the default json); the jsonl and csv types can only used for either documents or facets (not both in one query). In addition only a single facet can be returned in a format other than than json
2023-07-09 17:00ops
  • Fix bug where admin param was required for account/list; this regression occured in the 2023-06-05 release
  • Support POST in addition to GET for account/list, env/list
  • Make rights parameter in account/user/add not required
  • Address CVE-2021-23214
  • Address CVE-2021-23222
  • Address CVE-2021-32027
  • Address CVE-2021-32028
  • Address CVE-2021-32029
  • Address CVE-2022-1552
  • Address CVE-2022-2625
  • Address CVE-2022-41862
  • Address CVE-2023-2454
  • Address CVE-2023-2455
2023-07-09 17:00svc
  • No user facing changes
2023-07-09 17:00session
  • No user facing changes
2023-07-09 17:00store
  • No user facing changes
2023-07-04 09:10ops
  • Change a couple of http error codes from 409 (CONFLICT) to 400 (BAD REQUEST)
2023-07-04 09:10svc
  • No user facing changes
2023-07-04 09:10session
  • No user facing changes
2023-07-04 09:10store
  • No user facing changes
2023-06-27 20:50ops
  • No user facing changes
2023-06-27 20:50svc
  • No user facing changes
2023-06-27 20:50session
  • No user facing changes
2023-06-27 20:50store
  • No user facing changes
2023-06-26 13:26reports
  • Fix bug where incorrect # of documents would get exported when the number of documents to export exceeded 1,000,000 documents
2023-06-21 10:41ops
  • Fix bug with env/rescale ZDD deployments; previously a rescale may have caused a temporary outage observed as 503 errors
  • Make various environment related methods return a 400 in the case of a user error rather than a 409
2023-06-21 10:41svc
  • Fix a regression introduced in 2023-06-05 release that broke CORS
  • Better error message and status code in store/add and session/add when trying to add a store that already exists
2023-06-21 10:41session
  • No user facing changes
2023-06-21 10:41store
  • No user facing changes
2023-06-20 17:06reports
  • Fix bug where incorrect number of documents were getting exported
2023-06-05 10:15ops
  • General performance improvements
2023-06-05 10:15svc
  • General performance improvements
  • /next, /store/list, /session/list, /token/list, /health endpoints can now accept POST requests in addition to GETs
2023-06-05 10:15session
  • General performance improvements
2023-06-05 10:15store
  • No user facing changes
2023-05-11 22:15ops
  • No user facing changes
2023-05-11 22:15svc
  • Better error messages for data store related issues
  • Better error messages when an extremely long string can't be coerced into a an expected type; previously the long string would be truncated and any characters after the first 80 would be omitted. Now the first 40 and last 40 characters are shown.
  • /health now shows memory usage for svc, data stores, and session stores
  • /health now shows disk usage for data stores
  • Rename weightedAvg aggregator to avg; weightedAvg is deprecated and will be removed in a future release
  • The previous behavior of avg, which returned the avg of unique values of a field, can be obtained by a new aggregator uniqueAvg
2023-05-11 22:15store
  • Provide disk/memory information exposed via environment /health service
2023-05-11 22:15session
  • Provide memory information exposed via environment /health service
2023-05-01 20:30ops
  • No user facing changes
2023-05-01 20:30svc
  • No user facing changes
2023-05-01 20:30session
  • No user facing changes
2023-05-01 09:50svc
  • Change in behavior regarding boolean types:
  • Previously all values other than the string "true" (including null) were interpreted as false;
  • Now null is simply null and consistent with other data types
  • In addition to null, valid boolean values are "true", "1", "t", "y", "yes", "false", "0", "f", "n", "no", 1, and 0 and any cased variations
  • Publishing a boolean value not in that valid set will cause an error if publish-permissive is false or do nothing if publish-permissive is true (this is consistent with behavior of other data types)
2023-04-23 13:30svc
  • New system property property-source: when populated, published documents will have an additional attribute indicating the source (typically an s3 file) of the document.
  • Add system property property-unknown: when publish-permissive is true and a document was only partially loaded, property-unknown names a property that will contain all properties that were not loaded because the property was not present in the schema.
  • Add system property property-error: when publish-permissive is true and a document was only partially loaded, property-error names a property that will contain all properties that were not loaded for reasons other than a missing schema element; this will generally be because of data type mismatches ("xyz" for a date or numeric field, 1.2 for a double field, etc.)
2023-04-18 22:30ops
  • No user facing changes
2023-04-18 22:30svc
  • No user facing changes
2023-04-18 22:30session
  • No user facing changes
2023-04-16 19:00svc
  • Add store/rename and session/rename endpoints
  • Raise error if store param is missing for /session/key
  • Fix a couple of potential resource leaks related to db resources
  • Better handling of OOM situations; a service that runs into an OOM situation is killed so that it can be brought back up cleanly
2023-04-16 19:00session
  • Fix a couple of potential resource leaks related to db resources
  • Better handling of OOM situations; a service that runs into an OOM situation is killed so that it can be brought back up cleanly
2023-04-16 19:00ops
  • Add env/store/rename and /env/session/rename endpoints
  • Environment TLS policy now disallows tls 1 and tls1.1; services now rated an A by ssllabs.com
  • Fix a couple of potential resource leaks related to db resources
  • Better handling of OOM situations; a service that runs into an OOM situation is killed so that it can be brought back up cleanly
2023-03-29 10:05svc
  • Bulletproof geo appending when matched geo data does not contain latitude/longitude data
2023-03-28 20:55svc
  • Bulletproof geo appending when client supplies ip address that is not a true ip address
2023-03-25 21:30ops
  • More helpful error messages when request params fail validation
  • Store names can only have lower case letter, numbers, or hyphens; uppercase letters are no longer allowed
2023-03-25 21:30svc
  • More helpful error messages when request params fail validation
  • Store names can only have lower case letter, numbers, or hyphens; uppercase letters are no longer allowed
  • Fix bug that was thought to be fixed in 2023-03-10 release involving sending back the query params in the response to /query.
2023-03-25 21:30session
  • No specific session store fixes but rebuilding image because of a number of changes with common code
2023-03-16 19:30reports
  • Small layout fix
2023-03-13 18:00reports
  • Fix some bugs in 2023-03-10 deployment
  • Change to support svc breaking change from 2023-03-10
2023-03-10 18:00reports
  • Support brandability: Override brand.css and brand.js in the theme directory.
2023-03-10 03:42svc
  • Fix bug where /query was not sending back exact params sent to it
  • Breaking change: /query response responseHeader.params.json was previously the raw json passed in; this string is now json parsed
2023-03-09 18:00reports
  • Allow Ctrl+F style searchability of column headers
  • Fixed bug returning rows in case of facets query.
2023-03-09 14:30svc
  • Fix /query NPE bug if facet keys contain periods
2023-03-08 13:20svc
  • Fix bug where session store key was not respected
  • Environment data and session store definitions are now cached and refreshed every 5 seconds; note when using /store/* and /session/* services. This is to improve performance in for high volume usages of /insert or /session/update
  • Support yyyy-mm-dd style dates
  • Date related formatters in transform rules sets now use Java 8 DateTimeFormatter syntax instead of SimpleDateFormat syntax; DateTimeFormatter provides a superset of functionality and is backwards compatible
  • Substantial json serialization performance improvement
  • Support countUnique/avg/weightedAvg facet aggregators in /query
  • Better error messages around /query; ignore (rather than error) unhandled params
2023-03-08 13:20session
  • No user facing changes
2023-03-07 14:00store
  • Fix bug introduced in 2023-02-27 store release that would prevent a boost store from getting created (related to dynamically setting memory usage)
2023-02-27 21:00store
  • Default default search operator back to OR (from AND) (this changed somewhat accidentally in Dec-2023)
2023-02-26 18:00ops
  • Substantial json serialization performance improvement
2023-02-10 10:25ops
  • Error message grammar fix when unable to create an environment

© 2021-2026 MinusOne, Inc.