Since 2016-07-28 there were no updates in our currency tables. This was fixed today and all records were pushed into all projects that have Currency Extractor set up.
We're sorry for this inconvenience, let us know, if you have any concerns about this at support@keboola.com.
It's my pleasure to introduce another component into the family of Keboola Connection ecosystem: IBM dashDB Writer.
IBM dashDB is a new generation analytical datawarehouse. Build on core of DB2, Powered by in-memory and columnar storage and enhanced by in-database analytical functions migrated from IBM Netezza. You will find more in the documentation.
The current version of the writer supports transfers of the objects from Keboola Storage into dashDB tables and at the moment just full loads are supported. But you should have no problem to transfer even bigger files in decent time.
This writer is developed independently by Radek Tomášek with huge support of IBM. For more information on how to use the writer, please refer to the documentation.
We've recently introduced the configuration versioning management in transformations: http://status.keboola.com/transformation-versions-management
Now we've added a diff feature which allows comparisons of two adjacent versions, i,e., the differences between two configuration updates. For example, the user can now track and compare changes of sql queries in their transformations or changes in other parameters(input/output mapping).
Moreover, we extendeded this feature to other components such as all database extractors, all generic components and more are coming soon..
Feel free to try it and let us know how you like it :)
We have launched a new version of Storage API Importer which is replacing old one running at https://syrup.keboola.com/sapi-importer/run
Storage API Importer simplifies the whole process of importing a table into Storage . The SAPI Importer allows you to make an HTTP POST request and import a file directly into a Storage table.
The HTTP request must contain the tableId and data form fields. Therefore to upload the new-table.csv CSV file (and replace the contents) into the new-table table in the in.c-main bucket, call:
curl --request POST --header "X-StorageApi-Token:storage-token" --form "tableId=in.c-main.new-table" --form "data=@new-table.csv" "https://import.keboola.com/write-table"
New Importer is now running as a standalone service so it gives us more control about service scaling, stability and performance.
Read more details in New Storage API Importer Documentation
The services are fully compatible the only difference is in hostname and path. That means all you need to do is replace https://syrup.keboola.com/sapi-importer/run to https://import.keboola.com/write-table in your scripts.
So the following script:
curl --request POST --header "X-StorageApi-Token:storage-token" --form "tableId=in.c-main.new-table" --form "data=@new-table.csv" "https://syrup.keboola.com/sapi-importer/run"
Will become:
curl --request POST --header "X-StorageApi-Token:storage-token" --form "tableId=in.c-main.new-table" --form "data=@new-table.csv" "https://import.keboola.com/write-table"
We will support old service December 2016. All customers using old service will be notified soon.
In fall last year we introduced Custom Science applications at Keboola Meetup, it was exactly one day old at that time. From that time we worked in a lot of improvements (support for private repositories, encryption, error handling and documentation) and many bug fixes. Now we also improved the UI, so this post is a summary of what is currently possible.
Custom Science is the easiest way ever to integrate arbitrary code (in R and Python and now also in PHP) into your KBC projects. To create a CS application, you just need to provide a Git repository, which contains the code to transform your data, we will take care of the rest.
Sounds similar to transformations? Good, because it really is, but with some awesome twists. With custom science:
The point of all this is that you can hire a 3rd party developer, point him to our documentation and let him do his work. When he is done, you can integrate his application with a few clicks. We see this as an ultimate connection between You and hardcore Ph.D. data scientists who have algorithms you're ailing for (but they do not have the infrastructure to run them in a usable form). We care about protecting you, because those developers do not need access to your project. If you are really concerned, than you can also isolate the application completely from any network. We also care about protecting the developers, because if they share a git repository with you, they can use a private repository, without sharing the password with you. We don't really want to interrupt anyones business and we try to stay out of the way as much as possible, so what the application does is completely upon the agreement between you and 3rd party.
You might also consider using custom applications for your own transformations code. We are long aware that some of your transformations are really complicated. You can now take a complex transformation, split it into several files, classes (or whatever you want), and you can run tests on it. Again, your code can be stored in private git repositories, and be protected if you want to. Also, this way, you can share transformation code between multiple KBC projects.
Because it is designed to connect a 3rd party (data) scientist with you, so that he can provide you with Science customized to your needs.
Certainly not. Transformations are there to stay. Custom Science is another option, not replacement.
It depends on demand. If you require another language, let us know. So far we got request for R, Python 3.x and Python 2.x and PHP so we have those.
Almost none, there are minor differences in handling packages (they are installed automatically in R/Python applications and have to be installed manually in CS) and handling file inputs.
Great, fill out the checklist and let us know that you want to register it as a KBC application. When registered it will be available as any other KBC component.
Many of current configurations of database extractors are set using fixed IPs and VPN connections. We think it's time to move to the 21st century and use SSH tunnels (yeah those were designed in 90s too). Therefore we won't be offering fixed IPs and VPN setups for new customers, effective from August 2016.
Because there are never-ending problems. IPs which are not supposed to change, do change. VPNs are prone to outages. Servers get restarted unexpectedly. It is sometimes very complicated to identify the source of connection problems and many other issues. Overall, these setups are not up to our reliability and traceability standards.
We will support all of you - existing customers - till August 2017. This should give you enough time to migrate to SSH tunnels. We recommend that you (or your system administrator) read our guide for setting up an SSH tunnel. If you have any questions, do not hesitate to contact us.
We are experiencing some issues with our infrastructure which causes occasional job failures. The jobs fail with generic message "Internal error occurred ...". We have identified the issue and we applied a fix already.
Currently we are monitoring the situation closely and we restarted the failed orchestrations. In case you encounter the issue, the solution is to restart the failed job, because the failure is transient.
Introducing the new design for email notifications from Keboola Connection. No more plain text mail from us, now you can jump straight to your project from within the notification.
This design was also applied to Orchestration error emails. So now each failed task contains the result message from the originating component.
We`ve launched a new version of the Zendesk extractor, which completely replace old version of Zendesk extractor.
It is based on our Generic Extractor with predefined templates to helps download your data easily.
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 Zendesk (DEPRECATED) in Keboola Connection, is now deprecated and will be shut down on 27th of October 2016.
If you need help with migration please let us know.
Are you tired of loading CSV files into a table over and over again? Do you sometimes forget to set the incremental flag or specify a wrong delimiter?... Well those days are over! Now there's a simple new way to load CSV files.
The new CSV Import allows you to create and save a configuration and just select the file next time. You'll find it under Extractors in your project and you can read a bit more in our documentation.