Joaopolo opened a new issue, #8243:
URL: https://github.com/apache/hop/issues/8243

   ### What would you like to happen?
   
   ## Development Requirement
   
   The current data load flow is split into several sub-pipelines. In some 
scenarios, the column used to apply the group filter may have different names 
across tables, or may not exist directly in the processed table.
   
   Because of this structural variation, it is not possible to apply a single 
generic filter in the final pipeline step, such as a `Filter Rows` step, using 
a fixed column like `GROUP` or `GRUPO`.
   
   ### Problem
   
   The final pipeline receives data from different tables and sub-pipelines, 
but not all of them share the same column structure.
   
   For example:
   
   - Some tables contain the `GRUPO` column directly;
   - Some tables need to obtain the group through a relationship with a parent 
table;
   - Some tables may not have an applicable group filter.
   
   As a result, applying a generic group filter at the end of the flow may 
cause execution errors when the expected column does not exist or has a 
different name.
   
   ### Requirement
   
   The group filter must be handled before the final load step, according to 
the specific structure of each table.
   
   The solution should allow:
   
   - Tables that contain the `GRUPO` column to be filtered directly by it;
   - Tables that depend on a parent table relationship to be filtered using the 
parent table’s `GRUPO` value;
   - Tables without an applicable group filter to be handled separately;
   - The final pipeline to receive only records that have already been filtered 
and standardized for loading.
   
   ### Goal
   
   Avoid making the final pipeline step depend on a column that may not exist 
in every processed table. This reduces execution errors and avoids creating an 
overly complex workflow only to handle column name variations or table 
relationship differences.
   
   ### Expected Result
   
   Each sub-pipeline should deliver data already filtered according to its 
specific rule, ensuring that the final load step can execute without directly 
depending on the existence of the `GRUPO` column.
   
   <img width="1308" height="937" alt="Image" 
src="https://github.com/user-attachments/assets/0d9652b8-2ae1-40f6-a3af-5e9c27238322";
 />
   
   
   ### Issue Priority
   
   Priority: 3
   
   ### Issue Component
   
   Component: Transforms


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to