Team, I wanted to discuss implementation details around dynamic properties for C++ processors. Currently Processor.cpp prevents any property present in config.yml and not in the set of supported properties from being read.
In general I'm wondering if it should be the responsibility of each processor developed to override the setProperty function and handle the dynamic properties internally or if there should be something like a "dynamicProperty" variable present in Processor.cpp much like the map that is currently their for <string, Property> but rather <string, string> in this case. The Processor.cpp setProperty logic could then be altered to something like that if a property read from config.yml is not in the list of supported properties it can safely assume and considered a dynamic property and then placed there. Likewise the Processor.cpp getProperty function could be altered to return from the dynamic property map if the key is not located in the supported properties map. I lean more towards the "dynamicProperty" approach but wanted to hear others opinions.
