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

[Anonymous]

Hi all,

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.

Can anyone please help?

[lojdr]

Hello,

Can you please provide output from the execution and also schemas used in both components with an example of working and not working row? Thanks.

Regards

lojdr

[Anonymous]

Thanks lojdr,

Print screens are attached:

compile-error.jpg  > The execution error

scheme-fail.jpg> The scheme structure while failed

scheme-success.jpg > The scheme structure while succeeding (string only)

success-output.jpg>  execution output while using string only

error-java.jpg > The JAVA code error source

error-java.jpg
success-output.JPG
scheme-success.JPG
scheme-fail.JPG
compile-error.JPG

[lojdr]

int cannot be compared to null, which is a null reference to an object. Compare with zero instead.

Also... In schema where you have an ID (int), you use it as a primary key. Primary key can't be NULL.

Please post here a screenshot of the job.

[Anonymous]

How can I change the comparison to 0 instead of NULL (though the UI interface)?

I understand the problem is in the code, but I do not have the option to change it, so I guess that I need to change something in the variables configuration?

The job screenshot is attached

Thanks again,

job.JPG

[lojdr]

Hello,

I was able to reproduce it. Maybe it is a bug...

Regards
lojdr

[Anonymous]

Thanks for the help

[rlmagidson]

Good morning - 

This seems to be (for me, anyway) related to the data types in the Schema. I had this same error and was scratching my head about it when I decided to try setting all input columns to String from whatever type they were (int, decimal, etc). Lo and behold it worked after doing that.

The interesting thing is that although the error is identified with the source (table input), if I replace the BigQuery component to a tLogRow (with the original schema) then it works. Clearly BigQuery is an issue.

Hope this helps 

 - Russell

operator undefined error.jpg
Having Integer Caused my Problem.jpg