Thive Row log.info error on compile

[Anonymous]

Talend version : Talend 7.01 for data integration
Libraries : All installed
Java version : 1.8.0 201
Windows 10 64 bit

After creating THiveConnection -> trigger on component ok -> THiveRow ->TCloseConnection

A compile error on row 719 appears from autogenerated code 
log.info("Query sent to HiveServer2 to be executed with [Application Name(MapReduce)/DAG Name(Tez): "
+ queryIdentifier + "]");

This is the row which generates the error and says that :
org.talend.designer.runprocess.ProcessorException: Job compile errors
At least job "pippo" has a compile errors, please fix and export again.
Error Line: 719
Detail Message: log cannot be resolved
There may be some other errors caused by JVM compatibility. Make sure your JVM setup is similar to the studio.
at org.talend.designer.runprocess.JobErrorsChecker.checkLastGenerationHasCompilationError(JobErrorsChecker.java:338)
at org.talend.designer.runprocess.DefaultRunProcessService.checkLastGenerationHasCompilationError(DefaultRunProcessService.java:464)
at org.talend.designer.runprocess.RunProcessService.checkLastGenerationHasCompilationError(RunProcessService.java:316)
at org.talend.designer.runprocess.ProcessorUtilities.generateBuildInfo(ProcessorUtilities.java:812)
at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:586)
at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:1736)
at org.talend.designer.runprocess.RunProcessContext$1.run(RunProcessContext.java:582)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:527)
at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:284)
at org.eclipse.ui.internal.progress.ProgressManager.run(ProgressManager.java:1190)
at org.talend.designer.runprocess.RunProcessContext.exec(RunProcessContext.java:534)
at org.talend.designer.runprocess.ui.ProcessComposite.exec(ProcessComposite.java:1401)
at org.talend.designer.runprocess.ui.views.ProcessView$RunAction.run(ProcessView.java:701)
at org.talend.designer.runprocess.ui.actions.RunProcessAction.run(RunProcessAction.java:58)
at org.talend.designer.core.debug.JobLaunchConfigurationDelegate$1.run(JobLaunchConfigurationDelegate.java:84)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4147)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3764)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.talend.rcp.intro.Application.start(Application.java:265)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)

Deleting THiveRow and trying TConnection and TCloseConnection, the job runs smoothly

[Anonymous]

@xdshi

[Anonymous]

Hello,

What does your query look like in tHiveRow component? Could you please check your "Code" tab in your job to see if there will be your compile error highlighted in red line when you get some compile errors?

Best regards

Sabrina

[Anonymous]

@xdshi my query is
"show databases".
The row line which gives compiles error is the following
log.info("Query sent to HiveServer2 to be executed with [Application Name(MapReduce)/DAG Name(Tez): "
+ queryIdentifier + "]");

which says "log cannot be resolved"

It is surely your bug, because this code is autogenerated from Talend

[Anonymous]

Problem is still there..

[Anonymous]

Hello,

Are you using talend subscription solution?

Normally it will work when you active the log4j, the error is because the "log" variable is not defined at the beginning of the class if you didn't active log4j.

Best regards

Sabrina

[Anonymous]

@xdshiif log4J is not enabled, it should not be in the code.
Anyway, I've looked to the post you linked me and I cannot find the option to disable/enable Log4J ,

please see the attached images and guide me to enable/ fix log4J.

Thank you

talend3.jpg
talend2.jpg

[Anonymous]

Hello,

Talend open studio don't have option to enable log4j logging.

Best regards

Sabrina

[Anonymous]

This is not a proper answer.
If Talend open studio for Big data can't fix or enable Log4J, then your product is worthless and unavalaible since I can't use Thive components.
Please indicate a Solution with a proper answer.

[Anonymous]

Hello,

We tried to reproduce this issue on talend open studio from our end and didn't get this issue.

Would you mind giving us some detailed steps? In this way, I will take a testing from my end and then report it to talend component manager directly.

Really thanks for your time!

Best regards

Sabrina