New version of Geocoding Augmentation Extractor

Geocoding Augmentation Extractor has been rewritten as Docker component and the old version will be switched off by the end of June. Till then its users are kindly requested to migrate their configuration to the new version. Here is how to do it:

  1.  Choose Geocoding v2 from list of extractors
  2. Create new configuration and give it some name as usual
  3. Add extraction configuration
    1. Add one or more input tables to input mapping. Please note that the table must have exactly one column with locations (or two columns with latitudes and longitudes in case of reverse geocoding) or you have to map the one (or two) columns in the input mapping.
    2. Add exactly one table to output mapping which will be filled with result of geocoding.
    3. Fill parameters configuration. It is in json format and must contain method of geocoding, data provider and other optional parameters like api key or locale. See for more details

Week in Review – April 11, 2016

New Extractors and Writers

Last week were introduced some new components:
  • Conductor Searchlight API Extractor
  • Portadi Extractor
  • Stripe Extractor
  • Mode Analytics Writer

Enhancement to components with oAuth authorization

If you need to authorize access to a service from someone who does not have account in Keboola you can generate external link which will guide him through this process. Components supporting this feature so far are AdWords, BingAds, and Gmail, others like Google Drive, Google Analytics and Twitter will follow soon.

Job Events fixes

  • new lines in event messages are formatted correctly
  • ui stopped to poll for new events as soon as job finished which caused that some of them were not displayed without reload of the page

Other posts this week

GoodData API issues

Some older GoodData Writer configurations may experience fails of update model jobs which are accompanied by error message "You can not use a model that contains two or more facts identified by ids having same two tailing segments.". The problems are caused by some unexpected changes in GoodData's Project Model API after their Saturday's release. We are trying to fix the situation in cooperation with GoodData support. Thanks for your patience.

UPDATE (18:00 CET): The problem still isn't solved and apparently will take some more time. We will keep you updated. However you should be able to load data if you avoid updating of project model. It means use API calls load-data or load-data-multi instead of update-table and update-project (see API documentation)

UPDATE (Mar 22 17:30 CET): GoodData released a fix which prevents those failures of update model jobs. Writer should work without problem now. Thanks for your patience.

AdWords Exractor API Update

Extractor will update to API v201601 of AdWords API in the beginning of April. Please be sure to review your configuration so that it does not use no-longer supported metric names till the end of March. Also do not use new metrics until the update, we will let you know about it.