Type Resolver UI isn't giving option to convert from Source attribute type to target attribute type

[shakirhusain]

I upgraded to Teiid Designer 8.1 beta 1 from Teiid Desiger 8.0 Final

This functionality used to work just fine old Type Resolver UI.

I have target attribute as float and source attribute as double.

The Type Resolver UI is only giving option to change the data type of target attribute to double, but the option for converting the values of source attribute to float is disabled.

Is this a bug or am I missing something here?

Thanks,

Shakir

[blafond]

Shakir,

I just re-tested with simple source/view table transformation using "double" and "float" and my button is enabled.

Please log a JIRA and attach your source and view models (or an exported Model Project Set) so we can debug it.

https://issues.jboss.org/browse/TEIIDDES/

Thx

Barry

Teiid Designer Project

[jane_lj]

Barry,

We figured out we can have that button enabled now if we do mapping in another way.

Now the problem is, we picked the "convert" option for the virtual column, but we can't query against that column, we got this error:

14:18:55,546 WARN  [org.teiid.PROCESSOR] (Worker4_QueryProcessorQueue39) TEIID30020 Processing exception 'TEIID30328 Unable to evaluate convert(Petrel_SM.PetrelMarker.DipAngle, float): TEIID30384 Error while evaluating function convert' for request jPSnK8VBPZty.6.  Exception type org.teiid.api.exception.query.ExpressionEvaluationException thrown from org.teiid.core.types.Transform.checkValueRange(Transform.java:112). Enable more detailed logging to see the entire stacktrace.

Any idea?

BTW, the middle column "Matched Datatype", what is that for? How to pick the type for it?

Thanks.

[blafond]

For the exception, maybe check your datatype properties (precision, length, etc.) to make sure the number you are converting is compatible.

The Matched Datatype is what Designer discovers as the compatible runtime datatype based on the source column datatype

[shakirhusain]

For the benefit of all, let me elaborate little on what jane_lj found.

Usual way of doing the mapping is select an apporpriate SQL symbol (i.e., source attribute) and select a virtual target column and use "< Bind" button to map them.

The convert of souce SQL Symbol to target datatype will be enabled in this scenario.

The other way of achieving the same is click and, select "Column" radio button and then select the source column.

Though the resulting SQL will be same as in the previous case, the convert of souce SQL Symbol to target datatype will be disabled.

[jane_lj]

Barry,

Thanks for your hint, the root cause is some bad data, nothing else was wrong.