May 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2481) common table (with) push down improvements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2481?page=com.atlassian.jira.plugin... ] Work on TEIID-2481 started by Steven Hawkins. > common table (with) push down improvements > ------------------------------------------ > > Key: TEIID-2481 > URL: https://issues.jboss.org/browse/TEIID-2481 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.8 > > > The general strategy for with pushdown should better handle: > - a with clause that can be pushed against a source that does not support common table. If a single reference or some other sufficient condition is met then we should just inline the pushdown rather than inhibiting the whole query from pushing down. > - even if a source supports with pushdown, it may be more performant in some circumstances to inline the common table reference (such as only a single reference). This is complicated slightly by subqueries. > - alternatively in some situations even if a with clause can be pushed, it may be better to not perform the pushdown -e.g. two separate pushdown accesses to a common table that is expensive to compute (this may need to be hint driven). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2782) add another log context VDBLifeCycleListener

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2782?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2782. ----------------------------------- Resolution: Done Now we'll consistently log all lifecycle events to org.teiid.RUNTIME.VDBLifeCycleListener at an info level > add another log context VDBLifeCycleListener > -------------------------------------------- > > Key: TEIID-2782 > URL: https://issues.jboss.org/browse/TEIID-2782 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: luca gioppo > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.8 > > > It would be nice to have a logging context / logs for the lifecycle events of a VDB -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2782) add another log context VDBLifeCycleListener

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2782?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2782: --------------------------------------- I should have looked at this a little more... The EventListener that can be registered via the EventDistibutor already exposes all of the vdb events except for beforeRemove. So for now we'll just add/consolidate logging. > add another log context VDBLifeCycleListener > -------------------------------------------- > > Key: TEIID-2782 > URL: https://issues.jboss.org/browse/TEIID-2782 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: luca gioppo > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.8 > > > It would be nice to have a logging context / logs for the lifecycle events of a VDB -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2782) add another log context VDBLifeCycleListener

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2782?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-2782: ------------------------------------- Assignee: Steven Hawkins I'll have a look to see if it makes sense to pursue being able to register listeners. > add another log context VDBLifeCycleListener > -------------------------------------------- > > Key: TEIID-2782 > URL: https://issues.jboss.org/browse/TEIID-2782 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: luca gioppo > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.8 > > > It would be nice to have a logging context / logs for the lifecycle events of a VDB -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2666) Extend OData output formats, currently JSON and XML supported

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2666?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2666: --------------------------------------- Just in case you want to pursue this work on your own in the mean time, you would look at patching classes such as JSONFeedFormatWriter and JSONFormatWriter under http://code.google.com/p/odata4j/source/browse/odata4j-core/src/main/java... You can see there where the format is hardcoded to show the metadata, use the name "results", etc. > Extend OData output formats, currently JSON and XML supported > ------------------------------------------------------------- > > Key: TEIID-2666 > URL: https://issues.jboss.org/browse/TEIID-2666 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.4 > Environment: N/A > Reporter: Cojan van Ballegooijen > Priority: Trivial > > We would like to see the available output formats of the OData services be extended with CSV (Command Seperated Values) upon customer request. > It would be great if we could extend it ourselves using for example XSLT or other transformation mechanism. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2666) Extend OData output formats, currently JSON and XML supported

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2666?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2666: ------------------------------------- OData query always works in the context of a given entity, that may be reason there is no reason to qualify it, or look at metadata > Extend OData output formats, currently JSON and XML supported > ------------------------------------------------------------- > > Key: TEIID-2666 > URL: https://issues.jboss.org/browse/TEIID-2666 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.4 > Environment: N/A > Reporter: Cojan van Ballegooijen > Priority: Trivial > > We would like to see the available output formats of the OData services be extended with CSV (Command Seperated Values) upon customer request. > It would be great if we could extend it ourselves using for example XSLT or other transformation mechanism. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2666) Extend OData output formats, currently JSON and XML supported

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2666?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2666: --------------------------------------- No I don't think there is a JIRA yet and I'm not entirely sure what the timeline looks like. You can go ahead and create a placeholder issue for this effort if you want. Ted Jones is one of our team members who is now a committer for olingo so we should have more responsiveness from that project. > Extend OData output formats, currently JSON and XML supported > ------------------------------------------------------------- > > Key: TEIID-2666 > URL: https://issues.jboss.org/browse/TEIID-2666 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.4 > Environment: N/A > Reporter: Cojan van Ballegooijen > Priority: Trivial > > We would like to see the available output formats of the OData services be extended with CSV (Command Seperated Values) upon customer request. > It would be great if we could extend it ourselves using for example XSLT or other transformation mechanism. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2666) Extend OData output formats, currently JSON and XML supported

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIID-2666?page=com.atlassian.jira.plugin... ] Ted Jones commented on TEIID-2666: ---------------------------------- John, it sounds like what you are describing is covered by the OData v4 JSON format: http://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-for... > Extend OData output formats, currently JSON and XML supported > ------------------------------------------------------------- > > Key: TEIID-2666 > URL: https://issues.jboss.org/browse/TEIID-2666 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.4 > Environment: N/A > Reporter: Cojan van Ballegooijen > Priority: Trivial > > We would like to see the available output formats of the OData services be extended with CSV (Command Seperated Values) upon customer request. > It would be great if we could extend it ourselves using for example XSLT or other transformation mechanism. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2666) Extend OData output formats, currently JSON and XML supported

by John Muller (JIRA)

[ https://issues.jboss.org/browse/TEIID-2666?page=com.atlassian.jira.plugin... ] John Muller commented on TEIID-2666: ------------------------------------ Thanks Steven, I wasn't aware of the move to Apache Olingo, but we'd really look forward to OData V4 aggregate support down the road. You have our use case exact: mobile apps consuming OData endpoints want a "clean" JSON object (single row) or array (multiple rows) with the entity name set to be the collection name and no metadata aside from the "nextLink" Is there a JIRA feature request out for Olingo, or is that driven internally? > Extend OData output formats, currently JSON and XML supported > ------------------------------------------------------------- > > Key: TEIID-2666 > URL: https://issues.jboss.org/browse/TEIID-2666 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.4 > Environment: N/A > Reporter: Cojan van Ballegooijen > Priority: Trivial > > We would like to see the available output formats of the OData services be extended with CSV (Command Seperated Values) upon customer request. > It would be great if we could extend it ourselves using for example XSLT or other transformation mechanism. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2263) makedep makenotdep hints should allow for more complicated scenarios

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2263?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2263. ----------------------------------- Resolution: Done Implemented the view handling when the hint target starts with \@ There are a couple of corner case issues here, such as a potential conflict with hints that target tables starting with \@ and the hint can only match short names. However neither of these seem like too great of issues. Logic to handle subqueries and unions will need to be added at some point, but the logic (and possibly all hints handling) will need to be moved to run prior to rewriting the query as it's possible for subqueries and even union branches to to be removed at that point. Alternatively we'd have to look at numbering or otherwise identifying query parts as part of resolving to be available for hint application. > makedep makenotdep hints should allow for more complicated scenarios > -------------------------------------------------------------------- > > Key: TEIID-2263 > URL: https://issues.jboss.org/browse/TEIID-2263 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.8 > > Attachments: dep.patch > > > In the option clause makedep and makenotdep take what are typically fully-qualified names and mark all matching tables/views in the query. This is not generally a good idea. We should allow for something akin to oracle global table syntax (view.)*table to drill down more specifically. Ideally we'd also account for subqueries and set operations as well. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2014