Follow the suggestions in these topics to help resolve common issues with Pentaho metadata including thePentaho Metadata Editor and the Pentaho User Console components which auto-generate metadata models:
- Managing multiple outer-joins
- Slow responses or inconsistent results in reports
- Metadata-based reports generated in version 4.8 produce different results in version 5.x
Managing multiple outer-joins
- Join TABLE1 and TABLE2 (shown in red)
- Join TABLE3 and A = B (shown in blue)
- Join TABLE4 with B = Result
To force conditions that would ordinarily be processed in the JOIN condition to be processed in the WHERE clause, follow the directions below to create a delay_outer_join_conditions custom property.
Right-click on a business model and select Edit.
Add a property by clicking the green + icon.
Select Add a Custom Property and set its ID to delay_outer_join_conditions and select boolean for the Type, then click OK.
Select the newly-created delay_outer_join_conditions property, then click the checkbox for delay_outer_join_conditions under the Custom heading on the right side of the window, then click OK.
Slow responses or inconsistent results in reports
Beginning in version 5.0, inner joins are resolved before outer joins. If you have several tables that require outer joins, the order in which the tables are joined is critical because different join orders produce different results. To make the join order consistent, set the Join Order Key field in the Relationship Properties window. For more information, see: Managing multiple outer-joins.
Metadata-based reports generated in version 4.8 produce different results in version 5.x
- 4.8 method: Set legacy_join_order to: true
- 5.0 method: Set legacy_join_order to: false
In addition to setting the legacy_join_order parameter, set the Join Order Key field in the Relationship Properties window.