@Sundar Lakshmanan You can simply use "sort" command. [root@node1 ~]# cat /tmp/a.txt abcd_2_20180703 abcd_4_20180703 abcd_5_20180703 abcd_1_20180703 abcd_3_20180703 abcd_6_20180703 [root@node1 ~]# sort /tmp/a.txt abcd_1_20180703 abcd_2_20180703 abcd_3_20180703 abcd_4_20180703 abcd_5_20180703 abcd_6_20180703 Let me know if this helps. ... View more

@Erkan ŞİRİN Here you go. /var/lib/ambari-server/resources/scripts/configs.py --action=delete --host=<ambarihost> --cluster=<clustername> --config-type=sqoop-atlas-application.properties --user admin --password admin --key=atlas.jaas.KafkaClient.option.renewTicket /var/lib/ambari-server/resources/scripts/configs.py --action=delete --host=<ambarihost> --cluster=<clustername> --config-type=sqoop-atlas-application.properties --user admin --password admin --key=atlas.jaas.KafkaClient.option.useTicketCache ... View more

@rmr1989 This is the jira : https://issues.apache.org/jira/browse/SPARK-2750 , you can refer the fixed version or the commit branch from pull request. **If this answers your question, feel free to click on 'accept' and close this thread. ... View more

after reading above comments, realised that you already tried running configs.py. What is the error you got when using configs.py ... View more

@Erkan ŞİRİN If you are not using kerberos and seeing this error. Do check if you have below properties in sqoop-atlas-application.properties atlas.jaas.KafkaClient.option.renewTicket atlas.jaas.KafkaClient.option.useTicketCache If they are present, delete them using below commands on ambari-server machine. /var/lib/ambari-server/resources/scripts/configs.sh -u admin -p <password> delete localhost <cluster> sqoop-atlas-application.properties atlas.jaas.KafkaClient.option.renewTicket /var/lib/ambari-server/resources/scripts/configs.sh -u admin -p <password> delete localhost <cluster> sqoop-atlas-application.properties atlas.jaas.KafkaClient.option.useTicketCache P.S if you are using new version of ambari use configs.py instead of configs.sh Let me know if this helps. ... View more

@Sara Alizadeh, The first command was executed with 10 mappers (-m 10) for 1.3 millions and your mappers might be going out of memory if you are using the same number of mappers for 12 million records. Do increase the number of mappers (i'd say 100) and re-run the job. ... View more

@Sameer Mrinal If you found this answer addressed your question, please take a moment to login and click the "accept" link on the answer. 🙂 ... View more

@SAD KHALED Please take a moment to click "Accept" if this answer helps you. 🙂 ... View more

@Vinod C Kaggal Please take a moment to click "Accept" if this answer helps you. 🙂 ... View more