[JBoss JIRA] Created: (TEIID-691) Missing message for key "FileStoreageManager.batch_error" in: com.metamatrix.query.execution.i18n
by Paul Nittel (JIRA)
Missing message for key "FileStoreageManager.batch_error" in: com.metamatrix.query.execution.i18n
-------------------------------------------------------------------------------------------------
Key: TEIID-691
URL: https://jira.jboss.org/jira/browse/TEIID-691
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.2.0
Environment: Fedora 10, OpenJDK 1.6.0_0, teiid-embedded-6.2.0-SNAPSHOT (6/24/2009)
Reporter: Paul Nittel
Assignee: Steven Hawkins
While running BQT testing with the new (and improved) ctc, I encountered this as an error: "Missing message for key "FileStoreageManager.batch_error" in: com.metamatrix.query.execution.i18n". (We were expecting a result set of data.)
Not sure if the misspelling is carried from the code, but "storeage" is spelled "storage".
To reproduce, run this query (from RDBMS_Test_Queries_4500_TestQuery59) against the Oracle 11 BQT VDB: SELECT AVG(DISTINCT ByteNum) FROM BQT1.HugeA
--
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
16 years, 8 months
[JBoss JIRA] Created: (TEIID-730) A VDB with a materialized view model is created with errors
by Paul Nittel (JIRA)
A VDB with a materialized view model is created with errors
-----------------------------------------------------------
Key: TEIID-730
URL: https://jira.jboss.org/jira/browse/TEIID-730
Project: Teiid
Issue Type: Bug
Environment: Fedora 10, JDK 1.6 Teiid Designer circa early July
Reporter: Paul Nittel
Assignee: Steven Hawkins
I'm in the process of recreating the Genentech projects, one of which uses Materialized Views (which aren't yet available in Teiid). The VDB validation routines are generating erros in teh VDB, so it cannot be used. The errors are not shown in the log file, jus tthe VDB's Problems tab. An example of the errors are:
Error creating truncate scripts for VDB <name of the VDB>
Error creating swap scripts for VDB <name of the VDB>
Whether the Designer should expose this property or the validation should produce a warning instead of an error is up to you guys.
--
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
16 years, 8 months
[JBoss JIRA] Commented: (TEIID-99) Stored procedures should work in multisource connector binding scenarios
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-99?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIID-99:
-------------------------------------
For this to work seamlessly there will need be two valid forms of the procedure
exec (params)
exec (params, source_name)
which will require some changes to the exec resolver to allow optional parameters specified at the end of the procedure to be omitted even if not using named parameter syntax. If the multisource value is included it must be set to a valid source, otherwise the function will not execute.
Since we know the valid input set, procedure relational validation will also be modified to allow the procedure to execute even without the source_name parameter specified in criteria.
The MultisourcePlanToProcessConverter will need to do special handling with DependendProcedureAccessNode (evaluating the input criteria and removing the source_name parameter) and AccessNodes containing procedures (testing if the source name parameter if set and if the value matches the current source).
> Stored procedures should work in multisource connector binding scenarios
> ------------------------------------------------------------------------
>
> Key: TEIID-99
> URL: https://jira.jboss.org/jira/browse/TEIID-99
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 6.x
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 6.2.0
>
>
> Defect Tracker #24614: Stored procedures should work in multisource connector binding scenarios by adding another input parameter named SOURCE_NAME
--
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
16 years, 8 months