[JBoss JIRA] (TEIID-5230) Postgis functions are not resolvable in the public schema
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5230:
-------------------------------------
Summary: Postgis functions are not resolvable in the public schema
Key: TEIID-5230
URL: https://issues.jboss.org/browse/TEIID-5230
Project: Teiid
Issue Type: Quality Risk
Components: ODBC
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.1
Some clients fully qualify references to PostGIS_Lib_Version as public.PostGIS_Lib_Version. Our emulation layer however has the function under pg_catalog. It and the other informational functions should resolvable using the fully qualified name as well.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (TEIID-5093) Amazon s3 csv/xml lookup querry exception
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-5093?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-5093:
------------------------------------------------
Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1499869|https://bugzilla.redhat.com/show_bug.cgi?id=1499869] from ON_QA to VERIFIED
> Amazon s3 csv/xml lookup querry exception
> -----------------------------------------
>
> Key: TEIID-5093
> URL: https://issues.jboss.org/browse/TEIID-5093
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.x-6.4
> Reporter: Mario Majernik
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 10.0, 8.12.x-6.4
>
>
> Querry :
> {code:java}
> SELECT IntKey, StringKey, lookup('BQT1.SmallB', 'DoubleNum', 'IntKey', IntKey) AS DoubleNum FROM BQT1.SmallA UNION SELECT IntKey, lookup('BQT1.SmallA', 'StringKey', 'IntKey', IntKey) AS StringKey, DoubleNum FROM BQT1.SmallA
> {code}
> returns TeiidSQLException for csv and xml files from amazon s3.
> Stacktrace:
> {code:java}
> WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue41) TEIID30020 Processing exception for request 8O9K6VJIjd9y.7 'TEIID30180 java.sql.SQLException: java.sql.SQLException: TEIID60019 Streaming result has already been read once. Ensure that only one read operation needs to be performed, for example XMLPARSE without the WELLFORMED operation must read the entire stream to validate its contents. Or you may choose to use a non-streaming result. '. Originally TeiidProcessingException BinaryWSProcedureExecution.java:78. Enable more detailed logging to see the entire stacktrace.
> {code}
> Teiid command log for querry:
> {code:java}
> 15:11:34,160 INFO [org.teiid.COMMAND_LOG] (New I/O worker #2) 8O9K6VJIjd9y START USER COMMAND: startTime=2017-10-09 15:11:34.16 requestID=8O9K6VJIjd9y.7 txID=null sessionID=8O9K6VJIjd9y applicationName=JDBC principal=user@teiid-security vdbName=csv vdbVersion=1 sql=SELECT IntKey, StringKey, lookup('BQT1.SmallB', 'DoubleNum', 'IntKey', IntKey) AS DoubleNum FROM BQT1.SmallA UNION SELECT IntKey, lookup('BQT1.SmallA', 'StringKey', 'IntKey', IntKey) AS StringKey, DoubleNum FROM BQT1.SmallA
> 15:11:34,192 DEBUG [org.teiid.COMMAND_LOG] (Worker0_QueryProcessorQueue40) 8O9K6VJIjd9y START DATA SRC COMMAND: startTime=2017-10-09 15:11:34.192 requestID=8O9K6VJIjd9y.7 sourceCommandID=6 executionID=2 txID=null modelName=sourceModel translatorName=user-s3 sessionID=8O9K6VJIjd9y principal=user@teiid-security sql=EXEC sourceModel.getTextFile('csv/smallaCsv.csv')
> 15:11:34,856 DEBUG [org.teiid.COMMAND_LOG] (Worker2_QueryProcessorQueue41) 8O9K6VJIjd9y END SRC COMMAND: endTime=2017-10-09 15:11:34.856 requestID=8O9K6VJIjd9y.7 sourceCommandID=6 executionID=2 txID=null modelName=sourceModel translatorName=user-s3 sessionID=8O9K6VJIjd9y principal=user@teiid-security finalRowCount=1 cpuTime(ns)=34673443
> 15:11:34,862 INFO [org.teiid.COMMAND_LOG] (Worker2_QueryProcessorQueue41) 8O9K6VJIjd9y ERROR USER COMMAND: endTime=2017-10-09 15:11:34.862 requestID=8O9K6VJIjd9y.7 txID=null sessionID=8O9K6VJIjd9y principal=user@teiid-security vdbName=csv vdbVersion=1 finalRowCount=null
> 15:11:34,876 INFO [org.teiid.COMMAND_LOG] (Worker2_QueryProcessorQueue41) 8O9K6VJIjd9y END USER COMMAND: endTime=2017-10-09 15:11:34.876 requestID=8O9K6VJIjd9y.7 txID=null sessionID=8O9K6VJIjd9y principal=user@teiid-security vdbName=csv vdbVersion=1 finalRowCount=0
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (TEIID-5229) Google Spreadsheet translator NoSuchElementException for DELETE with criteria on char
by Jan Stastny (JIRA)
Jan Stastny created TEIID-5229:
----------------------------------
Summary: Google Spreadsheet translator NoSuchElementException for DELETE with criteria on char
Key: TEIID-5229
URL: https://issues.jboss.org/browse/TEIID-5229
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.x-6.4
Reporter: Jan Stastny
Assignee: Steven Hawkins
DELETE fails when there's WHERE criteria on a column with type char.
{code:sql}
DELETE FROM SmallA WHERE CharValue IN ('2', '3')
{code}
Error:
{code}
14:04:41,627 ERROR [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue60) TEIID30019 Unexpected exception for request Bc4xXOpFO/lu.32: java.util.NoSuchElementException
at java.util.ArrayList$Itr.next(ArrayList.java:860) [rt.jar:1.8.0_151]
at org.teiid.query.rewriter.QueryRewriter.createPkCriteria(QueryRewriter.java:3104) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.query.rewriter.QueryRewriter.createDeleteProcedure(QueryRewriter.java:3238) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.query.rewriter.QueryRewriter.rewriteInherentDelete(QueryRewriter.java:3177) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.query.rewriter.QueryRewriter.rewriteDelete(QueryRewriter.java:3130) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.query.rewriter.QueryRewriter.rewriteCommand(QueryRewriter.java:238) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.query.rewriter.QueryRewriter.rewrite(QueryRewriter.java:168) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.query.rewriter.QueryRewriter.rewrite(QueryRewriter.java:172) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:426) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.dqp.internal.process.Request.processRequest(Request.java:476) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:642) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:337) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.11.6_4-redhat-64-11.jar:8.12.11.6_4-redhat-64-11]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151]
at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151]
{code}
UPDATE works as expected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (TEIID-5174) Filter internal constructs from oracle metadata
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5174?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5174.
-----------------------------------
Fix Version/s: 10.0.3
Resolution: Done
Changed the oracle import to always filter the SYS schema. Also changed the import logic to not use the one shot import of columns, and instead always fetch per table as that was a significant performance issue for oracle and is generally not enough of a performance benefit to use for other databases as column information will be indexed by schema/table names.
> Filter internal constructs from oracle metadata
> -----------------------------------------------
>
> Key: TEIID-5174
> URL: https://issues.jboss.org/browse/TEIID-5174
> Project: Teiid
> Issue Type: Quality Risk
> Components: JDBC Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.1, 10.0.3
>
>
> Even with the import table types set to TABLE, an Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 accessed with the 12.1.0.1.0 driver will contain internal tables which will cause the deployment to error:
> TEIID31071 Invalid table; Table oracleModel.HS_PARTITION_COL_NAME has no columns defined
> It would be good if these were filtered by default. The workaround is to specify a schema or regex to prevent such tables from being imported.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (TEIID-5228) Reference to "element in the tree" in documentation
by Andrej Šmigala (JIRA)
Andrej Šmigala created TEIID-5228:
-------------------------------------
Summary: Reference to "element in the tree" in documentation
Key: TEIID-5228
URL: https://issues.jboss.org/browse/TEIID-5228
Project: Teiid
Issue Type: Bug
Components: Documentation
Reporter: Andrej Šmigala
Assignee: Steven Hawkins
The section "Writing a Visitor" of the Developer's Guide contains this quote:
bq. For instance, if you wanted to count the number of elements in the tree, you need only override the visit(ColumnReference) method.
This is old terminology and shoud be replaced with "column reference"
{quote}
shawkins: it's mixing terminology. in the engine (from the old metamatrix days) column references are called element symbols, so a lot of the logic refers to them as elements
shawkins: it should use the term column reference instead
{quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months