Hitachi Vantara Pentaho Community Wiki
Child pages
  • Updates for BISERVER-2735 (Row Limit, Timeout, Read Only)
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Liberty And Later Documentation Only

This document contains documentation for the BI Platform (including the BI Server) version 2.1. Older documentation for version 1.x is here

Document Purpose

The bug reported in BISERVER-2735 resulted in various changes in platform components. Imposing row limits and timeouts on queries is sometimes important to avoid causing out of memory errors or processes that consume too many resources on the database server. The purpose of this document is to document the ways to control row limits, timeouts and the read-only setting in the JDBC connection object.

Affected Platform Areas

  • Action sequences
    • Certain action sequence (BI) components have been updated to recognize some or all of the new capabilities as action inputs.
  • Web-based Adhoc Query And Reporting
    • If appropriate meta-data is provided on the business model, Web-based adhoc will respect the settings and limit the queries accordingly.
  • Pentaho Metadata Editor (PME)
    • PME can be used to provide the settings that will be respected by the metadata query components in the platform.

Affected Components

  • SQLBaseComponent and subclasses
    • SQLLookupRule
    • MQLRelationalDataComponent
  • HQLBaseComponent and subclasses
    • HQLLookupRule
  • XQueryBaseComponent and subclasses
    • XQueryLookupRule

New component inputs

The components above now accept up to three new "known" optional inputs.

max_rows

All of the above components look for, and respect the new input max_rows. For SQLBaseComponent, and HQLBaseComponent, when max_rows comes in as an input through the normal

  • No labels