Map instantiation: Get columns from cache table instead of using `LIMIT 0` when avaiblable about camshaft HOT 9 CLOSED

I don't understand the context/problem. 😕

from camshaft.

Case 1:

• Modify a analysis (for example AOI) with cache and change the name of an output column.
• Forget to update version.
  Current result: Map fails to instantiate and it's inaccessible in builder.

Case 2:

• Modify a analysis (for example AOI) with cache and change the name of an output column.
• Update version.
  Current result: The analysis is rerun automagically.

This would address the first case and enables that the rerun in Case 2 is optional (since the map wouldn't be broken).

from camshaft.

Understood. Thank you.

About the "Case 2": As re-running is optional, how do we enable the user to re-run it?

from camshaft.

My idea is that this could be done in the UI after the instantiation (something like This analysis can be updated).
That should be another ticket after this one since it'd involve:

• Not doing the version update automatically when a difference is found.
• Returning extra information in the instantiation.
• Adding the UI stuff with the alert to trigger the update.

from camshaft.

And how that would work at API level?

from camshaft.

My initial idea is to add an extra (non-persisted) state to the analysis, upgradable which means that the analysis is ready but there is an update available. Then to update it you could push the new config as if the parameters had changed.

The analysis backend to handle changes seems to be defined in Builder (app/controllers/carto/api/analyses_controller.rb and app/models/carto/analysis.rb) so I expect some changes to be needed there to handle version mismatches in a different way.

from camshaft.

We've not deployed the new metadata columns for street geocoding because this affects us. Old analyses fail with this error:

The fix is simple: either change the data or, more correctly, change the analysis version to force rerunning it. But this implies a cost, so we chose not to expose those columns.

from camshaft.

Was the initial issue for this ticket solved with #372 ?

from camshaft.

Was the initial issue for this ticket solved with #372 ?

Yes, it was.

from camshaft.