fwiw. i would not have the repair table statement as part of a production
job stream.  That's kinda a poor man's way to employ dynamic partitioning
off the back end.

Why not either use hive's dynamic partitioning features or pre-declare your
partitions? that way you are explicitly coding for your purpose rather than
running a general repair table on the backend knowing you "broke it" up

just a suggestion!
On Thu, Mar 27, 2014 at 3:18 AM, fab wol <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB