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

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Load numeric / boolean data

Hello,

 

I'm using  "Open Studio for Data Integration" and I have a simple job which reads from mysql and writes to Google BigQuery.

 

I'm getting the following error while trying to read from a table that includes any numeric/boolean values:

"the operator =! is undefined for the argument type(s) int, null" 

 

If the source table contains only strings, the job works fine.

 

Both input and output schemes are defined with the corrected variable types.

 

The JAVA code compare int to null which makes this exception, but I do not have the option to change it.

 

Am I doing something wrong,  or its a bug?

 

Print screen is attached,

 

Thanks in advance!

Labels (4)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

Hi  

The operator != is not defined for int type, If I check 'Nullable' box on the schema, the type will be changed to Integer and the compilation error is fixed.

0683p000009LrkG.png

 

Regards

Shong

View solution in original post

7 Replies
Anonymous
Not applicable
Author

Check the 'nullable' box of id column on the schema. Let me know if it works.

TRF
Champion II
Champion II

In Java, Int can't be null. However, Integer can be null.

Check this link https://stackoverflow.com/questions/2254435/can-an-int-be-null-in-java

Anonymous
Not applicable
Author

Hi Shong,

It's still not working

 

Thanks

Anonymous
Not applicable
Author

Thanks TRF,

I don't think that I have the option to change the JAVA code through the UI interface

 
 
TRF
Champion II
Champion II

No, you don't.
But you probably may convert int value to Integer then compare to null
Anonymous
Not applicable
Author

Hi  

The operator != is not defined for int type, If I check 'Nullable' box on the schema, the type will be changed to Integer and the compilation error is fixed.

0683p000009LrkG.png

 

Regards

Shong

Anonymous
Not applicable
Author

I tried now and it worked, thank you for the clarification