Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

How to integrate Qlik sense with hiveserver2

Solved Go to solution
Highlighted

How to integrate Qlik sense with hiveserver2

Contributor

I need to integrate the Qlik sense with Hive server2 running in my cluster

1 ACCEPTED SOLUTION

Accepted Solutions

Re: How to integrate Qlik sense with hiveserver2

New Contributor

The QlikView Hybrid Solution is also referred to as "QlikView Direct Discovery", whereby data is not cached in QlikView but is, instead, loaded on demand, directly from the source. This allows Qlik to run against the vast amount of data in a Hadoop Data Lake without memory restrictions.

One simple modification to the load script would be replacing the word "SELECT" with "DIRECT QUERY" within the SQL statement. You can find the documentation from Qlik at https://help.qlik.com/en-US/connectors/Subsystems/ODBC_connector_QV_help/Content/1.0/ApacheHive/Load....

There are other functions related to the "DIRECT QUERY" option and you can find further documentation at https://help.qlik.com/en-US/qlikview/12.1/Subsystems/Client/Content/DirectDiscovery/direct-discovery....

3 REPLIES 3

Re: How to integrate Qlik sense with hiveserver2

Re: How to integrate Qlik sense with hiveserver2

New Contributor

@Sandeep Nemuri

Thanks for the link.

But in this documents there are two different ways of ingesting data .

Can you or anyone please explain the 2nd method .ie QlickView Hybrid solution ?

In this link its been described that with simple modification in the load script , the application can be configured to run hydrid soluiton.

It would be really of great help, if anyone can please describe this simple modification. ?

Thanks in advance.

Re: How to integrate Qlik sense with hiveserver2

New Contributor

The QlikView Hybrid Solution is also referred to as "QlikView Direct Discovery", whereby data is not cached in QlikView but is, instead, loaded on demand, directly from the source. This allows Qlik to run against the vast amount of data in a Hadoop Data Lake without memory restrictions.

One simple modification to the load script would be replacing the word "SELECT" with "DIRECT QUERY" within the SQL statement. You can find the documentation from Qlik at https://help.qlik.com/en-US/connectors/Subsystems/ODBC_connector_QV_help/Content/1.0/ApacheHive/Load....

There are other functions related to the "DIRECT QUERY" option and you can find further documentation at https://help.qlik.com/en-US/qlikview/12.1/Subsystems/Client/Content/DirectDiscovery/direct-discovery....