In a query involving multiple datasets, when creating coalesced fields that combine fields from various datasets—whether through direct reference or dynamic references using interaction syntax from another query—broadcasting may not occur if the coalesced projected field name does not match an API field name from the first loaded dataset.
For example, if you create a coalesced field using the foreach generate syntax, the output field alias should match an API field from the first dataset in the query to allow broadcasting to function correctly.
E.g: q = foreach q generate coalesce(q1.'ds1.customFieldA', q2.'ds2.customFieldA') as 'ds1.customFieldA', etc...
Related Help Content:
002471442

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.