Raul Ochoa
Raul Ochoa
That way we can use SQL API deployments configured as subdomainless.
Do a general pre-flight check that validates the table input size. If the table is gonna be used to generate a second table with extra information but it's already big...
Current progress: https://github.com/CartoDB/camshaft/pull/177.
Current status: https://github.com/CartoDB/camshaft/pull/35.
If there is a missing table, and although the catalog has the node as ready, we should populate the table once more. cc @zenitraM
Having a "points close to N meters (distance)" analysis would replace the current Buffer+Intersection anti-pattern. We have a `closest` analysis that only gets the closest geom for dataset B for...
The invalidation trigger should be similar to the one found at cdb_cartodbfytable. Reference: https://github.com/CartoDB/cartodb/issues/8571.
It will allow to use bigger jobs as they will use less memory in datastore. For really small jobs it will use more space, but that shouldn't be a problem....
See https://github.com/CartoDB/CartoDB-SQL-API/issues/271