@herriojr, have you considered overwriting the schema file that you're putting on HDFS, rather than putting it by ID (at line 171, above)? By overwriting the same file, you would not need to issue the update table statement at all. It would be "updated automatically".

I'm not sure if there are tradeoffs to each approach, for example, in the case where the table def or referenced avro file changed in the middle of a running Hive job.

That being said, keeping several schemas by IDs in HDFS is interesting, but it is not guaranteed to contain every item in the schema repo (because there could have been several changes in the repo between two camus2hive runs), so I'm not sure if there is really an interest in putting on HDFS anything else than the latest schema for each topic.

What are your thoughts on this?