February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Commented: (TEIID-309) System Host setup issues

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-309?page=com.atlassian.jira.plug... ] Van Halbert commented on TEIID-309: ----------------------------------- The moving of the host properties to the metamatrix.properties and removing them from the config.xml has resulted in them disappearing in the console when the host is displayed under Configuration / Deployments. > System Host setup issues > ------------------------ > > Key: TEIID-309 > URL: https://jira.jboss.org/jira/browse/TEIID-309 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 6.0.0 > > > 1) izpack does not make the startserver, stopserver, scripts as executable in the linux > 2) There is no option for *not* starting the server (either way it does not look like starting the server). This option should be extended to "setupmm" driven process too, with additional property. > 3) multicast port is not available in the IZpack + it is hard coded; Any two machines are seeing each other on the same multicast address. This needs to be fixed as soon as possible.(FEDERATE-340) > 4) System name is always defaulting to $hostname, even when it is blank. I fixed this in install. > 5) With "systenhostsetup.sh" I can not pass in the properties file, it is looking for the file in a fixed location. > 6) systemhostsetup.sh creates the "metamatrix.properties" file, but does not write to the configuration about what it's config name is, thus never can be started. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-374) Change metadata reference to return the metadata object rather than the metadataid

by Steven Hawkins (JIRA)

Change metadata reference to return the metadata object rather than the metadataid ---------------------------------------------------------------------------------- Key: TEIID-374 URL: https://jira.jboss.org/jira/browse/TEIID-374 Project: Teiid Issue Type: Sub-task Components: Connector API Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.0.0 Returning the metadata id forces the developer to keep track of the runtime metadata object, when it would be much simpler to return the metadataobject instead. -- 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

15 years, 9 months

2
4
0 / 0

[JBoss JIRA] Closed: (TEIID-309) System Host setup issues

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-309?page=com.atlassian.jira.plug... ] Ramesh Reddy closed TEIID-309. ------------------------------ Fix Version/s: 6.0.0 (was: 6.1.0) Resolution: Done Host specific properties like install dir, data dir, log dir moved from config.xml into the bootstrap properties file "metamatrix.properties". Since these properties are specific to a given host this would be appropriate place. Also, this bring consistency in adding the Host with setupmm during either primary server or cluster host. > System Host setup issues > ------------------------ > > Key: TEIID-309 > URL: https://jira.jboss.org/jira/browse/TEIID-309 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 6.0.0 > > > 1) izpack does not make the startserver, stopserver, scripts as executable in the linux > 2) There is no option for *not* starting the server (either way it does not look like starting the server). This option should be extended to "setupmm" driven process too, with additional property. > 3) multicast port is not available in the IZpack + it is hard coded; Any two machines are seeing each other on the same multicast address. This needs to be fixed as soon as possible.(FEDERATE-340) > 4) System name is always defaulting to $hostname, even when it is blank. I fixed this in install. > 5) With "systenhostsetup.sh" I can not pass in the properties file, it is looking for the file in a fixed location. > 6) systemhostsetup.sh creates the "metamatrix.properties" file, but does not write to the configuration about what it's config name is, thus never can be started. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Reopened: (TEIID-309) System Host setup issues

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-309?page=com.atlassian.jira.plug... ] Ramesh Reddy reopened TEIID-309: -------------------------------- Assignee: Ramesh Reddy (was: Van Halbert) More issues found during the system host setup they are 7) Host information put in for cluster member is not complete. When primary host is created the host information is created using property replacement in the config.xml, which accounts for all properties. However, during the admin api based host addition, it will not add all the necessary information. > System Host setup issues > ------------------------ > > Key: TEIID-309 > URL: https://jira.jboss.org/jira/browse/TEIID-309 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 6.1.0 > > > 1) izpack does not make the startserver, stopserver, scripts as executable in the linux > 2) There is no option for *not* starting the server (either way it does not look like starting the server). This option should be extended to "setupmm" driven process too, with additional property. > 3) multicast port is not available in the IZpack + it is hard coded; Any two machines are seeing each other on the same multicast address. This needs to be fixed as soon as possible.(FEDERATE-340) > 4) System name is always defaulting to $hostname, even when it is blank. I fixed this in install. > 5) With "systenhostsetup.sh" I can not pass in the properties file, it is looking for the file in a fixed location. > 6) systemhostsetup.sh creates the "metamatrix.properties" file, but does not write to the configuration about what it's config name is, thus never can be started. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-380) Upgrade to JUnit 4.4 for project tests

by Steven Hawkins (JIRA)

Upgrade to JUnit 4.4 for project tests -------------------------------------- Key: TEIID-380 URL: https://jira.jboss.org/jira/browse/TEIID-380 Project: Teiid Issue Type: Task Components: Common Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.0.0 -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Commented: (TEIID-168) Remove resultset caching

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-168?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIID-168: -------------------------------------- That's a mischaracterization of what is happening. It's just an intermediate state that the memory backed used for connector result sets was moved to jboss cache. JBoss cache without additional work is not appropriate for large data volumes requiring intelligent paging, which is the desired end state of this feature. > Remove resultset caching > ------------------------ > > Key: TEIID-168 > URL: https://jira.jboss.org/jira/browse/TEIID-168 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector, Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > Resultset caching should be replaced with relation and procedure caching. This would initially be backed by the buffermanager, based upon hints/costing, and be utilized by the planner rather than the resolver. It would be good if we also detected the level of determinism. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-168) Remove resultset caching

by Ken Johnson (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-168?page=com.atlassian.jira.plug... ] Ken Johnson commented on TEIID-168: ----------------------------------- Why the move away from JBCache and back to buffer manager? > Remove resultset caching > ------------------------ > > Key: TEIID-168 > URL: https://jira.jboss.org/jira/browse/TEIID-168 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector, Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > Resultset caching should be replaced with relation and procedure caching. This would initially be backed by the buffermanager, based upon hints/costing, and be utilized by the planner rather than the resolver. It would be good if we also detected the level of determinism. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-361) LogManager is tied with Current Conficuration and makes it hard to use with Embedded

by Ramesh Reddy (JIRA)

LogManager is tied with Current Conficuration and makes it hard to use with Embedded ------------------------------------------------------------------------------------ Key: TEIID-361 URL: https://jira.jboss.org/jira/browse/TEIID-361 Project: Teiid Issue Type: Task Components: Common Affects Versions: 6.x Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.0.0 Remove the configuration of logging listeners and configuration out of the Log Manager, and make them injectable. Once this is done Server and Embedded can use it how it fits their needs. -- 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

15 years, 9 months

1
3
0 / 0

[JBoss JIRA] Moved: (TEIID-376) Resources: SSL: Parameters are in a weird order and not terribly clear as to what is what

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-376?page=com.atlassian.jira.plug... ] Steven Hawkins moved JBEDSP-564 to TEIID-376: --------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-376 (was: JBEDSP-564) Component/s: Console (was: Console) Fix Version/s: 6.0.0 (was: 5.5.4) Affects Version/s: 6.1.0 (was: 5.5.3) > Resources: SSL: Parameters are in a weird order and not terribly clear as to what is what > ----------------------------------------------------------------------------------------- > > Key: TEIID-376 > URL: https://jira.jboss.org/jira/browse/TEIID-376 > Project: Teiid > Issue Type: Task > Components: Console > Affects Versions: 6.1.0 > Environment: All > Reporter: Paul Nittel > Assignee: Van Halbert > Priority: Optional > Fix For: 6.0.0 > > Attachments: SslParameters.png > > > The Resources panel of the Console covers a number of resources, one of which is SSL. The test script I'm executing dictates I change the keystore and its password. There are two password fields, one labeled "Password" and the other labeled "TrustStore Password". > Neither password field is adjacent to its associated file's field. > Please reorder these properties so they make sense and relabel the keystore's password field to be "KeyStore Password". > I'll leave it up to someone else to determine if these things are TrustStore vs Truststore and KeyStore versus Keystore. Whichever wins, they should be consistent. > See attached screenshot. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-375) The XML connector consumes too much memory, large documents cause OutOf Memory errors.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-375?page=com.atlassian.jira.plug... ] Steven Hawkins moved JBEDSP-692 to TEIID-375: --------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-375 (was: JBEDSP-692) Issue Type: Quality Risk (was: Feature Request) Component/s: XML Connector (was: Connectors) Fix Version/s: 6.1.0 (was: 5.5.4) Affects Version/s: 6.0.0 (was: 5.5.2) (was: 5.5.1) > The XML connector consumes too much memory, large documents cause OutOf Memory errors. > -------------------------------------------------------------------------------------- > > Key: TEIID-375 > URL: https://jira.jboss.org/jira/browse/TEIID-375 > Project: Teiid > Issue Type: Quality Risk > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: John Doyle > Fix For: 6.1.0 > > > See the link to the issue tracket ticket. > In this POC, the customer has many such large XML documents. A fix for this memory problem probably requires that the connector or the connector cache run in it's own process so that memory can be managed without regard to the server process. > The solution should: > provide better control over the memory parameters of the connector > reduce the amount of memory required to parse the document (streaming) -- 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

15 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2009