Only if you're using a dataset in HBase. Maybe we could do the same sort
of logic we use for Hive when submitting jobs. We currently check
whether the dataset is Hive and will run via MR and then add
dependencies for it. We could do the same for HBase, though the initial
classpath needs to include everything to know where to pull the jars from.
rb
On 10/07/2015 12:16 AM, Andrew Stevenson wrote:
> Hi Ryan,
>
> I was wondering if the contents of hbase/lib are also added unnecessarily?
>
> Regards
>
> Andrew
> ------------------------------------------------------------------------
> From: Andrew Stevenson <mailto:
astev...@outlook.com>
> Sent: 06/10/2015 21:13
> To: Ryan Blue <mailto:
bl...@cloudera.com>;
cdk...@cloudera.org
> <mailto:
cdk...@cloudera.org>
> Subject: RE: Turn on cli debugging
>
> I'll try that. I did see the hadoop class path was rather large.
>
> Regards
>
> Andrew
> ------------------------------------------------------------------------
> From: Ryan Blue <mailto:
bl...@cloudera.com>
> Sent: 06/10/2015 20:53
> To: Andrew Stevenson <mailto:
astev...@outlook.com>;
>
cdk...@cloudera.org <mailto:
cdk...@cloudera.org>