Seems the annotation approach allows you to add HBase specific information to the sub-classes of AbstractProcessor that are HBase aware without having to modify AbstractProcessor itself.
+1 for annotations on subclasses. On Sat, Jul 10, 2010 at 8:05 PM, Eric Yang <[email protected]> wrote: > Hi all, > > I am planning on modifying AbstractProcessor to have 2 additional methods: > > Public String getTableName > Public String getColumnFamily > > This allows HBaseWriter to validate the output schema and add data to > different Htable. This should have no impact to existing demux. > > Another approach is to use annotation and insert annotation to existing > parser class like: > > Public class HadoopLogProcessor extends Abstract Processor { > @Table > public static final String recordType = ³HadoopLog²; > @ColumnFamily > public static final String nameNodeType = ³NameNode²; > @ColumnFamily > public static final String dataNodeType = ³DataNode²; > ... > } > > Which method makes more sense? > > Regards, > Eric >
