Allow users to map source columns to Java and Avro types based on rules rather than a list.
About half the data types on my current project are NUMERIC, and many of those have a SCALE of 0. It would be helpful to be able to process those as Integers or Longs. The map-column-java feature is helpful, but it requires continuous surveillance of the source tables and maintenance of lists of columns and what type they should be mapped to.
It would be helpful to be able to create a rules-based interpretation of the type inference provided by Sqoop.