Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-03-10 Thread Jilani Shaik
Hi Bogi, I have updated the patch and submitted review request for the same with changes as a patch at both the places. Changes applied on trunk version. Thanks, Jilani On Fri, Mar 10, 2017 at 2:10 PM, Boglarka Egyed wrote: > Hi Jilani, > > Information of a JIRA creation/modification are sent

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-03-10 Thread Boglarka Egyed
Hi Jilani, Information of a JIRA creation/modification are sent to dev@ so you don't need to share the JIRA here again. Also, if you have set "Sqoop" at the ReviewBoard as a group to review people in that group will receive a notification about it. I can see that you have created a JIRA

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-03-10 Thread Jilani Shaik
Hi Bogi, Do I need to share the JIRA and review ticket etc here again or Once I create a JIRA and review ticket and submit the detail, workflow will follows from there like validating, comment/suggestion etc. Thanks, Jilani On Fri, Mar 10, 2017 at 7:57 AM, Jilani Shaik wrote: > Yes you are cor

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-03-10 Thread Jilani Shaik
Yes you are correct, I am running from eclipse. Will run from command line. Sent from my iPhone > On Mar 10, 2017, at 6:48 AM, Boglarka Egyed wrote: > > Hi Jilani, > > Please try to execute "ant compile" and then "ant test" from command line, it > will run unit tests. If I understood you well

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-03-10 Thread Boglarka Egyed
Hi Jilani, Please try to execute "ant compile" and then "ant test" from command line, it will run unit tests. If I understood you well, you tried run tests from Eclipse which won't work. Thanks, Bogi On Fri, Mar 10, 2017 at 6:10 AM, Jilani Shaik wrote: > Hi Bogi, > > Thanks for the providing d

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-03-09 Thread Jilani Shaik
Hi Bogi, Thanks for the providing direction. As you suggested I explored further and resolved the issue and able to test the fix on trunk based code changes in my hadoop cluster. Root cause for my issue: 1.4.6 code base using the same avro version which is there in my hadoop cluster so there is

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-03-09 Thread Jilani Shaik
Hi Bogi, - Prepared jar using trunk with "jar-all" target - Copied the jar to /opt/mapr/sqoop/sqoop-1.4.6/ - Moved out existing jar to some other location - then execute the below command to do import sqoop import --connect jdbc:mysql://10.0.0.300/database123 --verbose --username test --passwor

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-03-09 Thread Boglarka Egyed
Hi Jilani, I suspect that you have an old version of Avro or even multiple Avro versions on your classpath and thus Sqoop uses an older one. Could you please provide a list of the exact commands you have performed so that I can reproduce the issue? Thanks, Bogi On Thu, Mar 9, 2017 at 2:51 AM, J

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-03-08 Thread Jilani Shaik
Can some one provide me the pointers what am I missing with trunk vs 1.4.6 builds, which is giving some error as mentioned in below mail chain. I did followed the same ant target to prepare jar for both branches, but even though 1.4.6 jar is different to 1.4.7 which is created form trunk. Thanks,

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-03-08 Thread Jilani Shaik
Hi Bogi, I am getting below error, when I have prepared jar from trunk and try to do sqoop import with mysql database table and got below exception, where as similar changes are working with branch 1.4.6. 17/03/08 01:06:25 INFO sqoop.Sqoop: Running Sqoop version: 1.4.7-SNAPSHOT 17/03/08 01:06:25

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-03-01 Thread Boglarka Egyed
Hi Jilani, This is an example: SQOOP-3053 with the review linked. Please make your changes on trunk as it will be used to cut the future release so your patch definitely needs to be be able to apply on it. Th

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-02-28 Thread Jilani Shaik
Hi Bogi, Can you provide me sample Jira tickets and Review requests similar to this, to proceed further. I applied the code changes from sqoop git from this branch "sqoop-release-1.4.6-rc0", If you suggest right branch I will take the code from there and apply the changes before submit review for

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-02-27 Thread Boglarka Egyed
Hi Jilani, To get your change committed please do the following: * Open a JIRA ticket for your change in Apache's JIRA system for project Sqoop * Create a review request at Apache's review board for project Sqoop and li

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-02-24 Thread Jilani Shaik
Do we have any update? I did checkout of the 1.4.6 code and done code changes to achieve this and tested in cluster and it is working as expected. Is there a way I can contribute this as a patch and then the committers can validate further and suggest if any changes required to move further. Pleas

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-02-05 Thread Jilani Shaik
Hi Liz, lets say we inserted data in a table with initial import, that looks like this in hbase shell 1 column=pay:amount, timestamp=1485129654025, value=4.99 1 column=pay:customer_id, timestamp=1485129654025, value=1 1

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-01-31 Thread Erzsebet Szilagyi
Hi Jilani, I'm not sure I completely understand what you are trying to do. Could you give us some examples with e.g. 4 columns and 2 rows of example data showing the changes that happen compared to the changes you'd like to see? Thanks, Liz On Tue, Jan 31, 2017 at 5:18 AM, Jilani Shaik wrote: >

Re: sqoop hbase incremental import - Sqoop 1.4.6

2017-01-30 Thread Jilani Shaik
Please help in resolving the issue, I am going through source code some how the required nature is missing, But not sure is it for some reason we avoided this nature. Provide me some suggestions how to go with this scenario. Thanks, Jilani On Sun, Jan 22, 2017 at 6:45 PM, Jilani Shaik wrote: >