Some GoodData Writer jobs were failing between 13:45 and 14:20 CEST due to internal error in the application. Hotfix was deployed immediately afterwards and it is properly fixed by now. Thanks for your understanding.
- Users from support does not count to the users per project limit.
- Partial imports no longer supported in the UI(Storage Api Console).
- JSON editor in the generic ui keeps the order of attributes when changed.
We did a little cleaning and dropped unused or deprecated components:
old Sklik extractor, old Adwords extractor, Instagram extractor, Telfa extractor, Marketo extractor, Elasticsearch extractor and writer, Linkdex extractor, App Annie extractor, Mandrill extractor.
Don't worry if you found yourself missing one of those, we are able to bring them back and have found effectively betters ways to do it ;)
Between 11:08am CEST and 2:03pm CEST under certain circumstances transformation jobs were forking from existing processing transformation jobs. We have found the root cause, fixed it, terminated all forks and restarted all failed orchestrations. If you're still seeing this issue, please let us know.
UPDATE: This issue occurred again between 4:49pm CEST and 8:05pm CEST.
We're sincerely sorry for this inconvenience.
We've launched a completely new version of the Twitter extractor which replaces the now slightly outdated version of Twitter extractor.
With the new extractor you can have Twitter data in Keboola Connection in just a few clicks. Just authorize your account, select whether you want timeline, mentions, followers or you can do a tweet search, save it and run the extraction.
There are two types of authorization available, you can authorize instantly if you have access to the target Twitter account, or you can use the external authorization and send an authorization link to the Twitter account user to authorize it for you.
If you are interested in more details like extractor limits and output data format please visit our new documentation.
Feel free to try the new extractor and in if you have any questions or something is missing, please contact us at support@keboola.com.
The old extractor, now named Twitter (DEPRECATED) in Keboola Connection, is now deprecated and will be shut down on 19th of June 2016.
If you need help with migration please let us know.
Dropbox writer improvements
You can now more finely configure output settings. Previously you weren't able to specify output file name, it was alway generated, now you are able to choose any file name you want.
Tableau writer improvements
Exported TDE file name can be changed from default in writer table settings.
Transformations
Sandbox load data dialog was simplified, you can now select buckets or tables to load in one input.
Storage API
Partial import is deprecated from now. This feature is supported only by MySQL backend and it is not used anymore by any of extractors or writers so it's deprecation and later shut down should not affect any projects.
Documentation
- User Documentation now supports https for better security.
-
User Documentation style was unified with Developers Documentation
Developers
We've open source GoodData PHP Client under MIT licence. This library is used by Keboola Connection GoodData writer.
Some of Good Data writer jobs have failed between 22:59 PDT and 23:44 PDT.
It was caused by incident in Keen.io service which Good Data writer uses.
We are sorry for any inconvenience.
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
We have discovered a bug in the Generic extractor, offsetting the string generated by user function `date` by two hours to the "Europe/Prague" timezone.
This error has been fixed and the fix will be deployed on wednesday April 14th. If your extractor uses a date function with `previousStart` time, it might cause a two hour overlap in results of some queries, in case it has been used to set a "since" date for some extraction.
The affected configuration would contain an object such as the following:
{
"start_date": {
"function": "date",
"args": [
"Y-m-d+H: i",
{
"time": "previousStart"
}
]
}
}We apologize for the inconvenience.
On Friday April 8th we'll be switching our Facebook Ads extractor to Facebook Marketing API from v2.4 to v2.5. If your configuration is using a fixed API version (api_version bucket attribute), please update it manually.
Please see the Graph API changelog to verify your configuration won't break, here's a shortlist:
Marketing API Changes from v2.4 to v2.5
- Consistent naming for three-level campaign structure between API and UI. This changes naming at endpoint, params, fields, and enum level. For the full list of changes, refer here.
- Change /adcampaign_groups to /campaigns
- Change /adcampaigns to /adsets
- Change /adgroups to /ads
- In the write path, change campaign_group_status, campaign_status, adgroup_status to status
- Campaign
- Change naming of objectives
- WEBSITE_CLICKS to LINK_CLICKS
- WEBSITE_CONVERSIONS to CONVERSIONS
- Targeting
- Response for call to /search?type=adgeolocation will contain only the 'City' instead of 'City, State'
- Change {cpc, cpm, cpa}_{min, max, median}, such as cpc_min fields in /reachestimate to bid_amount_min, bid_amount_median, bid_amount_max. Change bid_for to optimize_for
Should you encounter any issues after the update, please let us know at support@keboola.com.
In case you need a bit more time to migrate your configuration, use bucket attribute api_version and set it to v2.4. This will give you time until Facebook shuts down this version completely (Monday April 11th).
UPDATE: this issue has been solved and one shall not encounter the problem described below.
We have encountered problem when running orchestration manually from the orchestration detail page:
error message detail: "Error. [Task 0] Job task is different from orchestration task"
We are working on the fix of the problem which should be released within a short while.
Temporal workaround: if you are experiencing such a problem, you can fix it by resaving the orchestration tasks(Edit Tasks->Save).
All other orchestration features are working normally. We are sorry for any inconvenience.