August 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-671) Teiid should accept LongNum, DoubleNum, and BigDecimalValue in numeric function

by Warren Gibson (JIRA)

Teiid should accept LongNum, DoubleNum, and BigDecimalValue in numeric function ------------------------------------------------------------------------------- Key: TEIID-671 URL: https://jira.jboss.org/jira/browse/TEIID-671 Project: Teiid Issue Type: Bug Affects Versions: 6.1.0 Environment: CTC Reporter: Warren Gibson Assignee: Steven Hawkins Teiid Query Testing 1. Ran CTC query testing against Teiid and received Exception when actual results were expected. 2. The queries contained LongNum, DoubleNum, and BigDecimalValue. We should accept LongNum, DoubleNum, and BigDecimalValue in numeric function. 3. Attached is a spreadsheet with a sampling of the queries and results. -- 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, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-688) Text Connector should be Medata Aware Connector

by Ramesh Reddy (JIRA)

Text Connector should be Medata Aware Connector ----------------------------------------------- Key: TEIID-688 URL: https://jira.jboss.org/jira/browse/TEIID-688 Project: Teiid Issue Type: Sub-task Components: Misc. Connectors Reporter: Ramesh Reddy Fix For: 6.2.0 Based on TEIID-685, Text Connector must implement this interface(s), so that any Text sources can be used in dynamic data integration. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-703) Configuration service is assuming the Session Service roles in some instances

by Ramesh Reddy (JIRA)

Configuration service is assuming the Session Service roles in some instances ----------------------------------------------------------------------------- Key: TEIID-703 URL: https://jira.jboss.org/jira/browse/TEIID-703 Project: Teiid Issue Type: Quality Risk Components: Embedded Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 EmbeddedConfiguration service acts as the session service and keeps track of the connections for the admin api purposes. Now that engine has direct access to the session service this needs to handled by the SessionService. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-706) Deployed vdbs should have a consistent unzipped location.

by Steven Hawkins (JIRA)

Deployed vdbs should have a consistent unzipped location. --------------------------------------------------------- Key: TEIID-706 URL: https://jira.jboss.org/jira/browse/TEIID-706 Project: Teiid Issue Type: Sub-task Components: Embedded, Query Engine Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 Deployed vdbs, or vdb less configurationinfo.def files should have a consistent location for their exploded form. Under <teiid home>/deploy there will be folders <vdb name>/<vdb version> - with lower cased names. On the initial scan for vdbs and def files we will use the corresponding def file to see if the <teiid home>/deploy/<vdb name>/<vdb version> already exists. If it does not we will create the exploded location, otherwise we'll use it rather than the archive file itself. Any changes after deployment time ConfigurationInfo, roles, etc. will only be made to the exploded location. This will make it easy to document how to modify these files without constantly zipping and unzipping them. Ideally this exploded location should also be used by the index file logic rather than using yet another temporary location. -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-698) Create AdminShell Kit

by Ramesh Reddy (JIRA)

Create AdminShell Kit --------------------- Key: TEIID-698 URL: https://jira.jboss.org/jira/browse/TEIID-698 Project: Teiid Issue Type: Task Components: AdminApi, Common, Tools Reporter: Ramesh Reddy Priority: Blocker Fix For: 6.2.0 Create the AdminShell kit for the Teiid runtime. This will be used as the external tool to manage the Teiid runtime environment. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-702) Define/Provide ways to create and use encrypted passwords in Teiid

by Ramesh Reddy (JIRA)

Define/Provide ways to create and use encrypted passwords in Teiid ------------------------------------------------------------------ Key: TEIID-702 URL: https://jira.jboss.org/jira/browse/TEIID-702 Project: Teiid Issue Type: Task Components: Common Reporter: Ramesh Reddy Fix For: 6.2.0 Teiid runtime is capable of decrypting the encrypted passwords from the Teiid Designer (when the same key certs are used), however does not provide a mechanism to provide a utility to encrypt passwords itself. Often times the Designer might be using a different certificate or may be the user did not use the Designer at all. So, Teiid needs 1) Script to create a new certificate for password encryption 2) Script to encrypt a given password 3) Integration of the this cert with runtime, such that it can decrypt password(s) at runtime. 4) Documentation as how this can be done. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-666) Add "Session" service

by Ramesh Reddy (JIRA)

Add "Session" service --------------------- Key: TEIID-666 URL: https://jira.jboss.org/jira/browse/TEIID-666 Project: Teiid Issue Type: Sub-task Components: Embedded, Query Engine, Server Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.2.0 Add "session" service to "embedded" that tracks the users that are logged into the system. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-680) Add "socket" transport as service

by Ramesh Reddy (JIRA)

Add "socket" transport as service ---------------------------------- Key: TEIID-680 URL: https://jira.jboss.org/jira/browse/TEIID-680 Project: Teiid Issue Type: Sub-task Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 Add mechanism to start a socket transport as service when query engine starts. The socket transport can be used in two fold. 1) In client/server mode 2) In embedded mode (on demand). When a embedded is started then socket transport is started, then some other client can connect to it until "embedded" is alive. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-606) Connector Bindings password property is not shown on Connector Bindings Properties panel until user checks "include optional properties" box

by Warren Gibson (JIRA)

Connector Bindings password property is not shown on Connector Bindings Properties panel until user checks "include optional properties" box -------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-606 URL: https://jira.jboss.org/jira/browse/TEIID-606 Project: Teiid Issue Type: Bug Components: Console Affects Versions: 6.0.0 Environment: Teiid Console on Windows Reporter: Warren Gibson Assignee: Steven Hawkins The Teiid Console connector bindings properties panel does not show the Password property until the user checks the optional properties box. The password property has always been visable without requiring user to check the optional properties. It seems more like a primary property than an optional property and from a usability standpoint should not be hidden. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-602) Connecting to server from client fails with SingleInstanceCommunicationException and MMProcess goes into a loop

by Paul Nittel (JIRA)

Connecting to server from client fails with SingleInstanceCommunicationException and MMProcess goes into a loop --------------------------------------------------------------------------------------------------------------- Key: TEIID-602 URL: https://jira.jboss.org/jira/browse/TEIID-602 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Environment: Fedora 10, JBEDSP 13 May Reporter: Paul Nittel Assignee: Steven Hawkins Priority: Blocker I tried to connect to the server from SQuirreL and, while it appeared to be on its way to success, finally failed with the exception noted above. As I have noted a few times now, the jvm running MMProcess is in a loop, consuming 99+% of the CPU. I did a kill -3 and will attach the host controller log to the Jira. -- 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, 4 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2009