Talend TMAP not behaving with variable expressions

[DonMcCarty]

I've just installed Talend OpenSource in a new instance.

I'm using a licensed version at work and wanted to explore some other uses personally.

TMAP in my paid version is behaving differently than in my free version.

First thing I noticed was my variables are not listed by name, but instead by expression.

Free Version

And a similar example on my paid version

Further, references to any variable in the TMAP expression build do not work on the free version

YET when I put this code in place and run the job, everything works EXACTLY AS EXPECTED.

Any help in understanding what could cause this odd TMAP bahvior would be greatly appreciated.

[Anonymous]

Hi

The Var/Value table list the expression might be used in your expression field, take a look at the Testing expressions in the tMap component part in this page to know more information about this function.

I hardly ever use this button because it's just for testing simple functions, not executing an entire job.

Regards

Shong

[Anonymous]

Looking for the same issue. Bumped into your thread. Thanks for creating it. Looking forward for solution.

Toys r us credit card

[DonMcCarty]

Thank you for your reply Shong.

I'm not sure if I understand your response when considering my question.

My issue is that Talend Studio paid version is behaving very differently than Talen Studio Open Source in this space.

Agree testing is for simply expressions.

HOWEVER, what is being displayed is just wrong AND the testing button simply does not work.

This renders a portion of the TMAP functionality unusable.

[DonMcCarty]

I can't believe this is the case - I'm 5 minutes into trying out the Open Source option and find a gross difference between the two.

What other issues await me as I get deeper into it?

[DonMcCarty]

Not sure if Shong is responding officially.

But such drastically different behavior will limit the adoption of this tool in any organization.

The entire business model is to trial and prototype with the open-source, get developers dependent on it, and then only be able to put it into production with a license.

If the entry point, the open-source version of the product, does not provide a good experience the trial for the tool ends there.

[DonMcCarty]

I thought version 8 might contain the problem so I downgraded to v 7.4.

Unfortunately - this was not helpful and produces the same problem.

[Anonymous]

@Don McCarty​, both of community version and paid version has the same tMap, if the functionality exists on both community version and paid version, it should behave the same. I'm sorry if I don't understand your question well, from your first post, I don't see what's the difference of the 'Test' button behave between community version and paid version.

Regards

Shong

[DonMcCarty]

@Shicong Hong​ - No worries. Let's put the "test" button aside and focus on what is displayed.

The free version displays the Expression in the "Var" column. While the paid version displays the variable name in the "Var" column.

This leads to issues when double-clicking the entry.

• In the free version, the expression is pasted in - this is wrong
• In the paid version, the variable reference is pasted in - this is correct (i.e. Var.curr_date in my example)

Let's focus on this first and then next we can dig into the behavior of the testing button.

Further, @Joseph Cronin​ seems to have encountered the same scenario in an entirely different install so it is not unique to my situation.

Does this help explain the situation better?

[DonMcCarty]

My screen shots and reports of other would contradict your statement of tmap behaving same in free and paid version Have you tried it Jin your instances?