January 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5595) Solve the maven duplicate PartSupplier.vdb issue

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5595?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5595: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/1125 > Solve the maven duplicate PartSupplier.vdb issue > ------------------------------------------------ > > Key: TEIID-5595 > URL: https://issues.jboss.org/browse/TEIID-5595 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Trivial > > When changing to use the basebom, it triggered a duplicate artifiact issue with PartsSupplier.vdb between the metadata project and the connector projects. If its the exact same vdb, then the connector vdb could be removed. Otherwise, I would suggest the connectors rename their vdb and fix the related dependent tests. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5590) vdb-maven-plugin - version 1.3 breaks build lifecycle

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5590?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-5590. --------------------------------- Fix Version/s: 12.0 (was: 12.x) Resolution: Done Re-introduced processing of resources into the plugin as it was easier workflow, otherwise, the user needs to create a new directory called "uberresources" that will be picked by the Thorntail maven plugin as resources file. Since it is additional work on user + additional knowledge needs to acquired by the user, even though it does not make sense to put the properties file/yml file in .vdb artifact as it works exactly same otherwise. This change is in 1.4 release of vdb-maven-plugin > vdb-maven-plugin - version 1.3 breaks build lifecycle > ----------------------------------------------------- > > Key: TEIID-5590 > URL: https://issues.jboss.org/browse/TEIID-5590 > Project: Teiid > Issue Type: Bug > Components: Build/Kits, VDB > Environment: {code} > 2019-01-08 15:49:30 > rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % uname -a > Linux eanna 4.20.0-arch1-1-ARCH #1 SMP PREEMPT Mon Dec 24 03:00:40 UTC 2018 x86_64 GNU/Linux > 2019-01-08 15:52:36 > rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % mvn -v > Apache Maven 3.5.4 (NON-CANONICAL_2018-09-08T01:02:16+02:00_root; 2018-09-07T16:02:16-07:00) > Maven home: /opt/maven > Java version: 1.8.0_192, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-8-openjdk/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.20.0-arch1-1-arch", arch: "amd64", family: "unix" > 2019-01-08 15:52:40 > rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % java -version > openjdk version "1.8.0_192" > OpenJDK Runtime Environment (build 1.8.0_192-b26) > OpenJDK 64-Bit Server VM (build 25.192-b26, mixed mode) > {code} > Reporter: G. Richard Bellamy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.0 > > > When building a VDB with version 1.3 of the vdb-maven-plugin, the {{src/main/resources}} directory is NOT processed as expected. When using version 1.1, the "package" phase has the following (correct) phases: > {code} > [INFO] 'package' is a phase corresponding to this plugin: > org.teiid:vdb-maven-plugin:vdb > It is a part of the lifecycle for the POM packaging 'vdb'. This lifecycle includes the following phases: > * validate: Not defined > * initialize: Not defined > * generate-sources: Not defined > * process-sources: Not defined > * generate-resources: Not defined > * process-resources: org.apache.maven.plugins:maven-resources-plugin:resources > * compile: org.apache.maven.plugins:maven-compiler-plugin:compile > * process-classes: Not defined > * generate-test-sources: Not defined > * process-test-sources: Not defined > * generate-test-resources: Not defined > * process-test-resources: org.apache.maven.plugins:maven-resources-plugin:testResources > * test-compile: org.apache.maven.plugins:maven-compiler-plugin:testCompile > * process-test-classes: Not defined > * test: org.apache.maven.plugins:maven-surefire-plugin:test > * prepare-package: Not defined > * package: org.teiid:vdb-maven-plugin:vdb > * pre-integration-test: Not defined > * integration-test: Not defined > * post-integration-test: Not defined > * verify: Not defined > * install: org.apache.maven.plugins:maven-install-plugin:install > * deploy: org.apache.maven.plugins:maven-deploy-plugin:deploy > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5587) Oracle 11 drivers don't accept NVARCHAR type

by Johnathon Lee (Jira)

[ https://issues.jboss.org/browse/TEIID-5587?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5587: --------------------------------- Fix Version/s: 8.12.17.6_4 > Oracle 11 drivers don't accept NVARCHAR type > -------------------------------------------- > > Key: TEIID-5587 > URL: https://issues.jboss.org/browse/TEIID-5587 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0, 8.12.17.6_4, 11.2.2 > > > Older oracle drivers, such as 11.2.0.1.0 do not accept the sql type NVARCHAR as an argument to set object, which results in an exception like: > {code} > Caused by: java.sql.SQLException: Invalid column type > at oracle.jdbc.driver.OraclePreparedStatement.setObjectCritical(OraclePreparedStatement.java:12187) > at oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(OraclePreparedStatement.java:11577) > at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedStatement.java:12286) > at oracle.jdbc.driver.OraclePreparedStatementWrapper.setObject(OraclePreparedStatementWrapper.java:548) > at org.teiid.translator.jdbc.JDBCExecutionFactory.bindValue(JDBCExecutionFactory.java:1145) > {code} > We can also safely narrow our usage of the n types with oracle as anything in the latin 1 supplement is still allowed in varchar values. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5600) Use Caffeine as default cache implementation with Teiid Spring Boot applications

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5600?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5600: --------------------------------------- I'll also look to then replace the two-queue caches used by the buffer manager and memory buffer tier at which point we will just pull this into the core. > Use Caffeine as default cache implementation with Teiid Spring Boot applications > -------------------------------------------------------------------------------- > > Key: TEIID-5600 > URL: https://issues.jboss.org/browse/TEIID-5600 > Project: Teiid > Issue Type: Enhancement > Components: spring-boot > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > > Currently, Teiid Spring Boot uses LRU based cache as default caching layer, this should be replaced with [caffeine|https://github.com/ben-manes/caffeine] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5512) No transaction associated with the current thread

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5512?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5512. ----------------------------------- Resolution: Cannot Reproduce Marking as non-reproducible for now. If you can get this to occur with Teiid 11, please reopen and if possible provide a trace log of org.teiid.TXN_LOG > No transaction associated with the current thread > ------------------------------------------------- > > Key: TEIID-5512 > URL: https://issues.jboss.org/browse/TEIID-5512 > Project: Teiid > Issue Type: Bug > Affects Versions: 10.3.4 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Priority: Major > > I'm facing this problem but I'm not sure where or when it occurs. It seems to be randomly. The virtual procedure that is run while this problem occurs, copies data from one xa-datasource to a temp table and then inserts it into a non-xa datasource. > 2018-10-22 09:50:28,361 WARN [org.teiid.PROCESSOR] (Worker25_QueryProcessorQueue73179) F274YMAVci29 TEIID31200 Lower level transaction Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffffac130002:-2cc3b1fb:5bcd8cc9:f717 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider) not properly ended, rolling back. > 2018-10-22 09:50:28,361 WARN [org.teiid.PROCESSOR] (Worker25_QueryProcessorQueue73179) F274YMAVci29 TEIID30028 Failed to properly rollback autowrap transaction properly: org.teiid.client.xa.XATransactionException: TEIID30535 java.lang.IllegalStateException: No transaction associated with the current thread > at org.teiid.dqp.internal.process.TransactionServerImpl.rollbackDirect(TransactionServerImpl.java:432) > at org.teiid.dqp.internal.process.TransactionServerImpl.rollback(TransactionServerImpl.java:551) > at sun.reflect.GeneratedMethodAccessor127.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.teiid.logging.LogManager$LoggingProxy.invoke(LogManager.java:117) > at com.sun.proxy.$Proxy25.rollback(Unknown Source) > at org.teiid.dqp.internal.process.RequestWorkItem.close(RequestWorkItem.java:574) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:375) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:47) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:276) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:277) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:115) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:206) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException: No transaction associated with the current thread > at org.wildfly.transaction.client.ContextTransactionManager.rollback(ContextTransactionManager.java:81) > at org.teiid.dqp.internal.process.TransactionServerImpl.rollbackDirect(TransactionServerImpl.java:426) > ... 16 more > 2018-10-22 09:50:28,389 WARN [org.teiid.PROCESSOR] (Worker22_QueryProcessorQueue73181) F274YMAVci29 TEIID30020 Processing exception for request F274YMAVci29.39 'TEIID30538 java.lang.IllegalStateException: WFTXN0007: A transaction is already associated with the current thread'. Originally XATransactionException ContextTransactionManager.java:140. Enable more detailed logging to see the entire stacktrace. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5503) Create or change ODBC driver to be compatible with Microsoft Power BI

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5503?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5503: ---------------------------------- Fix Version/s: Open To Community > Create or change ODBC driver to be compatible with Microsoft Power BI > --------------------------------------------------------------------- > > Key: TEIID-5503 > URL: https://issues.jboss.org/browse/TEIID-5503 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Major > Fix For: Open To Community > > Attachments: qs-connect-data_02.png, qs-connect-data_03.png > > > Customer request to customise the ODBC driver, adding extra feature as reported here: https://docs.microsoft.com/en-us/power-query/odbc -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5523) Allow for xsd schema association with vdb.xml

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5523?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5523: --------------------------------------- I'll validate that this works as expected for at least embedded. > Allow for xsd schema association with vdb.xml > --------------------------------------------- > > Key: TEIID-5523 > URL: https://issues.jboss.org/browse/TEIID-5523 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Using Teiid Thorntail an exception is thrown at deployment when I attempt to associate an xsd with the vdb.xml file. This would be helpful to assist with vdb editing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5590) vdb-maven-plugin - version 1.3 breaks build lifecycle

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5590?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5590: ---------------------------------- Fix Version/s: 12.x > vdb-maven-plugin - version 1.3 breaks build lifecycle > ----------------------------------------------------- > > Key: TEIID-5590 > URL: https://issues.jboss.org/browse/TEIID-5590 > Project: Teiid > Issue Type: Bug > Components: Build/Kits, VDB > Environment: {code} > 2019-01-08 15:49:30 > rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % uname -a > Linux eanna 4.20.0-arch1-1-ARCH #1 SMP PREEMPT Mon Dec 24 03:00:40 UTC 2018 x86_64 GNU/Linux > 2019-01-08 15:52:36 > rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % mvn -v > Apache Maven 3.5.4 (NON-CANONICAL_2018-09-08T01:02:16+02:00_root; 2018-09-07T16:02:16-07:00) > Maven home: /opt/maven > Java version: 1.8.0_192, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-8-openjdk/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.20.0-arch1-1-arch", arch: "amd64", family: "unix" > 2019-01-08 15:52:40 > rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % java -version > openjdk version "1.8.0_192" > OpenJDK Runtime Environment (build 1.8.0_192-b26) > OpenJDK 64-Bit Server VM (build 25.192-b26, mixed mode) > {code} > Reporter: G. Richard Bellamy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.x > > > When building a VDB with version 1.3 of the vdb-maven-plugin, the {{src/main/resources}} directory is NOT processed as expected. When using version 1.1, the "package" phase has the following (correct) phases: > {code} > [INFO] 'package' is a phase corresponding to this plugin: > org.teiid:vdb-maven-plugin:vdb > It is a part of the lifecycle for the POM packaging 'vdb'. This lifecycle includes the following phases: > * validate: Not defined > * initialize: Not defined > * generate-sources: Not defined > * process-sources: Not defined > * generate-resources: Not defined > * process-resources: org.apache.maven.plugins:maven-resources-plugin:resources > * compile: org.apache.maven.plugins:maven-compiler-plugin:compile > * process-classes: Not defined > * generate-test-sources: Not defined > * process-test-sources: Not defined > * generate-test-resources: Not defined > * process-test-resources: org.apache.maven.plugins:maven-resources-plugin:testResources > * test-compile: org.apache.maven.plugins:maven-compiler-plugin:testCompile > * process-test-classes: Not defined > * test: org.apache.maven.plugins:maven-surefire-plugin:test > * prepare-package: Not defined > * package: org.teiid:vdb-maven-plugin:vdb > * pre-integration-test: Not defined > * integration-test: Not defined > * post-integration-test: Not defined > * verify: Not defined > * install: org.apache.maven.plugins:maven-install-plugin:install > * deploy: org.apache.maven.plugins:maven-deploy-plugin:deploy > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5523) Allow for xsd schema association with vdb.xml

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5523?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5523: ---------------------------------- Fix Version/s: 12.1 > Allow for xsd schema association with vdb.xml > --------------------------------------------- > > Key: TEIID-5523 > URL: https://issues.jboss.org/browse/TEIID-5523 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Using Teiid Thorntail an exception is thrown at deployment when I attempt to associate an xsd with the vdb.xml file. This would be helpful to assist with vdb editing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5590) vdb-maven-plugin - version 1.3 breaks build lifecycle

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5590?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-5590: ------------------------------------- Assignee: Ramesh Reddy (was: Barry LaFond) > vdb-maven-plugin - version 1.3 breaks build lifecycle > ----------------------------------------------------- > > Key: TEIID-5590 > URL: https://issues.jboss.org/browse/TEIID-5590 > Project: Teiid > Issue Type: Bug > Components: Build/Kits, VDB > Environment: {code} > 2019-01-08 15:49:30 > rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % uname -a > Linux eanna 4.20.0-arch1-1-ARCH #1 SMP PREEMPT Mon Dec 24 03:00:40 UTC 2018 x86_64 GNU/Linux > 2019-01-08 15:52:36 > rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % mvn -v > Apache Maven 3.5.4 (NON-CANONICAL_2018-09-08T01:02:16+02:00_root; 2018-09-07T16:02:16-07:00) > Maven home: /opt/maven > Java version: 1.8.0_192, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-8-openjdk/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.20.0-arch1-1-arch", arch: "amd64", family: "unix" > 2019-01-08 15:52:40 > rbellamy@eanna i ~/Development/Terradatum/metrics-vdb master % java -version > openjdk version "1.8.0_192" > OpenJDK Runtime Environment (build 1.8.0_192-b26) > OpenJDK 64-Bit Server VM (build 25.192-b26, mixed mode) > {code} > Reporter: G. Richard Bellamy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.x > > > When building a VDB with version 1.3 of the vdb-maven-plugin, the {{src/main/resources}} directory is NOT processed as expected. When using version 1.1, the "package" phase has the following (correct) phases: > {code} > [INFO] 'package' is a phase corresponding to this plugin: > org.teiid:vdb-maven-plugin:vdb > It is a part of the lifecycle for the POM packaging 'vdb'. This lifecycle includes the following phases: > * validate: Not defined > * initialize: Not defined > * generate-sources: Not defined > * process-sources: Not defined > * generate-resources: Not defined > * process-resources: org.apache.maven.plugins:maven-resources-plugin:resources > * compile: org.apache.maven.plugins:maven-compiler-plugin:compile > * process-classes: Not defined > * generate-test-sources: Not defined > * process-test-sources: Not defined > * generate-test-resources: Not defined > * process-test-resources: org.apache.maven.plugins:maven-resources-plugin:testResources > * test-compile: org.apache.maven.plugins:maven-compiler-plugin:testCompile > * process-test-classes: Not defined > * test: org.apache.maven.plugins:maven-surefire-plugin:test > * prepare-package: Not defined > * package: org.teiid:vdb-maven-plugin:vdb > * pre-integration-test: Not defined > * integration-test: Not defined > * post-integration-test: Not defined > * verify: Not defined > * install: org.apache.maven.plugins:maven-install-plugin:install > * deploy: org.apache.maven.plugins:maven-deploy-plugin:deploy > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 January 2019