February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Closed: (TEIID-246) Create a ZipFile utility method for finding all entries that meet the regex expression

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-246?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-246. -------------------------------- > Create a ZipFile utility method for finding all entries that meet the regex expression > -------------------------------------------------------------------------------------- > > Key: TEIID-246 > URL: https://jira.jboss.org/jira/browse/TEIID-246 > Project: Teiid > Issue Type: Feature Request > Components: Common > Affects Versions: 6.0.0 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 6.0.0 > > > Need the ability to search a jar file and find all entries that meet the specified criteria. This criteria is expressed using the java.util.regex expression syntax. -- 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] Updated: (TEIID-246) Create a ZipFile utility method for finding all entries that meet the regex expression

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-246?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-246: --------------------------------- Component/s: Common > Create a ZipFile utility method for finding all entries that meet the regex expression > -------------------------------------------------------------------------------------- > > Key: TEIID-246 > URL: https://jira.jboss.org/jira/browse/TEIID-246 > Project: Teiid > Issue Type: Feature Request > Components: Common > Affects Versions: 6.0.0 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 6.0.0 > > > Need the ability to search a jar file and find all entries that meet the specified criteria. This criteria is expressed using the java.util.regex expression syntax. -- 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] Updated: (TEIID-247) Add support for array types

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-247?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-247: --------------------------------- Component/s: Connector API JDBC Driver Query Engine > Add support for array types > --------------------------- > > Key: TEIID-247 > URL: https://jira.jboss.org/jira/browse/TEIID-247 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Driver, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.x > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Add language support for array types. Push down and client support should also be added. -- 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] Updated: (TEIID-247) Add support for array types

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-247?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-247: --------------------------------- Fix Version/s: 6.x Affects Version/s: 6.0.0 Affects: [Documentation (Ref Guide, User Guide, etc.), Release Notes] > Add support for array types > --------------------------- > > Key: TEIID-247 > URL: https://jira.jboss.org/jira/browse/TEIID-247 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Driver, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.x > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Add language support for array types. Push down and client support should also be added. -- 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] Closed: (TEIID-248) Add function for calculating timestamp based on Unix time (like MySQL FROM_UNIXTIME function)

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-248?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-248. -------------------------------- > Add function for calculating timestamp based on Unix time (like MySQL FROM_UNIXTIME function) > --------------------------------------------------------------------------------------------- > > Key: TEIID-248 > URL: https://jira.jboss.org/jira/browse/TEIID-248 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.0.0 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Add a function to take a value in seconds and return a timestamp value. Client use case of storing the unix time created a need for a way to convert the value to a timestamp. A workaround is available by using TIMESTAMPADD to add the seconds recorded in the unix time value to a timestamp value created from January 1, 1970 GMT. -- 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] Updated: (TEIID-249) Need well-known multi-payload container

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-249?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-249: --------------------------------- Component/s: Connector API Query Engine > Need well-known multi-payload container > --------------------------------------- > > Key: TEIID-249 > URL: https://jira.jboss.org/jira/browse/TEIID-249 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Driver, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #21547: Currently it's up to users to build some container and extend connectors if they want to pass multiple payloads through the system. Would probably be better if we provided such a container, JDBC connectors were aware of it, and our commandPayload() functions worked with it. -- 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] Updated: (TEIID-249) Need well-known multi-payload container

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-249?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-249: --------------------------------- Component/s: JDBC Driver Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, Release Notes] Complexity: Medium > Need well-known multi-payload container > --------------------------------------- > > Key: TEIID-249 > URL: https://jira.jboss.org/jira/browse/TEIID-249 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #21547: Currently it's up to users to build some container and extend connectors if they want to pass multiple payloads through the system. Would probably be better if we provided such a container, JDBC connectors were aware of it, and our commandPayload() functions worked with it. -- 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] Updated: (TEIID-316) Repackage connector api classes

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-316?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-316: --------------------------------- Parent: TEIID-164 Issue Type: Sub-task (was: Task) > Repackage connector api classes > ------------------------------- > > Key: TEIID-316 > URL: https://jira.jboss.org/jira/browse/TEIID-316 > Project: Teiid > Issue Type: Sub-task > Components: Connector API > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > > We moved several classes into the connector api from the jbdc connector, common, and dqp. These need to be repackaged. The only chance for a customer impact is with the jdbc connector extension class ValueTranslator. -- 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] Closed: (TEIID-316) Repackage connector api classes

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-316?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-316. -------------------------------- These classes have now been repackaged further as com.metamatrix.connector > Repackage connector api classes > ------------------------------- > > Key: TEIID-316 > URL: https://jira.jboss.org/jira/browse/TEIID-316 > Project: Teiid > Issue Type: Sub-task > Components: Connector API > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > > We moved several classes into the connector api from the jbdc connector, common, and dqp. These need to be repackaged. The only chance for a customer impact is with the jdbc connector extension class ValueTranslator. -- 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] Updated: (TEIID-250) Enable Axis data compression in SFDC Connector, per SFDC API guidelines

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-250?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-250: --------------------------------- Component/s: Salesforce Connector Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 Complexity: Low > Enable Axis data compression in SFDC Connector, per SFDC API guidelines > ----------------------------------------------------------------------- > > Key: TEIID-250 > URL: https://jira.jboss.org/jira/browse/TEIID-250 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 6.0.0 > Environment: MetaMatrix 5.5.2 with patch 0037/SFDC GA connector > Reporter: Greg Haber > Assignee: John Doyle > Fix For: 6.1.0 > > > The SFDC doc includes a set of performance guidelines for using their API (http://blog.sforce.com/sforce/2005/04/performance_tip.html). One of the guidelines: > Use compression, unless you have an OC45 connection into the back of your machine, compression will help reduce transmission times, the Sforce API supports gzip and deflate compression for both request and response. > does not look like it has been implemented in our connector. In theory, this will be a big optimization when returning large data sets, as is the case at Genentech. This is also a trivial optimization to implement, so we should at least try this out and see what the impact is. > The process for enabling this is described on http://wiki.apexdevnet.com/index.php/Compression_with_Axis_1.3 - essentially, you subclass the SforceServiceLocator class in the salesforce.jar to set a few Axis-specific properties (complete code for subclass is at the link), and then in our connector (in ConnectionImpl) we call this subclass instead of calling the SforceServiceLocator directly, as we are doing today. > This is a very low hanging fruit with a big upside - please implement soon. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2009