Can we eliminate enumerting & filtering individual jars from hadoop and
hbase classpaths when including them into flume's own classpath as
flume/lib/* takes precedenc anyway.

The CLASSPATH is has roughly the following components  in order:

1) flume/lib/*
2) flume/conf/*  (as specified by -c arg)
3) jars from hadoop-classpath
4) jars from hbase-classpath

The issue is that enumerating jars can make the internal command line very
long and can run into length limitations.

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Reply via email to