New methods for Sqoop import with SQL query

Not sure if we want to do it and I didn't do this before :), but with the Sqoop API we are guaranteeing :-
1) Data is copied to a path
2) Return the path for further processing
3) Return the count

Here we are verifying that the data is copied and the count is correct (which is great) but do we want to confirm that the path we return is in fact the correct one or atleast looks like it. It's a minor point but if you look at it from an API point of view, correctness implies that all these three should happen. I am not sure whether we do this across maestro so I would leave this you but would be interested to hear thoughts on this.