I don't see where the TableContext created in outputformat could have access to the cluster's configuration or jar files. Maybe when the cluster is initialized it should write the configuration and jars to HDFS, making it available to the output format? If so, should the writer be arranged with zk? Or is there another plan I'm not seeing in there?
Thanks, --tim On Tue, Nov 12, 2013 at 10:34 AM, Aaron McCurry <[email protected]> wrote: > It should be supported, this seems like a bug. > > Aaron > > > On Tue, Nov 12, 2013 at 10:29 AM, Tim Williams <[email protected]> wrote: > >> It seems to be the case that when building a table with the >> BlurOutputFormat, we need to follow the per-table custom field >> definitions vs. cluster-wide. If there's no plan to support >> cluster-wide custom defs with m/r we should just document the >> per-table version I reckon, thoughts? >> >> Thanks, >> --tim >>
