[JBoss JIRA] (TEIID-2485) Remove the resteasy patch thats no longer needed in EAP 6.1 ER5
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2485?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2485:
---------------------------------------
After talking with Ramesh, there are two approaches here. The first would be to fork the kit so there is both a community and a product kit. The other specific to this issue is to make the resteasy patch a separate download and or upgrade or resteasy for the community user to do.
> Remove the resteasy patch thats no longer needed in EAP 6.1 ER5
> ---------------------------------------------------------------
>
> Key: TEIID-2485
> URL: https://issues.jboss.org/browse/TEIID-2485
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 8.4
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 8.4.1
>
>
> The resteasy patch thats provided in the kit is no longer needed. As of EAP 6.1 ER5, resteasy has been upgraded to 2.3.6, and resolves RESTEASY-812 issue.
> I have verified the fix and have several EAP 6.1 ER5 servers running with Teiid 8.4 alpha without the patch applied.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2390) Improve xml/json production
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2390?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2390:
----------------------------------
Fix Version/s: 8.4.1
(was: 8.4)
> Improve xml/json production
> ---------------------------
>
> Key: TEIID-2390
> URL: https://issues.jboss.org/browse/TEIID-2390
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4.1
>
>
> The current xml/json logic can produce a lot of intermediate results that are recopied and can result in a slower performance for larger documents.
> The logic could allow for nested evaluations to delay creating their full string forms or simply allow the return values to remain appendable rather than requiring full copies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2514) Switch to AS 7 consults only first multi-source source during getMetadata() processing
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2514?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2514.
-----------------------------------
Resolution: Done
Updated the metadata loading for both the server and embedded.
> Switch to AS 7 consults only first multi-source source during getMetadata() processing
> --------------------------------------------------------------------------------------
>
> Key: TEIID-2514
> URL: https://issues.jboss.org/browse/TEIID-2514
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.1
> Reporter: Tim Bruce
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> In a multi-source VDB model, the ExecutionFactory getMetadata() processing is driven only within the context of the first source that is defined in the multi-source model. If this data source is unavailable, the VDB model is not deployed. In prior releases, Teiid would redrive the getMetadata() process within the context of each of the defined data sources (first to last) until metadata is returned or the list of data sources is exhausted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2381) Expanded source hint support
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2381?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2381:
----------------------------------
Fix Version/s: 8.4.1
(was: 8.4)
Pushing this to 8.4.1 as it will not make it in for CR1.
> Expanded source hint support
> ----------------------------
>
> Key: TEIID-2381
> URL: https://issues.jboss.org/browse/TEIID-2381
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4.1
>
> Attachments: HintsExecutionFactory.java, RandomExecutionFactory.java, RandomNumberStoredProcedureExecution.java, SysviewHintsExecutionTest.java
>
>
> We currently look at the source hint in only the root user query (not in subqueries nor the with clause) and only consider it in a very narrow set of circumstances when it's used in a view.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2502) Oracle Struct Serialization Error
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2502?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2502:
----------------------------------
Summary: Oracle Struct Serialization Error (was: org.teiid.net.socket.SingleInstanceCommunicationException)
Issue Type: Enhancement (was: Bug)
Fix Version/s: 8.5
Priority: Major (was: Critical)
Given the number of workarounds (custom translator, udf, or even use of OBJECTTABLE with the javascript or other capable binding to wrap the values as a SerialClob) and this effectively being new type handling, marking this as a major enhancement rather than a critical bug.
A related bug/quality risk would be to more gracefully handle these situations the data stream has not yet actually become compromised, we could trigger sending the client a very generic exception message that would be handled by the base communication layer.
Given the short time remaining for 8.4, putting into 8.4.1.
> Oracle Struct Serialization Error
> ---------------------------------
>
> Key: TEIID-2502
> URL: https://issues.jboss.org/browse/TEIID-2502
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.2
> Environment: centos 6.3
> Reporter: luca gioppo
> Assignee: Steven Hawkins
> Fix For: 8.5
>
> Attachments: ora.patch
>
>
> I'm issuing a query (a simple select * from table) on a VDB's table that contains a geometric column from oracle spatial.
> I'm getting the following error in SquirrelSQL
> Error: org.teiid.net.socket.SingleInstanceCommunicationException
> SQLState: 08S01
> ErrorCode: 0
> Afterwards the connection is broken and I cannot access any other table and have to reconnect since I get:
> Error: Error Code:TEIID20013 Message:Error Code:TEIID20013 Message:java.net.SocketException: Socket closed
> SQLState: TEIID20013
> ErrorCode: 0
> I'm trying to access a SDO table and a geometry type column, but hoped that TEIID could read it as a BLOB without caring about the real type.
> Probably it doesn't like it too much.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months