Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
deep2021
Creator III
Creator III

App size increasing after fetching data from Rest API

Hi all,

PFB screenshot , I have 2 apps,

deep2021_0-1703699822755.png

Entitlement and lineage analysis - I am fetching data from csv.

Entitlement and lineage analysis_API_Raw - I am fetching data from rest API.

It seems that after fetching the same data the app size from rest API data is incresing drastically.

I am haing the same data sets. although there are less number of rows in rest api app as compared to csv data the app size incresed.

Below are the snaps from metadata analyzer,

Entitlement and lineage analysis (CSv data)-

deep2021_1-1703700079813.png

Entitlement and lineage analysis_API_Raw (Rest API)-

deep2021_2-1703700157244.png

Can you please suggest how should I reduce the app size.

 

Thanks

 

Labels (2)
2 Replies
deep2021
Creator III
Creator III
Author

Hi,

Please find the attached word document and excel regarding comparison for the same.

Thanks 

deep2021
Creator III
Creator III
Author

Hi,

I applied the right join as per the below and my application size has reduced drastically.

I gone though the below article.

 

https://qlikviewcookbook.com/2008/05/when-less-data-means-more-ram/

i am having same number of data sets and results also matching.

U:
load 
docType as A.docType
, businessDate
,protocol as A.protocol
,location as A.location
,cutoff as A.cutoff
,version as A.version
,date(date#(actionDate,'YYYYMMDD'),'YYYYMMDD') as A.actionDate
//,year(actionDate) as A.actionYear
//,year(actionDate)*100+num(month(actionDate)) as A.actionYearMonth
 
 
,if(WildMatch(actionType,1,2),'READ',if(WildMatch(actionType,4,3),'WRITE')) as A.rwAccess    
,usageType as A.usageType
 
,accountId as A.accountId
,asAccountId as A.asAccountId
,isImpersonated as A.isImpersonated
 
,actionType as A.actionType
 
,1 as A.counter
,accountId
&'_'
&upper(docType)
&'_'
&upper(protocol)
&'_'
& if(WildMatch(actionType,1,2),'READ',if(WildMatch(actionType,4,3),'WRITE'))  as EU_Key
  FROM [lib://MSS_MCA_XDS_Base_Folder1 (hnah_45284320)/DEV/QVD/Extracts_Raw_QVD/XDS_Audit_Log_202309*.qvd](qvd);   
  
  right join(U)
 
load
 
            text(A.docType) as A.docType,
                date(date#(businessDate,'YYYYMMDD'),'YYYYMMDD')  as A.businessDate,
                Text(A.protocol) as A.protocol,
                text(A.location) as A.location,
                text(A.cutoff) as A.cutoff,
                num(A.version) as A.version,
                num(A.usageType) as A.usageType,
                text(A.accountId) as A.accountId,
                text(A.asAccountId) as A.asAccountId,
                num(A.isImpersonated) as A.isImpersonated,
                //text(actionDate) as actionDate,
                 text(A.rwAccess) as A.rwAccess,
                date(date#(A.actionDate,'YYYYMMDD'),'YYYYMMDD')  as A.actionDate,
                num(A.actionType) as A.actionType,
                num(A.counter) as A.counter,
                EU_Key as EU_Key
                
                Resident U;
  
 Store U into  [lib://MSS_MCA_XDS_Base_Folder1 (hnah_45284320)/DEV/QVD/Extracts_Raw_QVD/MergeTestRight/09.qvd](qvd);    
 
 Drop table U;
 
But sometimes the calculation is going out of memory.
Can you please suggest the best approach to avoid  out of memory issue.
 
Thanks