dm4-contacts: suppress automatic geocoding when updating address topics from within a migration

[Malte]

From within a migration, it might be necessary to perform manual updates on existing "Address" topics, when updating an address topic the caller (up to my knowledge) can not easily append/create/inject a Cookie (e.g. "dm4_no_geocoding") into its update call.

Thus, when running such a migration i loose all my existing coordinate values in the to new ones from Google.

[Malte]

So, as it looks to me, "enhancing" the API this way is important for me updating and installing the kiezatlas2 to 4.8 in the couple of weeks. I know of a "workaround" (since this currently only affects a migration for which i could comment the geo-coder) but what is your take on this, is this easy to do?

[Malte]

Hi just wanted to ask again, since i will need to deploy this migration during the next week (final demo at 20.7) so: would a fix of this during the next two or three days be feasible? If not, i will find my way to deploy the migration without this, wouldn't be a huge deal.

Thanks for your help.

[jri]

Today I could implement a runWithoutGeoCoding() mechanism (analogous to runWithoutWorkspaceAssignment()).
Would this be still useful for you?
Sorry for the late reply.

[Malte]

Thanks, yes, it certainly would be helpful if contained in the 4.8.3 release.
The only requirement i have is that i can make use this feature in a migration.

[Jörg Richter <jri@…>]

In 569dfd1d7f453881e28a4226464d3da965ce2ed6/deepamehta:

Core: add ContextTracker utility (#980).

1 new class in de.deepamehta.core.util:

ContextTracker

See #980.

[Jörg Richter <jri@…>]

In 4682bbf797180d1b0d588eaf7e8d616ac7d83fc4/deepamehta:

Geomaps: suppress geocoding by code block (#980).

1 new method in GeomapsService:

<V> V runWithoutGeocoding(Callable<V> callable) throws Exception;

Executes the passed codeblock and suppresses geocoding for Address topics created/updated while execution.
Returns the value returned by the codeblock.

Note: suppressing geocoding by adding the dm4_no_geocoding cookie to the request still works.

Geocoding is suppressed if at least one condition is met: the cookie is present, or code executes via runWithoutGeocoding().

The latter is useful e.g. for code running in migrations.

See #980.