[JBoss JIRA] (TEIID-3036) Update CXF to current version (3.0.0)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3036?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3036:
----------------------------------
Assignee: (was: Steven Hawkins)
> Update CXF to current version (3.0.0)
> -------------------------------------
>
> Key: TEIID-3036
> URL: https://issues.jboss.org/browse/TEIID-3036
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded
> Affects Versions: 8.8
> Reporter: Gary Gregory
>
> In the same vein as TEIID-3030, we embed CXF and Teiid in our server. We use CXF 2.7.10 and are about to update to 3.0.0. At worse, we'll go to 2.7.11 as an interim step to 3.0.0.
> Teiid embedded delivers CXF 2.6.6 for web services support.
> It would be great if we could get Teiid to the latest and greatest from CXF so we can all live in the same space without being forced to deal with any incompatibilities or class loader hacks.
> Thank you,
> Gary
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIID-784) Enhance distinct set op processing
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-784?page=com.atlassian.jira.plugin.... ]
Steven Hawkins updated TEIID-784:
---------------------------------
Assignee: (was: Steven Hawkins)
> Enhance distinct set op processing
> ----------------------------------
>
> Key: TEIID-784
> URL: https://issues.jboss.org/browse/TEIID-784
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Steven Hawkins
> Priority: Minor
> Fix For: 9.0
>
>
> The sort operation should be able to pushed for each set op child (distinct is already eligible for pushing, but typically won't be because there's no order by). Also for union the sorted children should be fed directly into the second phase of sorting.
> All of this relies on the connector guaranteeing null ordering (TEIID-715 should be repurposed to cover the language enhancement of nulls first|last)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIID-1248) Clob usability
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1248?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-1248:
----------------------------------
Assignee: (was: Steven Hawkins)
> Clob usability
> --------------
>
> Key: TEIID-1248
> URL: https://issues.jboss.org/browse/TEIID-1248
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 8.0
> Reporter: Steven Hawkins
> Priority: Minor
>
> In many circumstances, clobs should be treated as charsequences to allow for use in string functions (concat returning clob, insert, left, etc.).
> There have also been customer requests to treat clobs as comparable, but that there are a lot of places including at design time where we validate against clobs being comparable that it may not be a good idea.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIID-2123) Per model getMetadata() timeout
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2123?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2123:
----------------------------------
Assignee: (was: Steven Hawkins)
> Per model getMetadata() timeout
> -------------------------------
>
> Key: TEIID-2123
> URL: https://issues.jboss.org/browse/TEIID-2123
> Project: Teiid
> Issue Type: Feature Request
> Affects Versions: 8.0
> Reporter: Mark Addleman
> Priority: Minor
>
> A way of specifying, per model, a timeout for the getMetadata() call. The timeout should be processed in such a way that delegating translators have an opportunity to intercept the interruption and, potentially, supply default metadata. I think the normal Thread.interrupt() approach should work.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months