February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-388) When determining kestore algorithm, the logic wasn't considering the setting "ssl.KeyManagerFactory.algorithm" for defining an algorithm to use

by Van Halbert (JIRA)

When determining kestore algorithm, the logic wasn't considering the setting "ssl.KeyManagerFactory.algorithm" for defining an algorithm to use ------------------------------------------------------------------------------------------------------------------------------------------------ Key: TEIID-388 URL: https://jira.jboss.org/jira/browse/TEIID-388 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 6.1.0 Reporter: Van Halbert Assignee: Van Halbert This is a rolled forward change from 5.5.4. The problem was discovered when running on an IBM Z900 machine using the IBM jdk. It uses the Security property "ssl.KeyManagerFactory.algorithm" to specify the algorithm to use, and our logic doesn't include an alternative when the metamatrix algorithm property is not defined, it always defaulted to "SunX509". Therefore, the change is to check the Security property as an override to the default, but the metamatrix property will be the override to all. -- 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] Created: (TEIID-385) Replace client logging with java logging

by Steven Hawkins (JIRA)

Replace client logging with java logging ---------------------------------------- Key: TEIID-385 URL: https://jira.jboss.org/jira/browse/TEIID-385 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.0.0 The client code is unnecessarily concerned with logging and log configuration with the socketlogger and the drivermanagerlogger. These calls should be replaced with standard java logging. -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIID-387) Improper Grammer in ShutdownServer Message

by Ted Jones (JIRA)

Improper Grammer in ShutdownServer Message ------------------------------------------ Key: TEIID-387 URL: https://jira.jboss.org/jira/browse/TEIID-387 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Reporter: Ted Jones Assignee: Steven Hawkins In svcmgr after typing ShutdownServer, the following message is displayed: "All the servers in Cluster is being shutdown" Should read: "All the servers in Cluster are being shutdown" -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-355) deprecate select into targeting a table

by Steven Hawkins (JIRA)

deprecate select into targeting a table --------------------------------------- Key: TEIID-355 URL: https://jira.jboss.org/jira/browse/TEIID-355 Project: Teiid Issue Type: Quality Risk Components: Documentation, Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.0.0 We should deprecate the usage of select into targeting a table. We are emulating SQL Server specific behavior, but not exactly (with set operations for example). It's much better promote usage of the standard insert with a query expression - and add proper pushdown support (TEIID-124). -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Work started: (TEIID-161) Move common type conversion logic into a centralized facility for connectors

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-161?page=com.atlassian.jira.plug... ] Work on TEIID-161 started by Steven Hawkins. > Move common type conversion logic into a centralized facility for connectors > ---------------------------------------------------------------------------- > > Key: TEIID-161 > URL: https://jira.jboss.org/jira/browse/TEIID-161 > Project: Teiid > Issue Type: Sub-task > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > > Since we allow the flexibility for physical model types to not actually match source type (as in not simply the closest runtime type), every connector is currently responsible for not only converting to a known runtime type but potentially converting to the desired runtime type. This logic has been encapsulated behind the typefacility converttoruntimetype and transformvalue. It would be nice however to automatically handle the known 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-382) QUARTER function and the BITAND/NOT/OR/XOR functions not covered in Teiid documentation

by Greg Haber (JIRA)

QUARTER function and the BITAND/NOT/OR/XOR functions not covered in Teiid documentation --------------------------------------------------------------------------------------- Key: TEIID-382 URL: https://jira.jboss.org/jira/browse/TEIID-382 Project: Teiid Issue Type: Bug Components: Documentation Reporter: Greg Haber Assignee: Steven Hawkins Priority: Minor There is no mention of the QUARTER date function, or the BIT comparison functions (BITAND, BITNOT, BITOR, and BITXOR) in the Teiid Reference Guide (http://docs.jboss.org/teiid/6.0/reference/en-US/html). -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Commented: (TEIID-143) Query should 'find' connector types and jars rather than have them predefined in the config.

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-143?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIID-143: ------------------------------------ The requirements are 1) It must be discoverable, should be able define them without modifications to other parts of system 2) Prefer to inherit common properties, so that the all connector specific properties can be defined in one place 3) Should be able to load dependent jars in non-delegating class loader 4) Should be able to define the third party dependencies externally to the artifact (CAF includes them, but should have option to specify externally, if needed) 5) Preferably single artifact (Like CAF) The comment above in one solution, where CAF file includes the type information and all the necessary jars. But this does not satisfy (4). We could additionally support ".cdk" files in a directory along with their dependencies to support the item (4). > Query should 'find' connector types and jars rather than have them predefined in the config. > -------------------------------------------------------------------------------------------- > > Key: TEIID-143 > URL: https://jira.jboss.org/jira/browse/TEIID-143 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 6.0.0 > Reporter: John Doyle > Fix For: 6.1.0 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Currently, dqp as delived with Designer is preconfigured with connector types. I think it should discover the connectors that are available upon startup. This would make it easier to add connectors to a kit. The current process for adding a connector to a kit is manual and error prone. We have problems with it on nearly every release. > This is also an attractive feature for embedding query in other environments. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (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 commented on TEIID-309: ------------------------------------ I added the host properties to the Host object, so they are available when asked for Host information through Admin API. However, looks like Console directly tries to feed from configuration and uses Property definitions to show them. Looks like to show them in the Console requires more work. > 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-384) Remove the ValidateCriteriaVisitor

by Steven Hawkins (JIRA)

Remove the ValidateCriteriaVisitor ---------------------------------- Key: TEIID-384 URL: https://jira.jboss.org/jira/browse/TEIID-384 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.0.0 The ValidateCriteriaVisitor is enforcing a confusing restricting on searchability - based upon virtual layer metadata and only for the user query. This is meaningless since the searchability should actually be associated with the datatype. With our runtime types the only restrictions are on BLOB - not searchable CLOB - searchable like XML - not searchable OBJECT - not searchable These should be imposed appropriately by the ValidationVisitor. Searchability metadata will then only be used to determine pushdown eligibility. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-383) Whe running svcmgr the output is sent to the hostcontroller log instead of the console

by Van Halbert (JIRA)

Whe running svcmgr the output is sent to the hostcontroller log instead of the console -------------------------------------------------------------------------------------- Key: TEIID-383 URL: https://jira.jboss.org/jira/browse/TEIID-383 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Reporter: Van Halbert Assignee: Steven Hawkins When svcmgr is run, the output is going to the hostcontroller log file, when it should be going to the console. There's no ability to execute any of the options. -- 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, 10 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2009