November 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Closed: (TEIID-1300) EDS adminshell - getSessions() - each session object returned always shows a VDB of null

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1300?page=com.atlassian.jira.plugin.s... ] Steven Hawkins closed TEIID-1300. --------------------------------- > EDS adminshell - getSessions() - each session object returned always shows a VDB of null > ---------------------------------------------------------------------------------------- > > Key: TEIID-1300 > URL: https://jira.jboss.org/browse/TEIID-1300 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 7.1 > Reporter: Len DiMaggio > > With these VDBs deployed > [Interoperability.1[TextFileData[text-connector/file/java:TextFileDS]], weather.1[Weather[Weather/MessageWeather/java:WeatherDS]], ModeShape.1[ModeShapeFunctions[], ModeShape[ModeShape/modeshape/ModeShapeDS]]] > And these in use: Interoperability, weather > Every session created shows a VDB of null: > [session: sessionid=pC2AQPpaMZr3; userName=admin@jmx-console; vdbName=null; vdbVersion=0; createdTime=Thu Oct 07 22:52:13 EDT 2010; applicationName=null; clientHostName=localhost.localdomain; IPAddress=127.0.0.1; securityDomain=jmx-console; lastPingTime=Thu Oct 07 22:52:53 EDT 2010, session: sessionid=1oGdlWx+B3Te; userName=admin@jmx-console; vdbName=null; vdbVersion=0; createdTime=Thu Oct 07 21:38:34 EDT 2010; applicationName=null; clientHostName=localhost.localdomain; IPAddress=127.0.0.1; securityDomain=jmx-console; lastPingTime=Thu Oct 07 22:51:30 EDT 2010, session: sessionid=TA2+3kyQ1Wff; userName=admin@jmx-console; vdbName=null; vdbVersion=0; createdTime=Thu Oct 07 21:38:04 EDT 2010; applicationName=null; clientHostName=localhost.localdomain; IPAddress=127.0.0.1; securityDomain=jmx-console; lastPingTime=Thu Oct 07 22:51:04 EDT 2010, session: sessionid=dEl7em6K6o0u; userName=admin@jmx-console; vdbName=null; vdbVersion=0; createdTime=Thu Oct 07 21:17:04 EDT 2010; applicationName=null; clientHostName=localhost.localdomain; IPAddress=127.0.0.1; securityDomain=jmx-console; lastPingTime=Thu Oct 07 22:51:04 EDT 2010, session: sessionid=SDyHIyvSgVUg; userName=admin@teiid-security; vdbName=Interoperability; vdbVersion=1; createdTime=Thu Oct 07 22:52:48 EDT 2010; applicationName=null; clientHostName=localhost.localdomain; IPAddress=127.0.0.1; securityDomain=teiid-security; lastPingTime=Thu Oct 07 22:52:48 EDT 2010, session: sessionid=Sc8tMciQJfbP; userName=admin@teiid-security; vdbName=Interoperability; vdbVersion=2; createdTime=Thu Oct 07 22:52:50 EDT 2010; applicationName=null; clientHostName=localhost.localdomain; IPAddress=127.0.0.1; securityDomain=teiid-security; lastPingTime=Thu Oct 07 22:52:50 EDT 2010] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1285) fixes from Data Services Platform version of the Teiid Developer Guide

by Darrin Mison (JIRA)

fixes from Data Services Platform version of the Teiid Developer Guide ---------------------------------------------------------------------- Key: TEIID-1285 URL: https://jira.jboss.org/browse/TEIID-1285 Project: Teiid Issue Type: Patch Components: Documentation Affects Versions: 7.1 Reporter: Darrin Mison Assignee: Steven Hawkins Attachments: EDS.patch Attached is the patch for the changes made downstream in the Data Services Platform version of this doc. Some of the changes are for compatibility with the docbook tool Publican, some are fixes, some are best practices changes. 1 - separated main.xml into Developer_Guide.xml & Book_Info.xml (main.xml removed) updated pom.xml. This is for better compatibility with Publican. Publican also expects a Developer_Guide.ent file with all the entities defined in it but this is impractical to do with yours since you have a shared entities file. 2 - moved a number of <programlisting> from inside <para>s. Having non-translatable block elements inside of translatable block elements (programlisting inside para) creates issues for translators. Best practice. 3 - reformatted a few <programlistings> for better presentation. Mainly made the alignment consistent & ensured they fit on one page without scrolling, very important for PDF output. 3- changed a number of usages of <link> to <xref> also changed them to show the target title instead of the specified text. ie. changed <link linkend="target">info here</link> to <link linkend="target"/> This is a best practice. It makes their intent clearer & presents much better in the PDF output. Also did similar to <ulink>. 4 - moved a number of lists (<itemizedlist> & <orderedlist>) outside of <para>s. See 2. 5 - added language & role attributes to <programlisting>s - provides syntax highlighting ;-) 6 - changed colwidths to integers - Compatibilty with Publican. 7 - changed a few itemizedlists to orderedlists where appropriate. 8 - changed a few itemizedlists to variablelists - was the best way to present these items. However there seems to be a formatting bug with jDocbook, doesn't always format the headings - logging a JIRA for it. 9 - changed "smart quotes" to regular quotes. These are invalid in code samples, if someone copy/pastes the code sample it will not compile. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1272) Join planning should make better decisions when mixing costing and unknown values

by Steven Hawkins (JIRA)

Join planning should make better decisions when mixing costing and unknown values --------------------------------------------------------------------------------- Key: TEIID-1272 URL: https://jira.jboss.org/browse/TEIID-1272 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 When faced with an unknown value during join planning we use the default assumption of 100000 rows. However this may cause non-performant cross joins to be pushed in the worst case. It would be better to either not cost these scenarios or get a more accurate estimate of the post join cardinality based upon the the other side of the join. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1309) The engine should validate against using an insert with a query expression in a multisource scenario.

by Steven Hawkins (JIRA)

The engine should validate against using an insert with a query expression in a multisource scenario. ----------------------------------------------------------------------------------------------------- Key: TEIID-1309 URL: https://jira.jboss.org/browse/TEIID-1309 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.2 SELECT INTO or an INSERT with a query expression will not work correctly under a multisource scenario since we do not modify ProjectIntoNodes. We also do not properly handle a pushdown of a insert with a query expression, since the query may pull from multiple sources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1290) Application name is null in JOPR

by Steven Hawkins (JIRA)

Application name is null in JOPR -------------------------------- Key: TEIID-1290 URL: https://jira.jboss.org/browse/TEIID-1290 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 Application name is null in JOPR -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Closed: (TEIID-984) For JON monitoring, add support for monitoring the audit logs

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-984?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins closed TEIID-984. -------------------------------- > For JON monitoring, add support for monitoring the audit logs > ------------------------------------------------------------- > > Key: TEIID-984 > URL: https://jira.jboss.org/browse/TEIID-984 > Project: Teiid > Issue Type: Feature Request > Components: Jopr Plugin > Affects Versions: 7.1 > Reporter: Van Halbert > Assignee: Ted Jones > > Add the ability to monitor the audit logs (or audit database table) from JON -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1240) Exception with false join predicate

by Steven Hawkins (JIRA)

Exception with false join predicate ----------------------------------- Key: TEIID-1240 URL: https://jira.jboss.org/browse/TEIID-1240 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 Issuing a query such as select ... from a full outer join b on (false) where a.x = 1 will throw an exception because we'll attempt to update the join predicate, but the list is non-modifiable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1278) vdb-deployer.xsd should have a description for translators.

by Steven Hawkins (JIRA)

vdb-deployer.xsd should have a description for translators. ----------------------------------------------------------- Key: TEIID-1278 URL: https://jira.jboss.org/browse/TEIID-1278 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 The marshall unmarshall test is failing in product tests since it appears to be using the description attribute from the translator. The fix is to just update the xsd to allow the description attribute. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Closed: (TEIID-1156) Description fields for UDF Model objects are limited to 128 characters

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1156?page=com.atlassian.jira.plugin.s... ] Steven Hawkins closed TEIID-1156. --------------------------------- > Description fields for UDF Model objects are limited to 128 characters > ---------------------------------------------------------------------- > > Key: TEIID-1156 > URL: https://jira.jboss.org/browse/TEIID-1156 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Steven Hawkins > Fix For: 7.2 > > > While setting descriptions for the SalesForce UDF functions, I received validation errors stating that: "Description exceeds maximum length of: 128" > The com.metamatrix.query.function.metadata.FunctionMetadataValidator class has a hard-coded limit of 128. Noone seems to know why?? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1255) Add documentation about usage of Multi-Source

by Ramesh Reddy (JIRA)

Add documentation about usage of Multi-Source --------------------------------------------- Key: TEIID-1255 URL: https://jira.jboss.org/browse/TEIID-1255 Project: Teiid Issue Type: Task Components: Documentation Affects Versions: 7.1 Reporter: Ramesh Reddy Fix For: 7.1.1 Add documentation about multi-source, how to define it, benefits, and extra column it adds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2010