Issue when Using 2 tBigQueryOutput in 1 job.

[Anonymous]

Hi all.

I have following failing scenario: 

Sources: File and BQ table

ETL: Join and Filter

Target: BQ table1 and BQ table2.

It fails with error:

org.talend.designer.runprocess.ProcessorException: Job compile errors
At least job "BigQueryFileJoinToBQAndBQ" has a compile errors, please fix and export again.
Error Line: 2496
Detail Message: Duplicate local variable tableNotExist

I have also following passing scenario: 

Sources: File and BQ table

ETL: Join and Filter

Target: BQ table1 and File.

so the question, does any body used 2 tBigQueryOutput in 1 job ?

and is it working ?

I am using Talend BD Studio : TOS_BD-20181026_1147-V7.1.1

[Anonymous]

Hello @ssomanchi ,

Could you please check your "Code" tab in your job? There will be your compile error highlighted in red line. Could you post it here, please?

Best regards

Sabrina

[vapukov]

Hi,

with versions 7.* - it looks like a global "pattern error" for several not often used components

we have already registered 3 tickets for different components for the subscription version (at least 1 resolved)

what to do with Open Studio? I just hope Talend team will fix it in the feature version

as a bypass - split the job into 2 separate subjobs (in the same job). 

For example - store data into 2 local csv file and then 1 by 1 transfer them to BigQuery

it little ugly, but Community version - don't mean support between releases

regards, Vlad

[Anonymous]

Thanks Sabrina

Thanks Vapukov. - Thanks for suggestion, It is not critical,  Since its a evaluation. I am just trying to see the functionality and limitations.

here is the code :

boolean tableNotExist = table_tBigQueryOutput_1_tBQBE == null;
if (false || tableNotExist) {
boolean typeSupported = true;
java.util.List<com.google.cloud.bigquery.Field> fields_tBigQueryOutput_1_tBQBE = new java.util.ArrayList<>();

if (!typeSupported) {
throw new IllegalArgumentException(
"unsupported type for column [id_]: "
+ "id_String");
}
com.google.cloud.bigquery.Field field_0 = com.google.cloud.bigquery.Field
.of("id_",
com.google.cloud.bigquery.LegacySQLTypeName.STRING);
fields_tBigQueryOutput_1_tBQBE.add(field_0);

if (!typeSupported) {
throw new IllegalArgumentException(
"unsupported type for column [date_]: "
+ "id_String");
}

[Anonymous]

Hello,

I see the that the bug is marked as rejected because it's duplicated with TBD-8102.

Do you know when this will be fixed? The 7.0.X versions are affected?

We are depending on this to choose this ETL for the company or not also...

[Anonymous]

Splitting the job in subjobs inside the same job won't work...