Bug 533789 - metadata query for each stored procedure
Summary: metadata query for each stored procedure
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 4.7.0   Edit
Hardware: PC Windows 10
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Birt-DataAccess CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-18 16:26 EDT by VinceG CLA
Modified: 2018-04-18 16:26 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description VinceG CLA 2018-04-18 16:26:15 EDT 
At runtime, for each unique stored procedure call in a BIRT report, a metadata query is issued on the DB. 
It appears the metadata call is made in the prepare method of the DataSourceQuery to figure out the parameters. This seems unnecessary as already done in BIRT designer when designing the report. The metadata does not change.

This is a performance issue. Oracle for instance, indicates to limit request against metadata tables. Because of this, unable to scale BIRT architecture in large application when multiple reports, containing several unique procedure calls,  are generated on regular bases.


Metadata is not being cached at the application level.