Qlik-PE / Rapid-ML-Gateway

Rapid Machine Learning Gateway
MIT License
2 stars 3 forks source link
business-intelligence machine-learning qlik qlik-application qlik-partner-engineering

Introduction

Rapid ML Gateway Logo

Rapid Machine Learning Gateway Simple way to BI tools to tap your ML Endpoints from your BI tools.

Rapid ML Gateway(RML) is an open source Python implementation of QlikTM Server Side Extension that simplifies bi-directional data exchange between Qlik Application and Popular ML endpoint data. The Origins of this project started as Qlik Rapid API Gateway but due to complications it was fully opensourced

As of May 2021 It was decided that this project will become a OSS Project for the larger community and Qlik, Inc will no have involvement in this project. Following Decisions were made

The intial use case was to allow Qlik to use AI/ML functions and interact with other executions engines. The system utilizes GRPC messaging from Qlik and currently in the inital release support REST, Websocket APIs.

Integration Use Cases are Following

The system is built around quickly using qrag.ini and functions.json to send request and add results back into QIX engine. The goal of Rapid ML Gateway is to It's goal is to help Qlik users integrate into API/Microservices Architecture.

Note: RML is in the Beta TESTING PHASE. Core functionality is complete, please let This g Team know if you run into any data, compatibility or install issues! Thank you for reporting any BUGS in the issue tracking system here, and We welcome your feedback and questions on usage/features.

Things that may happen if there is Developer/Customer demand.

For Initial Release our target is support AWS Sagemaker Platform. Please take a look at Readme inside Sagemaker folder

Licenses

RML is published under MIT License Model which allows users to easily modify and share with your fellow Developers. For anyone interested in license please take a look at MIT License wiki

Code of Conduct.

Qlik Partner Engineering will adopt. Contributor Covenant Code of Conduct. Please act accordingly.

Example

Breast Cancer Predictions Using Sage Maker
This Qlik Application uses Data from UCI ML Repo and uses winning Model from Kaggle to Predict Breast Cancer Diagnosis based on SagmeMaker Endpoint. Components used in integrations are AWS API Gateway, Lambda, AWS Sagemaker and Qlik

Features

version 0.1.0 - Released August, 2020

version 0.1.1 Released November, 2020

versions 0.1.2

(More Fatures and versions will be released)

Limitation

Installation

QRAG currently supports Python 3.8+ and Qlik Server 13.72.5+. Official Docker and Exe Support is due soon. Each API Connector will need small different setting changes

Modules

Please pull from Docker hub from Partner Engineering Organization
Qlik Partner Engineering Docker Hub
Qlik PE QRAG Realse Notes

For Sample Test Please run (Please note Sagemaker Service is turned on and it is recommended you only turn on signle module for each Container for Production Use Case)

docker run -d -p 50057:50057 --name qrag4 qlikpe/qrag:latest

Basic Usage

  1. Install QRAG on Qlik Server/ Remote Server
  2. Define functions in functions.json
  3. Define QRAG setting in QRAG.ini
  4. Restart Qlik Engine

For Specific Installation and Details Please see specific installations below

AWS Sagemaker

Contribute

I (John Park) built it to be the most useful tool possible and take frustration out of writing SSEs. I also want to have all partner tools compatible with RML. If you have a toolset that you want to build compatibility with please let us know we can setup a folder and you can commit your code.

1. Spread the word !

A STAR here on GitHub(https://github.com/Qlik-PE/Qlik-Rapid-API-Gateway), and a mention on Twitter or Instagram @jpark328 and blog post are the easiest contribution and can potentially help grow this project tremendously!

Medium articles, YouTube video tutorials and other content take more time but will help all the more!

2. Report bugs & issues

I expect there to be many quirks once the project is used by more and more people with a variety of new (& "unclean") data. If you found a bug, please open a new issue here. Please change logging level to "DEBUG" and upload log files/snippets.

3. Suggest and discuss usage/features

To make RML as useful as possible we need to hear what you would like it to do, or what it could do better! Head over to Github Wiki to Place Feature/Request.

4. Contribute to the development

We definitely welcome the help I can get on this project, simply get in touch on the issue tracker.

5. Bug Fixes and Pull Requests

There will be a monthly Pull Requests Merge done. Please stay tuned.

6. About Author and Team Behind the Project

Please email people on this list if there are questions and concerns about this project.