[JBoss JIRA] (TEIID-5108) Salesforce-34 ra loads also cxf.xml from default location
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-5108?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-5108:
------------------------------------------------
Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1503500|https://bugzilla.redhat.com/show_bug.cgi?id=1503500] from ON_QA to VERIFIED
> Salesforce-34 ra loads also cxf.xml from default location
> ---------------------------------------------------------
>
> Key: TEIID-5108
> URL: https://issues.jboss.org/browse/TEIID-5108
> Project: Teiid
> Issue Type: Quality Risk
> Components: Misc. Connectors
> Affects Versions: 8.12.x-6.4
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Minor
>
> When I am using salesforce-34 resource-adapter together with ConfigFile property set to a custom location, the adapter instantiates a WebClient instance, which tries to load a default ApplicationContext from /META-INF/cxf/cxf.xml location on classpath. This results to FileNotFound error logged at WARNING level:
> {code}
> 09:52:20,365 WARNING [org.apache.cxf.bus.spring.SpringBusFactory] (teiid-async-threads - 4) Initial attempt to create application context was unsuccessful.: org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [META-INF/cxf/cxf.xml]; nested exception is java.io.FileNotFoundException: class path resource [META-INF/cxf/cxf.xml] cannot be opened because it does not exist
> at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:342)
> at org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.internalLoadBeanDefinitions(ControlledValidationXmlBeanDefinitionReader.java:154)
> at org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.access$000(ControlledValidationXmlBeanDefinitionReader.java:66)
> at org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader$1.run(ControlledValidationXmlBeanDefinitionReader.java:141)
> at org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader$1.run(ControlledValidationXmlBeanDefinitionReader.java:139)
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_121]
> at org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.loadBeanDefinitions(ControlledValidationXmlBeanDefinitionReader.java:139)
> at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:303)
> at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:174)
> at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:123)
> at org.apache.cxf.bus.spring.BusApplicationContext.loadBeanDefinitions(BusApplicationContext.java:322)
> at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
> at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:539)
> at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:451)
> at org.apache.cxf.bus.spring.BusApplicationContext$1.run(BusApplicationContext.java:107)
> at org.apache.cxf.bus.spring.BusApplicationContext$1.run(BusApplicationContext.java:105)
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_121]
> at org.apache.cxf.bus.spring.BusApplicationContext.<init>(BusApplicationContext.java:105)
> at org.apache.cxf.bus.spring.SpringBusFactory.createApplicationContext(SpringBusFactory.java:157)
> at org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:148)
> at org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:124)
> at org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:94)
> at org.apache.cxf.jaxrs.client.WebClient.getBean(WebClient.java:1221)
> at org.apache.cxf.jaxrs.client.WebClient.create(WebClient.java:202)
> at org.teiid.resource.adapter.salesforce.transport.SalesforceCXFTransport.connectRaw(SalesforceCXFTransport.java:115)
> at org.teiid.resource.adapter.salesforce.transport.SalesforceCXFTransport.connectLocal(SalesforceCXFTransport.java:84)
> at org.teiid.resource.adapter.salesforce.transport.SalesforceCXFTransport.connectLocal(SalesforceCXFTransport.java:79)
> at org.teiid.resource.adapter.salesforce.transport.SalesforceCXFTransport.connect(SalesforceCXFTransport.java:75)
> at com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:95) [force-wsc-34.0.0.jar:]
> at com.sforce.soap.partner.PartnerConnection.describeSObjects(PartnerConnection.java:950) [force-partner-api-34.0.0.jar:]
> at org.teiid.resource.adapter.salesforce.SalesforceConnectionImpl.getObjectMetaData(SalesforceConnectionImpl.java:491)
> at org.teiid.translator.salesforce.SalesForceMetadataProcessor.getColumnsAndRelationships(SalesForceMetadataProcessor.java:189) [translator-salesforce-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.salesforce.SalesForceMetadataProcessor.processMetadata(SalesForceMetadataProcessor.java:158) [translator-salesforce-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.salesforce.SalesForceMetadataProcessor.process(SalesForceMetadataProcessor.java:106) [translator-salesforce-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.salesforce.SalesForceMetadataProcessor.process(SalesForceMetadataProcessor.java:54) [translator-salesforce-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:950) [teiid-api-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.salesforce.SalesForceExecutionFactory.getMetadata(SalesForceExecutionFactory.java:133) [translator-salesforce-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> at org.teiid.translator.salesforce.SalesForceExecutionFactory.getMetadata(SalesForceExecutionFactory.java:58) [translator-salesforce-8.12.11.6_4-redhat-64-6.jar:8.12.11.6_4-redhat-64-6]
> 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:395)
> at org.teiid.jboss.VDBService$7.run(VDBService.java:446)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: java.io.FileNotFoundException: class path resource [META-INF/cxf/cxf.xml] cannot be opened because it does not exist
> at org.springframework.core.io.ClassPathResource.getInputStream(ClassPathResource.java:171)
> at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:329)
> ... 46 more
> {code}
> When the ConfigFile property is not set, such issue doesn't appear.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (TEIID-5211) Allow ability to forward-engineer into underlying data stores
by Don Krapohl (JIRA)
[ https://issues.jboss.org/browse/TEIID-5211?page=com.atlassian.jira.plugin... ]
Don Krapohl commented on TEIID-5211:
------------------------------------
[~shawkins] not sure if the question was for me but for our concept, Teiid gives us excellent abstraction and we have a large number of sources, some of which move around datacenters as they evolve. So we're looking at a generalized capability to forward engineer independent of dialect. We understand well that the data structures don't necessarily translate if we change underlying storage/retrieval but applying the current (baseline) structures give us a starting point.
It would also make it possible to do Teiid-first development and back into our storage later..
> Allow ability to forward-engineer into underlying data stores
> -------------------------------------------------------------
>
> Key: TEIID-5211
> URL: https://issues.jboss.org/browse/TEIID-5211
> Project: Teiid
> Issue Type: Enhancement
> Components: Connector API
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
>
> As a platform I am better able to better engineer my underlying data stores starting with a virtual model.
> Please add the ability to create, alter, and drop schema objects and relationahips (DDL) in underlying data sources. Example, if I design a source in Teiid Designer I may wish to have Teiid do the DDL against the underlying data source(s). This allows better abstraction an portability of the data model.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (TEIID-5236) Document and update GeoServer compatibility
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5236:
-------------------------------------
Summary: Document and update GeoServer compatibility
Key: TEIID-5236
URL: https://issues.jboss.org/browse/TEIID-5236
Project: Teiid
Issue Type: Quality Risk
Components: Documentation, ODBC, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.2
It is not documented on the geoserver integration page, but most of the initial work was done against versions between 2.6 and 2.8. It appears that even 2.8 can have issues as it can use the 9.4 postgresql driver, which expects additional syntax support for type metadata.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (TEIID-5211) Allow ability to forward-engineer into underlying data stores
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5211?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5211:
---------------------------------------
@blafond does Teiid Designer still have facilities for generated DDL of different dialects?
How would you expect this to work from a runtime perspective - a simple create if absent on the source for missing objects based upon generated ddl? Or is there some broader migration that you are looking to achieve?
> Allow ability to forward-engineer into underlying data stores
> -------------------------------------------------------------
>
> Key: TEIID-5211
> URL: https://issues.jboss.org/browse/TEIID-5211
> Project: Teiid
> Issue Type: Enhancement
> Components: Connector API
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
>
> As a platform I am better able to better engineer my underlying data stores starting with a virtual model.
> Please add the ability to create, alter, and drop schema objects and relationahips (DDL) in underlying data sources. Example, if I design a source in Teiid Designer I may wish to have Teiid do the DDL against the underlying data source(s). This allows better abstraction an portability of the data model.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (TEIID-5232) Add ability to call system functions on VDB Datasource
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5232?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5232:
---------------------------------------
[~dsteigne] I don't quite follow what is being requested here. Is it saying that there is vdb, that uses datasources which are other vdbs and they want to be able to call a session function on those?
> Add ability to call system functions on VDB Datasource
> ------------------------------------------------------
>
> Key: TEIID-5232
> URL: https://issues.jboss.org/browse/TEIID-5232
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Add ability to call the system function teiid_session_set on a EAP VDB datasource
> When i send :
> select teiid_session_set('project','myProject');
> My session variable is changed only on my vdb. I would want to send this command to my VDB EAP datasource. I need to let my vdb's client the opportunity to call teiid_session_set in one of my datasource dynamically. For now, the only way i have found is putting this on my datasource configuration :
> <new-connection-sql>select teiid_session_set('country','BELGIUM')</new-connection-sql>
> The problem is that this sql request is only called once, at the vdb deployment. I would like to be able to call this request at runtime.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (TEIID-5133) XmlTable path language is not always identical to XPathValue expressions
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-5133?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-5133:
------------------------------------------------
Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1508911|https://bugzilla.redhat.com/show_bug.cgi?id=1508911] from ON_QA to VERIFIED
> XmlTable path language is not always identical to XPathValue expressions
> ------------------------------------------------------------------------
>
> Key: TEIID-5133
> URL: https://issues.jboss.org/browse/TEIID-5133
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.4
> Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Fix For: 10.0, 8.12.x-6.4, 9.2.7, 9.3.5
>
>
> The same Path value, used in XPathValue and XmlTable->Path brings different results.
> That is for the following query:
> {code:sql}
> Select * From
> (select '<root>
> <item>
> <id>id1</id>
> <val>val1</val>
> </item>
> </root>' as resp) w,
> XMLTABLE(
> '/root' passing XMLPARSE(document w.resp) columns
> valOption2 string PATH 'item[id = "id1"]/val'
> --,valOption1 string PATH 'item[id/text() = "id1"]/val'
> ) x;;
> {code}
> returned value for "valOption2" will be changed from "val1" to "null" that is incorrect and unexpected behavior.
> Using "node/text()" in Path expressions may result in side effects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (TEIID-5235) Could not find symbol in processing an inline view using except
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5235?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5235:
----------------------------------
Fix Version/s: 10.0.3
> Could not find symbol in processing an inline view using except
> ---------------------------------------------------------------
>
> Key: TEIID-5235
> URL: https://issues.jboss.org/browse/TEIID-5235
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.1, 10.0.3
>
>
> With a query such as:
> SELECT case when agent_tin_id is null then 'Y' else 'N' end agent_tin_id from (SELECT agent_tin_id from MySQL_Server.bitool.AGENT_DIM where agent_tin_id>100 except( SELECT agent_tin_id from MySQL_Server.bitool.AGENT_DIM where agent_tin_id=100)) a
> When not fully pushed is processed as an anti semi join, but results in an exception:
> {code}
> org.teiid.core.TeiidRuntimeException: Planning error. Could not find symbol: a.agent_tin_id
> at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:363)
> at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:129)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:92)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:98)
> at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:87)
> at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:223)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (TEIID-5235) Could not find symbol in processing an inline view using except
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5235?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5235.
-----------------------------------
Resolution: Done
Updated the logic to insert a project node to account for the source node above the created join.
> Could not find symbol in processing an inline view using except
> ---------------------------------------------------------------
>
> Key: TEIID-5235
> URL: https://issues.jboss.org/browse/TEIID-5235
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.1
>
>
> With a query such as:
> SELECT case when agent_tin_id is null then 'Y' else 'N' end agent_tin_id from (SELECT agent_tin_id from MySQL_Server.bitool.AGENT_DIM where agent_tin_id>100 except( SELECT agent_tin_id from MySQL_Server.bitool.AGENT_DIM where agent_tin_id=100)) a
> When not fully pushed is processed as an anti semi join, but results in an exception:
> {code}
> org.teiid.core.TeiidRuntimeException: Planning error. Could not find symbol: a.agent_tin_id
> at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:363)
> at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:129)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:92)
> at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:98)
> at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:87)
> at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:223)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months