Quisque mattis rutrum ligula et pellentesque. Pellentesque massa enim, pulvinar quis quam quis, aliquet dapibus augue. Aliquam feugiat suscipit turpis, nec ultrices dolor adipiscing ut.
Pentaho Metadata-Based Reports Produce Slow Responses and Generate Inconsistent Results
If a report contains inconsistent or incorrect results, and the SQL command contains several joins, make sure the join order has been specified for that report. 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 Outer Joins.
Pentaho Metadata-Based Reports Generated in Version 4.8 Produce Different Results in Version 5.x
In version 5.0 of the software, inner joins are resolved before outer joins by default. If you are migrating a report from version 4.8 to 5.x, you can specify which method to use by setting the legacy_join_order parameter in the report’s .xmi file. Set legacy_join_order to true to use the 4.8 method. Set legacy_join_order to false to use the 5.0 method.
In addition to setting the legacy_join_order parameter, set the Join Order Key field in the Relationship Properties window. For more information, see Managing Outer Joins.