Change Details

Before we can widely enable constraint checks, we almost certainly need to cache check results, otherwise the constraint checks will likely be too expensive. The problem is that for the most expensive constraints – type and value type – we can’t know when to invalidate the cache. Having a fairly short max-age (e. g. five minutes) will probably have to do, perhaps combined with an indication that the result may be outdated (similar to {T170672}).

Before we can widely enable constraint checks, we almost certainly need to cache check results, otherwise the constraint checks will likely be too expensive. The problem is that for the most expensive constraints – type and value type – we can’t know when to invalidate the cache. Having a fairly short max-age (e. g. five minutes) will probably have to do, perhaps combined with an indication that the result may be outdated (similar to {T170672}). [[ https://grafana.wikimedia.org/dashboard/db/wikidata-quality?orgId=1 | Grafana board ]]

Before we can widely enable constraint checks, we almost certainly need to cache check results, otherwise the constraint checks will likely be too expensive. The problem is that for the most expensive constraints – type and value type – we can’t know when to invalidate the cache. Having a fairly short max-age (e. g. five minutes) will probably have to do, perhaps combined with an indication that the result may be outdated (similar to {T170672}). [[ https://grafana.wikimedia.org/dashboard/db/wikidata-quality?orgId=1 | Grafana board ]]