Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

If I understand what you're trying to do correctly, you can add a Stream Selector processor before your Hive Metadata processors. Configure that stream selector to only pass through records with the attribute you want (i.e. use a condition like ${record:attribute('jdbc.tables') != null}) to pass through the records you want to keep in that stream, and send others to trash or some other location.

However, I wonder if this is even overkill for what you're trying to do. Please bear in mind that the jdbc.tables attribute is just a preconfigured attribute name coming out of the origin. You are not bound to use that name in your Hive processor. You could potentially put an expression evaluator processor to "unify" the attribute names - using whatever logic is required - into a single common one (ex: table_name_final) that the Hive metadata processor is expecting.