[JBoss JIRA] (TEIIDDES-2033) Need to provide all system functions (i.e, aggregates) that user can use
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2033?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2033:
-----------------------------------
Component/s: Teiid Integration
Transformations
> Need to provide all system functions (i.e, aggregates) that user can use
> ------------------------------------------------------------------------
>
> Key: TEIIDDES-2033
> URL: https://issues.jboss.org/browse/TEIIDDES-2033
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling, Teiid Integration, Transformations
> Affects Versions: 8.3.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 8.5
>
>
> The designer should present the full set of functions a user can use. The initial set of functions not seen are the aggregates (maybe there are others), sum, count, avg, etc., that we support.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIIDDES-2046) Replace Existing XML Document Functionality with other JBoss Technologies
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2046?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-2046:
------------------------------------------
Moving over to Designer as the intent here is an approach that starts from a tooling perspective.
> Replace Existing XML Document Functionality with other JBoss Technologies
> -------------------------------------------------------------------------
>
> Key: TEIIDDES-2046
> URL: https://issues.jboss.org/browse/TEIIDDES-2046
> Project: Teiid Designer
> Issue Type: Task
> Affects Versions: 7.0
> Reporter: Ted Jones
> Assignee: Steven Hawkins
>
> The current XML Document homegrown technologies in the Teiid Designer with existing JBoss technologies. The following use cases should be satisfied:
> 1. Start with an XML Schema to build a Document that can be filled with relational, heterogeneous data and "shipped around"
> 2. Given an XML document/message definition, submit a query on the document with criteria defined within the document structure
> 3. Send an input document, produce and output document
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIIDDES-2046) Replace Existing XML Document Functionality with other JBoss Technologies
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2046?page=com.atlassian.jira.plu... ]
Steven Hawkins moved TEIID-1035 to TEIIDDES-2046:
-------------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-2046 (was: TEIID-1035)
Affects Version/s: 7.0
(was: 7.0)
> Replace Existing XML Document Functionality with other JBoss Technologies
> -------------------------------------------------------------------------
>
> Key: TEIIDDES-2046
> URL: https://issues.jboss.org/browse/TEIIDDES-2046
> Project: Teiid Designer
> Issue Type: Task
> Affects Versions: 7.0
> Reporter: Ted Jones
> Assignee: Steven Hawkins
>
> The current XML Document homegrown technologies in the Teiid Designer with existing JBoss technologies. The following use cases should be satisfied:
> 1. Start with an XML Schema to build a Document that can be filled with relational, heterogeneous data and "shipped around"
> 2. Given an XML document/message definition, submit a query on the document with criteria defined within the document structure
> 3. Send an input document, produce and output document
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIIDDES-2014) 8.4 Release Work
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2014?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2014 at 2/10/14 4:23 PM:
-----------------------------------------------------------------
New Features:
TEIIDDES-1863 - native type property to procedure *OUT* parameters
TEIIDDES-1794 - ability to define virtual table as *global temporary table*
was (Author: blafond):
New Features:
TEIIDDES-1863
TEIIDDES-1794
> 8.4 Release Work
> ----------------
>
> Key: TEIIDDES-2014
> URL: https://issues.jboss.org/browse/TEIIDDES-2014
> Project: Teiid Designer
> Issue Type: Task
> Components: Release Work
> Affects Versions: 8.4
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.4
>
>
> Work related to 8.4.0 release including:
> * Version upgrades
> * Copyright changes
> * build/publish
> * documentation
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIIDDES-1794) Designer support for global temporary tables
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1794?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1794:
----------------------------------------
Code I'm committing includes
* a check-box in the New Virtual Table wizard for "Is Global Temporary Table"
* boolean extension property named "Global Temp Table" enabled for only virtual tables
* Turned SQL validation OFF for any virtual table where Global Temp Table == TRUE
The concepts you described above are pretty abstract from Designer's standpoint. We'll need them to be fleshed out in how they would be exposed to the user and what structural (EMF/ext. props) would have to be made to accomodate them.
> Designer support for global temporary tables
> --------------------------------------------
>
> Key: TEIIDDES-1794
> URL: https://issues.jboss.org/browse/TEIIDDES-1794
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Reporter: Mark Addleman
> Assignee: Barry LaFond
> Fix For: 8.4
>
>
> Teiid has added support for a global temporary tables - they share a common definition, but each session has their own instance. Internally this is modeled as a virtual table (without a transformation) with a table type of "TemporaryTable" (int code 6). If you provided matching index metadata we would recognize the entry as a global temporary table.
> Alternatively extension metadata could be used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIIDDES-1794) Designer support for global temporary tables
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1794?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-1794:
------------------------------------------
Ramesh is correct. You can just allow them on a virtual model and that will be sufficient.
Not to confuse things, but the full array of temp table stuff we currently support is:
Teiid global temporary table (a virtual entry - which from an engine perspective can be on any model type)
Teiid temporary table (not a schema entry in the design time metadata, scoped to a session/block)
Teiid temporary table backed by a physical table (not a schema entry in the design time metadata, scoped to a session/block - the physical table could be a temporary one)
Eventually we would also like to have an ease of use path to simply create a teiid temporary table and have the backing table created on a source automatically - similar to the data shipment join temporary table creation.
> Designer support for global temporary tables
> --------------------------------------------
>
> Key: TEIIDDES-1794
> URL: https://issues.jboss.org/browse/TEIIDDES-1794
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Reporter: Mark Addleman
> Assignee: Barry LaFond
> Fix For: 8.4
>
>
> Teiid has added support for a global temporary tables - they share a common definition, but each session has their own instance. Internally this is modeled as a virtual table (without a transformation) with a table type of "TemporaryTable" (int code 6). If you provided matching index metadata we would recognize the entry as a global temporary table.
> Alternatively extension metadata could be used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIIDDES-1863) Add native type to procedure parameters
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1863?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-1863:
------------------------------------------
Any string is currently valid for a column/parameter native type.
> Add native type to procedure parameters
> ---------------------------------------
>
> Key: TEIIDDES-1863
> URL: https://issues.jboss.org/browse/TEIIDDES-1863
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling, Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Fix For: 8.4
>
>
> TEIID-2644 adds out parameter cursor handling for oracle, and adds a native type property to procedure parameters (just like regular columns). That is not currently in the index metadata. This value would need to be captured on import and either a new index version used, or an extension property (with additional Teiid handling), or the vdb.xml can use alter statements to add an option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months