[JBoss JIRA] (TEIID-992) Improve update of source costing statistics
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-992?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-992.
----------------------------------
Resolution: Out of Date
Bulk resolving older issues as out of date.
> Improve update of source costing statistics
> -------------------------------------------
>
> Key: TEIID-992
> URL: https://issues.redhat.com/browse/TEIID-992
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors, Query Engine
> Reporter: Marc Shirley
> Priority: Major
> Fix For: Backlog
>
>
> It is very important that we support the ability to update source statistics at runtime. This is important due to the changing nature of read/write sources and differences between a development data source and a production data source.
> The following options should be possible:
> 1) Update model/source statistics on VDB deployment.
> 2) Update model/source statistics on connector startup.
> 3) Update model/source statistics on at a scheduled time.
> 4) Update model/source statistics upon a manual request.
> case 5920
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (TEIID-3347) Most subplans do not show node stats
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-3347?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-3347.
-----------------------------------
Resolution: Out of Date
Bulk resolving older issues as out of date.
> Most subplans do not show node stats
> ------------------------------------
>
> Key: TEIID-3347
> URL: https://issues.redhat.com/browse/TEIID-3347
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: Backlog
>
>
> When looking at the node stats, only the direct nodes of the current plan have stats. Subqueries, which are executed off of a cloned plan, do not have stats.
> There isn't an easy solution for this with the current design.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (TEIID-4219) Support variable and Parameters in HANA Translator
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-4219?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-4219.
-----------------------------------
Resolution: Out of Date
Bulk resolving older issues as out of date.
> Support variable and Parameters in HANA Translator
> --------------------------------------------------
>
> Key: TEIID-4219
> URL: https://issues.redhat.com/browse/TEIID-4219
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.13.4
> Reporter: Ted Jones
> Priority: Major
> Fix For: Backlog, Open To Community
>
>
> •Variables:
>
> A Variable can be specified before executing a query on the view. Usually variable values are entered manually by the user on a UI (variable popup). A variable defines a filter on an attribute of the view. Therefore it always has to be assigned to an attribute. The variable values are passed to the engine via the WHERE clause of the SQL statement. Variables are not known by the engine, but only by the clients like Datapreview, MDX, Advanced Analysis for Office or BO Explorer. It is the task of the client to convert the user input into the WHERE clause when accessing the data.
>
> •Parameters or Input Parameters:
>
> A parameter (like a variable) can be specified before executing a query on the view. Usually parameter values are entered manually by the user on a UI (variable popup). A Parameter defines an internal parameterization of the view. This means the engine needs to know it and uses the parameter value during the execution (e.g. to calculate a formula for a calculated measure). The parameter value is passed to the engine via the PLACEHOLDER clause of the SQL statement. A parameter can only have single values. For the end user there is no distinction between variables and parameters. Both appear as input fields on the variable popup.
>
> ------------------
>
> There are 4 system tables under the schema _SYS_BI which contains information about Variables.
> · BIMC_VARIABLE
> · BIMC_VARIABLE_ASSIGNMENT
> · BIMC_VARIABLE_VIEW
> · BIMC_VARIABLE_VALUE
>
> SAP HANA documentation on Input parameters: http://help.sap.com/saphelp_hanaplatform/helpdata/en/d5/c8230abb571014acc...
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months