[JBoss JIRA] (TEIID-5248) Upgrade to v4 api for google spreadsheets
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5248?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5248:
---------------------------------------
I have the changes for the hybrid approach. Essentially v4 simplifies some of the code, but is useful only for metadata extraction and inserting. Querying still needs the visualization api and update/delete still needs v3. So at some later point update/delete functionality will break.
> Upgrade to v4 api for google spreadsheets
> -----------------------------------------
>
> Key: TEIID-5248
> URL: https://issues.jboss.org/browse/TEIID-5248
> Project: Teiid
> Issue Type: Quality Risk
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.2
>
>
> Our integration is based upon the v3 api, which will soon be deprecated. This will be a large change given the api differences. We can also look to include TEIID-5040
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5221) OData4 Translator generates invalid metadata
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5221?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5221:
---------------------------------------
[~jolee] Using commit efa4044 there is only a single conflict in TestODataQueryExecution, which can be resolved by removing the change. TEIID-3909 is not needed for 6.4 unless it is specifically requested by a customer.
> OData4 Translator generates invalid metadata
> ---------------------------------------------
>
> Key: TEIID-5221
> URL: https://issues.jboss.org/browse/TEIID-5221
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors, OData
> Affects Versions: 8.12
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 10.1, 10.0.3, 9.3.7
>
>
> The OData V4 translator does not generate metadata correctly in situations
> 1) When multiple navigations are defined on the EnitityType.
> 2) The PSEDEO column usage is incorrect, as this should be only used with ComplexType structures when the association to EntityType is made. But this is also used in cases where incorrect referential constraints are used. This may lead to the additional columns on Entities which are hard to resolve during the runtime.
> 3) Usage of MERGE property is also incorrect when multiple navigation properties are defined as these may be overridden for (1)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5229) NoSuchElementException for inherent DELETE with no pk on source table
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-5229?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated TEIID-5229:
---------------------------------
Fix Version/s: 8.12.12.6_4
> NoSuchElementException for inherent DELETE with no pk on source table
> ---------------------------------------------------------------------
>
> Key: TEIID-5229
> URL: https://issues.jboss.org/browse/TEIID-5229
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.11.6_4
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 10.1, 8.12.12.6_4
>
>
> DELETE fails when there's WHERE criteria on a column with type char.
> {code:sql}
> DELETE FROM SmallA WHERE CharValue IN ('2', '3')
> {code}
> Error:
> {code}
> 14:04:41,627 ERROR [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue60) TEIID30019 Unexpected exception for request Bc4xXOpFO/lu.32: java.util.NoSuchElementException
> at java.util.ArrayList$Itr.next(ArrayList.java:860) [rt.jar:1.8.0_151]
> at org.teiid.query.rewriter.QueryRewriter.createPkCriteria(QueryRewriter.java:3104) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.query.rewriter.QueryRewriter.createDeleteProcedure(QueryRewriter.java:3238) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.query.rewriter.QueryRewriter.rewriteInherentDelete(QueryRewriter.java:3177) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.query.rewriter.QueryRewriter.rewriteDelete(QueryRewriter.java:3130) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.query.rewriter.QueryRewriter.rewriteCommand(QueryRewriter.java:238) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.query.rewriter.QueryRewriter.rewrite(QueryRewriter.java:168) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.query.rewriter.QueryRewriter.rewrite(QueryRewriter.java:172) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:426) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.dqp.internal.process.Request.processRequest(Request.java:476) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:642) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:337) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151]
> {code}
> UPDATE works as expected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5248) Upgrade to v4 api for google spreadsheets
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5248?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5248:
---------------------------------------
There isn't a good way to create update/delete operations. The only queryable logic (visualization) does not return the cell ranges. There are only a couple of possibilities: use a hybrid resource adapter that still uses v3 for update/delete, simply disable update/delete operations, or require the user to specify a pk column using the row() function.
> Upgrade to v4 api for google spreadsheets
> -----------------------------------------
>
> Key: TEIID-5248
> URL: https://issues.jboss.org/browse/TEIID-5248
> Project: Teiid
> Issue Type: Quality Risk
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.2
>
>
> Our integration is based upon the v3 api, which will soon be deprecated. This will be a large change given the api differences. We can also look to include TEIID-5040
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5261) Add support for Teiid Spring vs VDB
by Arvind Gopinath (JIRA)
[ https://issues.jboss.org/browse/TEIID-5261?page=com.atlassian.jira.plugin... ]
Arvind Gopinath commented on TEIID-5261:
----------------------------------------
[~rareddy] when i change the wildfly-swarm version to 2018.2.0, I am getting issue in the following lines
import org.wildfly.swarm.teiid.VDBArchive;
VDBArchive vdb = ShrinkWrap.create(VDBArchive.class);
vdb.vdb(Main.class.getClassLoader().getResourceAsStream("sqlite-vdb.xml"));
Error:(36, 8) java: cannot find symbol
symbol: method vdb(java.io.InputStream)
location: variable vdb of type org.wildfly.swarm.teiid.VDBArchive
> Add support for Teiid Spring vs VDB
> -----------------------------------
>
> Key: TEIID-5261
> URL: https://issues.jboss.org/browse/TEIID-5261
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Arvind Gopinath
> Assignee: Steven Hawkins
> Priority: Minor
> Attachments: Errorlogs.txt
>
>
> The virtual View construction happens with Annotations using Teiid Spring Boot.
> Without annotations, it will be value added if Teiid Spring Boot supports VDB.
> Referring below example to implement the same using Spring Boot -
> https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months