February 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Moved: (TEIID-987) Problem regarding how often availability is called on the Facet

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-987?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1037 to TEIID-987: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-987 (was: JBEDSP-1037) Component/s: Jopr Plugin (was: JON Plugin) > Problem regarding how often availability is called on the Facet > --------------------------------------------------------------- > > Key: TEIID-987 > URL: https://jira.jboss.org/jira/browse/TEIID-987 > Project: Teiid > Issue Type: Bug > Components: Jopr Plugin > Reporter: Van Halbert > Assignee: Van Halbert > > There's a problem where the Facet (resource) availability is being checked about 5 times consecutively for every resource. There is an embedded jopr issue regarding this issue (EMBJOPR-129) > However, until this can be fixed, we might have to add a system property to handle how often to allow availability to be checked to limit the calls. Otherwise, this could a large processing overhead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-985) Provide information regarding the JGroups traffic

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-985?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-777 to TEIID-985: ------------------------------------------ Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-985 (was: JBEDSP-777) Component/s: Jopr Plugin (was: JON Plugin) > Provide information regarding the JGroups traffic > ------------------------------------------------- > > Key: TEIID-985 > URL: https://jira.jboss.org/jira/browse/TEIID-985 > Project: Teiid > Issue Type: Feature Request > Components: Jopr Plugin > Reporter: Van Halbert > Assignee: Van Halbert > > Provide information regarding the JGroups traffic -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-986) Add the ability to monitor other MM logs

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-986?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-778 to TEIID-986: ------------------------------------------ Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-986 (was: JBEDSP-778) Component/s: Jopr Plugin (was: JON Plugin) > Add the ability to monitor other MM logs > ----------------------------------------- > > Key: TEIID-986 > URL: https://jira.jboss.org/jira/browse/TEIID-986 > Project: Teiid > Issue Type: Feature Request > Components: Jopr Plugin > Reporter: Van Halbert > Assignee: Van Halbert > > Add the ability to monitor other MM Logs. (i.e., HC log, ODBC, JGroups, Auditing) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-984?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1013 to TEIID-984: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-984 (was: JBEDSP-1013) Component/s: Jopr Plugin (was: JON Plugin) Affects Version/s: 7.1 (was: Westport) > For JON monitoring, add support for monitoring the audit logs > ------------------------------------------------------------- > > Key: TEIID-984 > URL: https://jira.jboss.org/jira/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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-983) Getting Started With Designer kit needs updating to fix schema differences between SQL Server and MySQL

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-983?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1169 to TEIID-983: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-983 (was: JBEDSP-1169) Component/s: Documentation (was: Documentation) Affects Version/s: 7.1 (was: 5.5.3) > Getting Started With Designer kit needs updating to fix schema differences between SQL Server and MySQL > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-983 > URL: https://jira.jboss.org/jira/browse/TEIID-983 > Project: Teiid > Issue Type: Task > Components: Documentation > Affects Versions: 7.1 > Reporter: Larry O'Leary > > The Intro to Designer training was originally written to use the MMFinancials schema for SQL Server. It appears that some data types are not imported the same way when the MySQL schema is used. This results in data type differences between the written instructions and the MySQL schema that is most commonly used in the Getting Started kit. > For example, the ProductShares column in the AccountHoldings table is being imported as a biginteger when using SQL Server but as a bigdecimal when using MySQL. This difference then results in reconciler/transformation errors due to type incompatibility which require explicit conversions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-983) Getting Started With Designer kit needs updating to fix schema differences between SQL Server and MySQL

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-983?page=com.atlassian.jira.plug... ] Van Halbert reassigned TEIID-983: --------------------------------- Assignee: Van Halbert > Getting Started With Designer kit needs updating to fix schema differences between SQL Server and MySQL > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-983 > URL: https://jira.jboss.org/jira/browse/TEIID-983 > Project: Teiid > Issue Type: Task > Components: Documentation > Affects Versions: 7.1 > Reporter: Larry O'Leary > Assignee: Van Halbert > > The Intro to Designer training was originally written to use the MMFinancials schema for SQL Server. It appears that some data types are not imported the same way when the MySQL schema is used. This results in data type differences between the written instructions and the MySQL schema that is most commonly used in the Getting Started kit. > For example, the ProductShares column in the AccountHoldings table is being imported as a biginteger when using SQL Server but as a bigdecimal when using MySQL. This difference then results in reconciler/transformation errors due to type incompatibility which require explicit conversions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-982) Materialized Views should be treated as a service in MMx through the Console

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-982?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1168 to TEIID-982: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-982 (was: JBEDSP-1168) Component/s: Jopr Plugin (was: Server) (was: Console) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5) > Materialized Views should be treated as a service in MMx through the Console > ---------------------------------------------------------------------------- > > Key: TEIID-982 > URL: https://jira.jboss.org/jira/browse/TEIID-982 > Project: Teiid > Issue Type: Feature Request > Components: Jopr Plugin > Reporter: Marc Shirley > Assignee: Van Halbert > > Should be a service, controlled in Console, logs controlled by Log Settings, viewable by Log Viewer. There should also be a way to verify success/failure, last run time, from within Console. This could also be linked into the scheduling service (JBEDSP-144) if that existed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-981) Ability to cache XML documents

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-981?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1167 to TEIID-981: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-981 (was: JBEDSP-1167) Component/s: Query Engine (was: Query) (was: Server) Fix Version/s: (was: PostWestport) Affects Version/s: (was: 5.5) > Ability to cache XML documents > ------------------------------ > > Key: TEIID-981 > URL: https://jira.jboss.org/jira/browse/TEIID-981 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Lance Phillips > > We can currently cache relational result sets but have to re-create the XML document. XML being verbose this re-creation could take some time. This requirement would probably need a materialized flag on the document model, and the ability to store the XML document in an RDBMS (As a blob?) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-980) Add ability to apply XSLT stylesheets at the datasource level

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-980?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1166 to TEIID-980: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-980 (was: JBEDSP-1166) Component/s: XML Connector (was: Connectors) Fix Version/s: (was: PostWestport) Affects Version/s: (was: 5.5.3) > Add ability to apply XSLT stylesheets at the datasource level > ------------------------------------------------------------- > > Key: TEIID-980 > URL: https://jira.jboss.org/jira/browse/TEIID-980 > Project: Teiid > Issue Type: Feature Request > Components: XML Connector > Reporter: Marc Shirley > > XML data source contains a varying unknown number of "word" elements inside a "segment" that they wish to convert to a single string on the data source side. XQuery did not meet their needs and trying to do a concat fails due to the unknown number of elements. They would like to be able to apply the stylesheet before querying against the file to be able to retrieve a single paragraph, rather than attempt to piece together an unknown number of elements. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-979) Add support for Oracle XML queries in our Oracle connector

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-979?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-123 to TEIID-979: ------------------------------------------ Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-979 (was: JBEDSP-123) Component/s: JDBC Connector (was: Connectors) Fix Version/s: (was: PostWestport) > Add support for Oracle XML queries in our Oracle connector > ---------------------------------------------------------- > > Key: TEIID-979 > URL: https://jira.jboss.org/jira/browse/TEIID-979 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: Marc Shirley > > Oracle 9i and 10g have added special functionality for storing XML data, and for querying it. Genentech would like to be able to use these special SQL statements to extract XML data from Oracle via our Oracle connector. > case 5715 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2010