On Tue, Feb 28, 2012 at 10:52 AM, Jarek Jarcec Cecho <jar...@apache.org>wrote:
> Hi Alex and Alan, > we already moved entire logic to org.apache namespace. We're keeping > classes in com.cloudera in place only for compatibility with tools that are > based on sqoop (for example various connectors). Cloudera's compatibility issues are not our problem. These packages need to go. > However those classes do not contain any logic, This has nothing to do with whether or not they contain functionality. That namespace is a mark of Cloudera. It has no place in an Apache Product. We have no control over that namespace nor do we want it. > they are just inheriting from org.apache namespace and do nothing. Let me > show you what I mean on following example: > > > https://svn.apache.org/repos/asf/incubator/sqoop/trunk/src/java/com/cloudera/sqoop/manager/MySQLManager.java > > All other files in com.cloudera namespace have similar structure. They are > just skeleton code that is in place for compatibility without any logic > (additional code). > > Do we really need to remove entirely com.cloudera namespace or is this > state acceptable for graduating? > > It is NOT acceptable. -- Best Regards, -- Alex
