[JBoss JIRA] (TEIID-4559) Support for SAP Variables to enable accessing multi-cubes
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-4559?page=com.atlassian.jira.plugi... ]
Steven Hawkins reassigned TEIID-4559:
-------------------------------------
Fix Version/s: Backlog
Open To Community
Assignee: (was: Edwin Jones)
> Support for SAP Variables to enable accessing multi-cubes
> ---------------------------------------------------------
>
> Key: TEIID-4559
> URL: https://issues.redhat.com/browse/TEIID-4559
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 9.2
> Reporter: Van Halbert
> Priority: Major
> Fix For: Backlog, Open To Community
>
>
> When there is OLAP with multi-cubes, we can't currently handle the data stream back.. Because we are currently using olap4j for our MDX support, we run into issues since SAP has proprietery extensions to the MDX language called SAP Variables that we need to support.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 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 reassigned TEIID-4219:
-------------------------------------
Fix Version/s: Backlog
Open To Community
Assignee: (was: Edwin Jones)
> 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: Edwin 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, 10 months
[JBoss JIRA] (TEIID-5211) Allow ability to forward-engineer into underlying data stores
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5211?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5211:
----------------------------------
Fix Version/s: Backlog
> Allow ability to forward-engineer into underlying data stores
> -------------------------------------------------------------
>
> Key: TEIID-5211
> URL: https://issues.redhat.com/browse/TEIID-5211
> Project: Teiid
> Issue Type: Enhancement
> Components: Connector API
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: Backlog
>
>
> As a platform I am better able to better engineer my underlying data stores starting with a virtual model.
> Please add the ability to create, alter, and drop schema objects and relationahips (DDL) in underlying data sources. Example, if I design a source in Teiid Designer I may wish to have Teiid do the DDL against the underlying data source(s). This allows better abstraction an portability of the data model.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months