[ https://jira.jboss.org/jira/browse/TEIID-161?page=com.atlassian.jira.plug... ]
Steven Hawkins resolved TEIID-161.
----------------------------------
Resolution: Done
moved common type to runtime type and runtime type to desired type conversions above the connector level into connector work item.
> Move common type conversion logic into a centralized facility for connectors
> ----------------------------------------------------------------------------
>
> Key: TEIID-161
> URL: https://jira.jboss.org/jira/browse/TEIID-161
> Project: Teiid
> Issue Type: Sub-task
> Components: Connector API, Query Engine
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 6.0.0
>
>
> Since we allow the flexibility for physical model types to not actually match source type (as in not simply the closest runtime type), every connector is currently responsible for not only converting to a known runtime type but potentially converting to the desired runtime type. This logic has been encapsulated behind the typefacility converttoruntimetype and transformvalue. It would be nice however to automatically handle the known conversions.
--
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
Missing Message Key After Server Failed to Start
------------------------------------------------
Key: TEIID-391
URL: https://jira.jboss.org/jira/browse/TEIID-391
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 6.0.0
Reporter: Ted Jones
Assignee: Steven Hawkins
My server failed to start due to my database connectivity going down and the following error was logged:
Mar 02, 2009 16:23:22.399 [RegistryUpdate6|0] ERROR <RESOURCE_POOLING|0> <Missing message for key "WorkerPool.uncaughtException" in: com.metamatrix.common.i18n>
java.lang.IllegalStateException: Cache not in STARTED state!
--
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-364?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIID-364:
---------------------------------
Component/s: Console
(was: Misc. Connectors)
Fix Version/s: 6.1.0
(was: 6.0.0)
Assignee: (was: Jerry Helbling)
> Is Immutable should be an expert property
> -----------------------------------------
>
> Key: TEIID-364
> URL: https://jira.jboss.org/jira/browse/TEIID-364
> Project: Teiid
> Issue Type: Bug
> Components: Console
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Priority: Optional
> Fix For: 6.1.0
>
>
> Is immutable is displayed as a non-expert property, it seems better to have it as an expert property.
--
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-61?page=com.atlassian.jira.plugi... ]
Steven Hawkins closed TEIID-61.
-------------------------------
Resolution: Done
fix applied to ResolverUtil.resolveNullLiterals
> Fix for exception when CASE resolves to NULL.
> ---------------------------------------------
>
> Key: TEIID-61
> URL: https://jira.jboss.org/jira/browse/TEIID-61
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 6.0.0
> Reporter: Jerry Helbling
> Assignee: Jerry Helbling
> Priority: Minor
> Fix For: 6.0.0
>
>
> Refer to internal case 232624.
--
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
Console log is using windows based path deliminters, causing the log location to not work right on linux
--------------------------------------------------------------------------------------------------------
Key: TEIID-389
URL: https://jira.jboss.org/jira/browse/TEIID-389
Project: Teiid
Issue Type: Bug
Components: Console
Affects Versions: 6.0.0
Reporter: Van Halbert
Assignee: Van Halbert
The console defines the location of the logfile:
"..\\log\\console_%VM_NAME%.log";
using windows path delimiters.
--
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-375?page=com.atlassian.jira.plug... ]
Work on TEIID-375 started by John Doyle.
> 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