October 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2715) Created and registered MXD, extra metadata is not visible when queried.

by Alex Khvatov (JIRA)

[ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin... ] Alex Khvatov commented on TEIID-2715: ------------------------------------- I did. The properties show up in table editor (base tables) as well as in the Properties window in Teiid Designer. I supplied all the required values and deployed the database. But when I navigate to : http://localhost:8080/odata/MCR_VDB/Tables(Name='ENTITY',SchemaName='MCR_ENTITY',VDBName='MCR_VDB')?$format=json only built-in properties show up. > Created and registered MXD, extra metadata is not visible when queried. > ----------------------------------------------------------------------- > > Key: TEIID-2715 > URL: https://issues.jboss.org/browse/TEIID-2715 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.6 > Environment: Windows 7 > Reporter: Alex Khvatov > Assignee: Steven Hawkins > > x`Hi, > I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: > http://localhost:8080/odata/MCR_VDB/Tables?$format=json > http://localhost:8080/odata/MCR_VDB/Columns?$format=json > Both documents returned did not contain any extra metadata I defined. > HELP! > Thanks. > Alex -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2717) Issues with unrelated sort over a union

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2717?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2717. ----------------------------------- Resolution: Done Corrected the planning error by always ensuring that an expression symbol is used in the order by item when needed. Also updated rule plan sorts to look for the simplistic case where the dup removal of the union can be combined with the sort above. > Issues with unrelated sort over a union > --------------------------------------- > > Key: TEIID-2717 > URL: https://issues.jboss.org/browse/TEIID-2717 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > Related to https://community.jboss.org/thread/233978 a query such as: > select e1 || 'a' from (select e1, e2 from pm1.g1 union select e1, e2 from pm1.g2) as x order by e2 || 'b' > will fail to plan and throw TEIID30259. The issue is that the unrelated sort item should still be an expression symbol, otherwise the assign output logic assumes that it is a must pushdown function. > Also the simpler form without an unrelated expression: > select e1 || 'a' from (select e1, e2 from pm1.g1 union select e1, e2 from pm1.g2) as x order by e2 > can have the dup remove and the sort operations combined. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2696) Update Teiid datasource examples to be fully parameterized

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2696?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2696: --------------------------------------- The latest changes were put into 8.6 and 8.4.1 > Update Teiid datasource examples to be fully parameterized > ---------------------------------------------------------- > > Key: TEIID-2696 > URL: https://issues.jboss.org/browse/TEIID-2696 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 8.4.1, 8.6 > > > Change the example datasources to be parameterized, and add an associated properties file so that to install, run: > jboss-cli.sh -c --file={datasource}-ds.cli --properties=/{datasource}-ds.properties -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2717) Issues with unrelated sort over a union

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2717: ------------------------------------- Summary: Issues with unrelated sort over a union Key: TEIID-2717 URL: https://issues.jboss.org/browse/TEIID-2717 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.6 Related to https://community.jboss.org/thread/233978 a query such as: select e1 || 'a' from (select e1, e2 from pm1.g1 union select e1, e2 from pm1.g2) as x order by e2 || 'b' will fail to plan and throw TEIID30259. The issue is that the unrelated sort item should still be an expression symbol, otherwise the assign output logic assumes that it is a must pushdown function. Also the simpler form without an unrelated expression: select e1 || 'a' from (select e1, e2 from pm1.g1 union select e1, e2 from pm1.g2) as x order by e2 can have the dup remove and the sort operations combined. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2715) Created and registered MXD, extra metadata is not visible when queried.

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2715: ------------------------------------- Alex: 1) What is that Designer complains (please explain in forum thread, or if it is bug, open Designer JIRA) 2) Did you apply the MXD to a *source* model? 3) Once applied, then have you supplied the values for those properties in your model > Created and registered MXD, extra metadata is not visible when queried. > ----------------------------------------------------------------------- > > Key: TEIID-2715 > URL: https://issues.jboss.org/browse/TEIID-2715 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.6 > Environment: Windows 7 > Reporter: Alex Khvatov > Assignee: Steven Hawkins > > x`Hi, > I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: > http://localhost:8080/odata/MCR_VDB/Tables?$format=json > http://localhost:8080/odata/MCR_VDB/Columns?$format=json > Both documents returned did not contain any extra metadata I defined. > HELP! > Thanks. > Alex -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2716) Add Insert/update/Delete capabilities to Cassandra translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2716?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2716. --------------------------------- Labels: Beta1 (was: ) Assignee: Ramesh Reddy (was: Steven Hawkins) Resolution: Done 1) Added code to support update operations on Cassendra translator 2) Removed "select *" representation from SQL string, as this will generate results out of order than expected by the engine 3) Cassendra does not support criteria to pushed on non-index columns, updated the metadata as such to non-searchable 4) Added exception handling during query execution, instead of bubling it up > Add Insert/update/Delete capabilities to Cassandra translator > ------------------------------------------------------------- > > Key: TEIID-2716 > URL: https://issues.jboss.org/browse/TEIID-2716 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.6 > > > - Provide capability to INSERT/UPDATE/DELETE > - I also find some minor issues with search columns, as Cassandra only allows criteria on the index columns -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2716) Add Insert/update/Delete capabilities to Cassandra translator

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2716: ----------------------------------- Summary: Add Insert/update/Delete capabilities to Cassandra translator Key: TEIID-2716 URL: https://issues.jboss.org/browse/TEIID-2716 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 8.6 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 8.6 - Provide capability to INSERT/UPDATE/DELETE - I also find some minor issues with search columns, as Cassandra only allows criteria on the index columns -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2704) DB2 lob values must be read inline

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2704?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2704: --------------------------------------- Addressed in master/8.6 by moving the type handling logic from datatiertuple source into the ConnectorWorkItem - this allows copyLobs to work on a row by row basis. So in 8.6 with copyLobs enabled, DB2 will work as expected with respect to lobs. This change though is broader than I would like and doesn't seem well suited for backport. At least for 7.7.9 the fix will just be to read all db2 lob values in a non-memory safe way as strings and byte arrays. > DB2 lob values must be read inline > ---------------------------------- > > Key: TEIID-2704 > URL: https://issues.jboss.org/browse/TEIID-2704 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.6, 7.7.9 > > > With the DB2 9 driver and selecting a lob column, the resulting instance becomes invalid after the next row of the result is transitioned to. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2715) Created and registered MXD, extra metadata is not visible when queried.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2715: ---------------------------------- Description: x`Hi, I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: http://localhost:8080/odata/MCR_VDB/Tables?$format=json http://localhost:8080/odata/MCR_VDB/Columns?$format=json Both documents returned did not contain any extra metadata I defined. HELP! Thanks. Alex was: Hi, I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: http://localhost:8080/odata/MCR_VDB/Tables?$format=json http://localhost:8080/odata/MCR_VDB/Columns?$format=json Both documents returned did not contain any extra metadata I defined. HELP! Thanks. Alex > Created and registered MXD, extra metadata is not visible when queried. > ----------------------------------------------------------------------- > > Key: TEIID-2715 > URL: https://issues.jboss.org/browse/TEIID-2715 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.6 > Environment: Windows 7 > Reporter: Alex Khvatov > Assignee: Steven Hawkins > > x`Hi, > I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: > http://localhost:8080/odata/MCR_VDB/Tables?$format=json > http://localhost:8080/odata/MCR_VDB/Columns?$format=json > Both documents returned did not contain any extra metadata I defined. > HELP! > Thanks. > Alex -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2704) DB2 lob values must be read inline

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2704?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2704: --------------------------------- Fix Version/s: 7.7.9 > DB2 lob values must be read inline > ---------------------------------- > > Key: TEIID-2704 > URL: https://issues.jboss.org/browse/TEIID-2704 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.6, 7.7.9 > > > With the DB2 9 driver and selecting a lob column, the resulting instance becomes invalid after the next row of the result is transitioned to. -- 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

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2013