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]

Hello,

The tHiveRow can capture the Application_ID values and write them in the Job logs once you have activated Log4j and set the Log4j output level to Info for your Job involving tHiveRow.

It has been mentioned in component reference and usage rule section.

TalendHelpCenter:tHiveRow

With open studio, we raised a bug https://jira.talendforge.org/browse/TBD-6469 before, however, it is set as Rejected.

More information about how to reproduce this issue will be highly appreciated.

Best regards

Sabrina

[Anonymous]

I saw the bug opened on Jira and I find it a bad move to reject the bug because you're not able to replicate it.

only one report this bug -> it would be a little ok to close the bug
more than one -> reject the bug because you're not able to replicate it, it is seriously a lack of listening
                             to your users and potential loss of users.

I don't want to be rude, but please take it as a tip to improve.
To reproduce my problem, download or find TOS for Big data 7.0.1 32 bit
1)Install all libraries needed
2)create a new project given a workspace

2.1)(not mandatory) download Mapr sandbox VM and execute it, run ifconfig and with that ip use it to access on 10000 port

3)select Tconnect to connect hive database
4)on subcomponent ok -> link to ThiveRow component and give it the settings taken from VM or another Hive db you have

[Anonymous]

Hello @newAtTalend 

Are you using 32 bit OS?

Best regards

Sabrina

[vroncalla]

Hello @xdshi

I have the same problem using Talend Big Data Platform 7.1.1

The error dissapear when I enable the Log4J, however, this generates an issue in tHiveInput Component https://community.talend.com/t5/Design-and-Development/tHiveInput-Error-dbUser-tHiveInput-1-cannot-b...

We just acquired Talend 7.1.1 and are trying to migrate our jobs from 6.3 to 7.1.1 however we are having several problems with hive components.

Please extend your support

[Anonymous]

Hello @vroncalla ,

Does this issue only repro on V 7.1.1? Did you enclose the query itself in double-quotes? Are you able to run a simple query without context value successfully?

Best regards

Sabrina

[vroncalla]

Helllo @xdshi 

Yes, this only happens on V 7.1.1.

Yes, I tried using a double-quotes

No, I am not able to run a simple query. I tried a simple query but it did not work

This is the version we have: Talend-Studio-20181026_1147-V7.1.1

Please your support

[Anonymous]

Hello @vroncalla ,

With your Talend Big Data Platform 7.1.1, the subscription solution, could you please create a case on talend support portal so that we could give a remote assistance(webex) to you to see if it is still a log.info bug through support cycle with priorty. Thanks for your time.

Best regards

Sabrina

[vroncalla · Accepted solution]

Hello @xdshi

As we need this resolved asap, we are using another approach, instead of using the connection from metadata we are using a tHiveConnection component and check the option "Use an existing connection" in tHiveRow component. In this way the additional bug code is not showed

[Anonymous]

Hello,

Thanks for your feedback and sharing the solution with us.

Best regards

Sabrina

[Anonymous]

good luck to you, we just discarded talend from our project, we're using the server version of contractor, so no more problems with Talend and with the contractor.