May 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2972) adminApi getSchema does not include namespace info in the DDL

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-2972?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIID-2972: ------------------------------------- Note that we're playing both sides of the house here with extension properties. We're dynamically building them from the Translator properties. These properties include the NS/URI in the name. In the DDL Importer, however, the DDL OPTIONS utilize the alias, so for Designer to work seamlessly, we need the SET NAMESPACE in the DDL. > adminApi getSchema does not include namespace info in the DDL > ------------------------------------------------------------- > > Key: TEIID-2972 > URL: https://issues.jboss.org/browse/TEIID-2972 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Attachments: excelSheet.ddl > > > I was following this community example > https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable > The DDL returned for the deployed dynamic vdb is attached. However, the DDL does not include a namespace statement like this > SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 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 updated TEIID-2666: ---------------------------------- Parent: TEIID-2973 Issue Type: Sub-task (was: Feature Request) > Extend OData output formats, currently JSON and XML supported > ------------------------------------------------------------- > > Key: TEIID-2666 > URL: https://issues.jboss.org/browse/TEIID-2666 > Project: Teiid > Issue Type: Sub-task > 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)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2973) Switch OData support to Olingo

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2973: ------------------------------------- Summary: Switch OData support to Olingo Key: TEIID-2973 URL: https://issues.jboss.org/browse/TEIID-2973 Project: Teiid Issue Type: Task Components: Misc. Connectors, OData Reporter: Steven Hawkins Fix For: 8.9 Whenever an olingo final is available for odata 3/4 we'll want to switch our support to utilize that. The best guess now is that this will happen in the 8.9 timeframe. Additional support can then be added for later odata features, which will have subtasks as necessary. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2972) adminApi getSchema does not include namespace info in the DDL

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2972?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2972: --------------------------------------- As long as we don't make it required to redclare the built-in ones, it seems fine by me. > worse the URI are being defined in-correctly I won't pretend to know what Designer is doing, but if they simply don't alter the literal form of the DDL in terms of the option property names it would still work on the server side. If at some point we could just allow for name value pairs for extension metadata again without all the management layers that would a welcomed simplification. > adminApi getSchema does not include namespace info in the DDL > ------------------------------------------------------------- > > Key: TEIID-2972 > URL: https://issues.jboss.org/browse/TEIID-2972 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Attachments: excelSheet.ddl > > > I was following this community example > https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable > The DDL returned for the deployed dynamic vdb is attached. However, the DDL does not include a namespace statement like this > SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2972) adminApi getSchema does not include namespace info in the DDL

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2972?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2972: ------------------------------------- I think we need to do this, otherwise as we seen we always playing catch up with Designer as built-in names never matching up, worse the URI are being defined in-correctly. > adminApi getSchema does not include namespace info in the DDL > ------------------------------------------------------------- > > Key: TEIID-2972 > URL: https://issues.jboss.org/browse/TEIID-2972 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Attachments: excelSheet.ddl > > > I was following this community example > https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable > The DDL returned for the deployed dynamic vdb is attached. However, the DDL does not include a namespace statement like this > SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2972) adminApi getSchema does not include namespace info in the DDL

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2972?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2972: --------------------------------------- This is always the way it has been for "built-in" namespaces, which are defined in the MetadataFactory. I don't think Designer has been kept aware as new ones have been added though. Non-built-in namespaces are declared in the ddl. We can of course start including the built-in namespaces as declarations, but we'll have to change our parsing validation logic as it would current through an error that the ddl is attempting to redefine a reserved namespace. > adminApi getSchema does not include namespace info in the DDL > ------------------------------------------------------------- > > Key: TEIID-2972 > URL: https://issues.jboss.org/browse/TEIID-2972 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Attachments: excelSheet.ddl > > > I was following this community example > https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable > The DDL returned for the deployed dynamic vdb is attached. However, the DDL does not include a namespace statement like this > SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2972) adminApi getSchema does not include namespace info in the DDL

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIID-2972?page=com.atlassian.jira.plugin... ] Mark Drilling updated TEIID-2972: --------------------------------- Attachment: excelSheet.ddl > adminApi getSchema does not include namespace info in the DDL > ------------------------------------------------------------- > > Key: TEIID-2972 > URL: https://issues.jboss.org/browse/TEIID-2972 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Attachments: excelSheet.ddl > > > I was following this community example > https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable > The DDL returned for the deployed dynamic vdb is attached. However, the DDL does not include a namespace statement like this > SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2972) adminApi getSchema does not include namespace info in the DDL

by Mark Drilling (JIRA)

Mark Drilling created TEIID-2972: ------------------------------------ Summary: adminApi getSchema does not include namespace info in the DDL Key: TEIID-2972 URL: https://issues.jboss.org/browse/TEIID-2972 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 8.7 Reporter: Mark Drilling Assignee: Ramesh Reddy I was following this community example https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable The DDL returned for the deployed dynamic vdb is attached. However, the DDL does not include a namespace statement like this SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2964) User can not use '.' for VDB name in order to version the VDB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2964?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2964. ----------------------------------- Resolution: Done Added back logic to look at the deployment name to determine if name based version is used. > User can not use '.' for VDB name in order to version the VDB > ------------------------------------------------------------- > > Key: TEIID-2964 > URL: https://issues.jboss.org/browse/TEIID-2964 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Reporter: Van Halbert > Priority: Critical > Fix For: 8.7.1, 8.8 > > > User can not use '.' for VDB name. > According to the Official document[1], user should be able to use '.' to specify the version for VDB. > [1]Administration_and_Configuration_Guide:11.2. Set the VDB Version > https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Data_Vir... > Version-Release number of selected component (if applicable): > Steps to Reproduce: > 1. Create a new VDB named "test1.1" > Actual results: > The version attribute from the vdb.xml is used instead. > Expected results: > User can use '.' for VDB name. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2930) SCROLL keyword for DECLARE CURSOR not being parsed correctly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2930?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2930. ----------------------------------- Resolution: Done Added back with(out) hold parsing. > SCROLL keyword for DECLARE CURSOR not being parsed correctly > ------------------------------------------------------------ > > Key: TEIID-2930 > URL: https://issues.jboss.org/browse/TEIID-2930 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.7.8 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 7.7.9, 8.7.1, 8.8 > > > The DECLARE cursor is defined as [1]. However, in [2] line #155, the SCROLL keyword is not being matched. Correction would be to match the pattern fully as defined in [1] > [1] > http://www.postgresql.org/docs/8.4/static/sql-declare.html > [2] > https://github.com/teiid/teiid/blob/master/runtime/src/main/java/org/teii... > Example of error: > TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking server method: executeQuery [BEGIN;declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY>;fetch 100 in "SQL_CUR0x11ad4120"] > DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: START TRANSACTION > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [START TRANSACTION] expecting: EITHER > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as transaction statement > TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: sendUpdateCount [BEGIN, 0] > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [show client_encoding] expecting: RESULTSET > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as show statement > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Creating ResultSet requestID: -1 beginRow: 1 resultsColumns: 1 parameters: 0 > TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: setEncoding [UTF-8] > FINE [org.teiid.jdbc] (New I/O server worker #3-1) Statement closed successfully. > DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY> -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2014