February 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1049) Create data source for each VDB deployed automaticaly

by Ramesh Reddy (JIRA)

Create data source for each VDB deployed automaticaly ----------------------------------------------------- Key: TEIID-1049 URL: https://jira.jboss.org/jira/browse/TEIID-1049 Project: Teiid Issue Type: Feature Request Components: Embedded Affects Versions: 7.0 Reporter: Ramesh Reddy Priority: Minor Fix For: 7.0 When a VDB is deployed, auto create a data source for the deployed VDB using the Teiid's "embedded" data source class. -- 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

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-1484) CLONE - Resolving changes to consolidate teiid/teiid designer handling

by Steven Hawkins (JIRA)

CLONE - Resolving changes to consolidate teiid/teiid designer handling ---------------------------------------------------------------------- Key: TEIID-1484 URL: https://issues.jboss.org/browse/TEIID-1484 Project: Teiid Issue Type: Task Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 Designer currently must supply external metadata that should be easily derived by Teiid. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-965) Need Excel file importer / connector

by Ivan Vasyliev (JIRA)

[ https://issues.jboss.org/browse/TEIID-965?page=com.atlassian.jira.plugin.... ] Ivan Vasyliev commented on TEIID-965: ------------------------------------- Additional XLS/JDBC driver (POI/jsqlparser based): http://code.google.com/p/sqlsheet/ Usage example: http://scriptella.javaforge.com/docs/api/scriptella/driver/xls/package-su... > Need Excel file importer / connector > ------------------------------------ > > Key: TEIID-965 > URL: https://issues.jboss.org/browse/TEIID-965 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 7.0 > Reporter: Steven Hawkins > > Really need to add an Excel connector in SP1. The easiest way to do this is probably with one of the open source JDBC drivers that work over Excel files. > Something like: > https://xlsql.dev.java.net/ - Excel JDBC driver (GPL unfortunately, so we probably can't distribute the driver) > http://www.andykhan.com/jexcelapi/ - Java Excel API (GPL too) > http://xlsjdbc.sourceforge.net/ - LGPL (uses Apache POI), really cheesy and maybe not being updated > http://jakarta.apache.org/poi/ - Excel API, event-based and not particularly friendly > http://www.vistaportal.com/products/vistajdbc-QA.htm - commercial -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-217) LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-217?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-217: -------------------------------------- Committed the proposed patch as there has not yet been feedback. Mike do you have any more to add on this feature? > LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result > ----------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-217 > URL: https://issues.jboss.org/browse/TEIID-217 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.0.0 > Reporter: Michael Walker > Assignee: Steven Hawkins > Priority: Minor > Fix For: 7.4 > > Attachments: ldap.patch.txt, LDAPSyncQueryExecution.java > > > If an attribute appears more than once, we should have some way to return all values. Currently, we only return one value, with no rhyme, reason, or determinism as to which one gets returned. Implementing this is difficult when multiple attributes appear more than once, of course. But a simple example of where this problem rears it's head is in modeling LDAP groups. Groups typically have repeating attributes to represent each member, and it would be nice to query all members of a given group, but impossible to do so with the current logic. > A sophisticated solution would create a normalized view of a DN, breaking out multi-valued attributes into a separate table that could be joined by a primary key. A simple solution might allow attributes to be flagged as "multi-valued", in which case, they could be maintained in a single denormalized table that represents all values in the DN. > If we build an importer for LDAP, we should consider how to best handle this issue in the importer design. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1472) EDS exceptions are very vague

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1472?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1472. ----------------------------------- Resolution: Incomplete Description Marking as resolved until additional information is provided. > EDS exceptions are very vague > ----------------------------- > > Key: TEIID-1472 > URL: https://issues.jboss.org/browse/TEIID-1472 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 7.1.1 > Reporter: Martin Vecera > > Exceptions thrown by EDS are not very helpful and descriptive. The messages are like "Error occured". > User might not recognize where a problem is. It is hard to develop applications with EDS since the bug tracking is very difficult without proper error message. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (TEIID-1477) Teiid ODBC has an issue supporting the postgres 8.01 client

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1477?page=com.atlassian.jira.plugin... ] Van Halbert reopened TEIID-1477: -------------------------------- Upon connection, ODBC client is issuing "set DataStyle to 'ISO' and causing below exception: StartTime=2011-02-23 14:57:46.38 requestID=8R+Ok34XSYmM.1 txID=null sessionID=8R+Ok34XSYmM applicationName=ODBC principal=pnittel@teiid-security vdbName=MyFirstVDB vdbVersion=1 sql=set DateStyle to 'ISO' 2011-02-23 14:57:46,386 DEBUG [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue13) Request Thread 8R+Ok34XSYmM.1 with state NEW 2011-02-23 14:57:46,386 DEBUG [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue13) 8R+Ok34XSYmM.1 No cache directive 2011-02-23 14:57:46,386 DEBUG [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue13) 8R+Ok34XSYmM.1 executing set DateStyle to 'ISO' 2011-02-23 14:57:46,386 DEBUG [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue13) [Ljava.lang.Object;@da6080 [QueryParserException]Parsing error: Encountered "set" at line 1, column 1. Was expecting one of: "call" ... "create" ... "delete" ... "drop" ... "exec" ... "execute" ... "insert" ... "select" ... "update" ... "(" ... "{" ... > Teiid ODBC has an issue supporting the postgres 8.01 client > ----------------------------------------------------------- > > Key: TEIID-1477 > URL: https://issues.jboss.org/browse/TEIID-1477 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.1.1, 7.3 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 7.1.1 > > > Teiid doesn't support the 8.1 postges odbc client. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1477) Teiid ODBC has an issue supporting the postgres 8.01 client

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-1477?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-1477. --------------------------------- Resolution: Done Adding support to handle "select version()" call, and couple other 'select' call I have seen with the other tools. Also fixed bug in specifying the pg_type so that pg_attribute transformation returns correct type for the table columns. Excel usually issues "SELECT name FROM master..sysdatabases" at the start of the connection. > Teiid ODBC has an issue supporting the postgres 8.01 client > ----------------------------------------------------------- > > Key: TEIID-1477 > URL: https://issues.jboss.org/browse/TEIID-1477 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.1.1, 7.3 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 7.1.1 > > > Teiid doesn't support the 8.1 postges odbc client. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (TEIID-1477) Teiid ODBC has an issue supporting the postgres 8.01 client

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1477?page=com.atlassian.jira.plugin... ] Van Halbert reopened TEIID-1477: -------------------------------- On each ODBC connection, the odbc client is issuing the query: select version() Producing this message in the server log: mmx@sllxqm27 simpleclient]$ 11:40:54,150 WARN [PROCESSOR] Processing exception 'Error Code:ERR.015.008.0039 Message:The function 'version()' is an unknown form. Check that the function name and number of arguments is correct.' for request +ps+jZn/HwvS.0. Exception type org.teiid.api.exception.query.QueryResolverException thrown from org.teiid.query.resolver.util.ResolverVisitor.resolveFunction(ResolverVisitor.java:468). Enable more detailed logging to see the entire stacktrace. 11:40:54,221 WARN [PROCESSOR] Processing exception 'Parsing error: Encountered "set" at line 1, column 1. Was expecting one of: "call" ... "create" ... "delete" ... "drop" ... "exec" ... "execute" ... "insert" ... "select" ... "update" ... "(" ... "{" ... ' for request +ps+jZn/HwvS.1. Exception type org.teiid.api.exception.query.QueryParserException thrown from org.teiid.query.parser.QueryParser.convertParserException(QueryParser.java:164). Enable more detailed logging to see the entire stacktrace. > Teiid ODBC has an issue supporting the postgres 8.01 client > ----------------------------------------------------------- > > Key: TEIID-1477 > URL: https://issues.jboss.org/browse/TEIID-1477 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.1.1, 7.3 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 7.1.1 > > > Teiid doesn't support the 8.1 postges odbc client. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1470) Deploying VDB XML file before data sources leads to failed deployment

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1470?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1470. ----------------------------------- Resolution: Done Updated the status checking code to relaunch the metadata load asynchronously if needed. This means that if a datasource has yet to be deployed, its deployment will trigger the metadata load. If a datasource has been deployed, but there is an error during the metadata load (db unavailable, etc.) then the vdb will be in an invalid state. just as with the previous case, redeploying the datasource will trigger the metadata load. There is no code yet for automatic retry/polling against a source that is available, but there is an error during load. > Deploying VDB XML file before data sources leads to failed deployment > --------------------------------------------------------------------- > > Key: TEIID-1470 > URL: https://issues.jboss.org/browse/TEIID-1470 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Paul Nittel > Assignee: Steven Hawkins > Fix For: 7.4 > > > Using the dynamic portfolio example, the readme instructs the user to: > Copy the following files to the <jboss.home>/server/default/deploy directory. > - portfolio-vdb.xml > - marketdata-file-ds.xml > If the user, in fact, deploys the files in that order, and waits to see the VDB deploy before copying the data source, here's what happens. > The VDB deploys (inactive state) > The data source deploys successfully > The VDB status changes to active. > Queries will fail however as the VDB does not have access to the metadata. Had the file been copied in the reverse order, it would have all worked. > Issues at play are: > 1) The readme's copying instructions are backwards, and > 2) The VDB is marked as active when it should not be > Both should be corrected. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Work started: (TEIID-1470) Deploying VDB XML file before data sources leads to failed deployment

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1470?page=com.atlassian.jira.plugin... ] Work on TEIID-1470 started by Steven Hawkins. > Deploying VDB XML file before data sources leads to failed deployment > --------------------------------------------------------------------- > > Key: TEIID-1470 > URL: https://issues.jboss.org/browse/TEIID-1470 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Paul Nittel > Assignee: Steven Hawkins > Fix For: 7.4 > > > Using the dynamic portfolio example, the readme instructs the user to: > Copy the following files to the <jboss.home>/server/default/deploy directory. > - portfolio-vdb.xml > - marketdata-file-ds.xml > If the user, in fact, deploys the files in that order, and waits to see the VDB deploy before copying the data source, here's what happens. > The VDB deploys (inactive state) > The data source deploys successfully > The VDB status changes to active. > Queries will fail however as the VDB does not have access to the metadata. Had the file been copied in the reverse order, it would have all worked. > Issues at play are: > 1) The readme's copying instructions are backwards, and > 2) The VDB is marked as active when it should not be > Both should be corrected. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 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 2011