As we have announced earlier, we have launched a bunch of new DB extractors, supporting various vendors. The "old" Database Extractor became deprecated and as we promised, we've prepared a tool for you, to help you migrate your configurations to the new extractors.

To initiate migration, click "Proceed to Migration" button in any configuration of the "old" Database Extractor.

A dialog window will open, where you will see what configuration will be migrated, status of the migration and also affected orchestrations.

If you need any assistance, contact support@keboola.com.

We have released bunch of new database extractors supporting wide range of vendors:

• MySQL
• Microsoft SQL Server
• PostgreSQL
• Oracle
• Cloudera Impala
• Firebird
• IBM DB2
• MongoDB (coming very soon)

All these new Extractors are running on container based architecture and supports SSH tunneling, so there's no need for tedious VPN setups.

The old Database Extractor is now deprecated, but we will continue to  support if for 3 more months.  After this period, we will migrate any remaining "old" configurations to the new extractors.

We are now preparing a migration tool to help with this task, and when it is ready we will share with you so you can easily migrate your existing configurations to the new extractors.

If you'd like to migrate your configurations immediately, it will have to be done manually, so please let us know at support@keboola.com and we can try to convince you to wait for the tool :)

Docker app configuration with JSON Schema

This feature is mainly useful for 3rd party developers. 

It is now possible to define configuration UI with JSON Schema.

Read more about this feature in documentation.

Slack Extractor

Another addition to our fast growing family of extractors! 

Slack is a great real time messaging app, read more about it.

Use this extractor and other KBC tools to analyse your conversations, see which users / clients are most active in what channels and when. You can do sentiment analyses of messages and much more.

GitHub Extractor

And another new extractor. This time for most popular Git repository hosting service.

The GitHub API provides access to the many public activities that happen on GitHub.com. 

Read more about GitHub Data. Now you can use these in Keboola Connection environment.

S3 Writer fixes

• default path 'kbc_upload' is now used when no remote path is specified or it's just '/'. 
• region 'us-east-1' is now set as default region
• updated documentation

SSL for Transformation Sandboxes

Connection through SSL is now available when creating sandboxes for transformations.

Intercom.io Extractor

Extractor for https://www.intercom.io/ has been added to Keboola Connection.

"Load more" button added in Notifications

You can now browse older notifictionas with "Load more" button on Keboola Connection Notifictions page.

Changes to R transformations

We have made some internal changes to R transformation backend which resolves a couple of edge-case issues and bring few new features:

• We have unified R Transformations and R Custom Science to use exactly the same environment - this solves issues when using code from transformations in Custom Science.
• R Transformation scripts now have properly set encoding to UTF8 - manually setting encoding with Sys.setlocale("LC_CTYPE", "cs_CZ.UTF-8") is no longer necessary
• R packages are now installed from multiple backup CRAN repositories - this solves an issue where a package installation would randomly fail in case of CRAN outage
• When installing R packages we now automatically load them - this solves an issue where a package was successfully installed, but failed to load. This also has the nice side effect that, you no longer need to call library() explicitly to load packages in your R code.
• R script output is now available in Transformation events, so you can do some basic logging with print('message') or a bit nicer write('message', stdout())

You don't need to make any changes to your R scripts. If you run into any incompatibilities, let us know.

Other posts this week

• New Version of AdWords Extractor
• Upcoming Configuration Changes in Gooddata Writer
  
• Transformation Failures
  
• Firebird Extractor
  
• Elasticsearch Writer
  

Latest addition to our growing family of database extractors is Firebird Extractor.

It is now available in our component list with generic UI. Check out sample configuration to help you get started.

As of today, January 21th, 2016, we won't be making any further improvements or updates on Elasticsearch Writer/Extractor. As of February 21th, 2016, Elasticsearch Writer/Extractor will be completely removed.

Please note, that Elasticsearch Extractor functionality can be easily replaced with our Generic Extractor. 

Feel free to contact our support if you need any assistance.

Telfa Extractor functionality is covered by our Generic Extractor. Therefore as of today, January 20th, 2016, we won't be making any further improvements or updates on Telfa Extractor. As of February 20th, 2016, Telfa Extractor will be completely removed.

Here is an example on how to configure Generic Extractor for Telfa API.

Contact our support, if you need any assistance with migration to Generic Extractor.

Google Analytics Extractor now supports Segments.

"Segments allow you to select users and sessions to answer questions that are important to your business. For example, users that have completed at least 2 transactions with a lifetime revenue of over $1,000, or users who visited first on a mobile device followed by a desktop browser."

Read more about Segments here.

Database Writer component has been split into MySQL Writer, Oracle Writer and Redshift Writer according to underlying database driver.

Starting now, we will gradually migrate existing configurations from Database Writer to these new writers. 

Please don't be frightened when your Database Writer changes to MySQL Writer for example ;)

In the past few days we encountered problems with imports from Google Drive.

These problems were caused by Google's auto-migration to "New Sheets".

If you have problem with your Google Drive Extractor, removing and re-adding the problematic sheet will fix the issue. 

Be aware of your previous sheet configuration like "output mapping to SAPI table" or "transposition". 

Contact support@keboola.com if you are not sure how to do it.