April 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2941) Add documentation that explains expected usage patterns

by Van Halbert (JIRA)

Van Halbert created TEIID-2941: ---------------------------------- Summary: Add documentation that explains expected usage patterns Key: TEIID-2941 URL: https://issues.jboss.org/browse/TEIID-2941 Project: Teiid Issue Type: Enhancement Components: Documentation Reporter: Van Halbert Assignee: Steven Hawkins Priority: Optional Would like to see documentation added to explains certain data source usage patterns for which cannot be explained just by using the data source. Example is: How to access a JSON REST service: You read JSON using file or web service translator, then use the JSONToXML function, to convert to XML, then use the XMLTABLE function to parse. This isn't straight forward in the documentation to a novice. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2940) SQL naming issue with several layers of inline views

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2940?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2940: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1092590 > SQL naming issue with several layers of inline views > ---------------------------------------------------- > > Key: TEIID-2940 > URL: https://issues.jboss.org/browse/TEIID-2940 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > Several layers of inline views in a source query can cause the alias generation logic to use improper names for higher level symbols resulting in invalid source sql. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2940) SQL naming issue with several layers of inline views

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2940: ------------------------------------- Summary: SQL naming issue with several layers of inline views Key: TEIID-2940 URL: https://issues.jboss.org/browse/TEIID-2940 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.8 Several layers of inline views in a source query can cause the alias generation logic to use improper names for higher level symbols resulting in invalid source sql. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2855) adding possibility to proxy URI in odata server

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2855?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2855: ------------------------------------- The URI "http://serverURI/VDBname" can be anything, however the "Table" is the part of the OData Spec, that can not be changed. Even the "http://serverURI/VDBname" can not be changed as it is part of the web context that OData servlet configured with and designed to work with all the VDBs in the system. What you try is some kind of HTTP proxy server with rewriting rules, that map between what you want to physical URL. > adding possibility to proxy URI in odata server > ----------------------------------------------- > > Key: TEIID-2855 > URL: https://issues.jboss.org/browse/TEIID-2855 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.6 > Reporter: luca gioppo > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.7 > > > As for https://community.jboss.org/thread/237239 there is the need to proxy the URI exposed by the odata server when this is behind a proxy and we do not want the URi to disclose and invalidate the reference. > The odata server should have some parameters gotten from deployment for proxy hostname and port and path up to the VDB name -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2855) adding possibility to proxy URI in odata server

by luca gioppo (JIRA)

[ https://issues.jboss.org/browse/TEIID-2855?page=com.atlassian.jira.plugin... ] luca gioppo commented on TEIID-2855: ------------------------------------ Could it be possible to also have the possibility to proxy-path-uri at VDB level. Right now it exposes the VDBname/tableName and thuis could be not nice for API publishing. It could be nice to have a way to proxy also the path so that we can have: http://proxy-base-uri/proxy-path-uri instead of http://serverURI/VDBname/Table It could be a property of the table like "oData-proxy-name" > adding possibility to proxy URI in odata server > ----------------------------------------------- > > Key: TEIID-2855 > URL: https://issues.jboss.org/browse/TEIID-2855 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.6 > Reporter: luca gioppo > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.7 > > > As for https://community.jboss.org/thread/237239 there is the need to proxy the URI exposed by the odata server when this is behind a proxy and we do not want the URi to disclose and invalidate the reference. > The odata server should have some parameters gotten from deployment for proxy hostname and port and path up to the VDB name -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2938) Provide ability to write command and audit logging to database

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2938?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-2938: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Provide ability to write command and audit logging to database > -------------------------------------------------------------- > > Key: TEIID-2938 > URL: https://issues.jboss.org/browse/TEIID-2938 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Ramesh Reddy > > Provide ability for command logging and audit logging to write to the database. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2938) Provide ability to write command and audit logging to database

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2938?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2938: ------------------------------------ That was my understanding. > Provide ability to write command and audit logging to database > -------------------------------------------------------------- > > Key: TEIID-2938 > URL: https://issues.jboss.org/browse/TEIID-2938 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Provide ability for command logging and audit logging to write to the database. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2938) Provide ability to write command and audit logging to database

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2938?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-2938 at 4/28/14 3:36 PM: ------------------------------------------------------------- Yes, that was my understanding. was (Author: van.halbert): That was my understanding. > Provide ability to write command and audit logging to database > -------------------------------------------------------------- > > Key: TEIID-2938 > URL: https://issues.jboss.org/browse/TEIID-2938 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Provide ability for command logging and audit logging to write to the database. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2939) Issues with applying row based security

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2939?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2939: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1092133 > Issues with applying row based security > --------------------------------------- > > Key: TEIID-2939 > URL: https://issues.jboss.org/browse/TEIID-2939 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > If a view over a left outer join has a row condition and is used in a simple aggregation: > select count\(*) from vw > Then a null pointer exception will occur when considering optional joins. > If intervening criteria is added: > select count\(*) from vw where ... > we can get past the initial error, but will fail in initializing the join node with an assertion error. Both of these have the same root issue, which is our attempt to make the logic selective about when assign output elements is run, which leads to the output elements not being in place when later needed. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2938) Provide ability to write command and audit logging to database

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2938?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2938: --------------------------------------- Was this intended for 8.7.1? > Provide ability to write command and audit logging to database > -------------------------------------------------------------- > > Key: TEIID-2938 > URL: https://issues.jboss.org/browse/TEIID-2938 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Provide ability for command logging and audit logging to write to the database. -- 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

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2014