May 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-529) Simplify ConnectorCapabilities

by Steven Hawkins (JIRA)

Simplify ConnectorCapabilities ------------------------------ Key: TEIID-529 URL: https://jira.jboss.org/jira/browse/TEIID-529 Project: Teiid Issue Type: Quality Risk Components: Connector API Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 In making the other connector changes I would like to open a dialog on refining the connector capabilities mechanism. At a minimum I would like to just use basicconnectorcapabilities rather than having the connectorcapabilities interface, which noonne is told to implement directly anyway. A more aggressive approach would be to use the same approach as dqp, a map with an enum key. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-572) Add direct support for bulk updates

by Steven Hawkins (JIRA)

Add direct support for bulk updates ----------------------------------- Key: TEIID-572 URL: https://jira.jboss.org/jira/browse/TEIID-572 Project: Teiid Issue Type: Feature Request Components: Connector API, Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 Our current approach to a jdbc preparedstatement batched update is to create an update command per batch row and allow the connector layer to determine if that can be collapsed again into a batched operation to the source. It would be better to send a single command with batched parameters so that we don't waste type translating the same command n times. The approach should be the same for insert/update/delete. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Resolved: (TEIID-124) insert with query should be supported at the connector level

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-124?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-124. ---------------------------------- Resolution: Done Added the capability supportsInsertWithQueryExpression and appropriate changes to the planner and connector api - inserts now take an IValueSource rather than just a list of expressions as values. > insert with query should be supported at the connector level > ------------------------------------------------------------ > > Key: TEIID-124 > URL: https://jira.jboss.org/jira/browse/TEIID-124 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #25005: Insert into with a query is now supported at the query level and is the ANSI standard way of representing select into. Insert with a query should become the dominant concept rather than select into, and it should be supported through the connector layer so that same source operations do not have the overhead of a select into. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-525) Eliminate redundencies in capabilities override and existing binding properties.

by Steven Hawkins (JIRA)

Eliminate redundencies in capabilities override and existing binding properties. -------------------------------------------------------------------------------- Key: TEIID-525 URL: https://jira.jboss.org/jira/browse/TEIID-525 Project: Teiid Issue Type: Quality Risk Components: Connector API Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 The max in size can now be specified by both an override and an existing setting for some connector types (such as JDBC). We should probably just rely on the override in cases like this. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-551) XML-Relational relational request-respons joins fail and produce no result.

by John Doyle (JIRA)

XML-Relational relational request-respons joins fail and produce no result. --------------------------------------------------------------------------- Key: TEIID-551 URL: https://jira.jboss.org/jira/browse/TEIID-551 Project: Teiid Issue Type: Bug Components: XML Connector Affects Versions: 6.0.0 Reporter: John Doyle Assignee: John Doyle Fix For: 6.1.0 The ResponseIn and Responseout columns have special Role properties that identify them to the connector. Designer validation changes disallow the old role values of Response In and Response Out because of the space. The connector has to change to recognize the new values without the space. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Closed: (TEIID-375) The XML connector consumes too much memory, large documents cause OutOf Memory errors.

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-375?page=com.atlassian.jira.plug... ] John Doyle closed TEIID-375. ---------------------------- Resolution: Done Duplicates JBEDSP-648 > The XML connector consumes too much memory, large documents cause OutOf Memory errors. > -------------------------------------------------------------------------------------- > > Key: TEIID-375 > URL: https://jira.jboss.org/jira/browse/TEIID-375 > Project: Teiid > Issue Type: Quality Risk > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: John Doyle > Fix For: 6.1.0 > > > See the link to the issue tracket ticket. > In this POC, the customer has many such large XML documents. A fix for this memory problem probably requires that the connector or the connector cache run in it's own process so that memory can be managed without regard to the server process. > The solution should: > provide better control over the memory parameters of the connector > reduce the amount of memory required to parse the document (streaming) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-569) The exporting a connector binding via adminapi expected the argument to have a host | vm to identify the binding

by Van Halbert (JIRA)

The exporting a connector binding via adminapi expected the argument to have a host | vm to identify the binding ----------------------------------------------------------------------------------------------------------------- Key: TEIID-569 URL: https://jira.jboss.org/jira/browse/TEIID-569 Project: Teiid Issue Type: Bug Components: AdminApi, Server Affects Versions: 6.1.0 Reporter: Van Halbert Assignee: Van Halbert Fix For: 6.1.1 The exporting of the connector binding was expecting the argument to contain the host | vm to identify the binding. This shouldn't be the case. All that is needed is the name of the binding, without regard to host or vm. (Paul and Warren agree). -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-470) New AdminAPI method needed to support deploying a Connector Binding to a VM

by Van Halbert (JIRA)

New AdminAPI method needed to support deploying a Connector Binding to a VM --------------------------------------------------------------------------- Key: TEIID-470 URL: https://jira.jboss.org/jira/browse/TEIID-470 Project: Teiid Issue Type: Feature Request Components: AdminApi Affects Versions: 6.1.0 Reporter: Van Halbert Assignee: Van Halbert Add a method that enables the deployment of one or more connector bindings to one or more vms. And the opposite, remove from deployment, will be needed. This is currently needed to support command line importvdb option that allows the deployment of the bindings associated with the imported vdb. Also, this will be needed in the future by the newly developed configuration tool. -- 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, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-493) Define a new modeling construct that can create a defaulted parameter.

by John Doyle (JIRA)

Define a new modeling construct that can create a defaulted parameter. ---------------------------------------------------------------------- Key: TEIID-493 URL: https://jira.jboss.org/jira/browse/TEIID-493 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: John Doyle Assignee: Steven Hawkins Priority: Minor I would like to be able to define on a physical model a defaulted parameter value for a column, much like an access pattern with a default value. At runtime the default value would be sent as a parameter if the user did not supply a value in the query. The use case that brought this to mind is the Salesforce connector. Each Salesforce object exposes a isDeleted column and since most uses of the connector do not want to see deleted objects, the user will have to know that they need to have isDeleted=false in the query. Having a 'defaulted access pattern' would allow us to encapsulate this SF API leakage better. -- 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, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (TEIID-547) Audit messages in the system log file

by Ramesh Reddy (JIRA)

Audit messages in the system log file ------------------------------------- Key: TEIID-547 URL: https://jira.jboss.org/jira/browse/TEIID-547 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Reporter: Ramesh Reddy Priority: Minor Fix For: 6.1.1 by default when server started, the audit log messages are being shown in server log file. These need to be correctly re-directed to audit log files. -- 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, 1 month

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2009