October 2016 - teiid-issues - Jboss List Archives

[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)

8 years, 2 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)

8 years, 2 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)

8 years, 2 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)

8 years, 2 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)

8 years, 2 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)

8 years, 2 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)

8 years, 2 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)

8 years, 2 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)

8 years, 2 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)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2016