When you read in a BigQuery table, it might incorrectly show or store the string variables with a length of 2000 when the following conditions are true:
- You use a CASLIB to connect to the BigQuery database.
- You use the SCANSTRINGCOLUMNS=TRUE option.
- You set the NUMREADNODES option to a value greater than 1 or to 0.
- You use the CASUTIL, CAS, or FedSQL procedures to read the BigQuery table.
The incorrect length might cause problems with further usage of the resulting CAS table or during the initial load of the BigQuery table.
The known issues at this time are as follows:
Scenario 1:
Trying to run a FedSQL query against the resulting CAS table might generate errors similar to the following:
ERROR: FedSQL query plan validation failed because a CAS worker node (rank 0) produced a query plan that was different from the query plan on the CAS controller node. The parameter cntl={planValidationDetails=true} can be added to the fedSql.execDirect invocation to report detailed error information to the CAS server logs.
ERROR: FedSQL query plan validation final status 0x8a7fc84a.
ERROR: FedSQL query plan fragment on rank 0 (worker XML) : ></T_Var></expr></T_TargetEntry><T_TargetEntry><resdom><T_Resdom><resno int= "42" /><restype type= "VARCHAR" /><restypmod int= "5" /><resname>COD_RATING_OUT</resname><ressortgroupref int= "42"/></T_Resdom></resdom><expr><T_Var><varno int= "2" /><varattno .
ERROR: FedSQL query plan fragment on rank 0 (controller XML) : ></T_Var></expr></T_TargetEntry><T_TargetEntry><resdom><T_Resdom><resno int= "42" /><restype type= "VARCHAR" /><restypmod int= "2000" /><resname>COD_RATING_OUT</resname><ressortgroupref int= "42" /></T_Resdom></resdom><expr><T_Var><varno int= "2" /><varatt.
ERROR: The action stopped due to errors.
ERROR: The FedSQL action was not successful.
Scenario 2:
During the initial loading of the BigQuery table, errors similar to the following might occur in the CAS log:
ERROR: Error received from worker 0: General Error - invalid Exception
ERROR: Function failed.
Also, in the failing worker log, errors similar to the following might occur:
fetch_thread: Fetch failed, rc = 0x80fff802
General Error - invalid Exception
The only workaround is to remove the NUMREADNODES= option from your CASLIB statement or as an option in your procedure step.