We've deployed a new version of Facebook Extractor, you can now see all extractor's jobs in the Jobs app.
The extractor is now fully asynchronous, so that means less (CURL) errors and more durability and better scalability.
If you encounter any problems, please let us know at support@keboola.com.
We just introduced an icon in input mapping to show, whether the input mapping is created as a view or a table.
Running Redshift transformations and reading data from Redshift Storage (which is the current recommended fastest option) you can choose between creating a table or a view in the input mapping. Whats the difference?
Views are lightning fast to create. Input mapping just aliases a table to your working schema within the cluster and that's it (including all filters). You can then layer another view on that and another... until you're done and you can set the final view as a source table for an output mapping. All the work is then done when processing the output mapping. That is the snatch - it is easier to reach the cluster's limits (memory, disk) with one large query (multiple nested views). And because the cluster is out of memory, it will also terminate all other queries running on the cluster at the same time.
So please be careful when using views. If you're not sure, feel free to reach out to support@keboola.com for more assistance.
UI for zendesk extractor has been visually redesigned.
Orchestrator's email notifications were redesigned.
If anything wrong happen, Orchestrator send you brief visual overview. All necessary details are accessible through UI. We're not spamming you by long list of logs anymore.
...were redesigned, so your debug scenario should work much smoothly. This is redesigned page with all Jobs and tasks details:
Paymo, Facebook, Facebook Ads and Salesforce extractors were returning curl(60) error in orchestrations from 3 PM - 11PM PST November 6th. Error was caused by invalid SSL certificates.
To finish your tasks, just re-run your orchestrators. We're sorry for any inconvenience!
Some files were not accessible between 7 PM - 10 PM PST November 4. It caused failures of loads to storage API tables and thus also orchestration failures.
Example of failed orchestration:
It was caused by failed Elasticsearch cluster node. We are still investigating the cause of this issue. However, our whole infrastructure works smoothly at this time. To finish your tasks, just re-run your orchestrators. We're sorry for any inconvenience!
Today we're announcing new Storage API feature: Bucket Credentials (api here).
If you're using Keboola Connection w/ Redshift backend, you can have read-only credentials (direct sql access) to any Redshift bucket.
In Storage API Console, go to Bucket Detail > Credentials and press "Create new credentials" button:
Describe new credentials (you can have multiple credentials assigned to each bucket!):
When you create credentials, carefully copy&paste credentials to you SQL client or preferred remote service (jackdb.com, chartio.com, etc.). After closing displayed credentials, you can't display it's settings:
In case you need to re-use already created credentials, you have to delete it and create new combination of username and password. All existing credentials are listed under it's bucket:
WARNING: Always employ SSL when accessing your data. Generated credentials are opening your dedicated AWS Redshift Cluster. Please read "Configure Security Options for Connections". Redshift Cluster's CA certificate can be downloaded here.
We released a new version of Orchestration API and UI. The UI is completely rebuildm is lightning fast and everything can be now configured within a single UI.
Here's a short list of the most exciting features:
Happy orchestrating!
UPDATE: A short outage occurred while migrating Orchestrator configurations causing some of the orchestrations to fail to start on schedule. We restarted all failed orchestrations manually. We're sorry for this inconvenience.
Today, 30 October 2014, Keboola is announcing an End-of-Life date of January 31, 2015 for all instances of the Old Twitter Extractor.
Customers that are currently using this version should evaluate our shiny, very powerful and fully configurable Twitter Extractor as a newer alternative. Information on the ex-twitter can be found in our documentation.
If you need any support, please contact us.
For those who love Tableau, we're officially launching "Tableau Writer". At this time, it's able to provision MySQL database or push data to your own MySQL server.
Our Tableau Writer allows you to rename tables, it's columns and define data types for better handling on Tableau side (which configuration is pretty straight forward too - just let Tableau connect to MySQL server with using proper credentials).
If you're "Tableau Desktop Personal Edition" user, you can enjoy TDE files very soon! (delivered to your Google Drive account automatically).