I have to implement Luhn Algorithem in Talend. I already have code for this for that is implemented in other ETL tool. Anyone can help me to implement that in talend as well.
The Luhn’s algorithm, also known as the modulus 10 or mod 10 algorithm, is a simple checksum formula used to validate a variety of identification numbers, such as credit card numbers, IMEI numbers, Canadian Social Insurance Numbers. The LUHN formula was created in the late 1960s by a group of mathematicians. Shortly thereafter, credit card companies adopted it. Because the algorithm is in the public domain, it can be used by anyone. Most credit cards and many government identification numbers use the algorithm as a simple method of distinguishing valid numbers from mistyped or otherwise incorrect numbers. It was designed to protect against accidental errors, not malicious attacks.
Luhn Algorithem is a Java code which I need to implement in Talend
I have to implement Luhn Algorithem in Talend. I already have code for this for that is implemented in other ETL tool. Anyone can help me to implement that in talend as well.
I have implemented the Luhn algorithm successful but did in a different way as I dont have much knowledge about talend.
I have created a function in sql server and then using tmssql I have called that algorithm. It was very simple to implement by this way. Just create a fucntion in your DB and call that.
Thanks for the info. create the sql function and calling it is the best way. are you just validating the credit card or doing the complete algorithm like 2x-9 and then mod 10 . if you have any sample sql luhn algorithm for cards , can you share it.
I was looking in Talend data preparation , there is something I noticed with data masking ( obfuscation ) which can mask all cards and if we can use the jar files of talend data preparation in Talend data quality or Talend data integartion. our issue is resolved without writing PL/SQL or TSQL . I don't know how to do it. Talend expert should help us out .
Looking at performance point of view . it is better "java" should handle the luhn algorithm . when we run millions of records , there would be memory space issues latter. we had these issues calling the other functions in db for ETL.
