[JBoss JIRA] (TEIID-3166) Allow allowDiskUse setting in MongoDB translator
by Ivan Chan (JIRA)
[ https://issues.jboss.org/browse/TEIID-3166?page=com.atlassian.jira.plugin... ]
Ivan Chan commented on TEIID-3166:
----------------------------------
I created another test case, but still bumped into error.
Here is my sql:
select "antiNucleus",
"eventFile",
"eventNumber",
"eventTime"
from "MongoDB_DS"."star2002"
order by "eventFile", "antiNucleus"
limit 900000001
And Teiid translates it to:
{"$project": {{ "c_0" : "$antiNucleus" , "c_1" : "$eventFile" , "c_2" : "$eventNumber" , "c_3
" : "$eventTime"}}}
{"$sort": {{ "c_1" : 1 , "c_0" : 1}}}
{"$skip": {0}}
{"$limit": {900000001}}
And I hit this error right away:
Caused by: com.mongodb.CommandFailureException: { "serverUsed" : "ec2-54-161-255-173.compute-1.amazonaws.com:27017" , "errmsg" : "exception: Sort exceeded memory limit of 104857600 bytes, but did not
opt in to external sorting. Aborting operation. Pass allowDiskUse:true to opt in." , "code" : 16820 , "ok" : 0.0}
at com.mongodb.CommandResult.getException(CommandResult.java:76)
at com.mongodb.CommandResult.throwOnError(CommandResult.java:131)
at com.mongodb.DBCollectionImpl.aggregate(DBCollectionImpl.java:100)
at com.mongodb.DBCollection.aggregate(DBCollection.java:1571)
- See more at: https://developer.jboss.org/message/928949?et=watches.email.thread#928949
> Allow allowDiskUse setting in MongoDB translator
> ------------------------------------------------
>
> Key: TEIID-3166
> URL: https://issues.jboss.org/browse/TEIID-3166
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Harrison Gentry
> Assignee: Ramesh Reddy
> Priority: Minor
> Labels: CR1
> Fix For: 8.9
>
>
> When querying a MongoDB, steps of computation are limited to 100MiB. Querying large databases can easily exceed this limit, so usually allowDiskUse:true is passed in the aggregate query:
> http://docs.mongodb.org/manual/reference/command/aggregate/
> In Teiid, however, there is currently no way to specify this with SQL.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIID-3429) Provide hooks to interrogate metadata prior to full import
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIID-3429?page=com.atlassian.jira.plugin... ]
Barry LaFond commented on TEIID-3429:
-------------------------------------
This feature was logged in response to 2 issues with Designer's Teiid Connection Importer:
The primary issue is around the generic nature of the exposed *importer* properties. There have been a number of complaints about the performance of Designer trying to grab the DDL/Schema in the importer. In some cases just setting tableType == TABLE can drastically improve it. Our JDBC importer is a little smarter because we can get the table types, schema names and assist the user in fine-tuning the *requests* so we don't bring back ALL the metadata.
* For the JDBC, what you offered in the description would be a great start. getTableTypes(), getCatalogNames(), getSchemaNames() would provide the user a shopping list to narrow down the import before calling getTableNames() and getProcedureNames().
A secondary issue is that some data source types are not supported through the importer. Flat File, XML File and Web Service (REST/SOAP) for instance. These require a conversation with the user to successfully model these sources.
* Support for these other data sources would probably hinge on what schema/metadata is available to you, if at all. I would think that since our Flat File SQL, for instance, contains actual "data format" information that you don't really hold any schema for these file.
> Provide hooks to interrogate metadata prior to full import
> -----------------------------------------------------------
>
> Key: TEIID-3429
> URL: https://issues.jboss.org/browse/TEIID-3429
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> To support the Desinger we should offer the ability to interrogate metadata prior to full import.
> Exploring metadata is effectively an entirely different mode of operation with respect to the current metadata processing logic on the Teiid side. Also partial metadata isn't something that would neatly be expressed through DDL - tables without columns, a list of schema names, etc.
> Ways around that would be to expose source procedures for metadata interrogation:
>
> getTableNames - which would probably give both the Teiid name and the name in source and consider the current translator metadata settings
> getProcedureNames
> And importer specific info such as for JDBC getTableTypes, getCatalogNames, getSchemaNames
>
> I'd want to keep it fairly high level though. Getting column or key information I'd expect would be done through the normal full import.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIID-3369) Add a extension point to manipulate incoming sql
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3369?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3369:
---------------------------------------
Can you log an issue for making this vdb specific as well? And would that supersede or be in addition to the globally defined rewrite?
> Add a extension point to manipulate incoming sql
> ------------------------------------------------
>
> Key: TEIID-3369
> URL: https://issues.jboss.org/browse/TEIID-3369
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Driver, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> We should look at adding a client or server extension point for manipulating sql - just the sql string, pre resolving. This will allow more flexibility in dealing with clients that don't send queries directly understood by Teiid. For example a select for update.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIID-3470) NPE in ConnectorWorkItem when using source hints
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3470?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3470.
-----------------------------------
Resolution: Done
Added the missing null check.
> NPE in ConnectorWorkItem when using source hints
> ------------------------------------------------
>
> Key: TEIID-3470
> URL: https://issues.jboss.org/browse/TEIID-3470
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.5
> Reporter: Mark Addleman
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> When using a source general source hint in a query that uses multple sources, I get an NPE:
> java.lang.NullPointerException
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.<init>(ConnectorWorkItem.java:141)
> at org.teiid.dqp.internal.datamgr.ConnectorManager.registerRequest(ConnectorManager.java:203)
> at org.teiid.dqp.internal.process.DataTierManagerImpl.registerRequest(DataTierManagerImpl.java:966)
> at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:179)
> at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:475)
> at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:248)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
> at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
> at org.teiid.query.processor.relational.RelationalPlan.open(RelationalPlan.java:136)
> at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:231)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138)
> 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:457)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:339)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:267)
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:298)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:175)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260)
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:173)
> at com.sun.proxy.$Proxy14.executeRequest(Unknown Source)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:661)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:527)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIID-3469) Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3469?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3469.
-----------------------------------
Resolution: Done
Updated the name qualification to use the catalog separator and changed our databasemetadata to return a .
> Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator
> -----------------------------------------------------------------------------------------------
>
> Key: TEIID-3469
> URL: https://issues.jboss.org/browse/TEIID-3469
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.0
> Reporter: Bruno Machado
> Assignee: Steven Hawkins
> Priority: Minor
> Labels: ddl, designer, informix, schema, teiid
> Fix For: 8.11
>
>
> When importing from Teiid Data Source Connection using an Informix Translator, an incorrect schema DDL is set as "catalog"."schema"."table-name" instead of "catalog":"schema"."table-name", the delimiter between catalog and schema is set to '.' but Informix uses ':'.
> The '.' character must be replaced by a ':' between catalog and schema name when importing from Teiid Data Source Connection using Informix translator.
> useCatalogName attribute could be set to false as a workaround to this and ignore the occurance of "catalog".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIID-3470) NPE in ConnectorWorkItem when using source hints
by Mark Addleman (JIRA)
[ https://issues.jboss.org/browse/TEIID-3470?page=com.atlassian.jira.plugin... ]
Mark Addleman commented on TEIID-3470:
--------------------------------------
I can provide a test case if required but it looks like a pretty straightforward bug
> NPE in ConnectorWorkItem when using source hints
> ------------------------------------------------
>
> Key: TEIID-3470
> URL: https://issues.jboss.org/browse/TEIID-3470
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.11
> Reporter: Mark Addleman
> Assignee: Steven Hawkins
>
> When using a source general source hint in a query that uses multple sources, I get an NPE:
> java.lang.NullPointerException
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.<init>(ConnectorWorkItem.java:141)
> at org.teiid.dqp.internal.datamgr.ConnectorManager.registerRequest(ConnectorManager.java:203)
> at org.teiid.dqp.internal.process.DataTierManagerImpl.registerRequest(DataTierManagerImpl.java:966)
> at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:179)
> at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:475)
> at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:248)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
> at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
> at org.teiid.query.processor.relational.RelationalPlan.open(RelationalPlan.java:136)
> at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:231)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138)
> 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:457)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:339)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:267)
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:298)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:175)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260)
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:173)
> at com.sun.proxy.$Proxy14.executeRequest(Unknown Source)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:661)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:527)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIID-3470) NPE in ConnectorWorkItem when using source hints
by Mark Addleman (JIRA)
[ https://issues.jboss.org/browse/TEIID-3470?page=com.atlassian.jira.plugin... ]
Mark Addleman updated TEIID-3470:
---------------------------------
Description:
When using a source general source hint in a query that uses multple sources, I get an NPE:
java.lang.NullPointerException
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.<init>(ConnectorWorkItem.java:141)
at org.teiid.dqp.internal.datamgr.ConnectorManager.registerRequest(ConnectorManager.java:203)
at org.teiid.dqp.internal.process.DataTierManagerImpl.registerRequest(DataTierManagerImpl.java:966)
at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:179)
at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:475)
at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:248)
at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
at org.teiid.query.processor.relational.RelationalPlan.open(RelationalPlan.java:136)
at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:231)
at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138)
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:457)
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:339)
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:267)
at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:298)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:175)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260)
at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:173)
at com.sun.proxy.$Proxy14.executeRequest(Unknown Source)
at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:661)
at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:527)
at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261)
> NPE in ConnectorWorkItem when using source hints
> ------------------------------------------------
>
> Key: TEIID-3470
> URL: https://issues.jboss.org/browse/TEIID-3470
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.11
> Reporter: Mark Addleman
> Assignee: Steven Hawkins
>
> When using a source general source hint in a query that uses multple sources, I get an NPE:
> java.lang.NullPointerException
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.<init>(ConnectorWorkItem.java:141)
> at org.teiid.dqp.internal.datamgr.ConnectorManager.registerRequest(ConnectorManager.java:203)
> at org.teiid.dqp.internal.process.DataTierManagerImpl.registerRequest(DataTierManagerImpl.java:966)
> at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:179)
> at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:475)
> at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:248)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
> at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
> at org.teiid.query.processor.relational.RelationalPlan.open(RelationalPlan.java:136)
> at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:231)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138)
> 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:457)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:339)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:267)
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:298)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:175)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260)
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:173)
> at com.sun.proxy.$Proxy14.executeRequest(Unknown Source)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:661)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:527)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (TEIID-3369) Add a extension point to manipulate incoming sql
by Mark Addleman (JIRA)
[ https://issues.jboss.org/browse/TEIID-3369?page=com.atlassian.jira.plugin... ]
Mark Addleman commented on TEIID-3369:
--------------------------------------
> We can consider later if it makes sense to offer this on a per vdb basis
The current approach works fine for my current use case but the value of providing a per vdb parser is pretty high, IMO: As mentioned in https://developer.jboss.org/message/928788#928788 I'm using the API to layer semantics onto a query because the client cannot generate appropriate SQL. I can easily imagine a case where some clients would generate proper SQL while others wouldn't and discriminating based them by VDB makes a lot of sense.
> Add a extension point to manipulate incoming sql
> ------------------------------------------------
>
> Key: TEIID-3369
> URL: https://issues.jboss.org/browse/TEIID-3369
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Driver, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> We should look at adding a client or server extension point for manipulating sql - just the sql string, pre resolving. This will allow more flexibility in dealing with clients that don't send queries directly understood by Teiid. For example a select for update.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months