[ https://jira.jboss.org/jira/browse/TEIID-499?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIID-499:
---------------------------------
Component/s: JDBC Connector
Fix Version/s: 6.x
Affects Version/s: 6.x
Complexity: High
This is actually a difficult feature. Our supported format/parsing grammars are based upon support in Java. Each database has it's own grammar. Translation is quite a bit of work. It may be better to introduce another parse/format argument(s) that is the pushdown form.
> pushdown of parsedate, parsetime, parsetimestamp
> ------------------------------------------------
>
> Key: TEIID-499
> URL: https://jira.jboss.org/jira/browse/TEIID-499
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector
> Affects Versions: 6.x
> Reporter: Marc Shirley
> Fix For: 6.x
>
>
> Client requesting pushdown of parsedate, parsetime, parsetimestamp functions.
--
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
[ https://jira.jboss.org/jira/browse/TEIID-499?page=com.atlassian.jira.plug... ]
Steven Hawkins moved JBEDSP-1020 to TEIID-499:
----------------------------------------------
Project: Teiid (was: JBoss Enterprise Data Services Platform)
Key: TEIID-499 (was: JBEDSP-1020)
> pushdown of parsedate, parsetime, parsetimestamp
> ------------------------------------------------
>
> Key: TEIID-499
> URL: https://jira.jboss.org/jira/browse/TEIID-499
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Marc Shirley
>
> Client requesting pushdown of parsedate, parsetime, parsetimestamp functions.
--
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
BatchedUpdateCommands possible need evaluation before executing
---------------------------------------------------------------
Key: TEIID-494
URL: https://jira.jboss.org/jira/browse/TEIID-494
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.1.0
The BatchedUpdateNode does not attempt to evaluate commands (unless they originated from a prepared batch update). So a batch from a statement that contains a delayed evaluation function will fail.
--
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
createRequestMessage in MMStatement is incorrect
------------------------------------------------
Key: TEIID-495
URL: https://jira.jboss.org/jira/browse/TEIID-495
Project: Teiid
Issue Type: Bug
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 6.1.0
The check for submitting an invalid request will always fail for a batched update.
--
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
Expose the cache to connectors.
-------------------------------
Key: TEIID-444
URL: https://jira.jboss.org/jira/browse/TEIID-444
Project: Teiid
Issue Type: Feature Request
Components: Connector API
Reporter: John Doyle
Assignee: Ramesh Reddy
The XML-Relational connectors have historically had their own cache. I'm modifying the connectors to use JBoss cache and it would benefit users if this connector and other connectors with need of a cache could use the teiid cache to ease cache configuration and monitoring.
--
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
[ https://jira.jboss.org/jira/browse/TEIID-81?page=com.atlassian.jira.plugi... ]
Steven Hawkins reassigned TEIID-81:
-----------------------------------
Assignee: Steven Hawkins
> Cached plans are too big - can cause out of memory errors
> ---------------------------------------------------------
>
> Key: TEIID-81
> URL: https://jira.jboss.org/jira/browse/TEIID-81
> 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 #12381: Running the coper load tests led to this conclusion:
> Each cached plan takes on average 31 KB of memory.
> At 140 unique queries / connection and 128 connection this requires over 550 MB of memory just for the plan cache.
> Half of the memory was consumed by char[]. Over 10% of the memory was used by ElementSymbol objects.
--
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
[ https://jira.jboss.org/jira/browse/TEIID-81?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-81:
--------------------------------
Fix Version/s: 6.1.0
(was: 6.x)
Assignee: (was: Steven Hawkins)
> Cached plans are too big - can cause out of memory errors
> ---------------------------------------------------------
>
> Key: TEIID-81
> URL: https://jira.jboss.org/jira/browse/TEIID-81
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 6.x
> Reporter: Steven Hawkins
> Fix For: 6.1.0
>
>
> Defect Tracker #12381: Running the coper load tests led to this conclusion:
> Each cached plan takes on average 31 KB of memory.
> At 140 unique queries / connection and 128 connection this requires over 550 MB of memory just for the plan cache.
> Half of the memory was consumed by char[]. Over 10% of the memory was used by ElementSymbol objects.
--
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
[ https://jira.jboss.org/jira/browse/TEIID-215?page=com.atlassian.jira.plug... ]
Steven Hawkins reopened TEIID-215:
----------------------------------
Assignee: (was: John Doyle)
> Create a less memory intensive implementation of the XML-Relational File connector.
> ------------------------------------------------------------------------------------
>
> Key: TEIID-215
> URL: https://jira.jboss.org/jira/browse/TEIID-215
> Project: Teiid
> Issue Type: Feature Request
> Components: XML Connector
> Affects Versions: 6.0.0
> Reporter: John Doyle
> Fix For: 6.1.0
>
>
> The XML-Relational file connector as currently implemented DOMs the XML document before parsing for results. Large files can exhaust the memory allocated to the server. We need an implementation that can handle arbitrarily large XML 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
[ https://jira.jboss.org/jira/browse/TEIID-215?page=com.atlassian.jira.plug... ]
Steven Hawkins closed TEIID-215.
--------------------------------
Resolution: Duplicate Issue
> Create a less memory intensive implementation of the XML-Relational File connector.
> ------------------------------------------------------------------------------------
>
> Key: TEIID-215
> URL: https://jira.jboss.org/jira/browse/TEIID-215
> Project: Teiid
> Issue Type: Feature Request
> Components: XML Connector
> Affects Versions: 6.0.0
> Reporter: John Doyle
> Fix For: 6.1.0
>
>
> The XML-Relational file connector as currently implemented DOMs the XML document before parsing for results. Large files can exhaust the memory allocated to the server. We need an implementation that can handle arbitrarily large XML 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
Reference evaluation should not rely on exact reference instances
-----------------------------------------------------------------
Key: TEIID-492
URL: https://jira.jboss.org/jira/browse/TEIID-492
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Fix For: 6.1.0
Reference cloning currently returns the reference itself and all associated evaluation code relies upon setting values directly on these references. It would be far better - and allow for follow on features (plan caches that aren't restricted to a single session) - to have references be properly clonable and have evaluation based upon dynamic value contexts.
--
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