The only thing I'm aware of is the workflow user required for reruns and late data.
On Thu, Jan 16, 2014 at 5:51 PM, Srikanth Sundarrajan <[email protected]>wrote: > Hi Venkatesh,Can we enlist what are the incompatibilities are? This will > help us make informed decision on which of these incompatibilities are a > deterrence to migration and which of the ones add too much debt to Falcon > code base to build in this compatibility and choose accordingly. > RegardsSrikanth Sundarrajan > > > Date: Thu, 16 Jan 2014 15:09:23 -0800 > > Subject: [DISCUSS] Backwards compatibility in Falcon > > From: [email protected] > > To: [email protected] > > > > Should we have falcon support backwards compatibility for jobs between > > secure and non-secure hadoop clusters? > > > > -- > > Regards, > > Venkatesh > > Hortonworks, Inc. > > > > -- > > 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. > > -- Regards, Venkatesh “Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.” - Antoine de Saint-Exupéry
