November 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1365) JCR_REFERENCE procedure defined in the ModeShape JCRFunctions.xmi model should return a boolean instead of a string

by Van Halbert (JIRA)

JCR_REFERENCE procedure defined in the ModeShape JCRFunctions.xmi model should return a boolean instead of a string ------------------------------------------------------------------------------------------------------------------- Key: TEIID-1365 URL: https://jira.jboss.org/browse/TEIID-1365 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 7.1.1 Reporter: Van Halbert Assignee: Van Halbert Fix For: 7.1.1 The JCR_REFERENCE procedure returns a string and it should return a boolean. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1333) Dynamic VDB can be set to ACTIVE, even when the data source is not available.

by Ramesh Reddy (JIRA)

Dynamic VDB can be set to ACTIVE, even when the data source is not available. ----------------------------------------------------------------------------- Key: TEIID-1333 URL: https://jira.jboss.org/browse/TEIID-1333 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1.1 Attachments: interoperability-vdb.xml Dynamic VDB upon deployment is set to active, it was still missing the data source. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1091) Add remaining SQL/XML functions

by Steve Hawkins (JIRA)

Add remaining SQL/XML functions ------------------------------- Key: TEIID-1091 URL: https://jira.jboss.org/browse/TEIID-1091 Project: Teiid Issue Type: Sub-task Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 We should add the remaining functions, xmlparse, xmlserialize, xmlroot, etc. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Resolved: (TEIID-1380) When server is shut down, and then a vdb is replaced in the deploy directory, the teiid metadata cache becomes out of sync, and requires the user to delete the <server>data/teiid directory

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-1380?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy resolved TEIID-1380. --------------------------------- Assignee: Ramesh Reddy Resolution: Done The metadata load process now checks for the VDB modified time with the previous metadata cache file time. As long as vdb modified time is before cached file time, it allows previously loaded metadata, otherwise the cached metadata is deleted and vdb is loaded from .vdb file. > When server is shut down, and then a vdb is replaced in the deploy directory, the teiid metadata cache becomes out of sync, and requires the user to delete the <server>data/teiid directory > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1380 > URL: https://jira.jboss.org/browse/TEIID-1380 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > > If a vdb is replaced while the server is shut down, the teiid metadata cache can become out-of-sync and the to fix it, the <server>data/teiid directory must be deleted to force it to refresh and sync up. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1380) When server is shut down, and then a vdb is replaced in the deploy directory, the teiid metadata cache becomes out of sync, and requires the user to delete the <server>data/teiid directory

by Van Halbert (JIRA)

[ https://jira.jboss.org/browse/TEIID-1380?page=com.atlassian.jira.plugin.s... ] Van Halbert updated TEIID-1380: ------------------------------- Priority: Blocker (was: Critical) > When server is shut down, and then a vdb is replaced in the deploy directory, the teiid metadata cache becomes out of sync, and requires the user to delete the <server>data/teiid directory > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1380 > URL: https://jira.jboss.org/browse/TEIID-1380 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Van Halbert > Priority: Blocker > > If a vdb is replaced while the server is shut down, the teiid metadata cache can become out-of-sync and the to fix it, the <server>data/teiid directory must be deleted to force it to refresh and sync up. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1380) When server is shut down, and then a vdb is replaced in the deploy directory, the teiid metadata cache becomes out of sync, and requires the user to delete the <server>data/teiid directory

by Van Halbert (JIRA)

[ https://jira.jboss.org/browse/TEIID-1380?page=com.atlassian.jira.plugin.s... ] Van Halbert moved SOA-2622 to TEIID-1380: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1380 (was: SOA-2622) Affects Version/s: 7.1.1 (was: 5.1.0.ER5) Security: (was: Public) Component/s: Server (was: EDS) > When server is shut down, and then a vdb is replaced in the deploy directory, the teiid metadata cache becomes out of sync, and requires the user to delete the <server>data/teiid directory > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1380 > URL: https://jira.jboss.org/browse/TEIID-1380 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Van Halbert > Priority: Critical > > If a vdb is replaced while the server is shut down, the teiid metadata cache can become out-of-sync and the to fix it, the <server>data/teiid directory must be deleted to force it to refresh and sync up. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1369) ModeShape jdbc driver is returning jdcr_path column, but the teiid modeshape translator is looking for mode_path. The translator should be changed to look for jcr_path.

by Van Halbert (JIRA)

[ https://jira.jboss.org/browse/TEIID-1369?page=com.atlassian.jira.plugin.s... ] Van Halbert resolved TEIID-1369. -------------------------------- Fix Version/s: 7.1.1 Resolution: Done changed the translator to look for jcr:path, instead of mode:path Committed revision 2741 > ModeShape jdbc driver is returning jdcr_path column, but the teiid modeshape translator is looking for mode_path. The translator should be changed to look for jcr_path. > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1369 > URL: https://jira.jboss.org/browse/TEIID-1369 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.1.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 7.1.1 > > > The Teiid Modeshape translator needs to be changed to look for the jcr_path column, instead of mode_path. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Work started: (TEIID-1369) ModeShape jdbc driver is returning jdcr_path column, but the teiid modeshape translator is looking for mode_path. The translator should be changed to look for jcr_path.

by Van Halbert (JIRA)

[ https://jira.jboss.org/browse/TEIID-1369?page=com.atlassian.jira.plugin.s... ] Work on TEIID-1369 started by Van Halbert. > ModeShape jdbc driver is returning jdcr_path column, but the teiid modeshape translator is looking for mode_path. The translator should be changed to look for jcr_path. > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1369 > URL: https://jira.jboss.org/browse/TEIID-1369 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.1.1 > Reporter: Van Halbert > Assignee: Van Halbert > > The Teiid Modeshape translator needs to be changed to look for the jcr_path column, instead of mode_path. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1336) EDS adminshell - clearCache() having no effect

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-1336?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy resolved TEIID-1336. --------------------------------- Resolution: Done try now > EDS adminshell - clearCache() having no effect > ---------------------------------------------- > > Key: TEIID-1336 > URL: https://jira.jboss.org/browse/TEIID-1336 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.1.1 > Environment: SOA-P 5.1 ER3 build > Reporter: Len DiMaggio > Assignee: Ramesh Reddy > Fix For: 7.1.1 > > > clearCache() doesn't look like it's doing anything - see below: > groovy:000> connectAsAdmin("mms://localhost:31443", "admin", "admin", "conn-1") > ===> null > groovy:000> getCacheStats("QUERY_SERVICE_RESULT_SET_CACHE") > ===> hitRatio=0.0; totalEntries=0; requestCount=3 > groovy:000> clearCache("QUERY_SERVICE_RESULT_SET_CACHE") > ===> null > groovy:000> getCacheStats("QUERY_SERVICE_RESULT_SET_CACHE") > ===> hitRatio=0.0; totalEntries=0; requestCount=3 > =================== > server.log: > 2010-10-29 12:13:07,065 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) processing message:MessageHolder: contents=org.teiid.net.socket.ServiceInvocationStruct@18cf5ea > 2010-10-29 12:13:07,065 DEBUG [org.teiid.SECURITY] (New I/O server worker #2-1) Ping MLwHWKFcHgcq > 2010-10-29 12:13:07,065 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) message: MessageHolder: contents=null for request ID:38 > 2010-10-29 12:13:07,067 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) processing message:MessageHolder: contents=org.teiid.net.socket.ServiceInvocationStruct@c171b7 > 2010-10-29 12:13:07,067 DEBUG [org.teiid.ADMIN_API] (New I/O server worker #2-1) before clearCache:org.teiid.adminapi.jboss.Admin@1a42c71(QUERY_SERVICE_RESULT_SET_CACHE) > 2010-10-29 12:13:07,067 DEBUG [org.teiid.ADMIN_API] (New I/O server worker #2-1) after clearCache : null > 2010-10-29 12:13:07,067 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) message: MessageHolder: contents=null for request ID:39 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-189) Temp tables should maintain their costing metadata

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-189?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins resolved TEIID-189. ---------------------------------- Fix Version/s: 7.2 (was: 7.3) Resolution: Partially Completed For now cardinality is enough. Will probably address other stats gathering as part of the runtime costing issue. > Temp tables should maintain their costing metadata > -------------------------------------------------- > > Key: TEIID-189 > URL: https://jira.jboss.org/browse/TEIID-189 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.2 > > > Defect Tracker #24522: Temp table cardinality is currently only used for staging tables. It would also be generally useful for ad hoc queries to have the TempTableStoreImpl maintain the cardinality of the tables. Other costing information could actually be incorrect now (such as column min/max) depending upon what has been selected into a temp table. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2010