December 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1877) CLONE - Teiid Designer (DTP) Execute All sends all queries at once to Server - Server should handle these bulk queries

by Steven Hawkins (Created) (JIRA)

CLONE - Teiid Designer (DTP) Execute All sends all queries at once to Server - Server should handle these bulk queries ---------------------------------------------------------------------------------------------------------------------- Key: TEIID-1877 URL: https://issues.jboss.org/browse/TEIID-1877 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1.1 Reporter: Paul Nittel Assignee: Steven Hawkins Fix For: 8.0 When a series of SELECT statements are sent to the server via Execute All, the server should execute the SQL statements in appropriate fashion (as when the queries are directed to other RDBMSes, such as Oracle). At present, no exceptions are thrown, but the queries fail to execute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIID-987) Problem regarding how often availability is called on the Facet

by Steven Hawkins (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-987?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-987: -------------------------------------- Is this issue still valid? > Problem regarding how often availability is called on the Facet > --------------------------------------------------------------- > > Key: TEIID-987 > URL: https://issues.jboss.org/browse/TEIID-987 > Project: Teiid > Issue Type: Bug > Components: Jopr Plugin > Affects Versions: 7.0 > Reporter: Van Halbert > Assignee: Ted Jones > Fix For: 8.0 > > > There's a problem where the Facet (resource) availability is being checked about 5 times consecutively for every resource. There is an embedded jopr issue regarding this issue (EMBJOPR-129) > However, until this can be fixed, we might have to add a system property to handle how often to allow availability to be checked to limit the calls. Otherwise, this could a large processing overhead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIID-1873) Security documentation does not provide adequate information to integrate additional domains for authentication

by Steven Hawkins (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1873?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1873. ----------------------------------- Fix Version/s: 7.6.1 8.0 Resolution: Done Updated the security chapter with more on the properties used to set the domains. > Security documentation does not provide adequate information to integrate additional domains for authentication > --------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1873 > URL: https://issues.jboss.org/browse/TEIID-1873 > Project: Teiid > Issue Type: Bug > Components: Documentation > Affects Versions: 7.4.1 > Reporter: Marc Shirley > Fix For: 7.6.1, 8.0 > > > The Administration Guide mentions modifying/adding domains that Teiid use for authentication, but never mentions how to accomplish it. There should be information to edit the 'teiid-jboss-beans.xml' file to add/edit domains in the "securityDomains" property in order for users to easily modify authentication according to their security needs. > > <property name="securityDomains">teiid-security</property> > <property name="adminSecurityDomain">jmx-console</property> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIID-1873) Security documentation does not provide adequate information to integrate additional domains for authentication

by Van Halbert (Moved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1873?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-3669 to TEIID-1873: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1873 (was: SOA-3669) Affects Version/s: 7.4.1 (was: 5.2.0 GA) Component/s: Documentation (was: Documentation) (was: EDS) Security: (was: Public) > Security documentation does not provide adequate information to integrate additional domains for authentication > --------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1873 > URL: https://issues.jboss.org/browse/TEIID-1873 > Project: Teiid > Issue Type: Bug > Components: Documentation > Affects Versions: 7.4.1 > Reporter: Marc Shirley > > The Data Services Administration Guide mentions modifying/adding domains that EDS/Teiid use for authentication, but never mentions how to accomplish it. There should be information to edit the 'teiid-jboss-beans.xml' file to add/edit domains in the "securityDomains" property in order for users to easily modify EDS authentication according to their security needs. > > <property name="securityDomains">teiid-security</property> > <property name="adminSecurityDomain">jmx-console</property> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIID-1873) Security documentation does not provide adequate information to integrate additional domains for authentication

by Van Halbert (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1873?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-1873: ------------------------------- Description: The Administration Guide mentions modifying/adding domains that Teiid use for authentication, but never mentions how to accomplish it. There should be information to edit the 'teiid-jboss-beans.xml' file to add/edit domains in the "securityDomains" property in order for users to easily modify authentication according to their security needs. <property name="securityDomains">teiid-security</property> <property name="adminSecurityDomain">jmx-console</property> was: The Data Services Administration Guide mentions modifying/adding domains that EDS/Teiid use for authentication, but never mentions how to accomplish it. There should be information to edit the 'teiid-jboss-beans.xml' file to add/edit domains in the "securityDomains" property in order for users to easily modify EDS authentication according to their security needs. <property name="securityDomains">teiid-security</property> <property name="adminSecurityDomain">jmx-console</property> > Security documentation does not provide adequate information to integrate additional domains for authentication > --------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1873 > URL: https://issues.jboss.org/browse/TEIID-1873 > Project: Teiid > Issue Type: Bug > Components: Documentation > Affects Versions: 7.4.1 > Reporter: Marc Shirley > > The Administration Guide mentions modifying/adding domains that Teiid use for authentication, but never mentions how to accomplish it. There should be information to edit the 'teiid-jboss-beans.xml' file to add/edit domains in the "securityDomains" property in order for users to easily modify authentication according to their security needs. > > <property name="securityDomains">teiid-security</property> > <property name="adminSecurityDomain">jmx-console</property> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIID-1866) Default Salesforce URL in teiid-connector-salesforce.rar needs update to SF v22

by Johnathon Lee (Created) (JIRA)

Default Salesforce URL in teiid-connector-salesforce.rar needs update to SF v22 ------------------------------------------------------------------------------- Key: TEIID-1866 URL: https://issues.jboss.org/browse/TEIID-1866 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 7.4 Reporter: Johnathon Lee Assignee: Ramesh Reddy Fix For: 7.6.1, 8.0 The salesforce jars were updated using v22 of the salesforce WSDL, however the default URL in teiid-connector.salesforce.rar was not updated. The URL config-property in ra.xml should be changed to: <config-property-value>https://www.salesforce.com/services/Soap/u/22.0</config-property-value> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] Created: (TEIID-1323) Add support for pushdown of non-literal procedure parameter expressions.

by Steven Hawkins (JIRA)

Add support for pushdown of non-literal procedure parameter expressions. ------------------------------------------------------------------------ Key: TEIID-1323 URL: https://jira.jboss.org/browse/TEIID-1323 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.2 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 We are forcing all push-down procedure arguments to be literals (for simplicity), when all expressions should be allowed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

[JBoss JIRA] (TEIID-3) Allow connectors to specify function capability for specific type signature

by Steven Hawkins (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-3?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins commented on TEIID-3: ------------------------------------ Further work could be done such as providing a built-in mechanism for the translator to support all implicit conversions. > Allow connectors to specify function capability for specific type signature > --------------------------------------------------------------------------- > > Key: TEIID-3 > URL: https://issues.jboss.org/browse/TEIID-3 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.0 > > > Defect Tracker #15144: Connectors should be able to specify pushdown capability for particular type signatures of a function. We have seen several cases where this would be helpful. This can probably be done without changing current Connector API by allowing the ConnectorCapabilities function method to return method signatures instead of just function names. For example, "mod(integer, integer)" instead of just "mod". Needs some further design still. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3) Allow connectors to specify function capability for specific type signature

by Steven Hawkins (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-3?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins resolved TEIID-3. -------------------------------- Assignee: Steven Hawkins Resolution: Partially Completed Added ExecutionFactory.supportsConvert to support specific convert signatures, but did not add a general typed based mechanism for other system functions as they generally only have a single form - or are highly related such as supporting several numeric types. Also pushdown functions have specific signatures that are set by the translator, so that case is covered as well. > Allow connectors to specify function capability for specific type signature > --------------------------------------------------------------------------- > > Key: TEIID-3 > URL: https://issues.jboss.org/browse/TEIID-3 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.0 > > > Defect Tracker #15144: Connectors should be able to specify pushdown capability for particular type signatures of a function. We have seen several cases where this would be helpful. This can probably be done without changing current Connector API by allowing the ConnectorCapabilities function method to return method signatures instead of just function names. For example, "mod(integer, integer)" instead of just "mod". Needs some further design still. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIID-1858) Misc. Salesforce Translator Issues (for SOA-P)

by Rick Wagner (Created) (JIRA)

Misc. Salesforce Translator Issues (for SOA-P) ---------------------------------------------- Key: TEIID-1858 URL: https://issues.jboss.org/browse/TEIID-1858 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 6.0.0 Reporter: Rick Wagner Assignee: Steven Hawkins Fix For: 7.6.1 Query the BusinessHours table imported from Salesforce, which contains columns with 'time' datatype. For example, the query: SELECT Name,CreatedDate,MondayStartTime FROM SFTest.salesforce.BusinessHours Results in: Error Code:ERR.003.029.0025 Message:Failed to transform String to Time. Expected format = hh:mm:ss for 08:00:00.000Z It looks like the code in QueryExecutionImpl.getCellDatum needs to handle translation of the salesforce time format Other issues: - nil string values will be returned as empty instead of null. - non-join criteria of the form column1 = column2 is rendered inappropriately (however it is not supported by SF we should look at restricting criteria support to literals) - IN predicate time/date/timestamp values are not formatted correctly - timezones are ignored on returned time/timestamp values. So unless the server is in the same timezone as the values (typically Z/GMT) the local value will be incorrect. - a timezone is not included on literal times, which has the same issue as above. - IS NULL support should be added using col = NULL -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2011