January 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2800) Teiid Login Issue with special characters

by Gautam Banerjee (JIRA)

Gautam Banerjee created TEIID-2800: -------------------------------------- Summary: Teiid Login Issue with special characters Key: TEIID-2800 URL: https://issues.jboss.org/browse/TEIID-2800 Project: Teiid Issue Type: Bug Affects Versions: 8.1 Environment: Mainframe Jboss 7.1.1 Reporter: Gautam Banerjee Assignee: Steven Hawkins When we try to login to teiid programmatically through datasource, we are having problem with username having special characters. We are encoding the special character as per url encoding eg : username %xyz is encoded as %25xyz but teiid does not decode the special character while passing username. So the username passed by teiid is %25xyz which fails authentication as the actual username is %xyz -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2799) Import metadata from Object translator is not defining primary key

by Van Halbert (JIRA)

Van Halbert created TEIID-2799: ---------------------------------- Summary: Import metadata from Object translator is not defining primary key Key: TEIID-2799 URL: https://issues.jboss.org/browse/TEIID-2799 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.4.1 Reporter: Van Halbert Assignee: Van Halbert Priority: Minor The infinispan implementation of the object translator getMetadata is not defining the primary key. If the resource-adapter has defined it, it should expose it. This key is important for push-down capability. The user could define this after the fact (i.e, in dynamic vdb or in designer), but from a usability stand point, it would be better if the translator exposed it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2798) Add creation of view when exposing metadata via Object translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2798?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2798: --------------------------------------- > But out of this, need to fix the metadata so that it doesn't include the Object source in the source table. It could be useful if the object was being returned to the client, but I don't think it should be added by default. What do you think? I think the current behavior is fine as the default. Generally speaking unless the object is a simple bean, then the members are going to be more complicated than just built-in type scalar values, which may require further use of an objecttable to denormalize/pull fields. > Add creation of view when exposing metadata via Object translator > ----------------------------------------------------------------- > > Key: TEIID-2798 > URL: https://issues.jboss.org/browse/TEIID-2798 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > > When the metadata is exposed for the java object via the Object translator, a view should also be created using a template similar to: > SELECT > t.{pkKeyField}, o.{colname}, o.{colname} > FROM Order > {ObjectSourceTable} as T, > OBJECTTABLE('x' PASSING T.{ObjectTypeName}Object as x COLUMNS > {colname} {type} 'teiid_row.{colname}', ….) as o > where > {pkKeyField} is the primary key column to the cache > {ObjectSourceTable} is the source table imported above > {ObjectTypeName} is the column added in {ObjectSourceTable} to reference the cache object > {colname} is the name of the columns that have “get” methods, see the {ObjectSourceTable} for columns to use > {type} is the data type for this column -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2798) Add creation of view when exposing metadata via Object translator

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2798?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2798: ------------------------------------ I took that to mean that the path to column will be used when deriving value from the Object source defined (referenced) in by the OBJECTTABLE function. So I really missed that. And after testing, you are right, don't need to model the object column or need to use OBJECTTABLE. But out of this, need to fix the metadata so that it doesn't include the Object source in the source table. It could be useful if the object was being returned to the client, but I don't think it should be added by default. What do you think? > Add creation of view when exposing metadata via Object translator > ----------------------------------------------------------------- > > Key: TEIID-2798 > URL: https://issues.jboss.org/browse/TEIID-2798 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > > When the metadata is exposed for the java object via the Object translator, a view should also be created using a template similar to: > SELECT > t.{pkKeyField}, o.{colname}, o.{colname} > FROM Order > {ObjectSourceTable} as T, > OBJECTTABLE('x' PASSING T.{ObjectTypeName}Object as x COLUMNS > {colname} {type} 'teiid_row.{colname}', ….) as o > where > {pkKeyField} is the primary key column to the cache > {ObjectSourceTable} is the source table imported above > {ObjectTypeName} is the column added in {ObjectSourceTable} to reference the cache object > {colname} is the name of the columns that have “get” methods, see the {ObjectSourceTable} for columns to use > {type} is the data type for this column -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2780) Provide Translator for Apache SOLR

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2780?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2780. --------------------------------- Labels: Alpha1 Alpha2 (was: ) Resolution: Done * Add limited support for some basic functions. * Added functionality to allow bulk insert. This should come tin handy if users trying to push other source's data into SOLR using "INSERT INTO ...SELECT" commands, where it batches multiple inserts in single call. * Added Documentation at https://docs.jboss.org/author/display/TEIID/Apache+SOLR+Translator Future TODO: * Support for Aggegate Functions (SUM, AVG, COUNT ..) * Solr supports one kind of JOIN that can be used as sub-query IN expression. > Provide Translator for Apache SOLR > ---------------------------------- > > Key: TEIID-2780 > URL: https://issues.jboss.org/browse/TEIID-2780 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha1, Alpha2 > Fix For: 8.7 > > > Create a translator for querying Apache SOLR > http://lucene.apache.org/solr/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2790) Add more options for costing during import

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2790?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2790: --------------------------------------- Added an initial checkin with two new jdbc import properties: useAnyIndexCardinality (defaults to false) - when importKeys or importIndex is enable and the database does not support statistical indexes (off-hand oracle is the only one that I know of that does) then we'll use the maximum cardinality reported on the other indexes as the table cardinality. For databases such as mysql this is typically sufficient to determine the cardinality provided an index of any kind exists. importStatistics (defaults to false) - initially supported by only oracle and mysql. For tables that do not have a cardinality set (which may be due to not using the useAnyIndexCarinality setting or not importing indexes) we'll use the database statistically information to determine the cardinality. We'll look at adding the column statistics at a later time. > Add more options for costing during import > ------------------------------------------ > > Key: TEIID-2790 > URL: https://issues.jboss.org/browse/TEIID-2790 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector, Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7 > > > With many jdbc sources full cardinality is reported from the index info for non statistical indexes (such as mysql). This should be used to set the cardinality of the table. Failing that there should be an option to use an aggregate call or other source stats. > This is not quite the same as TEIID-245 as it's happening at import time, but the two do overlap. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2797) buffer full requests is not cleaned up properly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2797?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2797: --------------------------------------- Since TEIID-2461 a timeout/slowdown approach has been used, so it's not necessary to hold the buffer full plans separately. In general we should consider using the timeout mechanism to regulate the flow of information into the buffer manager. > buffer full requests is not cleaned up properly > ----------------------------------------------- > > Key: TEIID-2797 > URL: https://issues.jboss.org/browse/TEIID-2797 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 7.7.9, 8.7 > > Attachments: TEIID-2797.patch > > > buffer full plans are held as the full work item, but we are cleaning them up by the request id. This means that the full plans will accumulate over time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2798) Add creation of view when exposing metadata via Object translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2798?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2798: --------------------------------------- The documentation does mention "All other columns will have their name in source (which defaults to the column name) interpreted as the path to the column value from the primary object." But it certainly can be made more clear that the example is just an that and not required for usage. > Add creation of view when exposing metadata via Object translator > ----------------------------------------------------------------- > > Key: TEIID-2798 > URL: https://issues.jboss.org/browse/TEIID-2798 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > > When the metadata is exposed for the java object via the Object translator, a view should also be created using a template similar to: > SELECT > t.{pkKeyField}, o.{colname}, o.{colname} > FROM Order > {ObjectSourceTable} as T, > OBJECTTABLE('x' PASSING T.{ObjectTypeName}Object as x COLUMNS > {colname} {type} 'teiid_row.{colname}', ….) as o > where > {pkKeyField} is the primary key column to the cache > {ObjectSourceTable} is the source table imported above > {ObjectTypeName} is the column added in {ObjectSourceTable} to reference the cache object > {colname} is the name of the columns that have “get” methods, see the {ObjectSourceTable} for columns to use > {type} is the data type for this column -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2798) Add creation of view when exposing metadata via Object translator

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2798?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2798: ------------------------------------ I didn't realize that the Object didn't need to be modeled in order to query the object. So what your saying is the documentation isn't complete on the options on how to use the Object translator. > Add creation of view when exposing metadata via Object translator > ----------------------------------------------------------------- > > Key: TEIID-2798 > URL: https://issues.jboss.org/browse/TEIID-2798 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > > When the metadata is exposed for the java object via the Object translator, a view should also be created using a template similar to: > SELECT > t.{pkKeyField}, o.{colname}, o.{colname} > FROM Order > {ObjectSourceTable} as T, > OBJECTTABLE('x' PASSING T.{ObjectTypeName}Object as x COLUMNS > {colname} {type} 'teiid_row.{colname}', ….) as o > where > {pkKeyField} is the primary key column to the cache > {ObjectSourceTable} is the source table imported above > {ObjectTypeName} is the column added in {ObjectSourceTable} to reference the cache object > {colname} is the name of the columns that have “get” methods, see the {ObjectSourceTable} for columns to use > {type} is the data type for this column -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2797) buffer full requests is not cleaned up properly

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2797?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2797: --------------------------------- Fix Version/s: 7.7.9 > buffer full requests is not cleaned up properly > ----------------------------------------------- > > Key: TEIID-2797 > URL: https://issues.jboss.org/browse/TEIID-2797 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 7.7.9, 8.7 > > Attachments: TEIID-2797.patch > > > buffer full plans are held as the full work item, but we are cleaning them up by the request id. This means that the full plans will accumulate over time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2014