Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
gaidamichal
Partner - Contributor III
Partner - Contributor III

Possible Where Exists() Optimized load BUG

Hello,

I've encountered a strange behavior in Where Exists(). When I use another name for the previously loaded filed I get an unoptimized load but when I rename the other field to match the field name I'm back to optimized. I've attached a sample app for this purpose:

1. Simple Where Exists(Dim1)

Result: Optimized load

2020-04-21 17_49_18.png

 

 

 

 

 

 

2. Changed the filter dim name to Dim5 - Where Exists(Dim5,Dim1)

Result: Unoptimized load

2020-04-21 17_49_52.png

 

 

 

 

 

 

3. Added field Dim1 as Dim5 to the original table, the clause is the same - where Exists(Dim5,Dim1)

Result: Back to optimized load

2020-04-21 17_50_39.png

 

 

 

 

 

 

This feels like a bug in optimized load not being used despite meeting the criteria. Have any of you encountered such behavior? Finding that out saved me a lot of time by simply adding additional field alias.

 
2 Replies
jsebrightqi
Partner - Contributor II
Partner - Contributor II

This is still an issue on cloud and windows.

marcus_sommer

I'm not sure if there is really an issue because it could also mean that Qlik knows that both fields are identically respectively there might be just a single field (one field-id with n field-names).

Creating the fields in different steps and/or ensuring that they are not identically by adding/removing any values or applying a different load-order or similar measures may change the behaviour.