Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

tHiveRow and log.info error

Hi there!

 

I'm trying just to make a simple example to connect to Hive and make a simple query. However, I got an error, because generated source code for the tHiveRow component uses a variable (log) which is not declared..

 

The tHiveConnection component works fine, and connect properly...

 

Any thoughts?

 

Thanks in advance!

 

0683p000009LsOf.png0683p000009LsXV.png0683p000009Lsah.png

Labels (3)
21 Replies
Anonymous
Not applicable
Author

This should be a blocker to new release.  You cannot use hive until it's fixed.

Hive is a standard solution in all the hadoop platforms and is basic functionality.

I'm surprised it's even a discussion  as to what the priority should be or that it made it through testing.

Even the most basic connection test will fail.

 

LBAGNI
Contributor
Contributor

Quick Fix for  tHiveRow:

edit the following file
TOS_BD-20180411_1414-V7.0.1/plugins/org.talend.designer.components.localprovider_7.0.1.20180411_1414/components/tHiveRow/tHiveRow_main.javajet

comment the line number 229

log.info("Query sent to HiveServer2 to be executed with [Application Name(MapReduce)/DAG Name(Tez): " + queryIdentifier + "]");

 

Reload Talend Big Data 7.0.1

Anonymous
Not applicable
Author

Hello,

After doing that, it would be great to delete the file <studio-install-dir>/configuration/ComponentCache.javacache and restart studio.

Best regards

Sabrina

Anonymous
Not applicable
Author

Hi Users,

me too facing the same issue in Talend DI hive row. As per Jira comments, they not able to reproduce the error.  Has anyone tried this approach? I tired but got another error.

 

https://community.talend.com/t5/Design-and-Development/tHiveRow-cannot-resolve-any-fields/td-p/11414...

 

if some one has working hiverow code please share screen shot

Anonymous
Not applicable
Author

Hello,

Are you still facing this error on the latest released version V 7.0.1?

Best regards

Sabrina

Anonymous
Not applicable
Author

Yes. The issue still exist. It was nearly a year since the first post complaint about this. And here we are in a situation where we still facing the same issue nine months later.

 

This line still exist and causing error when building the any job with tHiveRow:

log.info("Query sent to HiveServer2 to be executed with [Application Name(MapReduce)/DAG Name(Tez): " + queryIdentifier + "]");
LBAGNI
Contributor
Contributor

Hi @kurotsuki,

is this issue still present on release 7.1?

Thanks in advance.

Anonymous
Not applicable
Author

It is for me on TOS_BD-20181026_1147-V7.1.1.

 

There was this bug, but they closed/rejected it saying they could not reproduce.

https://jira.talendforge.org/browse/TBD-6469

 

I'm not sure they understand the issue, but I did not get a chance to try the version they said was ok (Talend-Studio-20180808_1933-V7.1.1SNAPSHOT).  I do find it hard to believe it was fixed and then reintroduced between the August snapshot and the October build.  Maybe they are only checking the paid version and it's not an issue there?

 

Pete

Anonymous
Not applicable
Author

Same for me, it is happening on Talend studio for big data 7.1.1 .

Please solve it, Talend has more bugs than Windows !  It can't happen that a problem that was present
in precedent and older version, re appears in TDBI 7.1  !!!

Anonymous
Not applicable
Author

I checked the sandbox of the paid version and by default it's not an issue.  In the paid version there is a checkbox you can use to turn on and off logging.  By default it's turned on, so everything for logging is defined and there is no issue.  If you un-check it, to turn off logging, the paid version has the same error as TOS.

 

In TOS logging is turned off and the check box to allow turning it on is hidden so there is no work around.  We can't upgrade, and have not been able to since 6.4.1 because of this bug.  It's prompting us to stop using Talend for anything and move what we have off.  This is really basic functionality and extremely easy to reproduce (and I think to fix).  TOS is just not a priority for them so if you need an open source etl tool I would start looking.  Lot's more around today than even a couple years ago.