[JBoss JIRA] (TEIID-3212) Materialized Views Documentation Issues
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3212?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3212:
-------------------------------------
1) The code looks like
{code}
if (statusTable == null || (stageTable == null && loadScript == null) || exception == null || ttl == null ) {
throw new TranslatorException(QueryPlugin.Util.gs(QueryPlugin.Event.TEIID31154));
}
{code}
per document when the load script is not defined, then this is required. So, did you define the LOAD_SCRIPT for this case?
2 & 4 ) Fixed
3) I did not see reference to "teiid_rel:ON_VDB_CREATE_SCRIPT" may be somebody already edited it out in latest docs.
> Materialized Views Documentation Issues
> ---------------------------------------
>
> Key: TEIID-3212
> URL: https://issues.jboss.org/browse/TEIID-3212
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
>
> On the documentation page https://docs.jboss.org/author/display/teiid87final/External+Materialization there are several inconsistencies within the text:
> 1. In doc property teiid_rel:MATVIEW_STAGE_TABLE is stated as optional, but in fact to activate the vdb setting of property teiid_rel:MATERIALIZED_STAGE_TABLE is required which is also in the sample code.
> 2. teiid_rel:MATVIEW_TTL stated as optional, but if not set error occurs on deploy.
> 3. In the table of properties is teiid_rel:ON_VDB_START_SCRIPT, but under the table there is teiid_rel:ON_VDB_CREATE_SCRIPT property.
> 4. in the sample vdb definition the Cache Hint with the query is misleading, as the teiid_rel:MATVIEW_TTL is required. In sync with issue TEIID-3209.
> On the https://docs.jboss.org/author/display/teiid87final/Internal+Materialization page:
> 1. in section "Updatable" the "Update SQL" query calls wrong procedure. It calls updateMatViewRow, but should call refreshMatViewRow as is stated in the surrounding text.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIID-3212) Materialized Views Documentation Issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3212?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3212:
---------------------------------------
2) will be an error and has been corrected in later docs, just not in the 8.7 version. This somewhat duplicates TEIID-3209
> Materialized Views Documentation Issues
> ---------------------------------------
>
> Key: TEIID-3212
> URL: https://issues.jboss.org/browse/TEIID-3212
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
>
> On the documentation page https://docs.jboss.org/author/display/teiid87final/External+Materialization there are several inconsistencies within the text:
> 1. In doc property teiid_rel:MATVIEW_STAGE_TABLE is stated as optional, but in fact to activate the vdb setting of property teiid_rel:MATERIALIZED_STAGE_TABLE is required which is also in the sample code.
> 2. teiid_rel:MATVIEW_TTL stated as optional, but if not set error occurs on deploy.
> 3. In the table of properties is teiid_rel:ON_VDB_START_SCRIPT, but under the table there is teiid_rel:ON_VDB_CREATE_SCRIPT property.
> 4. in the sample vdb definition the Cache Hint with the query is misleading, as the teiid_rel:MATVIEW_TTL is required. In sync with issue TEIID-3209.
> On the https://docs.jboss.org/author/display/teiid87final/Internal+Materialization page:
> 1. in section "Updatable" the "Update SQL" query calls wrong procedure. It calls updateMatViewRow, but should call refreshMatViewRow as is stated in the surrounding text.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIID-2700) Add CRUD support to Infinispan translator/connector
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2700?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2700.
-----------------------------------
Fix Version/s: 8.7.1
8.10
Resolution: Done
Marking as resolved based upon the last comment. This is also partially resolved for 8.9, but I'm not entirely sure what our infinispan story looks like there vs. master/8.7.x - Van is there anything that should be done before final or doc'd?
> Add CRUD support to Infinispan translator/connector
> ---------------------------------------------------
>
> Key: TEIID-2700
> URL: https://issues.jboss.org/browse/TEIID-2700
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 8.7.1, 8.10
>
>
> Add CRUD support to the Infinispan translator/connector to work with JDG 6.2.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIID-2020) Running Sybase procedure with jconnect driver in Teiid fails
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2020?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2020:
----------------------------------
Comment: was deleted
(was: Vivienne Westwood
vivenne westwood http://www.cellact.co.uk/uk/vwbag.html)
> Running Sybase procedure with jconnect driver in Teiid fails
> ------------------------------------------------------------
>
> Key: TEIID-2020
> URL: https://issues.jboss.org/browse/TEIID-2020
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.4.1
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 7.4.1, 7.7.1, 8.0
>
> Attachments: Sybase_test.vdb
>
>
> run the following against the Sybase_test.vdb
> exec sp_rows_between(1,6,'SmallA')
> You'll receive the below error:
> [TranslatorException] ZZZZZ: Error Code:ZZZZZ Message:'{ ?= call sp_rows_between(?,?,?)}' error executing statement(s): {1}
> 1 [SybSQLException]Execute cursor 'jconnect_implicit_3' is declared on a procedure which contains a non-SELECT or a SELECT with a COMPUTE clause. For the declaration of this cursor to be legal it should have a single SELECT statement without a COMPUTE clause.
> at org.teiid.translator.jdbc.JDBCProcedureExecution.execute(JDBCProcedureExecution.java:70)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:264)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:338)
> at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:80)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:138)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:135)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:121)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:230)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: com.sybase.jdbc3.jdbc.SybSQLException: Execute cursor 'jconnect_implicit_3' is declared on a procedure which contains a non-SELECT or a SELECT with a COMPUTE clause. For the declaration of this cursor to be legal it should have a single SELECT statement without a COMPUTE clause.
> at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
> I can use DBVisualizer and the same jConnect driver and run the exact same procedure with correct results.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (TEIID-3212) Materialized Views Documentation Issues
by Jan Stastny (JIRA)
Jan Stastny created TEIID-3212:
----------------------------------
Summary: Materialized Views Documentation Issues
Key: TEIID-3212
URL: https://issues.jboss.org/browse/TEIID-3212
Project: Teiid
Issue Type: Bug
Affects Versions: 8.7
Reporter: Jan Stastny
Assignee: Steven Hawkins
On the documentation page https://docs.jboss.org/author/display/teiid87final/External+Materialization there are several inconsistencies within the text:
1. In doc property teiid_rel:MATVIEW_STAGE_TABLE is stated as optional, but in fact to activate the vdb setting of property teiid_rel:MATERIALIZED_STAGE_TABLE is required which is also in the sample code.
2. teiid_rel:MATVIEW_TTL stated as optional, but if not set error occurs on deploy.
3. In the table of properties is teiid_rel:ON_VDB_START_SCRIPT, but under the table there is teiid_rel:ON_VDB_CREATE_SCRIPT property.
4. in the sample vdb definition the Cache Hint with the query is misleading, as the teiid_rel:MATVIEW_TTL is required. In sync with issue TEIID-3209.
On the https://docs.jboss.org/author/display/teiid87final/Internal+Materialization page:
1. in section "Updatable" the "Update SQL" query calls wrong procedure. It calls updateMatViewRow, but should call refreshMatViewRow as is stated in the surrounding text.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month