[JBoss JIRA] (TEIID-2175) document and possibly provide a workaround for 32-bit dates
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2175:
-------------------------------------
Summary: document and possibly provide a workaround for 32-bit dates
Key: TEIID-2175
URL: https://issues.jboss.org/browse/TEIID-2175
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 8.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
To have a more compact format Teiid is using a 32-bit serialized date. This is consistent with the jdbc spec as it allows for dates between 1900 and the end of 9999. Years prior to and after that range are allowed in java, so we make it explicit that these values may get truncated.
The workaround would be similar to the allow NAN property.
--
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, 1 month
[JBoss JIRA] (TEIID-2150) Allow procedures to be called with end defaultable inputs
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2150:
-------------------------------------
Summary: Allow procedures to be called with end defaultable inputs
Key: TEIID-2150
URL: https://issues.jboss.org/browse/TEIID-2150
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Affects Versions: 8.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
We should allow procedures to be called positionally and use default values for end parameters if they are not specified.
Condiser:
create foreign procedure proc (x integer, y string);
If you currently issue "call proc()", we'll assume named parameters and use "call proc(null, null)".
If you issue "call proc(1)", you'll get an exception. The new behavior would be to use "call proc(1, null)".
Of course something like "call proc('a')" would still result in an exception.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2180) Limiting source tables in dynamic VDBs using importer.excludeTables
by Samier Nadji (JIRA)
Samier Nadji created TEIID-2180:
-----------------------------------
Summary: Limiting source tables in dynamic VDBs using importer.excludeTables
Key: TEIID-2180
URL: https://issues.jboss.org/browse/TEIID-2180
Project: Teiid
Issue Type: Enhancement
Components: JDBC Connector
Affects Versions: 8.1
Reporter: Samier Nadji
Assignee: Steven Hawkins
JDBCMetdataProcessor.getColumns() calls metadata.getColumns() for all the tables even the excluded ones. The while loop to process the columns is what takes a long time.
Is it possible to change the code in JDBCMetdataProcessor.getColumns() to only get columns for the tables that are included in the tableMap? i.e. if an exclusion filter is specified, call metadata.getColumns() separately for each table.
--
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, 1 month
[JBoss JIRA] (TEIID-2148) Add enhancements to more efficiently handle large documents/files
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2148:
-------------------------------------
Summary: Add enhancements to more efficiently handle large documents/files
Key: TEIID-2148
URL: https://issues.jboss.org/browse/TEIID-2148
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
The default strategy of Teiid is to copy the inputstream sent back from CXF (or anything returning a Source/DataSource). To reduce latency this copy should be performed during read, rather than all at once.
Ideally we should investigate the CXF internals to see if we can get a handle to a temp file, which would completely eliminate the need for a copy. Alternatively or in addition to this approach, the ws translator should offer an option to return a single use SQL/XML value to the engine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month