Implicit conversion from source type
Moderators: chulett, rschirm, roy
Implicit conversion from source type
Hi All
I have a source column whichis having length of 40 , I need to do a lookup with another table and the olumn lngth of Looup table is 26 ,after running the job I am getting this Warning.
"Implicit conversion from source type "string[40]" to result type "ustring[max=26]": Possible truncation of fixed length string. "
How to handle this warning in job level.
Thanks in Advance
Kiran
I have a source column whichis having length of 40 , I need to do a lookup with another table and the olumn lngth of Looup table is 26 ,after running the job I am getting this Warning.
"Implicit conversion from source type "string[40]" to result type "ustring[max=26]": Possible truncation of fixed length string. "
How to handle this warning in job level.
Thanks in Advance
Kiran
KKSR
-
- Participant
- Posts: 251
- Joined: Mon Jun 09, 2008 5:52 am
-
- Participant
- Posts: 1
- Joined: Tue Dec 09, 2008 11:40 am
- Location: pune
-
- Participant
- Posts: 334
- Joined: Fri Dec 01, 2006 5:17 am
- Location: Texas
OrHari_Reddy wrote:just you can increse the lenth of Lookup table Column is 40. then you can not get this type of worning,
do substring in the source
Or
do substring in the lookup stage.
that is column_name[1,26]
Same solution as balajisr said! :D
Hope this will help you out!!
http://findingjobsindatastage.blogspot.com/
Theory is when you know all and nothing works. Practice is when all works and nobody knows why. In this case we have put together theory and practice: nothing works. and nobody knows why! (Albert Einstein)
Theory is when you know all and nothing works. Practice is when all works and nobody knows why. In this case we have put together theory and practice: nothing works. and nobody knows why! (Albert Einstein)
You can put a job level or project level handler to demote this warning message and suppress it from the log; but as you can see from the reactions of the other posters, this is not a good idea and the best (and correct) solution is to avoid this truncation problem by either making the fields appropriately sized or by using an explicit truncation function on the larger string and redefining it to the shorter length.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>