topic Re: Thive Row log.info error on compile in Installing and Upgrading

Thive Row log.info error on compile

Anonymous — Sat, 16 Nov 2024 06:47:00 GMT

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

Re: Thive Row log.info error on compile

Anonymous — Wed, 23 Jan 2019 14:52:40 GMT

@xdshi

Re: Thive Row log.info error on compile

Anonymous — Thu, 24 Jan 2019 07:17:07 GMT

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

Re: Thive Row log.info error on compile

Anonymous — Thu, 24 Jan 2019 08:25:44 GMT

@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

Re: Thive Row log.info error on compile

Anonymous — Mon, 28 Jan 2019 08:52:57 GMT

Problem is still there..

Re: Thive Row log.info error on compile

Anonymous — Wed, 30 Jan 2019 03:31:45 GMT

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

Re: Thive Row log.info error on compile

Anonymous — Wed, 30 Jan 2019 09:53:12 GMT

@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

Re: Thive Row log.info error on compile

Anonymous — Wed, 30 Jan 2019 11:30:37 GMT

Hello,

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

Best regards

Sabrina

Re: Thive Row log.info error on compile

Anonymous — Wed, 30 Jan 2019 11:37:41 GMT

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.

Re: Thive Row log.info error on compile

Anonymous — Wed, 30 Jan 2019 11:59:30 GMT

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

Re: Thive Row log.info error on compile

Anonymous — Wed, 30 Jan 2019 12:09:08 GMT

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

Re: Thive Row log.info error on compile

Anonymous — Wed, 30 Jan 2019 16:18:16 GMT

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

Re: Thive Row log.info error on compile

Anonymous — Thu, 31 Jan 2019 03:14:06 GMT

Hello @newAtTalend

Are you using 32 bit OS?

Best regards

Sabrina

Re: Thive Row log.info error on compile

vroncalla — Fri, 22 Mar 2019 19:06:24 GMT

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-be-resolved-to-a/m-p/155685#M95159

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

Re: Thive Row log.info error on compile

Anonymous — Mon, 25 Mar 2019 03:46:21 GMT

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

Re: Thive Row log.info error on compile

vroncalla — Mon, 25 Mar 2019 14:03:24 GMT

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

Re: Thive Row log.info error on compile

Anonymous — Tue, 26 Mar 2019 03:52:03 GMT

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

Re: Thive Row log.info error on compile

vroncalla — Fri, 29 Mar 2019 14:27:28 GMT

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

Re: Thive Row log.info error on compile

Anonymous — Mon, 01 Apr 2019 03:59:32 GMT

Hello,

Thanks for your feedback and sharing the solution with us.

Best regards

Sabrina

Re: Thive Row log.info error on compile

Anonymous — Mon, 01 Apr 2019 13:57:44 GMT

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.