October 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5107) teiid-olingo-*.war not deploying in wildfly when using domain

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5107?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5107: ---------------------------------- Description: The Teiid odata war is only deploying in standalone. The workaround in domain mode is to re-deploy the war using the admin console. was: The Teiid odata war, located: modules/system/layers/dv/org/jboss/teiid/main/deployments/teiid-odata-8.7.1.6_2-redhat-2.war was not being deployed. It's working in standalone. The workaround in domain mode is to re-deploy the war using the admin console. Fix Version/s: 10.0 (was: 8.7.1.6_2) Forum Reference: https://developer.jboss.org/message/977026 Affects Version/s: (was: 8.7.1.6_2) > teiid-olingo-*.war not deploying in wildfly when using domain > ------------------------------------------------------------- > > Key: TEIID-5107 > URL: https://issues.jboss.org/browse/TEIID-5107 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 10.0 > > > The Teiid odata war is only deploying in standalone. > The workaround in domain mode is to re-deploy the war using the admin console. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5107) teiid-olingo-*.war not deploying in wildfly when using domain

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5107: ------------------------------------- Summary: teiid-olingo-*.war not deploying in wildfly when using domain Key: TEIID-5107 URL: https://issues.jboss.org/browse/TEIID-5107 Project: Teiid Issue Type: Bug Components: OData Affects Versions: 8.7.1.6_2 Reporter: Van Halbert Assignee: Ramesh Reddy Priority: Critical Fix For: 8.7.1.6_2 The Teiid odata war, located: modules/system/layers/dv/org/jboss/teiid/main/deployments/teiid-odata-8.7.1.6_2-redhat-2.war was not being deployed. It's working in standalone. The workaround in domain mode is to re-deploy the war using the admin console. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5093) Amazon s3 csv/xml lookup querry exception

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5093?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5093: ------------------------------- Priority: Blocker (was: Major) > 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 > > 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)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5101) .vdb with JDG data source, with NATIVE defined, throws exception

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5101?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5101: ------------------------------------ I manually changed the internal vdb.xml in the .vdb file to add: <metadata type="INDEX"/> <metadata type="NATIVE"/> repackaged the .vdb and redeployed. It worked. > .vdb with JDG data source, with NATIVE defined, throws exception > ---------------------------------------------------------------- > > Key: TEIID-5101 > URL: https://issues.jboss.org/browse/TEIID-5101 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Attachments: Person.vdb > > > When a .vdb (created in designer), and the internal vdb.xml contains the <metadata type="NATIVE"></metadata>, the vdb will not deploy. > However, it will work if the .vdb is exported to vdb xml, because the DDL and the NATIVE tags are there. > Guessing that the translator doesn't know how to handle a .vdb file. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5101) .vdb with JDG data source, with NATIVE defined, throws exception

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5101?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5101: ------------------------------- Attachment: Person.vdb > .vdb with JDG data source, with NATIVE defined, throws exception > ---------------------------------------------------------------- > > Key: TEIID-5101 > URL: https://issues.jboss.org/browse/TEIID-5101 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Attachments: Person.vdb > > > When a .vdb (created in designer), and the internal vdb.xml contains the <metadata type="NATIVE"></metadata>, the vdb will not deploy. > However, it will work if the .vdb is exported to vdb xml, because the DDL and the NATIVE tags are there. > Guessing that the translator doesn't know how to handle a .vdb file. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5101) .vdb with JDG data source, with NATIVE defined, throws exception

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5101?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5101: ------------------------------------ For reference, the error is (copied from the i18.properties) TEIID25011=There are three ways to import the metadata, \n \ 1) Define "importer.ProtoFilePath" to read from a local .proto file.\n \ 2) Define "importer.ProtobufName" property to define .proto file name, when reading the .proto file from the Infinispan Cache directly.\n\ 3) Define the schema using DDL, then use also the "NATIVE" metadata repository to convert DDL into .proto file\n > .vdb with JDG data source, with NATIVE defined, throws exception > ---------------------------------------------------------------- > > Key: TEIID-5101 > URL: https://issues.jboss.org/browse/TEIID-5101 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > > When a .vdb (created in designer), and the internal vdb.xml contains the <metadata type="NATIVE"></metadata>, the vdb will not deploy. > However, it will work if the .vdb is exported to vdb xml, because the DDL and the NATIVE tags are there. > Guessing that the translator doesn't know how to handle a .vdb file. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5093) Amazon s3 csv/xml lookup querry exception

by Jan Stastny (JIRA)

[ https://issues.jboss.org/browse/TEIID-5093?page=com.atlassian.jira.plugin... ] Jan Stastny commented on TEIID-5093: ------------------------------------ [~rareddy],[~shawkins],[~mmajerni] The issue here is not with lookup function. If you notice the query in the description, it is a union of two queries on a single table. Simplified reproducers: {code:sql} SELECT IntKey, StringKey FROM BQT1.SmallA UNION SELECT IntKey, StringKey FROM BQT1.SmallA {code} {code:sql} SELECT a.IntKey, b.StringKey FROM BQT1.SmallA a , BQT1.SmallA b {code} Also note, that the issue happens for csv, where XMLPARSE is not being used at all. To complete the report, if I change the query in description, (so that it doesn't do union on a single table, but on two different) then it works well. {code: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.SmallB {code} > 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 > > 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)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5106) Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid.

by sameer P (JIRA)

[ https://issues.jboss.org/browse/TEIID-5106?page=com.atlassian.jira.plugin... ] sameer P commented on TEIID-5106: --------------------------------- [~shawkins], "The only near term solution would be to offer an auto rename option that is similar to renameDuplicateColumns" - Yes, that would be helpful and would be Ok for now. > Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid. > -------------------------------------------------------------------------- > > Key: TEIID-5106 > URL: https://issues.jboss.org/browse/TEIID-5106 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: sameer P > Assignee: Steven Hawkins > > In Postgres/Oracle/MS , I can create two tables with the same name (but different cases): test12 and Test12 (by quoting it in create script) , but, Teiid complains saying duplicate table name and fails with the below error: > {code:java} > 16:53:11,161 WARN [org.teiid.RUNTIME] (Worker0_async-teiid-threads0) TEIID50036 VDB test.1 model "dsms" metadata failed to load. Reason:TEIID60013 Duplicate Table public.test12: org.teiid.metadata.DuplicateRecordException: TEIID60013 Duplicate Table public.test12 > at org.teiid.metadata.Schema.addTable(Schema.java:51) > at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:179) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:368) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:351) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:324) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:166) > at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:306) > at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:69) > at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) > at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) > at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > at org.teiid.jboss.VDBService$6.run(VDBService.java:341) > at org.teiid.jboss.VDBService$7.run(VDBService.java:392) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) > 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:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5099) Add facility for passing header values in @JsonTable

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5099?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-5099: -------------------------------- Fix Version/s: 10.0 > Add facility for passing header values in @JsonTable > ---------------------------------------------------- > > Key: TEIID-5099 > URL: https://issues.jboss.org/browse/TEIID-5099 > Project: Teiid > Issue Type: Feature Request > Components: spring-boot > Reporter: ganesh pol > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 10.0 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5099) Add facility for passing header values in @JsonTable

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5099?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-5099. --------------------------------- Resolution: Done See @RestConfiguration and its javadoc to see how custom headers can be set > Add facility for passing header values in @JsonTable > ---------------------------------------------------- > > Key: TEIID-5099 > URL: https://issues.jboss.org/browse/TEIID-5099 > Project: Teiid > Issue Type: Feature Request > Components: spring-boot > Reporter: ganesh pol > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 10.0 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 2017