Thanks for pointing out the 2017 statement of direction Cotiso. Here's where R/Python is mentioned (emphasis mine)
| Our strategy for analytics in Qlik Sense extends into 2017 and beyond with planned capabilities focused on enhanced visualization, exploration and search, new forms of interactivity, comparative and predictive analysis, more flexible layout and customization, and new collaborative and mobile capabilities. We intend to offer new types of visualizations such as box plots, candlestick charts, distribution plots, waterfall charts, Sankey charts, and Gantt charts. We also plan to make improvements to the functionality and interactive behavior of visualizations and objects, such as providing ad-hoc grouping and binning, trellis charts, brushing and highlighting for comparative analysis, trend lines and forecasting, and a new calendar selection object. Our search capabilities will evolve to support capabilities such as search history, natural language search, self-service search — allowing content creation on the fly through search, and search from the hub and app overview across all objects. Based on our Qlik GeoAnalytics technology, we plan to make a number of geospatial and mapping improvements, such as supporting shapes, drill down, multi-layer maps, increased data density, and street level geocoding. And we are planning API support for integration with third party calculation engines such as R and Python, themes and app styling for adding company logos and using custom colors, advanced set analysis and comparative analysis with multiple states, custom calendars, and multi-language support. |
Obviously this did not make it into the 3.2 release, which means that the earliest that this would be generally available is with 4.0 in the June timeframe.
It's disappointing that we haven't publicly heard anything from Qlik about how exactly they expect his will work. You could, of course, talk to your Qlik rep and get access to the private beta site, but then you have to promise not to talk about it.
