Release 0.8.1 (May 24, 2017)


  • 140+ issues resolved
  • You can now assign users and groups access to feeds, categories, and templates giving you fine grain control of what users can see and do. Refer to the Access Control for more information.
  • Kylo can now be clustered for high availability. Refer to Clustering Kylo for more information.
  • You now mix and match the order of standardizers and validators giving you more control over the processing of your data.
  • The wrangler has been improved with a faster transformation grid and now shows column level profile statistics as you transform your data.

Upgrade Instructions from v0.7.1

  • If upgrading directly from v0.7.1, run the database update to enable Liquibase.
/opt/kylo/setup/sql/mysql/kylo/0.8.0/ <db-hostname> <db-user> <db-password>

Upgrade Instructions from v0.8.0

Build or download the RPM

  1. Uninstall Kylo:
  1. Install the new RPM:
rpm –ivh <RPM_FILE>
  1. Copy the file from the install. If you have customized the file you will want to copy the version and add the new properties that were added for this release.

    4.1 Find the /bkup-config/TIMESTAMP/kylo-services/ file

    • Kylo will backup the file to the following location, /opt/kylo/bkup-config/YYYY_MM_DD_HH_MM_millis/kylo-services/, replacing the “YYYY_MM_DD_HH_MM_millis” with a valid time:

    4.2 Copy the backup file over to the /opt/kylo/kylo-services/conf folder

    ### move the shipped with the .rpm to a backup file
    mv /opt/kylo/kylo-services/
    ### copy the backup properties  (Replace the YYYY_MM_DD_HH_MM_millis  with the valid timestamp)
    cp /opt/kylo/bkup-config/YYYY_MM_DD_HH_MM_millis/kylo-services/ /opt/kylo/kylo-services/conf

    4.3 Two new properties were added. Add in the 2 new properties to the /opt/kylo/kylo-services/conf/ file

    # Entity-level access control. To enable, uncomment below line and set value as true
    ## optional.  If added you can control the timeout when you delete a feed

    Refer to the Access Control document for more information about entity level access control. To enable entity access control ensure the property above is set to true.

    4.4 Ensure the property security.jwt.key in both kylo-services and kylo-ui file match. They property below needs to match in both of these files:

    • /opt/kylo/kylo-ui/conf/
    • /opt/kylo/kylo-services/conf/
  2. Backup the Kylo database. Run the following code against your kylp database to export the ‘kylo’ schema to a file. Replace the PASSWORD with the correct login to your kylo database.

mysqldump -u root -pPASSWORD --databases kylo >kylo-0_8_0_1_backup.sql
  1. Database updates. Kylo uses liquibase to perform database updates. Two modes are supported.
  • Automatic updates

    By default Kylo is set up to automatically upgrade its database on Kylo services startup. As such, there isn’t anything specific an end user has to do. When Kylo services startup the kylo database will be automatically upgraded to latest version if required. This is configured via an setting

  • Manual updates

    Sometimes, however you may choose to disable liquibase and manually apply the upgrade scripts. By disabling liquibase you are in control of how the scripts are applied. This is needed if the kylo database user doesnt have priviledges to make schema changes to the kylo database. Please follow this Database Upgrades on how to manually apply the additional database updates.

  1. Update the NiFi nars. Run the following shell script to copy over the new NiFi nars/jars to get new changes to NiFi processors and services.

  2. Re-import Data Ingest template (

  • Kylo now allows converting data ingested from a database into AVRO format, and then running it further through the flow.
  • To enable this, re-import the file (Templates -> + icon -> Import from a file -> Choose file -> Check yes to ‘overwrite’ feed template -> Check yes to ‘Replace the reusable template’ -> Import template)