falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pallavi Rao <pallavi....@inmobi.com>
Subject [DISCUSS] Namespace-ing properties and FALCON-1573
Date Mon, 16 Nov 2015 04:32:57 GMT
With FALCON-1573, Daniel came up with a very good suggestion of allowing
user-supplied properties at schedule time. He proposed 2 approaches

   1. Allow user to specify free form name-value pairs. Since user-supplied
   property names can clash with Falcon property names, give Falcon properties
   (generated when the bundle is built) priority over user-supplied ones, in
   case of clash.
   2. Namespace user-supplied properties, so we can distinguish user and
   system properties. This will allow user to supply properties without any
   clash with system properties.

Daniel has already uploaded patch for approach (1). Regarding this, wish to
solicit your input on 2 questions:

   1. Should we pursue approach (2) in FALCON-1573 itself or take it up
   2. When we eventually namespace the properties, what should the
   namespace format be?

My 2 cents:

Question (1) : I think we should pursue namespace approach in FALCON-1573
itself. Two reasons for the same:

   - When user supplies a name-value pair and we silently ignore (we only
   log) it when it clashes with system property, it is not very intuitive to
   the user.
   - If we don't introduce it now, but, bring it in later, we'll have to
   deal with 2 kinds of properties, one that is namespace-d and one that isn't.

Question (2) : I suggest we use falcon.system.* (or just falcon.*) for
system properties and falcon.user.* for user-supplied properties.

Apologies for the tad lengthy mail. Request you all to provide your inputs.

Thanks and Regards,

The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
on the contents of this information is strictly prohibited and may be 
unlawful. If you have received this communication in error, please notify 
us immediately by responding to this email and then delete it from your 
system. The firm is neither liable for the proper and complete transmission 
of the information contained in this communication nor for any delay in its 

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message