[JBoss JIRA] (TEIIDSB-161) Excessive warning about spring.teiid.model.package
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-161?page=com.atlassian.jira.plug... ]
Steven Hawkins commented on TEIIDSB-161:
----------------------------------------
So it's name of the property that's confusing. It's generally used for scanning, not just for Entities.
If the translators are marked as components, couldn't that be done with the ComponentScan annotation?
> Excessive warning about spring.teiid.model.package
> --------------------------------------------------
>
> Key: TEIIDSB-161
> URL: https://issues.redhat.com/browse/TEIIDSB-161
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: core
> Reporter: Steven Hawkins
> Priority: Minor
>
> when using a vdb project the warning:
> {code}
> 2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : ***************************************************************
> 2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : "spring.teiid.model.package" is NOT set, If you are using any custom translators, it is advised to that this property is set.
> 2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : consider setting this property to avoid time consuming scanning
> 2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : ***************************************************************
> {code}
> Seems unnecessary. Also what does it have to do with custom translators?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIIDSB-161) Excessive warning about spring.teiid.model.package
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-161?page=com.atlassian.jira.plug... ]
Ramesh Reddy commented on TEIIDSB-161:
--------------------------------------
It will scan the classpath and find the translator class in the classpath. If not set it will scan the entire classpath. You can set to scan certain packages.
> Excessive warning about spring.teiid.model.package
> --------------------------------------------------
>
> Key: TEIIDSB-161
> URL: https://issues.redhat.com/browse/TEIIDSB-161
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: core
> Reporter: Steven Hawkins
> Priority: Minor
>
> when using a vdb project the warning:
> {code}
> 2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : ***************************************************************
> 2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : "spring.teiid.model.package" is NOT set, If you are using any custom translators, it is advised to that this property is set.
> 2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : consider setting this property to avoid time consuming scanning
> 2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : ***************************************************************
> {code}
> Seems unnecessary. Also what does it have to do with custom translators?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIIDSB-161) Excessive warning about spring.teiid.model.package
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-161:
--------------------------------------
Summary: Excessive warning about spring.teiid.model.package
Key: TEIIDSB-161
URL: https://issues.redhat.com/browse/TEIIDSB-161
Project: Teiid Spring Boot
Issue Type: Bug
Components: core
Reporter: Steven Hawkins
when using a vdb project the warning:
{code}
2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : ***************************************************************
2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : "spring.teiid.model.package" is NOT set, If you are using any custom translators, it is advised to that this property is set.
2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : consider setting this property to avoid time consuming scanning
2020-01-17 17:03:22.491 WARN 6870 --- [ main] o.t.spring.autoconfigure.TeiidServer : ***************************************************************
{code}
Seems unnecessary. Also what does it have to do with custom translators?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIID-5879) Upgrade PrestoDB support to newer versions
by Ramesh Reddy (Jira)
Ramesh Reddy created TEIID-5879:
-----------------------------------
Summary: Upgrade PrestoDB support to newer versions
Key: TEIID-5879
URL: https://issues.redhat.com/browse/TEIID-5879
Project: Teiid
Issue Type: Enhancement
Components: Misc. Connectors
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
The presto db support is at 0.85 and current version is at 0.230. This translator needs to be updated on any latest capabilities
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIIDSB-160) Initialization order issue
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-160?page=com.atlassian.jira.plug... ]
Work on TEIIDSB-160 started by Steven Hawkins.
----------------------------------------------
> Initialization order issue
> --------------------------
>
> Key: TEIIDSB-160
> URL: https://issues.redhat.com/browse/TEIIDSB-160
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: core
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.4.0, 1.3.1
>
>
> In working with the infinispan translator there is a situation where defining a project that has no relational sources, but uses infinispan and a rest source on startup gives:
> {code}
> Description:
> The bean 'dataSource', defined in class path resource [org/teiid/spring/autoconfigure/TeiidAutoConfiguration.class], could not be registered. A bean with that name has already been defined in class path resource [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Tomcat.class] and overriding is disabled.
> Action:
> Consider renaming one of the beans or enabling overriding by setting spring.main.allow-bean-definition-overriding=true
> {code}
> Our starter has a reference to tomcat-jdbc, so that will always be in the classpath making that DataSourceConfiguration eligible.
> The best solution seems to be for the TeiidAutoConfiguration to be marked with {code}@AutoConfigureBefore({ DataSourceAutoConfiguration.class }){code} so that it will install the primary datasource bean first.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIIDSB-160) Initialization order issue
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-160?page=com.atlassian.jira.plug... ]
Steven Hawkins reassigned TEIIDSB-160:
--------------------------------------
Assignee: Steven Hawkins
> Initialization order issue
> --------------------------
>
> Key: TEIIDSB-160
> URL: https://issues.redhat.com/browse/TEIIDSB-160
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: core
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.4.0, 1.3.1
>
>
> In working with the infinispan translator there is a situation where defining a project that has no relational sources, but uses infinispan and a rest source on startup gives:
> {code}
> Description:
> The bean 'dataSource', defined in class path resource [org/teiid/spring/autoconfigure/TeiidAutoConfiguration.class], could not be registered. A bean with that name has already been defined in class path resource [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Tomcat.class] and overriding is disabled.
> Action:
> Consider renaming one of the beans or enabling overriding by setting spring.main.allow-bean-definition-overriding=true
> {code}
> Our starter has a reference to tomcat-jdbc, so that will always be in the classpath making that DataSourceConfiguration eligible.
> The best solution seems to be for the TeiidAutoConfiguration to be marked with {code}@AutoConfigureBefore({ DataSourceAutoConfiguration.class }){code} so that it will install the primary datasource bean first.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIIDSB-160) Initialization order issue
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-160?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIIDSB-160:
-----------------------------------
Description:
In working with the infinispan translator there is a situation where defining a project that has no relational sources, but uses infinispan and a rest source on startup gives:
{code}
Description:
The bean 'dataSource', defined in class path resource [org/teiid/spring/autoconfigure/TeiidAutoConfiguration.class], could not be registered. A bean with that name has already been defined in class path resource [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Tomcat.class] and overriding is disabled.
Action:
Consider renaming one of the beans or enabling overriding by setting spring.main.allow-bean-definition-overriding=true
{code}
Our starter has a reference to tomcat-jdbc, so that will always be in the classpath making that DataSourceConfiguration eligible.
The best solution seems to be for the TeiidAutoConfiguration to be marked with {code}@AutoConfigureBefore({ DataSourceAutoConfiguration.class }){code} so that it will install the primary datasource bean first.
was:
In working with the infinispan translator there is a situation where defining a project that has no relational sources, but uses infinispan and a rest source on startup gives:
{code}
Description:
The bean 'dataSource', defined in class path resource [org/teiid/spring/autoconfigure/TeiidAutoConfiguration.class], could not be registered. A bean with that name has already been defined in class path resource [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Tomcat.class] and overriding is disabled.
Action:
Consider renaming one of the beans or enabling overriding by setting spring.main.allow-bean-definition-overriding=true
{code}
Our starter has a reference to tomcat-jdbc, so that will always be in the classpath making that DataSourceConfiguration eligible.
The best solution seems to be for the TeiidAutoConfiguration to be marked with @AutoConfigureBefore({ DataSourceAutoConfiguration.class }) so that it will install the primary datasource bean first.
> Initialization order issue
> --------------------------
>
> Key: TEIIDSB-160
> URL: https://issues.redhat.com/browse/TEIIDSB-160
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: core
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 1.4.0, 1.3.1
>
>
> In working with the infinispan translator there is a situation where defining a project that has no relational sources, but uses infinispan and a rest source on startup gives:
> {code}
> Description:
> The bean 'dataSource', defined in class path resource [org/teiid/spring/autoconfigure/TeiidAutoConfiguration.class], could not be registered. A bean with that name has already been defined in class path resource [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Tomcat.class] and overriding is disabled.
> Action:
> Consider renaming one of the beans or enabling overriding by setting spring.main.allow-bean-definition-overriding=true
> {code}
> Our starter has a reference to tomcat-jdbc, so that will always be in the classpath making that DataSourceConfiguration eligible.
> The best solution seems to be for the TeiidAutoConfiguration to be marked with {code}@AutoConfigureBefore({ DataSourceAutoConfiguration.class }){code} so that it will install the primary datasource bean first.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIIDSB-160) Initialization order issue
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-160:
--------------------------------------
Summary: Initialization order issue
Key: TEIIDSB-160
URL: https://issues.redhat.com/browse/TEIIDSB-160
Project: Teiid Spring Boot
Issue Type: Bug
Components: core
Reporter: Steven Hawkins
Fix For: 1.4.0, 1.3.1
In working with the infinispan translator there is a situation where defining a project that has no relational sources, but uses infinispan and a rest source on startup gives:
{code}
Description:
The bean 'dataSource', defined in class path resource [org/teiid/spring/autoconfigure/TeiidAutoConfiguration.class], could not be registered. A bean with that name has already been defined in class path resource [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Tomcat.class] and overriding is disabled.
Action:
Consider renaming one of the beans or enabling overriding by setting spring.main.allow-bean-definition-overriding=true
{code}
Our starter has a reference to tomcat-jdbc, so that will always be in the classpath making that DataSourceConfiguration eligible.
The best solution seems to be for the TeiidAutoConfiguration to be marked with @AutoConfigureBefore({ DataSourceAutoConfiguration.class }) so that it will install the primary datasource bean first.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIIDSB-159) Test errors
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-159?page=com.atlassian.jira.plug... ]
Steven Hawkins commented on TEIIDSB-159:
----------------------------------------
The first thing to check would be running the tests serially. Beyond that we'll just have to identify the root cause of each issue.
> Test errors
> -----------
>
> Key: TEIIDSB-159
> URL: https://issues.redhat.com/browse/TEIIDSB-159
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: core
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 1.4.0, 1.3.1
>
>
> The Teiid spring boot tests are commonly erroring out in travis. It usually is reported as Failed To Load Application Context - but the underlying problem differs. Here: https://api.travis-ci.org/v3/job/638096554/log.txt the issue is likely that tests are executing concurrently that reference the same vdb. The current NioVirtualFile logic for Teiid expects only one mount for a given zip. If you open another, then the previous is closed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months