[JBoss JIRA] (TEIID-4712) Google translator throws exception for DELETE where <>
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIID-4712?page=com.atlassian.jira.plugin... ]
Lucie Fabrikova resolved TEIID-4712.
------------------------------------
Resolution: Done
> Google translator throws exception for DELETE where <>
> ------------------------------------------------------
>
> Key: TEIID-4712
> URL: https://issues.jboss.org/browse/TEIID-4712
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 9.2
> Reporter: Lucie Fabrikova
> Assignee: Steven Hawkins
> Attachments: googlespreadsheetcrud-vdb.xml, server.log
>
>
> Google translator throws exception "Invalid query parameter value for sq." for query DELETE FROM smalla WHERE col <> colValue (see attachment - server log after running query "delete from smalla where shortvalue <> 5303")
> I observed the exception is thrown for all types.
> Next, I observed following behavior for operator <>:
> - for datatypes double, float, bigdecimal, timestamp: SELECT returns no rows, UPDATE affects no rows
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4712) Google translator throws exception for DELETE where <>
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIID-4712?page=com.atlassian.jira.plugin... ]
Lucie Fabrikova commented on TEIID-4712:
----------------------------------------
I re-tested it with latest teiid and it worked correctly.
> Google translator throws exception for DELETE where <>
> ------------------------------------------------------
>
> Key: TEIID-4712
> URL: https://issues.jboss.org/browse/TEIID-4712
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 9.2
> Reporter: Lucie Fabrikova
> Assignee: Steven Hawkins
> Attachments: googlespreadsheetcrud-vdb.xml, server.log
>
>
> Google translator throws exception "Invalid query parameter value for sq." for query DELETE FROM smalla WHERE col <> colValue (see attachment - server log after running query "delete from smalla where shortvalue <> 5303")
> I observed the exception is thrown for all types.
> Next, I observed following behavior for operator <>:
> - for datatypes double, float, bigdecimal, timestamp: SELECT returns no rows, UPDATE affects no rows
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4713) HANA translator evaluates > as >=
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4713?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-4713:
-------------------------------------
Component/s: Misc. Connectors
Fix Version/s: 9.2
Assignee: Ted Jones (was: Steven Hawkins)
> HANA translator evaluates > as >=
> ---------------------------------
>
> Key: TEIID-4713
> URL: https://issues.jboss.org/browse/TEIID-4713
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.2
> Reporter: Lucie Fabrikova
> Assignee: Ted Jones
> Fix For: 9.2
>
> Attachments: sap-hana_crud-vdb.xml
>
>
> HANA translator evaluates > as >= in following query:
> DELETE FROM SmallA WHERE FloatNum > 11814.4
> I observed rows where FloatNum = 11814.4 were also deleted.
> Next observations:
> - query DELETE FROM SmallA WHERE FloatNum = 11814.4 deleted no rows.
> - <= was evaluated as <
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4703) The Oracle translator did not limit the number of values in "IN" clause, which were required by Oracle database.
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4703?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4703:
---------------------------------------
Ideally you could provide something that is sanitized. Starting with a representative user query and the translator configuration from the VDB would be a good start. For whole logs if it's not appropriate to post here, you can reach out through jboss.org - https://developer.jboss.org/people/shawkins
> The Oracle translator did not limit the number of values in "IN" clause, which were required by Oracle database.
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4703
> URL: https://issues.jboss.org/browse/TEIID-4703
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.13.4
> Reporter: SHI HONG CHIN
> Assignee: Steven Hawkins
>
> Database: Oracle + Firebird + Microsoft SQL Server.
> Oracle limit the maximum number of values in "IN" clause to 1000.
> In teiid, I am using the built-in Oracle translator.
> When running some SQL queries, Oracle database reported an error "No more data to read from socket". I had set the log level of Teiid to "ALL". According to the WildFly log files, Teiid executed a query with more than 10000 values in the "IN" clause.
> I tried to copy the whole SQL from WildFly log file into Oracle SQL Developer and execute it, the same error occurred. Then, I tried to edit the query by delete many values from the "IN" clause and then run the query again, and the query success.
> For teiid, as a workaround, I overrided the oracle translator and set the property of "MaxInCriteriaSize" to 50. After that, all SQL queries run success without any issue.
> I suggest that, by default, the built-in Oracle translator limit the number of values in "IN" clause to maximum 1000 values, and this behavior can be changed through properties.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4575) No such accessible property/method in the class after deploy vdb
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4575?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4575:
----------------------------------
Fix Version/s: 9.2.1
> No such accessible property/method in the class after deploy vdb
> ----------------------------------------------------------------
>
> Key: TEIID-4575
> URL: https://issues.jboss.org/browse/TEIID-4575
> Project: Teiid
> Issue Type: Bug
> Components: Documentation, JDG Connector
> Affects Versions: 9.2
> Reporter: Matej Kralik
> Assignee: Van Halbert
> Fix For: 9.2.1
>
> Attachments: JDGproject.zip
>
>
> When I want to deploy dynamic VDB with JDG materialization, the server shows me : TEIID31111 No such accessible property/method ISBN on class org.teiid.jdg.pojo.Book.
> I looked at Book.java and ISBN is there.
> The class is generated in the teiid designer. In the attachment is the project with dynamicVDB and generated JDG module.
> Stacktrace:
> {code:java}
> 12:34:07,140 WARN [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue223) Connector worker process failed for atomic-request=e3xcwoJghvNm.0.69.131: org.teiid.translator.TranslatorException: TEIID31111 No such accessible property/method ISBN on class org.teiid.jdg.pojo.Book.
> at org.teiid.translator.object.ObjectUpdateExecution.evaluate(ObjectUpdateExecution.java:524) [translator-object-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.translator.object.ObjectUpdateExecution.handleInsert(ObjectUpdateExecution.java:219) [translator-object-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.translator.object.ObjectUpdateExecution.executeUpdate(ObjectUpdateExecution.java:150) [translator-object-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.translator.object.ObjectUpdateExecution.execute(ObjectUpdateExecution.java:108) [translator-object-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:402) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at sun.reflect.GeneratedMethodAccessor169.invoke(Unknown Source) [:1.8.0_91]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_91]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_91]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at com.sun.proxy.$Proxy46.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:142) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.relational.ProjectIntoNode.checkExitConditions(ProjectIntoNode.java:264) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.relational.ProjectIntoNode.nextBatchDirect(ProjectIntoNode.java:164) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:69) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:70) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:84) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.common.buffer.AbstractTupleSource.hasNext(AbstractTupleSource.java:92) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.proc.ProcedurePlan.executePlan(ProcedurePlan.java:608) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.proc.CreateCursorResultSetInstruction.process(CreateCursorResultSetInstruction.java:69) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.proc.ExecDynamicSqlInstruction$1.process(ExecDynamicSqlInstruction.java:218) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.proc.ProcedurePlan.processProcedure(ProcedurePlan.java:389) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.proc.ProcedurePlan.nextBatchDirect(ProcedurePlan.java:298) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.proc.ProcedurePlan.nextBatch(ProcedurePlan.java:270) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.relational.PlanExecutionNode.nextBatchDirect(PlanExecutionNode.java:118) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:150) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91]
> Caused by: javax.script.ScriptException: TEIID31111 No such accessible property/method ISBN on class org.teiid.jdg.pojo.Book.
> at org.teiid.query.eval.TeiidScriptEngine$1.eval(TeiidScriptEngine.java:132) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.translator.object.ObjectUpdateExecution.evaluate(ObjectUpdateExecution.java:521) [translator-object-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> ... 47 more
> 12:34:07,146 WARN [org.teiid.MATVIEWS] (Worker0_QueryProcessorQueue225) org.teiid.jdbc.TeiidSQLException: TEIID30504 BookCacheSource: TEIID31111 No such accessible property/method ISBN on class org.teiid.jdg.pojo.Book.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4627) High-level event handling
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4627?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4627:
---------------------------------------
Yes, I'll have changes by Monday.
> High-level event handling
> -------------------------
>
> Key: TEIID-4627
> URL: https://issues.jboss.org/browse/TEIID-4627
> Project: Teiid
> Issue Type: Enhancement
> Components: Grammar, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> We should look into high-level plugability of event handling at a row level. This could even be handled at the language level with new trigger semantics for source tables: create trigger on tbl on cdc (insert|update...) - which could potentially even specify the topic mapping other details. There is complexity for multi-source models here though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4627) High-level event handling
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4627?page=com.atlassian.jira.plugin... ]
Ramesh Reddy edited comment on TEIID-4627 at 1/20/17 5:53 PM:
--------------------------------------------------------------
[~shawkins] I see that in the initial commit, there is no handling for OLD values in the {{SourceTriggerActionPlanner.java}} can you please add that support?
Also, for "Insert" case, I see that SourceEventCommand never finishes and keeps looping in QueryProcessor.nextBatchDirect() method, thus running the CPU cycles high. I think it does not have terminate flag on tuples as last batch.
was (Author: rareddy):
[~shawkins] I see that in the initial commit, there is no handling for OLD values in the {{SourceTriggerActionPlanner.java}} can you please add that support?
> High-level event handling
> -------------------------
>
> Key: TEIID-4627
> URL: https://issues.jboss.org/browse/TEIID-4627
> Project: Teiid
> Issue Type: Enhancement
> Components: Grammar, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> We should look into high-level plugability of event handling at a row level. This could even be handled at the language level with new trigger semantics for source tables: create trigger on tbl on cdc (insert|update...) - which could potentially even specify the topic mapping other details. There is complexity for multi-source models here though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4627) High-level event handling
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4627?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4627:
-------------------------------------
[~shawkins] I see that in the initial commit, there is no handling for OLD values in the {{SourceTriggerActionPlanner.java}} can you please add that support?
> High-level event handling
> -------------------------
>
> Key: TEIID-4627
> URL: https://issues.jboss.org/browse/TEIID-4627
> Project: Teiid
> Issue Type: Enhancement
> Components: Grammar, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> We should look into high-level plugability of event handling at a row level. This could even be handled at the language level with new trigger semantics for source tables: create trigger on tbl on cdc (insert|update...) - which could potentially even specify the topic mapping other details. There is complexity for multi-source models here though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months