October 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4516) Add support for updating/deleting child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4516: ------------------------------- Summary: Add support for updating/deleting child objects (was: Add support for updating child objects) > Add support for updating/deleting child objects > ----------------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.2, 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 9.2 > > > When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. > The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > INSERT queries to prepare data: > {code:sql} > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') > {code} > UPDATE queries and queries for checking results: > * 1-to-1 > {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} > {code:sql}SELECT * FROM Person,Address{code} > * 1-to-n > {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} > {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4533) Change the default max-staleness for the resultset cache to 0

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4533: ------------------------------------- Summary: Change the default max-staleness for the resultset cache to 0 Key: TEIID-4533 URL: https://issues.jboss.org/browse/TEIID-4533 Project: Teiid Issue Type: Quality Risk Components: Query Engine, Server Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.2 We have inherited the property setting for years and have to call it out in several places in the docs. It would be best to default to 0, and instead call out in the docs that cache can be made more tolerant to stale entries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4532) Provide one-way or cryptographic hash functions

by Van Halbert (JIRA)

Van Halbert created TEIID-4532: ---------------------------------- Summary: Provide one-way or cryptographic hash functions Key: TEIID-4532 URL: https://issues.jboss.org/browse/TEIID-4532 Project: Teiid Issue Type: Feature Request Components: Common Affects Versions: 9.2 Reporter: Van Halbert Assignee: Steven Hawkins provide one-way or cryptographic hash functions, such as any of the MD5, SHA-1, SHA-2, or SHA-3 functions? https://en.wikipedia.org/wiki/SHA-3#Comparison_of_SHA_functions <https://en.wikipedia.org/wiki/SHA-3#Comparison_of_SHA_functions> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4366) Provide CORS support on OData Service

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4366?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-4366 at 10/21/16 11:14 AM: ---------------------------------------------------------------- [~jdurani] and [~jolee] I found in my testing that SDK's _HttpURLConnection_ blocks the setting of the ORIGIN header, thus the issue you report. I think even the CXF HttpClient deep underneath also uses _HttpURLConnection_ The test needs to avoid using this class, I have not spent time figuring out how to do that in JAVA, may be you can try CURL or some perl/python script? As you see above in one of the comments, I used the anjular.js java script for testing. was (Author: rareddy): [~jdurani] and [~jolee] I found in my testing that SDK's _HttpURLConnection _ blocks the setting of the ORIGIN header, thus the issue you report. I think even the CXF HttpClient deep underneath also uses _HttpURLConnection_ The test needs to avoid using this class, I have not spent time figuring out how to do that in JAVA, may be you can try CURL or some perl/python script? As you see above in one of the comments, I used the anjular.js java script for testing. > Provide CORS support on OData Service > ------------------------------------- > > Key: TEIID-4366 > URL: https://issues.jboss.org/browse/TEIID-4366 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.1, 9.0.4, 8.12.7.6_3 > > > Good write up CORS can be found here https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS > OData needs to implement CORS support to be valuable with java script based client development technologies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4366) Provide CORS support on OData Service

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4366?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4366: ------------------------------------- [~jdurani] and [~jolee] I found in my testing that SDK's _HttpURLConnection _ blocks the setting of the ORIGIN header, thus the issue you report. I think even the CXF HttpClient deep underneath also uses _HttpURLConnection_ The test needs to avoid using this class, I have not spent time figuring out how to do that in JAVA, may be you can try CURL or some perl/python script? As you see above in one of the comments, I used the anjular.js java script for testing. > Provide CORS support on OData Service > ------------------------------------- > > Key: TEIID-4366 > URL: https://issues.jboss.org/browse/TEIID-4366 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.1, 9.0.4, 8.12.7.6_3 > > > Good write up CORS can be found here https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS > OData needs to implement CORS support to be valuable with java script based client development technologies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2578: --------------------------------------- I'll take another pass through as I made the refactoring to DatabaseStore/Storage without considering the remote nature of the service. In general the problem we have is that the locking is based upon a single vm, and can then would call into a shared service potentially with competing state. > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4518) Add module dependencies to support JDG 7.1

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4518?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4518: ------------------------------------ Created jira TEIID-4531 for this issue. > Add module dependencies to support JDG 7.1 > ------------------------------------------ > > Key: TEIID-4518 > URL: https://issues.jboss.org/browse/TEIID-4518 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Van Halbert > Assignee: Van Halbert > > The JDG 7.1 modules need to be added as dependencies in the infinispan translator and connector module.xml files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4531) Unable to configure the JDG schema using marshallers

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4531?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-4531: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Unable to configure the JDG schema using marshallers > ---------------------------------------------------- > > Key: TEIID-4531 > URL: https://issues.jboss.org/browse/TEIID-4531 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > > There appears to be a change in JDG 7.1 that now requires permission in order to configure the JDG schema using marshallers. There was a blog [1] found that describes the issue and a possible solution. > [1] https://blog.kenthua.com/2016/08/03/jdg-7-remote-query-register-proto-sch... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4531) Unable to configure the JDG schema using marshallers

by Van Halbert (JIRA)

Van Halbert created TEIID-4531: ---------------------------------- Summary: Unable to configure the JDG schema using marshallers Key: TEIID-4531 URL: https://issues.jboss.org/browse/TEIID-4531 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 9.2 Reporter: Van Halbert Assignee: Steven Hawkins There appears to be a change in JDG 7.1 that now requires permission in order to configure the JDG schema using marshallers. There was a blog [1] found that describes the issue and a possible solution. [1] https://blog.kenthua.com/2016/08/03/jdg-7-remote-query-register-proto-sch... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4518) Add module dependencies to support JDG 7.1

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4518?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4518: ------------------------------- Fix Version/s: (was: 8.12.7.6_3) > Add module dependencies to support JDG 7.1 > ------------------------------------------ > > Key: TEIID-4518 > URL: https://issues.jboss.org/browse/TEIID-4518 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Van Halbert > Assignee: Van Halbert > > The JDG 7.1 modules need to be added as dependencies in the infinispan translator and connector module.xml files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4518) Add module dependencies to support JDG 7.1

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4518?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4518: ------------------------------------ This appears to be something that was added post 7.0, as initial testing was done in community with JDG 7.0 Beta. > Add module dependencies to support JDG 7.1 > ------------------------------------------ > > Key: TEIID-4518 > URL: https://issues.jboss.org/browse/TEIID-4518 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.7.6_3 > > > The JDG 7.1 modules need to be added as dependencies in the infinispan translator and connector module.xml files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2578: --------------------------------------- > adminEventDistributor methods to deleteDataSources did not cross my mind, may be they should not be replicated. That's the part I'm questioning. Since these methods are called below EventDistributor replicated methods, they will end up being called by each cluster member. > can you elaborate this one? There is logic in the database drop that will try to drop associated servers, but it looks like there is a shared connectormanagerrepository among all vdbs. > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2578: ------------------------------------- DatabaseStorage is cluster aware service. See that is _SingletonPolicy_ i.e. there will be a single service of this kind in the whole cluster, any call made on this get routed to single instance on the master node. If the master node is down for some reason, this service will not be available. So, the replicated EventDistributor call is only for modifying the DatabaseStore copy. adminEventDistributor methods to deleteDataSources did not cross my mind, may be they should not be replicated. >Also what is the notion of server ownership on a databaseDrop? can you elaborate this one? > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4530) Add semicolons to generated ddl

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4530?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4530. ----------------------------------- Resolution: Done Pulled back the ddl generation change. > Add semicolons to generated ddl > ------------------------------- > > Key: TEIID-4530 > URL: https://issues.jboss.org/browse/TEIID-4530 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0.5, 9.1.1 > > > We should be generating DDL that is both forwards and backwards compatible with the TEIID-4528 change, which means that all ddl statements will need terminated with a semicolon. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4530) Add semicolons to generated ddl

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4530: ------------------------------------- Summary: Add semicolons to generated ddl Key: TEIID-4530 URL: https://issues.jboss.org/browse/TEIID-4530 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.1.1, 9.0.5 We should be generating DDL that is both forwards and backwards compatible with the TEIID-4528 change, which means that all ddl statements will need terminated with a semicolon. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4528) ddl generation / parsing semicolon handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4528?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4528. ----------------------------------- Resolution: Done DDL statements must now be separated by a semicolon - but we'll for now allow create table / procedure to not have a trailing delimiter. This will keep things backwards compatible with scripts generated by Teiid and Teiid Designer, but eventually we may need to remove this option. To that end, I'll backport the ddl generation changes to 9.1/9.0. > ddl generation / parsing semicolon handling > ------------------------------------------- > > Key: TEIID-4528 > URL: https://issues.jboss.org/browse/TEIID-4528 > Project: Teiid > Issue Type: Bug > Components: Grammar, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2 > > > The DDL to string logic omits the trailing semicolon with global temp tables and create procedure statements. The parser is also lax in that it will accept multiple ddl statements without a delimiter. With the addition of new keywords / statements in TEIID-2578 this introduces ambiguities into the grammar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4477) LDAP connector disconnects intermittently with error "TEIID12002"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4477?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4477: --------------------------------------- Thanks Jan > LDAP connector disconnects intermittently with error "TEIID12002" > ----------------------------------------------------------------- > > Key: TEIID-4477 > URL: https://issues.jboss.org/browse/TEIID-4477 > Project: Teiid > Issue Type: Bug > Components: LDAP Connector > Affects Versions: 8.12.5 > Environment: Red Hat JBoss Data Virtualization - Version 6.3.0 > Reporter: Rafael Coutinho > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.5, 8.12.7.6_3 > > > We are using LDAP connector for virtualizing the ldap employee directory data. For some reason every 3 to 4 hours we get a connection error between JDV and LDAP. > The exception says it could not find the context name, but after restarting it it works again. > Here is the exception: > 11:21:12,868 WARN [org.teiid.CONNECTOR] (Worker62_QueryProcessorQueue108177) Connector worker process failed for atomic-request=6S71mw5pkfvo.106.3.19906: org.teiid.translator.TranslatorException: TEIID12002 Failed to create LDAP search context from the specified context name ou=users,dc=redhat,dc=com. Check the table/group name in source to ensure the context exists. > at org.teiid.translator.ldap.LDAPSyncQueryExecution.createSearchContext(LDAPSyncQueryExecution.java:148) [translator-ldap-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.translator.ldap.LDAPSyncQueryExecution.execute(LDAPSyncQueryExecution.java:130) [translator-ldap-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) > at sun.reflect.GeneratedMethodAccessor184.invoke(Unknown Source) [:1.8.0-internal] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) [rt.jar:1.8.0-internal] > at java.lang.reflect.Method.invoke(Method.java:508) [rt.jar:2.6 (07-19-2016)] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy80.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at java.util.concurrent.FutureTask.run(FutureTask.java:277) [rt.jar:1.8.0-internal] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [rt.jar:1.8.0-internal] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [rt.jar:1.8.0-internal] > at java.lang.Thread.run(Thread.java:785) [vm.jar:1.8.0-internal] > Caused by: javax.naming.CommunicationException: connection closed [Root exception is java.io.IOException: connection closed]; remaining name 'ou=users,dc=redhat,dc=com' > at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:2014) [rt.jar:1.8.0-internal] > at com.sun.jndi.ldap.LdapCtx.doSearchOnce(LdapCtx.java:1945) [rt.jar:1.8.0-internal] > at com.sun.jndi.ldap.LdapCtx.c_lookup(LdapCtx.java:1039) [rt.jar:1.8.0-internal] > at com.sun.jndi.toolkit.ctx.ComponentContext.p_lookup(ComponentContext.java:554) [rt.jar:1.8.0-internal] > at com.sun.jndi.toolkit.ctx.PartialCompositeContext.lookup(PartialCompositeContext.java:189) [rt.jar:1.8.0-internal] > at com.sun.jndi.toolkit.ctx.PartialCompositeContext.lookup(PartialCompositeContext.java:178) [rt.jar:1.8.0-internal] > at javax.naming.InitialContext.lookup(InitialContext.java:428) [rt.jar:1.8.0-internal] > at javax.naming.InitialContext.lookup(InitialContext.java:428) [rt.jar:1.8.0-internal] > at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.lookup(LDAPConnectionImpl.java:193) > at org.teiid.translator.ldap.LDAPSyncQueryExecution.createSearchContext(LDAPSyncQueryExecution.java:146) [translator-ldap-8.12.5.redhat-8.jar:8.12.5.redhat-8] > ... 18 more > Caused by: java.io.IOException: connection closed > at com.sun.jndi.ldap.LdapClient.ensureOpen(LdapClient.java:1604) [rt.jar:1.8.0-internal] > at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:542) [rt.jar:1.8.0-internal] > at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1997) [rt.jar:1.8.0-internal] > ... 27 more > 11:21:12,871 ERROR [org.teiid.CONNECTOR] (Worker63_QueryProcessorQueue108178) null: java.lang.NullPointerException > at org.teiid.translator.ldap.LDAPSyncQueryExecution.close(LDAPSyncQueryExecution.java:186) [translator-ldap-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.close(ConnectorWorkItem.java:255) > at sun.reflect.GeneratedMethodAccessor185.invoke(Unknown Source) [:1.8.0-internal] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) [rt.jar:1.8.0-internal] > at java.lang.reflect.Method.invoke(Method.java:508) [rt.jar:2.6 (07-19-2016)] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy80.close(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.fullyCloseSource(DataTierTupleSource.java:338) > at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:394) > at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:161) > at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:391) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) > at org.teiid.query.processor.relational.SelectNode.nextBatchDirect(SelectNode.java:104) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:150) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) > at org.teiid.query.processor.relational.DupRemoveNode.nextBatchDirect(DupRemoveNode.java:62) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [rt.jar:1.8.0-internal] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [rt.jar:1.8.0-internal] > at java.lang.Thread.run(Thread.java:785) [vm.jar:1.8.0-internal] > 11:21:12,874 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Worker63_QueryProcessorQueue108178) LDAPSource: returnConnection(6306ef86, false) [1/20] > 11:21:12,874 WARN [org.teiid.PROCESSOR] (Worker63_QueryProcessorQueue108178) TEIID30020 Processing exception for request 6S71mw5pkfvo.106 'TEIID30504 local: TEIID12002 Failed to create LDAP search context from the specified context name ou=users,dc=redhat,dc=com. Check the table/group name in source to ensure the context exists.'. Originally TeiidProcessingException 'connection closed' LdapClient.java:1604. Enable more detailed logging to see the entire stacktrace. > 11:21:16,120 DEBUG [org.apache.catalina.session] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Start expire sessions StandardManager at 1474903276120 sessioncount 0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4527) Add cache-hint to dynamically create internal materialization

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4527?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4527. ----------------------------------- Resolution: Rejected Marking as rejected for now. > Add cache-hint to dynamically create internal materialization > ------------------------------------------------------------- > > Key: TEIID-4527 > URL: https://issues.jboss.org/browse/TEIID-4527 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Add the ability to use a cache-hint that will dynamically create an internal materialization of the results that can then be queried. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4477) LDAP connector disconnects intermittently with error "TEIID12002"

by Jan Stastny (JIRA)

[ https://issues.jboss.org/browse/TEIID-4477?page=com.atlassian.jira.plugin... ] Jan Stastny commented on TEIID-4477: ------------------------------------ [~shawkins] The issue has been resolved correctly. I was missing the validation and flush strategy configuration in my resource-adapter definition. With following everything is fine: {code:xml} <resource-adapter id="ra_inmemoryldap"> <module slot="main" id="org.jboss.teiid.resource-adapter.ldap"/> <transaction-support>NoTransaction</transaction-support> <connection-definitions> <connection-definition class-name="org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory" jndi-name="java:/inmemoryldap" pool-name="ra_inmemoryldap"> <config-property name="LdapAdminUserPassword"> secret </config-property> <config-property name="LdapAdminUserDN"> uid=admin,ou=system </config-property> <config-property name="LdapTxnTimeoutInMillis"> -1 </config-property> <config-property name="LdapUrl"> ldap://localhost:10389 </config-property> <pool> <flush-strategy>FailingConnectionOnly</flush-strategy> </pool> <validation> <background-validation>true</background-validation> <background-validation-millis>100</background-validation-millis> </validation> </connection-definition> </connection-definitions> </resource-adapter> {code} > LDAP connector disconnects intermittently with error "TEIID12002" > ----------------------------------------------------------------- > > Key: TEIID-4477 > URL: https://issues.jboss.org/browse/TEIID-4477 > Project: Teiid > Issue Type: Bug > Components: LDAP Connector > Affects Versions: 8.12.5 > Environment: Red Hat JBoss Data Virtualization - Version 6.3.0 > Reporter: Rafael Coutinho > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.5, 8.12.7.6_3 > > > We are using LDAP connector for virtualizing the ldap employee directory data. For some reason every 3 to 4 hours we get a connection error between JDV and LDAP. > The exception says it could not find the context name, but after restarting it it works again. > Here is the exception: > 11:21:12,868 WARN [org.teiid.CONNECTOR] (Worker62_QueryProcessorQueue108177) Connector worker process failed for atomic-request=6S71mw5pkfvo.106.3.19906: org.teiid.translator.TranslatorException: TEIID12002 Failed to create LDAP search context from the specified context name ou=users,dc=redhat,dc=com. Check the table/group name in source to ensure the context exists. > at org.teiid.translator.ldap.LDAPSyncQueryExecution.createSearchContext(LDAPSyncQueryExecution.java:148) [translator-ldap-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.translator.ldap.LDAPSyncQueryExecution.execute(LDAPSyncQueryExecution.java:130) [translator-ldap-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) > at sun.reflect.GeneratedMethodAccessor184.invoke(Unknown Source) [:1.8.0-internal] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) [rt.jar:1.8.0-internal] > at java.lang.reflect.Method.invoke(Method.java:508) [rt.jar:2.6 (07-19-2016)] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy80.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at java.util.concurrent.FutureTask.run(FutureTask.java:277) [rt.jar:1.8.0-internal] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [rt.jar:1.8.0-internal] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [rt.jar:1.8.0-internal] > at java.lang.Thread.run(Thread.java:785) [vm.jar:1.8.0-internal] > Caused by: javax.naming.CommunicationException: connection closed [Root exception is java.io.IOException: connection closed]; remaining name 'ou=users,dc=redhat,dc=com' > at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:2014) [rt.jar:1.8.0-internal] > at com.sun.jndi.ldap.LdapCtx.doSearchOnce(LdapCtx.java:1945) [rt.jar:1.8.0-internal] > at com.sun.jndi.ldap.LdapCtx.c_lookup(LdapCtx.java:1039) [rt.jar:1.8.0-internal] > at com.sun.jndi.toolkit.ctx.ComponentContext.p_lookup(ComponentContext.java:554) [rt.jar:1.8.0-internal] > at com.sun.jndi.toolkit.ctx.PartialCompositeContext.lookup(PartialCompositeContext.java:189) [rt.jar:1.8.0-internal] > at com.sun.jndi.toolkit.ctx.PartialCompositeContext.lookup(PartialCompositeContext.java:178) [rt.jar:1.8.0-internal] > at javax.naming.InitialContext.lookup(InitialContext.java:428) [rt.jar:1.8.0-internal] > at javax.naming.InitialContext.lookup(InitialContext.java:428) [rt.jar:1.8.0-internal] > at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.lookup(LDAPConnectionImpl.java:193) > at org.teiid.translator.ldap.LDAPSyncQueryExecution.createSearchContext(LDAPSyncQueryExecution.java:146) [translator-ldap-8.12.5.redhat-8.jar:8.12.5.redhat-8] > ... 18 more > Caused by: java.io.IOException: connection closed > at com.sun.jndi.ldap.LdapClient.ensureOpen(LdapClient.java:1604) [rt.jar:1.8.0-internal] > at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:542) [rt.jar:1.8.0-internal] > at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1997) [rt.jar:1.8.0-internal] > ... 27 more > 11:21:12,871 ERROR [org.teiid.CONNECTOR] (Worker63_QueryProcessorQueue108178) null: java.lang.NullPointerException > at org.teiid.translator.ldap.LDAPSyncQueryExecution.close(LDAPSyncQueryExecution.java:186) [translator-ldap-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.close(ConnectorWorkItem.java:255) > at sun.reflect.GeneratedMethodAccessor185.invoke(Unknown Source) [:1.8.0-internal] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) [rt.jar:1.8.0-internal] > at java.lang.reflect.Method.invoke(Method.java:508) [rt.jar:2.6 (07-19-2016)] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy80.close(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.fullyCloseSource(DataTierTupleSource.java:338) > at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:394) > at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:161) > at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:391) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) > at org.teiid.query.processor.relational.SelectNode.nextBatchDirect(SelectNode.java:104) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:150) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) > at org.teiid.query.processor.relational.DupRemoveNode.nextBatchDirect(DupRemoveNode.java:62) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [rt.jar:1.8.0-internal] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [rt.jar:1.8.0-internal] > at java.lang.Thread.run(Thread.java:785) [vm.jar:1.8.0-internal] > 11:21:12,874 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Worker63_QueryProcessorQueue108178) LDAPSource: returnConnection(6306ef86, false) [1/20] > 11:21:12,874 WARN [org.teiid.PROCESSOR] (Worker63_QueryProcessorQueue108178) TEIID30020 Processing exception for request 6S71mw5pkfvo.106 'TEIID30504 local: TEIID12002 Failed to create LDAP search context from the specified context name ou=users,dc=redhat,dc=com. Check the table/group name in source to ensure the context exists.'. Originally TeiidProcessingException 'connection closed' LdapClient.java:1604. Enable more detailed logging to see the entire stacktrace. > 11:21:16,120 DEBUG [org.apache.catalina.session] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Start expire sessions StandardManager at 1474903276120 sessioncount 0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4529) Remove the dynamic vdb terminology

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4529: ------------------------------------- Summary: Remove the dynamic vdb terminology Key: TEIID-4529 URL: https://issues.jboss.org/browse/TEIID-4529 Project: Teiid Issue Type: Quality Risk Components: Documentation Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0 We should remove/deprecate the dynamic term and instead reference native metadata import and ddl - soon tooling will provide vdbs defined with ddl and the dynamic differentiation won't be needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4366) Provide CORS support on OData Service

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4366?page=com.atlassian.jira.plugin... ] Juraj Duráni reopened TEIID-4366: --------------------------------- Teiid returns _TEIID16056_ even for requests with "Origin" header. {code:java|title=Sample code} String origin = "http://localhost"; HttpURLConnection con = (HttpURLConnection) new URL("http://localhost:8080/odata4/my_vdb/views/v1").openConnection(); con.setRequestProperty("Authorization", "Basic " + Base64.encodeBase64String("user:user".getBytes())); con.setRequestProperty("Origin", origin); con.setRequestMethod("OPTIONS"); con.connect(); try{ int code = con.getResponseCode(); Assert.assertEquals(code, HttpStatus.SC_NO_CONTENT, "Response code."); ... } finally { con.disconnect(); } {code} {code:plain|title=Test result} java.lang.AssertionError: Response code. expected [204] but found [400] {code} > Provide CORS support on OData Service > ------------------------------------- > > Key: TEIID-4366 > URL: https://issues.jboss.org/browse/TEIID-4366 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.12 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.1, 9.0.4, 8.12.7.6_3 > > > Good write up CORS can be found here https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS > OData needs to implement CORS support to be valuable with java script based client development technologies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4528) ddl generation / parsing semicolon handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4528?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4528: ------------------------------------- Assignee: Steven Hawkins (was: Barry LaFond) > ddl generation / parsing semicolon handling > ------------------------------------------- > > Key: TEIID-4528 > URL: https://issues.jboss.org/browse/TEIID-4528 > Project: Teiid > Issue Type: Bug > Components: Grammar, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2 > > > The DDL to string logic omits the trailing semicolon with global temp tables and create procedure statements. The parser is also lax in that it will accept multiple ddl statements without a delimiter. With the addition of new keywords / statements in TEIID-2578 this introduces ambiguities into the grammar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4518) Add module dependencies to support JDG 7.1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4518?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4518: ------------------------------------------------ Alex Szczuczko <aszczucz(a)redhat.com> changed the Status of [bug 1385628|https://bugzilla.redhat.com/show_bug.cgi?id=1385628] from MODIFIED to ON_QA > Add module dependencies to support JDG 7.1 > ------------------------------------------ > > Key: TEIID-4518 > URL: https://issues.jboss.org/browse/TEIID-4518 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.7.6_3 > > > The JDG 7.1 modules need to be added as dependencies in the infinispan translator and connector module.xml files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2578: --------------------------------------- The more I look at the remoting, the more trouble we may be getting ourselves in. Serializing the entire database can be a significant overhead. Also, just like was mentioned with the alter above, consistency can be an issue - performing a drop at the same time from two cluster members that are mutually exclusive. Unless I'm missing something, the DatabaseStore calls EventDistributor.dropDatabase, when in turn is called for each cluster member, which in turn each will call the adminEventDistributor methods to deleteDataSources. Shouldn't only the first succeed? Also what is the notion of server ownership on a databaseDrop? I've pushed changes to https://github.com/teiid/teiid/tree/TEIID-2578 so that we can coordinate on things from there. > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4528) ddl generation / parsing semicolon handling

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4528: ------------------------------------- Summary: ddl generation / parsing semicolon handling Key: TEIID-4528 URL: https://issues.jboss.org/browse/TEIID-4528 Project: Teiid Issue Type: Bug Components: Grammar, Query Engine Reporter: Steven Hawkins Assignee: Barry LaFond Fix For: 9.2 The DDL to string logic omits the trailing semicolon with global temp tables and create procedure statements. The parser is also lax in that it will accept multiple ddl statements without a delimiter. With the addition of new keywords / statements in TEIID-2578 this introduces ambiguities into the grammar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4527) Add cache-hint to dynamically create internal materialization

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4527?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4527: ------------------------------------ This came from that initial requirement. If you think this no longer applicable or shouldn't be done, go ahead and reject. > Add cache-hint to dynamically create internal materialization > ------------------------------------------------------------- > > Key: TEIID-4527 > URL: https://issues.jboss.org/browse/TEIID-4527 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Add the ability to use a cache-hint that will dynamically create an internal materialization of the results that can then be queried. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4527) Add cache-hint to dynamically create internal materialization

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4527?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4527: --------------------------------------- Can you elaborate on this? Is this another option of the cache hint / materialization metadata to only use the materialization table if the source is down? > Add cache-hint to dynamically create internal materialization > ------------------------------------------------------------- > > Key: TEIID-4527 > URL: https://issues.jboss.org/browse/TEIID-4527 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Add the ability to use a cache-hint that will dynamically create an internal materialization of the results that can then be queried. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4527) Add cache-hint to dynamically create internal materialization

by Van Halbert (JIRA)

Van Halbert created TEIID-4527: ---------------------------------- Summary: Add cache-hint to dynamically create internal materialization Key: TEIID-4527 URL: https://issues.jboss.org/browse/TEIID-4527 Project: Teiid Issue Type: Feature Request Components: Query Engine, Server Affects Versions: 9.2 Reporter: Van Halbert Assignee: Steven Hawkins Add the ability to use a cache-hint that will dynamically create an internal materialization of the results that can then be queried. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC for maintaining materialized views

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4526: --------------------------------------- > the above approach of using updatematViewRow is not correct because its updating the actual row in the mat view table without applying the actual View transformation logic The considerations here are that the updateMatViewRow is only for internal materialization, and yes it's directly tied to modifying the materialization table. To create an appropriate change value, you would need to do a select with no cache from view and pull appropriately updated rows, then update each one. This method largely exists because there was no other way to modify the internal materialization target other than to completely refresh and the change is easy to broadcast. > The only way to ensure the correct result is to only trigger the update when the "key" can be identified in a change. Yes, some "trigger" has to understand a base tables relationship to all consuming entities and propagate them accordingly. As mentioned above this can be done with a full row fresh, or what I've talked about is updating of materialization logic to support lazier row refreshing using an invalidation flag - but it still requires determining what row(s) are affected. > Am I over thinking this? Is there something simpler? Unfortunately it's much more complicated. Our problems with CDC starts with the metadata. Since we allow for hand editing and only capture a simple quoted name in source, we first have a matching problem from any event source to our source metadata. Then inferring values directly from the change event can be an issue as the CDC layer is broadcasting raw values, not what you would fetch over jdbc (there can be type issues, or even the consideration of masking and other affects). From there yes we have to sufficiently understand the view structure to make an appropriate update. That will not always be a simple changes as aggregates may need recomputed, multiple rows removed, etc. What we talked about at the face-to-face was at least keeping some notion of how "dirty" a particular materialized view was (number of updates that affect the view vs. number of view rows) and trigger a full refresh above a given threshold. We also need to determine if there are differing expectations for internal vs. external materialization. > Integrate with Debezium for CDC for maintaining materialized views > ------------------------------------------------------------------ > > Key: TEIID-4526 > URL: https://issues.jboss.org/browse/TEIID-4526 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC for maintaining materialized views

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4526: ------------------------------------ Maybe certain tables have to be tracked differently. Like: static or volatile When a static table is changed, all materialized views using the table will be refreshed When a volatile table is changed and it has field as part of the primary key to the view, then trigger the refresh. > Integrate with Debezium for CDC for maintaining materialized views > ------------------------------------------------------------------ > > Key: TEIID-4526 > URL: https://issues.jboss.org/browse/TEIID-4526 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC for maintaining materialized views

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4526: ------------------------------------ the above approach of using updatematViewRow is not correct because its updating the actual row in the mat view table without applying the actual View transformation logic. So what is needed is the ability to call SYSADMIN.refreshMatViewRow (example: EXEC SYSADMIN.refreshMatViewRow('TestMat.SAMPLEMATVIEW', '{id}') ) But even that really won't work, because on a very complex view transformation, the table change could be for a table in a subselect of the view transformation. The key value of the row change is not enough to limit the subselect correctly. Which could return the wrong results if its used in an "IN" subselect because other data is no longer included in the subselect. The only way to ensure the correct result is to only trigger the update when the "key" can be identified in a change. Am I over thinking this? Is there something simpler? > Integrate with Debezium for CDC for maintaining materialized views > ------------------------------------------------------------------ > > Key: TEIID-4526 > URL: https://issues.jboss.org/browse/TEIID-4526 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC for maintaining materialized views

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4526: ------------------------------------ Looking at the doc's of Programmatic Control [1] and the org.teiid.events.EventDistributor interface, would call the following method to perform the insert/update/delete: {code} @Replicated(remoteOnly=true) void updateMatViewRow(String vdbName, int vdbVersion, String schema, String viewName, List<?> tuple, boolean delete); {code} The order of the tuple is loaded should be driven by reading the table metadata. [1] https://teiid.gitbooks.io/documents/content/v/9.1.x/caching/Programmatic_... > Integrate with Debezium for CDC for maintaining materialized views > ------------------------------------------------------------------ > > Key: TEIID-4526 > URL: https://issues.jboss.org/browse/TEIID-4526 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC for maintaining materialized views

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4526: ------------------------------------ There needs to be a client written (see [1]) to consume all of the events in 1 or more topics. According Randal, right now, every table maps to a separate topic, but they are considering changing that to optionally write all changes in each database to a single topic. This would be easier and require less changes as tables are added/removed, and it would ensure that all change events for a single transaction are adjacent to each other. I suspect Teiid would prefer to use this approach, but it’ll be at least a few weeks before we have that. [1] http://www.confluent.io/blog/tutorial-getting-started-with-the-new-apache... > Integrate with Debezium for CDC for maintaining materialized views > ------------------------------------------------------------------ > > Key: TEIID-4526 > URL: https://issues.jboss.org/browse/TEIID-4526 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2578: ------------------------------------- On second that I do not think we wnat -vdb.ddl based deployment at all, there not much value at all in that. >> inverted the role of DatabaseStorage, so that DatabaseStore is primary. Also combined PersistenceProxy and DatabaseStorage. BTW, I reason behind this was DatabaseStorage is extension point for user to provide additional storages, where as the DatabaseStore is engine controlled, no user extensions here. PersistenceProxy is fine, as I mentioned before, this needs to be expanded for finer grade methods, since I was just doing file based persistence I took block methods for time being. >> we need to address the potential consistency issues with alter to prevent the entire vdb / repository from becoming unusable. The way I was trying do this is unless the metadata is valid, it will not make it into DatabaseStore, thus keeping it pristine. You are correct, in order to do it correctly, we need like SNAPSHOT of changes that can be overlaid on DatabaseStore, and validate. I could not think of a cleaver way to do this with out duplicated whole state of DatabaseStore. Needs a rethought here. >>databasestorage service has some wait cycles. shouldn't it just be able to wait for services? yeah, the data sources availability could not tie it, on server restart while loading the VDBs from repo, these will get ahead of the system start. This needs to wait until system started then it can do the loading. Then this can avoid creation of data sources if they exist. I think this can be avoided, need to take another look. > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4519) JDG prevent execution of delete or update on child objects

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4519?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4519: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1385644|https://bugzilla.redhat.com/show_bug.cgi?id=1385644] from NEW to MODIFIED > JDG prevent execution of delete or update on child objects > ---------------------------------------------------------- > > Key: TEIID-4519 > URL: https://issues.jboss.org/browse/TEIID-4519 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 9.2, 8.12.7.6_3 > > > When using JDG and complex pojos, delete query issued against child tables end with error. > * 1-1 relation: > When deleting a child object, whole parent object is deleted > * 1-n relation: > An exception is thrown: > {code:plain} > 13:31:28,926 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue91) Connector worker process failed for atomic-request=rKsoeHUfbaAW.21.0.21: org.teiid.translator.TranslatorException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:388) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.executeUpdate(ObjectUpdateExecution.java:137) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.execute(ObjectUpdateExecution.java:100) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:402) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) [:1.8.0_102] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_102] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at com.sun.proxy.$Proxy81.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_102] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_102] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_102] > Caused by: javax.script.ScriptException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectScriptEngine$1.eval(ObjectScriptEngine.java:144) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:372) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > ... 20 more > {code} > These two cases should be handled. Given the lack of DELETE support, all the DELETE queries on child entities should throw exception instead. > The DELETE on parent should be enabled though. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2578: --------------------------------------- > and mark the imported metadata as READONLY and not allow any ALTER or persistent operations. The side effect of supporting this style of import is that the vdb load becomes dependent upon services or we have to limit the import to only other ddl based vdbs and add logic to handle the load order. > But if want to go towards the deployment based, we can simply provide *-vdb.ddl based deployer back into this without much hassle, but we would not support ALTERS on that. That depends upon how far we want to go with these changes. If the effect of deployment was simply to tie the deployment to an equivalent databasestore state, then alter would be supported. Next changes: - inverted the role of DatabaseStorage, so that DatabaseStore is primary. Also combined PersistenceProxy and DatabaseStorage. - implemented an undo/restore of a change if there is a metadata validation issue - created a dummy command/plan to represent non-statement based ddl - suppressed the cancel exception for ddl Concerns: - we need to address the potential consistency issues with alter to prevent the entire vdb / repository from becoming unusable. - we may need to address the performance of metadata writes as eventually these files could grow to 10s of megabytes. - databasestorage service has some wait cycles. shouldn't it just be able to wait for services? - authorization is not checked for ddl operations I think the best approach at this point is for me to push my changes to a common branch under teiid and we'll continue to iterate on things from there. > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4284) Implement Salesforce Bulk API for SELECTS to Salesforce Connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4284?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4284: --------------------------------------- This has been addressed with another commit. > Implement Salesforce Bulk API for SELECTS to Salesforce Connector > ----------------------------------------------------------------- > > Key: TEIID-4284 > URL: https://issues.jboss.org/browse/TEIID-4284 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 8.13.5 > Environment: With Salesforce datasource > Reporter: sameer P > Assignee: Steven Hawkins > Fix For: 9.2 > > > There is some huge data (many GBs) in the Salesforce which has around 1.5 million rows and doing some simple select * on it fails with QUERY_TIMEOUT. > The salesforce guys suggested to try Bulk API for select with PK chunking as stated in https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asy... . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4284) Implement Salesforce Bulk API for SELECTS to Salesforce Connector

by sameer P (JIRA)

[ https://issues.jboss.org/browse/TEIID-4284?page=com.atlassian.jira.plugin... ] sameer P commented on TEIID-4284: --------------------------------- Yes exatly steven. I happens only when I enable bulk. > Implement Salesforce Bulk API for SELECTS to Salesforce Connector > ----------------------------------------------------------------- > > Key: TEIID-4284 > URL: https://issues.jboss.org/browse/TEIID-4284 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 8.13.5 > Environment: With Salesforce datasource > Reporter: sameer P > Assignee: Steven Hawkins > Fix For: 9.2 > > > There is some huge data (many GBs) in the Salesforce which has around 1.5 million rows and doing some simple select * on it fails with QUERY_TIMEOUT. > The salesforce guys suggested to try Bulk API for select with PK chunking as stated in https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asy... . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4518) Add module dependencies to support JDG 7.1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4518?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4518: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1385628|https://bugzilla.redhat.com/show_bug.cgi?id=1385628] from NEW to MODIFIED > Add module dependencies to support JDG 7.1 > ------------------------------------------ > > Key: TEIID-4518 > URL: https://issues.jboss.org/browse/TEIID-4518 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.7.6_3 > > > The JDG 7.1 modules need to be added as dependencies in the infinispan translator and connector module.xml files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2578: ------------------------------------- >> You loose ease of use of metadata reload in the import schema case. That is something we could workaround by adding a high-level operation that drops all the objects of the schema, >>then reruns the import as part of a "restart" operation. User has the ability to carry out this operation, it is not just tied to the restart/redeploy option. It provides a different way to update, so IMO this is OK as long as there is way to do this. On VDB import I agree. How about something like CREATE SCHEMA {name} IDENTIFIED BY DATABASE x VERSION y SCHEMA z; and mark the imported metadata as READONLY and not allow any ALTER or persistent operations. >>Not yet, they require a RuntimeVDB acquired from the VDBService, which is not associated with a DDL based VDB. I know I worked on this, I do not think I ran through all the methods. I do not think we can have this as complete replacement with other behavior wise, especially when there is no external concept of deployment. But if want to go towards the deployment based, we can simply provide *-vdb.ddl based deployer back into this without much hassle, but we would not support ALTERS on that. > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2578: --------------------------------------- > With this we are some what similar to other databases. To an extent. You loose ease of use of metadata reload in the import schema case. That is something we could workaround by adding a high-level operation that drops all the objects of the schema, then reruns the import as part of a "restart" operation. However we are fundamentally breaking the expectations of the vdb reuse feature. The reuse here is now only at the time of the import statement - any further changes to the imported vdb require a manual process on the part of the user to incorporate into all importing vdbs. I don't see a simple workaround here since the load operation from the databasestore assumes everything is fully realized and in a valid state. The load will need some work in general as any issue with any vdb load will cause the whole load to be aborted. > They should work Not yet, they require a RuntimeVDB acquired from the VDBService, which is not associated with a DDL based VDB. > I see the benefits of deployment and repository based vdbs, we need to articulate both positions in examples and documents to choose what is better for the user. I'm a little uncomfortable with that if it means they have different capabilities/behavior. > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2578: ------------------------------------- >>import operations have different semantics than the declarations in a vdb.xml where schema imports can be redone on restart/demand and vdb imports are based upon the service. Yes, these semantics are different. The way I am viewing this is, the act of restart/redpolying of the VDB or someone explicitly updating the schema, both are actions taken by the user. With this we are some what similar to other databases. >>there is no service / runtime vdb created for the ddl based vdbs. all of the admin VDBOperations won't work correct? They should work, the service is required so that we can tie a deployment artifact to the VDB. Since here there is no deployment of the VDB then that layer is not needed. I had to move some functionalities of other services around but it should work. I see the benefits of deployment and repository based vdbs, we need to articulate both positions in examples and documents to choose what is better for the user. > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4510) JDG Complex POJO 1-n relationship wrong results when joining parent and child table

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4510?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4510: --------------------------------- Fix Version/s: 8.12.7.6_3 > JDG Complex POJO 1-n relationship wrong results when joining parent and child table > ----------------------------------------------------------------------------------- > > Key: TEIID-4510 > URL: https://issues.jboss.org/browse/TEIID-4510 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.2, 8.12.6.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Blocker > Fix For: 9.2, 8.12.7.6_3 > > > When using infinispan-cache-dsl translator to access JDG cache incorrect results are returned for joins between the parent and child table. > POJO proto schema: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > /* @Indexed */ > message PhoneNumber { > /* @IndexedField */ > required string number = 1; > } > {code} > Source metadata: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE TRUE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE TRUE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > Tested scenario: > {code:sql} > SELECT COUNT(*) FROM PhoneNumber WHERE id=1 > {code} > returns 2. > {code:sql} > SELECT COUNT(*) FROM Person p, PhoneNumber pn WHERE p.id=pn.id AND p.id=1 > {code} > or > {code:sql} > SELECT COUNT(*) FROM Person p INNER JOIN PhoneNumber pn ON p.id=pn.id WHERE p.id=1 > {code} > both return only 1. > NOTE: issue appears also when using only nested descriptors in the proto schema. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4456) Enable the abiltiy to support nested and non-nested message descriptors

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4456?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4456: --------------------------------- Fix Version/s: 8.12.7.6_3 > Enable the abiltiy to support nested and non-nested message descriptors > ----------------------------------------------------------------------- > > Key: TEIID-4456 > URL: https://issues.jboss.org/browse/TEIID-4456 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.x, 9.1, 8.12.7.6_3 > > > Protobuf definition files can have messages defined in a nested and non-nested form. > Nested: > {code} > package bigdata; > message DataEntity { > .. > optional MetaData context = 6; > message MetaData { > ... > } > } > {code} > Non-nested: > {code} > package bigdata; > message DataEntity { > .. > optional MetaData context = 6; > } > message MetaData { > ... > } > {code} > The ProtobufMetadataProcessor needs to be changed to so that it can create the metadata from either use case. > Currently it obtains the child descriptor messages from the parent descriptor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4478) The 1-to-1 relationship currently doesn't work and doesn't error either

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4478?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4478: --------------------------------- Fix Version/s: 8.12.7.6_3 > The 1-to-1 relationship currently doesn't work and doesn't error either > ----------------------------------------------------------------------- > > Key: TEIID-4478 > URL: https://issues.jboss.org/browse/TEIID-4478 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > Fix For: 9.1, 8.12.7.6_3 > > > The 1-to-1 relationship currently doesn't work or produce an exception. It appears to not be specifically handled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC for maintaining materialized views

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4526: ------------------------------- Summary: Integrate with Debezium for CDC for maintaining materialized views (was: Integrate with Debezium for CDC) > Integrate with Debezium for CDC for maintaining materialized views > ------------------------------------------------------------------ > > Key: TEIID-4526 > URL: https://issues.jboss.org/browse/TEIID-4526 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4526: ---------------------------------- Priority: Critical (was: Blocker) This cannot block a release without being scoped in terms of effort / level of integration. There are existing hooks that we provide for emitting and reacting to events which can be already be leveraged with minimal work. However anything that is new feature work needs to be well defined first. > Integrate with Debezium for CDC > ------------------------------- > > Key: TEIID-4526 > URL: https://issues.jboss.org/browse/TEIID-4526 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4526: ------------------------------- Priority: Blocker (was: Major) > Integrate with Debezium for CDC > ------------------------------- > > Key: TEIID-4526 > URL: https://issues.jboss.org/browse/TEIID-4526 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > > Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC

by Van Halbert (JIRA)

Van Halbert created TEIID-4526: ---------------------------------- Summary: Integrate with Debezium for CDC Key: TEIID-4526 URL: https://issues.jboss.org/browse/TEIID-4526 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 9.2 Reporter: Van Halbert Assignee: Steven Hawkins Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4525) postgresql translator - remove all nulls & non printable characters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4525?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4525: ------------------------------------- Component/s: JDBC Connector Fix Version/s: Open To Community 9.2 Priority: Minor (was: Major) Assignee: (was: Steven Hawkins) Thanks for capturing this Omar. > postgresql translator - remove all nulls & non printable characters > ------------------------------------------------------------------- > > Key: TEIID-4525 > URL: https://issues.jboss.org/browse/TEIID-4525 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: Omar Khan > Priority: Minor > Fix For: Open To Community, 9.2 > > > Would like to see the postgresql translator enhanced to add a feature to minimum remove nulls from text strings as some other databases i.e. Teradata allow for them where Postgres does not. This feature would behave in a similar manner as TrimSpaces, but simply remove all \u0000 characters. > Furthermore, if possible, would like the ability to remove non printable characters to as another option provide another additional stripping mechanism, allowing the postgresql database to serve as a data cleaner if need be. > Please refer to https://developer.jboss.org/thread/272644 for details -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4510) JDG Complex POJO 1-n relationship wrong results when joining parent and child table

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4510?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4510. ----------------------------------- Resolution: Done Merged the pull request. > JDG Complex POJO 1-n relationship wrong results when joining parent and child table > ----------------------------------------------------------------------------------- > > Key: TEIID-4510 > URL: https://issues.jboss.org/browse/TEIID-4510 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.2, 8.12.6.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Blocker > Fix For: 9.2 > > > When using infinispan-cache-dsl translator to access JDG cache incorrect results are returned for joins between the parent and child table. > POJO proto schema: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > /* @Indexed */ > message PhoneNumber { > /* @IndexedField */ > required string number = 1; > } > {code} > Source metadata: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE TRUE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE TRUE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > Tested scenario: > {code:sql} > SELECT COUNT(*) FROM PhoneNumber WHERE id=1 > {code} > returns 2. > {code:sql} > SELECT COUNT(*) FROM Person p, PhoneNumber pn WHERE p.id=pn.id AND p.id=1 > {code} > or > {code:sql} > SELECT COUNT(*) FROM Person p INNER JOIN PhoneNumber pn ON p.id=pn.id WHERE p.id=1 > {code} > both return only 1. > NOTE: issue appears also when using only nested descriptors in the proto schema. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2578: --------------------------------------- Next set of changes: - don't allow ddl operations that have an immediate affect as prepared statements General concerns: - import operations have different semantics than the declarations in a vdb.xml where schema imports can be redone on restart/demand and vdb imports are based upon the service. - there is no service / runtime vdb created for the ddl based vdbs. all of the admin VDBOperations won't work correct? > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4284) Implement Salesforce Bulk API for SELECTS to Salesforce Connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4284?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4284: --------------------------------------- I don't think there is an issue with limit in general. This only happens when bulk is enabled correct? The BulkValidator isn't preventing pk chunking when there is a limit clause. > Implement Salesforce Bulk API for SELECTS to Salesforce Connector > ----------------------------------------------------------------- > > Key: TEIID-4284 > URL: https://issues.jboss.org/browse/TEIID-4284 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 8.13.5 > Environment: With Salesforce datasource > Reporter: sameer P > Assignee: Steven Hawkins > Fix For: 9.2 > > > There is some huge data (many GBs) in the Salesforce which has around 1.5 million rows and doing some simple select * on it fails with QUERY_TIMEOUT. > The salesforce guys suggested to try Bulk API for select with PK chunking as stated in https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asy... . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4284) Implement Salesforce Bulk API for SELECTS to Salesforce Connector

by sameer P (JIRA)

[ https://issues.jboss.org/browse/TEIID-4284?page=com.atlassian.jira.plugin... ] sameer P commented on TEIID-4284: --------------------------------- Hi Steven, thanks for the quick fix and the update. I have tested it and it seems to work. One small thing that it fails is when I use *Limit* in the query. {code:java} Error: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 TEIID30020 Processing exception for request NUTgU8jrEfAJ.19 : InvalidBatch : Failed to process query: MALFORMED_QUERY: FROM table_name LIMIT 100 where Id >= 'a03i000000QeywZ' and ^ ERROR at Row:1:Column:334 unexpected token: where'. Originally TeiidProcessingException SQLState: 50000 ErrorCode: 30504 {code} May be something wrong with the placement of Limits? > Implement Salesforce Bulk API for SELECTS to Salesforce Connector > ----------------------------------------------------------------- > > Key: TEIID-4284 > URL: https://issues.jboss.org/browse/TEIID-4284 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 8.13.5 > Environment: With Salesforce datasource > Reporter: sameer P > Assignee: Steven Hawkins > Fix For: 9.2 > > > There is some huge data (many GBs) in the Salesforce which has around 1.5 million rows and doing some simple select * on it fails with QUERY_TIMEOUT. > The salesforce guys suggested to try Bulk API for select with PK chunking as stated in https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asy... . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4519) JDG prevent execution of delete or update on child objects

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4519?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4519: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1385644 Bugzilla Update: Perform > JDG prevent execution of delete or update on child objects > ---------------------------------------------------------- > > Key: TEIID-4519 > URL: https://issues.jboss.org/browse/TEIID-4519 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 9.2, 8.12.7.6_3 > > > When using JDG and complex pojos, delete query issued against child tables end with error. > * 1-1 relation: > When deleting a child object, whole parent object is deleted > * 1-n relation: > An exception is thrown: > {code:plain} > 13:31:28,926 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue91) Connector worker process failed for atomic-request=rKsoeHUfbaAW.21.0.21: org.teiid.translator.TranslatorException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:388) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.executeUpdate(ObjectUpdateExecution.java:137) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.execute(ObjectUpdateExecution.java:100) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:402) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) [:1.8.0_102] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_102] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at com.sun.proxy.$Proxy81.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_102] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_102] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_102] > Caused by: javax.script.ScriptException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectScriptEngine$1.eval(ObjectScriptEngine.java:144) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:372) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > ... 20 more > {code} > These two cases should be handled. Given the lack of DELETE support, all the DELETE queries on child entities should throw exception instead. > The DELETE on parent should be enabled though. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2578: ------------------------------------- [~shawkins] I also need help with Arquaillian Integration test over JDBC. I was not able to decide a good way to handle the disconnection of session and cancellation of query correctly. > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2578: --------------------------------------- I've started to make changes locally as part of the merge, here's what I have so far: - changed all new reserved to non-reserved - minor changes to requestmessage serialization handling - changed "use schema" to "set schema" (more common) - also removed any side affect with create/drop in terms of altering the current schema The last change means that we should support "create schema" that also takes a list of ddl. I should hopefully have things merged tomorrow. > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4520) Support for Exasol Connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4520?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4520: ------------------------------------- Fix Version/s: 9.2 Assignee: (was: Steven Hawkins) Needs an initial evaluation in 9.2. Any takers? > Support for Exasol Connector > ---------------------------- > > Key: TEIID-4520 > URL: https://issues.jboss.org/browse/TEIID-4520 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Fix For: 9.2 > > > Requesting support for Exasol Connector -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4525) postgresql translator - remove all nulls & non printable characters

by Omar Khan (JIRA)

Omar Khan created TEIID-4525: -------------------------------- Summary: postgresql translator - remove all nulls & non printable characters Key: TEIID-4525 URL: https://issues.jboss.org/browse/TEIID-4525 Project: Teiid Issue Type: Feature Request Reporter: Omar Khan Assignee: Steven Hawkins Would like to see the postgresql translator enhanced to add a feature to minimum remove nulls from text strings as some other databases i.e. Teradata allow for them where Postgres does not. This feature would behave in a similar manner as TrimSpaces, but simply remove all \u0000 characters. Furthermore, if possible, would like the ability to remove non printable characters to as another option provide another additional stripping mechanism, allowing the postgresql database to serve as a data cleaner if need be. Please refer to https://developer.jboss.org/thread/272644 for details -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4393) Add new Geospatial functions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4393?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4393: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1385679, https://bugzilla.redhat.com/show_bug.cgi?id=1383776 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1383776) > Add new Geospatial functions > ---------------------------- > > Key: TEIID-4393 > URL: https://issues.jboss.org/browse/TEIID-4393 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.12.x, 9.x > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.1 > > > Adding a list of geospatial features to be added. Used the following specification: https://portal.opengeospatial.org/files/?artifact_id=829 > st_Dimension > st_GeometryType > st_IsEmpty > st_IsSimple > st_Boundary > st_Envelope > st_X > st_Y > st_StartPoint > st_EndPoint > st_Boundary > st_Boundary > st_Length > st_NumPoints > st_PointN > st_Centroid > st_PointOnSurface > st_Area > st_ExteriorRing > st_NumInteriorRings > st_InteriorRingN > st_NumGeometries > st_GeometryN > st_IsClosed > st_Length > st_Centroid > st_PointOnSurface > st_Area > st_Within > st_Relate > st_Intersection > st_Difference > st_Union > st_SymmetricDifference > st_Buffer > st_ConvexHull -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4524) Add support for Microsoft SQL Server Sequences to the translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4524?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4524. ----------------------------------- Fix Version/s: 9.2 Resolution: Done Added an example function for SQL Server sequence support. We do not do anything special in terms of detecting when push down is valid - that is all of the normal sql server restrictions on when a function can be used apply. > Add support for Microsoft SQL Server Sequences to the translator > ---------------------------------------------------------------- > > Key: TEIID-4524 > URL: https://issues.jboss.org/browse/TEIID-4524 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.2 > > > As of Microsoft SQL Server 2012 - https://msdn.microsoft.com/en-us/library/ff878058%28v=sql.110%29.aspx they have SEQUENCE like Oracle. Can the Microsoft SQL Server translator be changed to handle it the same or similar to the way we handle the Oracle SEQUENCE? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4524) Add support for Microsoft SQL Server Sequences to the translator

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-4524?page=com.atlassian.jira.plugin... ] Debbie Steigner commented on TEIID-4524: ---------------------------------------- That will be fine, thank you. > Add support for Microsoft SQL Server Sequences to the translator > ---------------------------------------------------------------- > > Key: TEIID-4524 > URL: https://issues.jboss.org/browse/TEIID-4524 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > As of Microsoft SQL Server 2012 - https://msdn.microsoft.com/en-us/library/ff878058%28v=sql.110%29.aspx they have SEQUENCE like Oracle. Can the Microsoft SQL Server translator be changed to handle it the same or similar to the way we handle the Oracle SEQUENCE? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4524) Add support for Microsoft SQL Server Sequences to the translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4524?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4524: ---------------------------------- Component/s: JDBC Connector If there is no objection, this will be resolved as a documentation issue. The same recommendation for oracle will be made for SQL Server, that is use a function: CREATE FOREIGN FUNCTION seq_nextval () returns integer OPTIONS ("teiid_rel:native-query" 'NEXT VALUE FOR seq'); > Add support for Microsoft SQL Server Sequences to the translator > ---------------------------------------------------------------- > > Key: TEIID-4524 > URL: https://issues.jboss.org/browse/TEIID-4524 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > As of Microsoft SQL Server 2012 - https://msdn.microsoft.com/en-us/library/ff878058%28v=sql.110%29.aspx they have SEQUENCE like Oracle. Can the Microsoft SQL Server translator be changed to handle it the same or similar to the way we handle the Oracle SEQUENCE? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4524) Add support for Microsoft SQL Server Sequences to the translator

by Debbie Steigner (JIRA)

Debbie Steigner created TEIID-4524: -------------------------------------- Summary: Add support for Microsoft SQL Server Sequences to the translator Key: TEIID-4524 URL: https://issues.jboss.org/browse/TEIID-4524 Project: Teiid Issue Type: Feature Request Reporter: Debbie Steigner Assignee: Steven Hawkins As of Microsoft SQL Server 2012 - https://msdn.microsoft.com/en-us/library/ff878058%28v=sql.110%29.aspx they have SEQUENCE like Oracle. Can the Microsoft SQL Server translator be changed to handle it the same or similar to the way we handle the Oracle SEQUENCE? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4284) Implement Salesforce Bulk API for SELECTS to Salesforce Connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4284?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4284. ----------------------------------- Resolution: Done Marking as resolved again for 9.2. The logic will now detect if pk chunking is possible. > Implement Salesforce Bulk API for SELECTS to Salesforce Connector > ----------------------------------------------------------------- > > Key: TEIID-4284 > URL: https://issues.jboss.org/browse/TEIID-4284 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 8.13.5 > Environment: With Salesforce datasource > Reporter: sameer P > Assignee: Steven Hawkins > Fix For: 9.2 > > > There is some huge data (many GBs) in the Salesforce which has around 1.5 million rows and doing some simple select * on it fails with QUERY_TIMEOUT. > The salesforce guys suggested to try Bulk API for select with PK chunking as stated in https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asy... . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4516) Add support for updating child objects

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4516: ---------------------------------- Fix Version/s: 9.2 > Add support for updating child objects > -------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.2, 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 9.2 > > > When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. > The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > INSERT queries to prepare data: > {code:sql} > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') > {code} > UPDATE queries and queries for checking results: > * 1-to-1 > {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} > {code:sql}SELECT * FROM Person,Address{code} > * 1-to-n > {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} > {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4517) Add support for deleting child objects

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4517?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4517: ---------------------------------- Fix Version/s: 9.2 > Add support for deleting child objects > -------------------------------------- > > Key: TEIID-4517 > URL: https://issues.jboss.org/browse/TEIID-4517 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.2, 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 9.2 > > > Infinispan cache dsl translator currently doesn't support deleting child objects when using complex POJO classes. > Example of complex POJO: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > Mapped metadata: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > Expected usage: > {code:sql} > DELETE FROM PhoneNumber WHERE id=3 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4523) CXF is not used by Salesforce BulkConnection

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4523: ------------------------------------- Summary: CXF is not used by Salesforce BulkConnection Key: TEIID-4523 URL: https://issues.jboss.org/browse/TEIID-4523 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 8.12 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.2 TEIID-3493 added the CXF transport, but it's not used by the salesforce BulkConnection. In v22 they make use of a static call, so we won't make a change there. With 34 we can extend the SalesforceConnectorConfig createConnection - but a HttpURLConnection is expected so this may not be straight-forward. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4522) Add module dependencies to support JDG 7.1

by Van Halbert (JIRA)

Van Halbert created TEIID-4522: ---------------------------------- Summary: Add module dependencies to support JDG 7.1 Key: TEIID-4522 URL: https://issues.jboss.org/browse/TEIID-4522 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.12.7.6_3 Reporter: Van Halbert Assignee: Van Halbert Fix For: 8.12.7.6_3 The JDG 7.1 modules need to be added as dependencies in the infinispan translator and connector module.xml files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4510) JDG Complex POJO 1-n relationship wrong results when joining parent and child table

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4510?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4510: ------------------------------- Fix Version/s: 9.2 > JDG Complex POJO 1-n relationship wrong results when joining parent and child table > ----------------------------------------------------------------------------------- > > Key: TEIID-4510 > URL: https://issues.jboss.org/browse/TEIID-4510 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.2, 8.12.6.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Blocker > Fix For: 9.2 > > > When using infinispan-cache-dsl translator to access JDG cache incorrect results are returned for joins between the parent and child table. > POJO proto schema: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > /* @Indexed */ > message PhoneNumber { > /* @IndexedField */ > required string number = 1; > } > {code} > Source metadata: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE TRUE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE TRUE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > Tested scenario: > {code:sql} > SELECT COUNT(*) FROM PhoneNumber WHERE id=1 > {code} > returns 2. > {code:sql} > SELECT COUNT(*) FROM Person p, PhoneNumber pn WHERE p.id=pn.id AND p.id=1 > {code} > or > {code:sql} > SELECT COUNT(*) FROM Person p INNER JOIN PhoneNumber pn ON p.id=pn.id WHERE p.id=1 > {code} > both return only 1. > NOTE: issue appears also when using only nested descriptors in the proto schema. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4510) JDG Complex POJO 1-n relationship wrong results when joining parent and child table

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4510?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4510: ------------------------------- Affects Version/s: 9.2 > JDG Complex POJO 1-n relationship wrong results when joining parent and child table > ----------------------------------------------------------------------------------- > > Key: TEIID-4510 > URL: https://issues.jboss.org/browse/TEIID-4510 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.2, 8.12.6.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Blocker > > When using infinispan-cache-dsl translator to access JDG cache incorrect results are returned for joins between the parent and child table. > POJO proto schema: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > /* @Indexed */ > message PhoneNumber { > /* @IndexedField */ > required string number = 1; > } > {code} > Source metadata: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE TRUE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE TRUE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > Tested scenario: > {code:sql} > SELECT COUNT(*) FROM PhoneNumber WHERE id=1 > {code} > returns 2. > {code:sql} > SELECT COUNT(*) FROM Person p, PhoneNumber pn WHERE p.id=pn.id AND p.id=1 > {code} > or > {code:sql} > SELECT COUNT(*) FROM Person p INNER JOIN PhoneNumber pn ON p.id=pn.id WHERE p.id=1 > {code} > both return only 1. > NOTE: issue appears also when using only nested descriptors in the proto schema. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4519) JDG prevent execution of delete or update on child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4519?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4519: ------------------------------- Summary: JDG prevent execution of delete or update on child objects (was: JDG prevent execution of delete on child objects) > JDG prevent execution of delete or update on child objects > ---------------------------------------------------------- > > Key: TEIID-4519 > URL: https://issues.jboss.org/browse/TEIID-4519 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 9.2, 8.12.7.6_3 > > > When using JDG and complex pojos, delete query issued against child tables end with error. > * 1-1 relation: > When deleting a child object, whole parent object is deleted > * 1-n relation: > An exception is thrown: > {code:plain} > 13:31:28,926 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue91) Connector worker process failed for atomic-request=rKsoeHUfbaAW.21.0.21: org.teiid.translator.TranslatorException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:388) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.executeUpdate(ObjectUpdateExecution.java:137) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.execute(ObjectUpdateExecution.java:100) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:402) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) [:1.8.0_102] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_102] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at com.sun.proxy.$Proxy81.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_102] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_102] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_102] > Caused by: javax.script.ScriptException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectScriptEngine$1.eval(ObjectScriptEngine.java:144) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:372) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > ... 20 more > {code} > These two cases should be handled. Given the lack of DELETE support, all the DELETE queries on child entities should throw exception instead. > The DELETE on parent should be enabled though. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4518) Add module dependencies to support JDG 7.1

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4518?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4518: ------------------------------- Fix Version/s: 8.12.7.6_3 > Add module dependencies to support JDG 7.1 > ------------------------------------------ > > Key: TEIID-4518 > URL: https://issues.jboss.org/browse/TEIID-4518 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.7.6_3 > > > The JDG 7.1 modules need to be added as dependencies in the infinispan translator and connector module.xml files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4517) Add support for deleting child objects

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4517?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4517: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1385639 Bugzilla Update: Perform > Add support for deleting child objects > -------------------------------------- > > Key: TEIID-4517 > URL: https://issues.jboss.org/browse/TEIID-4517 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.2, 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > > Infinispan cache dsl translator currently doesn't support deleting child objects when using complex POJO classes. > Example of complex POJO: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > Mapped metadata: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > Expected usage: > {code:sql} > DELETE FROM PhoneNumber WHERE id=3 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4519) JDG prevent execution of delete on child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4519?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4519: ------------------------------- Fix Version/s: 9.2 > JDG prevent execution of delete on child objects > ------------------------------------------------ > > Key: TEIID-4519 > URL: https://issues.jboss.org/browse/TEIID-4519 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 9.2, 8.12.7.6_3 > > > When using JDG and complex pojos, delete query issued against child tables end with error. > * 1-1 relation: > When deleting a child object, whole parent object is deleted > * 1-n relation: > An exception is thrown: > {code:plain} > 13:31:28,926 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue91) Connector worker process failed for atomic-request=rKsoeHUfbaAW.21.0.21: org.teiid.translator.TranslatorException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:388) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.executeUpdate(ObjectUpdateExecution.java:137) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.execute(ObjectUpdateExecution.java:100) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:402) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) [:1.8.0_102] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_102] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at com.sun.proxy.$Proxy81.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_102] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_102] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_102] > Caused by: javax.script.ScriptException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectScriptEngine$1.eval(ObjectScriptEngine.java:144) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:372) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > ... 20 more > {code} > These two cases should be handled. Given the lack of DELETE support, all the DELETE queries on child entities should throw exception instead. > The DELETE on parent should be enabled though. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4521) Add ability to sent ApplicationName thru ODBC connection

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4521?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4521: ---------------------------------- Description: add an ApplicationName property which can be set at connection for ODBC. This works for JDBC but for the Teiid ODBC driver does not seem to work. The ApplicationName is always set to 'ODBC'. Dutch police would like to distinct the entries from the Teiid Audit/Command Logging. (was: add an ApplicationName property which can be set at connection for ODBC. This works for JDBC but for the Teiid ODBC driver does not seem to work. The ApplicationName is always set to 'ODBC'.Would like to distinct the entries from the Teiid Audit/Command Logging.) Fix Version/s: 9.2 Looking at this more, we should go ahead and add server side support for set application_name as well as looking for application_name in the initialization - since these are standard mechanisms for postgresql. For example libpq supports the application_name option, but the odbc client does not pass it. Also the pg jdbc client will issue the set statement if the properties set contains ApplicationName and the server is 9.0+. > Add ability to sent ApplicationName thru ODBC connection > -------------------------------------------------------- > > Key: TEIID-4521 > URL: https://issues.jboss.org/browse/TEIID-4521 > Project: Teiid > Issue Type: Enhancement > Components: ODBC > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.2 > > > add an ApplicationName property which can be set at connection for ODBC. This works for JDBC but for the Teiid ODBC driver does not seem to work. The ApplicationName is always set to 'ODBC'. Dutch police would like to distinct the entries from the Teiid Audit/Command Logging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4521) Add ability to sent ApplicationName thru ODBC connection

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4521?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4521: ------------------------------- Description: add an ApplicationName property which can be set at connection for ODBC. This works for JDBC but for the Teiid ODBC driver does not seem to work. The ApplicationName is always set to 'ODBC'.Would like to distinct the entries from the Teiid Audit/Command Logging. (was: add an ApplicationName property which can be set at connection for ODBC. This works for JDBC but for the Teiid ODBC driver does not seem to work. The ApplicationName is always set to 'ODBC'. Dutch police would like to distinct the entries from the Teiid Audit/Command Logging.) > Add ability to sent ApplicationName thru ODBC connection > -------------------------------------------------------- > > Key: TEIID-4521 > URL: https://issues.jboss.org/browse/TEIID-4521 > Project: Teiid > Issue Type: Enhancement > Components: ODBC > Reporter: Van Halbert > Assignee: Steven Hawkins > > add an ApplicationName property which can be set at connection for ODBC. This works for JDBC but for the Teiid ODBC driver does not seem to work. The ApplicationName is always set to 'ODBC'.Would like to distinct the entries from the Teiid Audit/Command Logging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4521) Add ability to sent ApplicationName thru ODBC connection

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4521?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4521: ---------------------------------- Affects Version/s: (was: 9.x) Using an unmodified postgresql client, we don't have flexibility in what properties are sent at initialization time. This should not be worked until it's clear what is acceptable from a client perspective - do they expect this to be configured on the dsn, is it ok to issue a post connection statement, such as "set application_name 'foo'", etc. > Add ability to sent ApplicationName thru ODBC connection > -------------------------------------------------------- > > Key: TEIID-4521 > URL: https://issues.jboss.org/browse/TEIID-4521 > Project: Teiid > Issue Type: Enhancement > Components: ODBC > Reporter: Van Halbert > Assignee: Steven Hawkins > > add an ApplicationName property which can be set at connection for ODBC. This works for JDBC but for the Teiid ODBC driver does not seem to work. The ApplicationName is always set to 'ODBC'. Dutch police would like to distinct the entries from the Teiid Audit/Command Logging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4521) Add ability to sent ApplicationName thru ODBC connection

by Van Halbert (JIRA)

Van Halbert created TEIID-4521: ---------------------------------- Summary: Add ability to sent ApplicationName thru ODBC connection Key: TEIID-4521 URL: https://issues.jboss.org/browse/TEIID-4521 Project: Teiid Issue Type: Enhancement Components: ODBC Affects Versions: 9.x Reporter: Van Halbert Assignee: Steven Hawkins add an ApplicationName property which can be set at connection for ODBC. This works for JDBC but for the Teiid ODBC driver does not seem to work. The ApplicationName is always set to 'ODBC'. Dutch police would like to distinct the entries from the Teiid Audit/Command Logging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4520) Support for Exasol Connector

by Van Halbert (JIRA)

Van Halbert created TEIID-4520: ---------------------------------- Summary: Support for Exasol Connector Key: TEIID-4520 URL: https://issues.jboss.org/browse/TEIID-4520 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 9.x Reporter: Van Halbert Assignee: Steven Hawkins Requesting support for Exasol Connector -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4519) JDG prevent execution of delete on child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4519?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4519: ------------------------------- Fix Version/s: 8.12.7.6_3 > JDG prevent execution of delete on child objects > ------------------------------------------------ > > Key: TEIID-4519 > URL: https://issues.jboss.org/browse/TEIID-4519 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 8.12.7.6_3 > > > When using JDG and complex pojos, delete query issued against child tables end with error. > * 1-1 relation: > When deleting a child object, whole parent object is deleted > * 1-n relation: > An exception is thrown: > {code:plain} > 13:31:28,926 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue91) Connector worker process failed for atomic-request=rKsoeHUfbaAW.21.0.21: org.teiid.translator.TranslatorException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:388) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.executeUpdate(ObjectUpdateExecution.java:137) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.execute(ObjectUpdateExecution.java:100) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:402) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) [:1.8.0_102] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_102] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at com.sun.proxy.$Proxy81.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_102] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_102] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_102] > Caused by: javax.script.ScriptException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectScriptEngine$1.eval(ObjectScriptEngine.java:144) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:372) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > ... 20 more > {code} > These two cases should be handled. Given the lack of DELETE support, all the DELETE queries on child entities should throw exception instead. > The DELETE on parent should be enabled though. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4519) JDG prevent execution of delete on child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4519?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4519: ------------------------------------ Added the following message until this is implemented: Error: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 infinispan-cache-dsl-connector: TEIID21017 Unable to update or delete from child table Address, updating and deleting is currently disabled for child objects. SQLState: 50000 ErrorCode: 30504 > JDG prevent execution of delete on child objects > ------------------------------------------------ > > Key: TEIID-4519 > URL: https://issues.jboss.org/browse/TEIID-4519 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 8.12.7.6_3 > > > When using JDG and complex pojos, delete query issued against child tables end with error. > * 1-1 relation: > When deleting a child object, whole parent object is deleted > * 1-n relation: > An exception is thrown: > {code:plain} > 13:31:28,926 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue91) Connector worker process failed for atomic-request=rKsoeHUfbaAW.21.0.21: org.teiid.translator.TranslatorException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:388) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.executeUpdate(ObjectUpdateExecution.java:137) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.execute(ObjectUpdateExecution.java:100) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:402) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) [:1.8.0_102] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_102] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at com.sun.proxy.$Proxy81.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_102] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_102] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_102] > Caused by: javax.script.ScriptException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectScriptEngine$1.eval(ObjectScriptEngine.java:144) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:372) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > ... 20 more > {code} > These two cases should be handled. Given the lack of DELETE support, all the DELETE queries on child entities should throw exception instead. > The DELETE on parent should be enabled though. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4519) JDG prevent execution of delete on child objects

by Jan Stastny (JIRA)

Jan Stastny created TEIID-4519: ---------------------------------- Summary: JDG prevent execution of delete on child objects Key: TEIID-4519 URL: https://issues.jboss.org/browse/TEIID-4519 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.12.7.6_3 Reporter: Jan Stastny Assignee: Van Halbert Priority: Critical When using JDG and complex pojos, delete query issued against child tables end with error. * 1-1 relation: When deleting a child object, whole parent object is deleted * 1-n relation: An exception is thrown: {code:plain} 13:31:28,926 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue91) Connector worker process failed for atomic-request=rKsoeHUfbaAW.21.0.21: org.teiid.translator.TranslatorException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:388) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] at org.teiid.translator.object.ObjectUpdateExecution.executeUpdate(ObjectUpdateExecution.java:137) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] at org.teiid.translator.object.ObjectUpdateExecution.execute(ObjectUpdateExecution.java:100) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:402) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) [:1.8.0_102] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_102] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_102] at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] at com.sun.proxy.$Proxy81.execute(Unknown Source) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_102] at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_102] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_102] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_102] Caused by: javax.script.ScriptException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. at org.teiid.translator.object.ObjectScriptEngine$1.eval(ObjectScriptEngine.java:144) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:372) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] ... 20 more {code} These two cases should be handled. Given the lack of DELETE support, all the DELETE queries on child entities should throw exception instead. The DELETE on parent should be enabled though. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4517) Add support for deleting child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4517?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4517: ------------------------------- Affects Version/s: 9.2 > Add support for deleting child objects > -------------------------------------- > > Key: TEIID-4517 > URL: https://issues.jboss.org/browse/TEIID-4517 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.2, 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > > Infinispan cache dsl translator currently doesn't support deleting child objects when using complex POJO classes. > Example of complex POJO: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > Mapped metadata: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > Expected usage: > {code:sql} > DELETE FROM PhoneNumber WHERE id=3 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4516) Add support for updating child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4516: ------------------------------- Affects Version/s: 9.2 > Add support for updating child objects > -------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.2, 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > > When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. > The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > INSERT queries to prepare data: > {code:sql} > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') > {code} > UPDATE queries and queries for checking results: > * 1-to-1 > {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} > {code:sql}SELECT * FROM Person,Address{code} > * 1-to-n > {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} > {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4516) Add support for updating child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4516: ------------------------------- Summary: Add support for updating child objects (was: Add support for updating and deleting child objects) > Add support for updating child objects > -------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > > When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. > The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > INSERT queries to prepare data: > {code:sql} > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') > {code} > UPDATE queries and queries for checking results: > * 1-to-1 > {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} > {code:sql}SELECT * FROM Person,Address{code} > * 1-to-n > {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} > {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4518) Add module dependencies to support JDG 7.1

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4518?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-4518: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Add module dependencies to support JDG 7.1 > ------------------------------------------ > > Key: TEIID-4518 > URL: https://issues.jboss.org/browse/TEIID-4518 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Van Halbert > Assignee: Van Halbert > > The JDG 7.1 modules need to be added as dependencies in the infinispan translator and connector module.xml files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4518) Add module dependencies to support JDG 7.1

by Van Halbert (JIRA)

Van Halbert created TEIID-4518: ---------------------------------- Summary: Add module dependencies to support JDG 7.1 Key: TEIID-4518 URL: https://issues.jboss.org/browse/TEIID-4518 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.12.7.6_3 Reporter: Van Halbert Assignee: Steven Hawkins The JDG 7.1 modules need to be added as dependencies in the infinispan translator and connector module.xml files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4516) Add support for updating and deleting child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4516: ------------------------------- Summary: Add support for updating and deleting child objects (was: Add support for updating child objects) > Add support for updating and deleting child objects > --------------------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > > When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. > The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > INSERT queries to prepare data: > {code:sql} > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') > {code} > UPDATE queries and queries for checking results: > * 1-to-1 > {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} > {code:sql}SELECT * FROM Person,Address{code} > * 1-to-n > {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} > {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4517) Add support for deleting child objects

by Jan Stastny (JIRA)

Jan Stastny created TEIID-4517: ---------------------------------- Summary: Add support for deleting child objects Key: TEIID-4517 URL: https://issues.jboss.org/browse/TEIID-4517 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 8.12.7.6_3 Reporter: Jan Stastny Assignee: Van Halbert Priority: Critical Infinispan cache dsl translator currently doesn't support deleting child objects when using complex POJO classes. Example of complex POJO: {code:plain} package org.jboss.qe.jdg.remote.protobuf.complex; /* @Indexed */ message Person { /* @IndexedField(index=true, store=false) */ required int32 id = 1; /* @IndexedField */ required string name = 2; /* @IndexedField */ optional string email = 3; /* @IndexedField(index=true, store=false) */ repeated PhoneNumber phones = 4; /* @Indexed */ message Address { /* @IndexedField */ required string Address = 1; /* @IndexedField(index=true, store=false) */ required string City = 2; /* @IndexedField(index=true, store=false) */ required string State = 3; } /* @IndexedField(index=true, store=false) */ optional Address address = 5; } /* @Indexed */ message PhoneNumber { /* @IndexedField */ required string number = 1; } {code} Mapped metadata: {code:sql} CREATE FOREIGN TABLE Address ( Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') ) OPTIONS (UPDATABLE TRUE); CREATE FOREIGN TABLE Person ( id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), CONSTRAINT PK_ID PRIMARY KEY(id) ) OPTIONS (UPDATABLE TRUE); CREATE FOREIGN TABLE PhoneNumber ( number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') ) OPTIONS (UPDATABLE TRUE); {code} Expected result: {code:sql} DELETE FROM PhoneNumber WHERE id=3 {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4517) Add support for deleting child objects

by Jan Stastny (JIRA)

[ https://issues.jboss.org/browse/TEIID-4517?page=com.atlassian.jira.plugin... ] Jan Stastny updated TEIID-4517: ------------------------------- Description: Infinispan cache dsl translator currently doesn't support deleting child objects when using complex POJO classes. Example of complex POJO: {code:plain} package org.jboss.qe.jdg.remote.protobuf.complex; /* @Indexed */ message Person { /* @IndexedField(index=true, store=false) */ required int32 id = 1; /* @IndexedField */ required string name = 2; /* @IndexedField */ optional string email = 3; /* @IndexedField(index=true, store=false) */ repeated PhoneNumber phones = 4; /* @Indexed */ message Address { /* @IndexedField */ required string Address = 1; /* @IndexedField(index=true, store=false) */ required string City = 2; /* @IndexedField(index=true, store=false) */ required string State = 3; } /* @IndexedField(index=true, store=false) */ optional Address address = 5; } /* @Indexed */ message PhoneNumber { /* @IndexedField */ required string number = 1; } {code} Mapped metadata: {code:sql} CREATE FOREIGN TABLE Address ( Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') ) OPTIONS (UPDATABLE TRUE); CREATE FOREIGN TABLE Person ( id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), CONSTRAINT PK_ID PRIMARY KEY(id) ) OPTIONS (UPDATABLE TRUE); CREATE FOREIGN TABLE PhoneNumber ( number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') ) OPTIONS (UPDATABLE TRUE); {code} Expected usage: {code:sql} DELETE FROM PhoneNumber WHERE id=3 {code} was: Infinispan cache dsl translator currently doesn't support deleting child objects when using complex POJO classes. Example of complex POJO: {code:plain} package org.jboss.qe.jdg.remote.protobuf.complex; /* @Indexed */ message Person { /* @IndexedField(index=true, store=false) */ required int32 id = 1; /* @IndexedField */ required string name = 2; /* @IndexedField */ optional string email = 3; /* @IndexedField(index=true, store=false) */ repeated PhoneNumber phones = 4; /* @Indexed */ message Address { /* @IndexedField */ required string Address = 1; /* @IndexedField(index=true, store=false) */ required string City = 2; /* @IndexedField(index=true, store=false) */ required string State = 3; } /* @IndexedField(index=true, store=false) */ optional Address address = 5; } /* @Indexed */ message PhoneNumber { /* @IndexedField */ required string number = 1; } {code} Mapped metadata: {code:sql} CREATE FOREIGN TABLE Address ( Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') ) OPTIONS (UPDATABLE TRUE); CREATE FOREIGN TABLE Person ( id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), CONSTRAINT PK_ID PRIMARY KEY(id) ) OPTIONS (UPDATABLE TRUE); CREATE FOREIGN TABLE PhoneNumber ( number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') ) OPTIONS (UPDATABLE TRUE); {code} Expected result: {code:sql} DELETE FROM PhoneNumber WHERE id=3 {code} > Add support for deleting child objects > -------------------------------------- > > Key: TEIID-4517 > URL: https://issues.jboss.org/browse/TEIID-4517 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > > Infinispan cache dsl translator currently doesn't support deleting child objects when using complex POJO classes. > Example of complex POJO: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > Mapped metadata: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > Expected usage: > {code:sql} > DELETE FROM PhoneNumber WHERE id=3 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4516) Add support for updating child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4516: ------------------------------------ Added the following message until this is implmented: Error: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 infinispan-cache-dsl-connector: TEIID21017 Unable to update or delete from child table Address, updating and deleting is currently disabled for child objects. SQLState: 50000 ErrorCode: 30504 > Add support for updating child objects > -------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > > When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. > The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > INSERT queries to prepare data: > {code:sql} > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') > {code} > UPDATE queries and queries for checking results: > * 1-to-1 > {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} > {code:sql}SELECT * FROM Person,Address{code} > * 1-to-n > {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} > {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4516) Add support for updating child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4516: ------------------------------- Priority: Critical (was: Blocker) > Add support for updating child objects > -------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > > When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. > The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > INSERT queries to prepare data: > {code:sql} > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') > {code} > UPDATE queries and queries for checking results: > * 1-to-1 > {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} > {code:sql}SELECT * FROM Person,Address{code} > * 1-to-n > {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} > {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4516) Add support for updating child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4516: ------------------------------- Summary: Add support for updating child objects (was: JDG Complex POJO update on child table doesn't work) > Add support for updating child objects > -------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Blocker > > When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. > The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > INSERT queries to prepare data: > {code:sql} > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') > {code} > UPDATE queries and queries for checking results: > * 1-to-1 > {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} > {code:sql}SELECT * FROM Person,Address{code} > * 1-to-n > {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} > {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4516) JDG Complex POJO update on child table doesn't work

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4516: ------------------------------------ Updates to child objects is not yet supported, per the doc's. > JDG Complex POJO update on child table doesn't work > --------------------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Blocker > > When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. > The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > INSERT queries to prepare data: > {code:sql} > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') > {code} > UPDATE queries and queries for checking results: > * 1-to-1 > {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} > {code:sql}SELECT * FROM Person,Address{code} > * 1-to-n > {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} > {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4516) JDG Complex POJO update on child table doesn't work

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4516: ------------------------------- Issue Type: Feature Request (was: Bug) > JDG Complex POJO update on child table doesn't work > --------------------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Blocker > > When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. > The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > INSERT queries to prepare data: > {code:sql} > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') > {code} > UPDATE queries and queries for checking results: > * 1-to-1 > {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} > {code:sql}SELECT * FROM Person,Address{code} > * 1-to-n > {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} > {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4516) JDG Complex POJO update on child table doesn't work

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-4516: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > JDG Complex POJO update on child table doesn't work > --------------------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Blocker > > When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. > The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > INSERT queries to prepare data: > {code:sql} > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') > {code} > UPDATE queries and queries for checking results: > * 1-to-1 > {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} > {code:sql}SELECT * FROM Person,Address{code} > * 1-to-n > {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} > {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4516) JDG Complex POJO update on child table doesn't work

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-4516 at 10/17/16 7:37 AM: -------------------------------------------------------------- Updates to child objects is not yet supported, per the doc's. This is something that is still be done. was (Author: van.halbert): Updates to child objects is not yet supported, per the doc's. > JDG Complex POJO update on child table doesn't work > --------------------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Blocker > > When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. > The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > INSERT queries to prepare data: > {code:sql} > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') > {code} > UPDATE queries and queries for checking results: > * 1-to-1 > {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} > {code:sql}SELECT * FROM Person,Address{code} > * 1-to-n > {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} > {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4516) JDG Complex POJO update on child table doesn't work

by Jan Stastny (JIRA)

Jan Stastny created TEIID-4516: ---------------------------------- Summary: JDG Complex POJO update on child table doesn't work Key: TEIID-4516 URL: https://issues.jboss.org/browse/TEIID-4516 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.12.7.6_3 Reporter: Jan Stastny Assignee: Steven Hawkins Priority: Blocker When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: {code:plain} package org.jboss.qe.jdg.remote.protobuf.complex; /* @Indexed */ message Person { /* @IndexedField(index=true, store=false) */ required int32 id = 1; /* @IndexedField */ required string name = 2; /* @IndexedField */ optional string email = 3; /* @IndexedField(index=true, store=false) */ repeated PhoneNumber phones = 4; /* @Indexed */ message Address { /* @IndexedField */ required string Address = 1; /* @IndexedField(index=true, store=false) */ required string City = 2; /* @IndexedField(index=true, store=false) */ required string State = 3; } /* @IndexedField(index=true, store=false) */ optional Address address = 5; } /* @Indexed */ message PhoneNumber { /* @IndexedField */ required string number = 1; } {code} That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: {code:sql} CREATE FOREIGN TABLE Address ( Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') ) OPTIONS (UPDATABLE TRUE); CREATE FOREIGN TABLE Person ( id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), CONSTRAINT PK_ID PRIMARY KEY(id) ) OPTIONS (UPDATABLE TRUE); CREATE FOREIGN TABLE PhoneNumber ( number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') ) OPTIONS (UPDATABLE TRUE); {code} INSERT queries to prepare data: {code:sql} INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') {code} UPDATE queries and queries for checking results: * 1-to-1 {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} {code:sql}SELECT * FROM Person,Address{code} * 1-to-n {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4510) JDG Complex POJO 1-n relationship wrong results when joining parent and child table

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4510?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4510: ------------------------------------ It was incorrectly returning 2 for getMaxFromGroups(), should have been 1. What is needed is each table is individually queried, then the results are joined in Teiid (but that wasn't happening). > JDG Complex POJO 1-n relationship wrong results when joining parent and child table > ----------------------------------------------------------------------------------- > > Key: TEIID-4510 > URL: https://issues.jboss.org/browse/TEIID-4510 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.6.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Blocker > > When using infinispan-cache-dsl translator to access JDG cache incorrect results are returned for joins between the parent and child table. > POJO proto schema: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > /* @Indexed */ > message PhoneNumber { > /* @IndexedField */ > required string number = 1; > } > {code} > Source metadata: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE TRUE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE TRUE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > Tested scenario: > {code:sql} > SELECT COUNT(*) FROM PhoneNumber WHERE id=1 > {code} > returns 2. > {code:sql} > SELECT COUNT(*) FROM Person p, PhoneNumber pn WHERE p.id=pn.id AND p.id=1 > {code} > or > {code:sql} > SELECT COUNT(*) FROM Person p INNER JOIN PhoneNumber pn ON p.id=pn.id WHERE p.id=1 > {code} > both return only 1. > NOTE: issue appears also when using only nested descriptors in the proto schema. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2016