Qlik Community

QlikView Documents

Documents for QlikView related information.

Announcements
Modernize Your QlikView Deployment webinar, Nov. 3rd. REGISTER

Qlik Statement of Direction 2017

Employee
Employee

Qlik Statement of Direction 2017

Qlik has now published its 2017 Statement of Direction, which sets out our continued investment across our cloud-ready modern BI portfolio. The PDF is attached and also available on Qlik Statement of Direction

Attachments
Comments
Luminary
Luminary

I don't get it - why isn't making Qlik Sense Desktop available for mac on your road map?

0 Likes
Employee
Employee

Hi Martin. Thanks for the question. Our highest priority for 2017, from a desktop perspective, is closer alignment of desktop with enterprise and cloud which will bring a number of advantages for existing customers and prospects. In addition, we are also working on delivering offline mobile which is essentially the expansion of desktop capabilities on other platforms, and this will include IOS. This trajectory may lead to a Mac desktop in the future if the business needs also follow the same trajectory they have followed until now. Regards, James 

0 Likes
Luminary
Luminary

Same time, you are strongly promoting Mashups and extensions using the open and rich API; you even plan to sell the QAP itself as a product - this is pure Web Development which is being done by only by 22.5% of developers on windows operating systems (Stack Overflow Developer Survey 2016 Results).

How do you plan to address the remaining 77.5% of web developers who currently can't use Qlik Sense and apparently are key to growing a strong Qlik ecosystem?

Contributor III
Contributor III

We want to use python models from machine learning on data.
Those things have to run fast.

So i'ld be interested on your plans according to support python or R native.
Will we see those APIs in QlikView + and when?

0 Likes
Employee
Employee

Hi mahlerma,

We could not be more in agreement. The developer community certainly is fragmented when you view it with the lens of operating systems. As you may notice in the same Github survey, Mac OS represents 26.2% and Linux, 21.7% of developers. The question is, how best to address the 77.5% web developers? One way would certainly be to launch individual products for each platform. This would be responding to fragmentation with more fragmentation. Our answer is, instead, to address the full 100% of web developers with THE universal and resident platform of choice of web developers with our platform as a service offering. As you may have noticed on page 18 as also state that

“we are building towards an overall platform as-a-service vision, offering a complete development experience within cloud environments such as Amazon® Web Services (AWS) or Azure®. “

Watch this space

Employee
Employee

Thanks for the question Helmut. Let me break this down into 3 elements – performance, support for R and Python and QlikView v Qlik Sense.

Regarding performance then we will enable this via Server-side Extensions (SSE).  Performance of SSE will be bounded by 1) Qlik Sense server performance, 2) The R/Python server performance, 3) the network latency, 4) and the volume of data to be passed between the two systems. Items 1, 2, and 4 are all based on the specific use case, and 1, 2, and 3 are all also based on the physical environment. It’s extremely hard to make any generalizations about performance when it comes to SSE and we are also in the process of changing the transport protocol from named pipes to GRPC, which also has the potential to impact performance. We are working with our scalability team and they will be able to provide more details once this work is complete. However, feedback from customers and partners working with us on the development are very positive, although we expect to need to provide guidance on configurations to ensure optimal performance.

Regarding your question on support for R and Python then this depends on your definition of “native”.  As mentioned above, we won’t be shipping R or python executables in our installers, if that’s what you mean. But via SSE we will connect to ‘native’ R and Python (i.e. you don’t need any other intervening software beyond our SSE connector). The connectors to both R and Python will be open sourced and community maintained exactly as R and Python are themselves.

Finally regarding QlikView support then the first release will be for Qlik Sense. Our plan, once the Qlik Sense version is publicly available and we have had some feedback on it, will be to subsequently release a QlikView version. We do not have a timeline for this.

0 Likes
Contributor III
Contributor III

Hi James,
i was refering the Artikle here from 09.2016:
Qlik to add R, Python support | Computerworld

...
Qlik
will be adding R and Python integration to its data analysis tool later this month, continuing a BI trend that uses scripting languages to bulk up the power of drag-and-drop platforms.
...With its version 3.1 release, Qlik engine will be able to pass data in and out of both R and Python, including analysis context about a data set. For example, a user could call R to do a regression or forecast model on revenues by country, and then interactively decide to re-run the model while excluding a couple of data points while viewing a visual in Qlik. "You're not doing an export and then bringing it into Qlik," Deighton said. "R is treated as a first-class citizen in the data-analysis experience," leading to easier, interactive what-if scenarios.

The R and Python functionality will be available for Qlik's desktop and server software, both Qlik Sense and QlikView, although not immediately for the cloud service.
...

Now it sounds like those things, are not implemented till now, and if they will be only available on the server side.
Or did i misunderstand something?

0 Likes
Employee
Employee

Hi Helmut

I can appreciate the confusion. Sadly while the article was directionally accurate, the version and timing was not. The integration will be delivered via SSE but is currently planned for our June 2017 release.

Regards

James

0 Likes
Employee
Employee

Thanks for the feedback Ian and I fully agree with you that Qlik Sense should be a market leader and inspiration for other vendors.

In the statement that James posted we mention some of the functionality we want to make available as new capabilities rather than using the scripting language. And the way we want to do it is by giving users an "Easier yet more powerful creation" method. Which is one reason we are earning top rewards in the ease of use categories in many surveys.

So for the improved functionality we need to make sure we're just not adding more buttons and drop downs in a way that people need to spend a long time learning where every single click button is located. A single click is good if you don't get lost finding it. Instead it should be a gradual approach where a user starts out with easy creation and can then enable themselves to continue getting educated and getting access to more functionality and maybe in the end start using script where a UI just can't fulfill all requirements. At the same time this should not be a showstopper for advanced people with scripting knowledge to immediately get the result they want.

So it's something we are working on and leveling up our resources in so you should be seeing continued improvements in our future releases

Regards,

Patrik.

Luminary
Luminary

Thank you, James.

Page 19:

big data indexing that will enable the full associative experience on top of resident sources without having to load all the data into memory. And we are planning native support for streaming data such as IoT (internet of things) information.

Please, can you explain a bit more on this topic? Especially using associative experience without in-memory data and also streaming data capabilities?

Also, In one of the QlikDevGroup we were told by Qlik presenter that repository database will move from Postgres to Cassandra. I haven't seen anything in the above document.

Thanks,

DV

0 Likes
Version history
Revision #:
1 of 1
Last update:
‎2017-01-19 06:38 AM
Updated by: