[JBoss JIRA] (TEIID-4319) Deprecate automatically adding of the class object to the source table
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4319?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-4319:
------------------------------------
the inclusion of the Object column will now be controlled by the import property: supportsClassObjectAsColumn
example: <property name="importer.supportsClassObjectAsColumn" value="true"/>
> Deprecate automatically adding of the class object to the source table
> -----------------------------------------------------------…
[View More]-----------
>
> Key: TEIID-4319
> URL: https://issues.jboss.org/browse/TEIID-4319
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 9.x
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> If the source model is not defined with the metadata, but allowing the infinispan (object) translator to reverse engineer the metadata from the cache object class, the process will add a column that represents the cache object. This is a holdover from the original implementation that used the OBJECTTABLE function for transforming the object into a row in the result set. This column is not required and can be excluded (or removed) if modeling the object source table.
> This column also causes WARNING to show up in the server log because it is assumed by the engine to be part of materialization. However, this column is not updatable and can be excluded in materialization by not specifying it in the INSERT INTO statement.
> So to clean up all this, it would be good to stop adding the class object as a column in the source table. And the user can always add it back if they wish to use it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 8 months
[JBoss JIRA] (TEIID-4319) Deprecate automatically adding of the class object to the source table
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4319?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-4319:
-------------------------------
Git Pull Request: https://github.com/teiid/teiid/pull/776 (was: https://github.com/teiid/teiid/pull/772)
> Deprecate automatically adding of the class object to the source table
> ----------------------------------------------------------------------
>
> Key: TEIID-4319
> URL: https://issues.jboss.…
[View More]org/browse/TEIID-4319
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 9.x
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> If the source model is not defined with the metadata, but allowing the infinispan (object) translator to reverse engineer the metadata from the cache object class, the process will add a column that represents the cache object. This is a holdover from the original implementation that used the OBJECTTABLE function for transforming the object into a row in the result set. This column is not required and can be excluded (or removed) if modeling the object source table.
> This column also causes WARNING to show up in the server log because it is assumed by the engine to be part of materialization. However, this column is not updatable and can be excluded in materialization by not specifying it in the INSERT INTO statement.
> So to clean up all this, it would be good to stop adding the class object as a column in the source table. And the user can always add it back if they wish to use it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 8 months
[JBoss JIRA] (TEIID-4357) Add documentation on exposing Teiid as a GeoServer data souce
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4357?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4357:
----------------------------------
Description: Based on the details in TEIID-3869, need to document how Teiid can be exposed as a GeoServer data source (was: Based on the details in TEIID-3869, need to document how Teiid can be exposed as a GIS compliant data source)
Summary: Add documentation on exposing Teiid as a GeoServer data souce (was: Add documentation on …
[View More]exposing Teiid as a GIS compliant data souce)
> Add documentation on exposing Teiid as a GeoServer data souce
> -------------------------------------------------------------
>
> Key: TEIID-4357
> URL: https://issues.jboss.org/browse/TEIID-4357
> Project: Teiid
> Issue Type: Enhancement
> Components: Documentation
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> Based on the details in TEIID-3869, need to document how Teiid can be exposed as a GeoServer data source
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 8 months
[JBoss JIRA] (TEIID-4356) Add asort of connection test for "connection definitions" of resource adapters
by Marco Ardito (JIRA)
Marco Ardito created TEIID-4356:
-----------------------------------
Summary: Add asort of connection test for "connection definitions" of resource adapters
Key: TEIID-4356
URL: https://issues.jboss.org/browse/TEIID-4356
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Marco Ardito
Assignee: Steven Hawkins
Priority: Minor
Could a sort of "…
[View More]connection test" be implemented to verify if a "connection definition" specified for a resource adapter (eg: file, google, etc) is working, and can "connect" to the resource it's supposedly pointing to?
Data sources(jdbc) already have this kind of test, and it is quite useful to test if there's any error in their connection definition.
With resource adapters, one must define connection definitions, but it is not possible to test them, independently from later requests/queries (eg: reading data from .csv or .xls files, or oauth web services): one has to build all the chain and really try to get data from the source, using the vdb, hoping everything is correctly defined...
Recently I am struggling with a custom rest oauth2 RA, and I need to define
- security domain (with client id/secret, tokens, auth uri)
- RA using that domain
- a connection definition for the RA accessing the remote data source
- a VDB using the connection definition
- a client using the VDB to try get data in sql form
any step could be wrong, but only the last allows to check if the whole chain is working, or not.
For any error or failure, regular users (like me) can't do anything else than double check everything... a "test connection" button, for the connection definition, would do wonders to simplify setup debug...
Marco
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 8 months
[JBoss JIRA] (TEIID-4354) patch to CXF no longer needed with new version of the CXF in 9.0 series.
by Marco Ardito (JIRA)
[ https://issues.jboss.org/browse/TEIID-4354?page=com.atlassian.jira.plugin... ]
Marco Ardito commented on TEIID-4354:
-------------------------------------
ok, it was just to make sure it didn't went unnoticed, since you marked this solved so fast... :)
thx
> patch to CXF no longer needed with new version of the CXF in 9.0 series.
> ------------------------------------------------------------------------
>
> Key: TEIID-4354
> URL: https://…
[View More]issues.jboss.org/browse/TEIID-4354
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.x
> Reporter: Marco Ardito
> Assignee: Ramesh Reddy
> Fix For: 9.1, 9.0.3
>
>
> Using oauth2 authentication for rest webservice in Teiid (issuing sql request through invokeHTTP method in dynamic VDB), fails with an error like:
> ERROR [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue61) P8QCt6jWv5/F Connector worker process failed for atomic-request=P8QCt6jWv5/F.7.4.35838: java.lang.NoClassDefFoundError: javax/ws/rs/client/ClientException
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:287)
> ...many more
> (see forum reference for more stack trace)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 8 months
[JBoss JIRA] (TEIID-4354) patch to CXF no longer needed with new version of the CXF in 9.0 series.
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4354?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4354:
-------------------------------------
That may be separate issue, I will have look shortly :)
> patch to CXF no longer needed with new version of the CXF in 9.0 series.
> ------------------------------------------------------------------------
>
> Key: TEIID-4354
> URL: https://issues.jboss.org/browse/TEIID-4354
> …
[View More] Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.x
> Reporter: Marco Ardito
> Assignee: Ramesh Reddy
> Fix For: 9.1, 9.0.3
>
>
> Using oauth2 authentication for rest webservice in Teiid (issuing sql request through invokeHTTP method in dynamic VDB), fails with an error like:
> ERROR [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue61) P8QCt6jWv5/F Connector worker process failed for atomic-request=P8QCt6jWv5/F.7.4.35838: java.lang.NoClassDefFoundError: javax/ws/rs/client/ClientException
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:287)
> ...many more
> (see forum reference for more stack trace)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 8 months
[JBoss JIRA] (TEIID-4354) patch to CXF no longer needed with new version of the CXF in 9.0 series.
by Marco Ardito (JIRA)
[ https://issues.jboss.org/browse/TEIID-4354?page=com.atlassian.jira.plugin... ]
Marco Ardito commented on TEIID-4354:
-------------------------------------
Forgot to say: after upgrading to 9.0.2 (bundle)...
> patch to CXF no longer needed with new version of the CXF in 9.0 series.
> ------------------------------------------------------------------------
>
> Key: TEIID-4354
> URL: https://issues.jboss.org/browse/TEIID-4354
> …
[View More]Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.x
> Reporter: Marco Ardito
> Assignee: Ramesh Reddy
> Fix For: 9.1, 9.0.3
>
>
> Using oauth2 authentication for rest webservice in Teiid (issuing sql request through invokeHTTP method in dynamic VDB), fails with an error like:
> ERROR [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue61) P8QCt6jWv5/F Connector worker process failed for atomic-request=P8QCt6jWv5/F.7.4.35838: java.lang.NoClassDefFoundError: javax/ws/rs/client/ClientException
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:287)
> ...many more
> (see forum reference for more stack trace)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 8 months
[JBoss JIRA] (TEIID-4354) patch to CXF no longer needed with new version of the CXF in 9.0 series.
by Marco Ardito (JIRA)
[ https://issues.jboss.org/browse/TEIID-4354?page=com.atlassian.jira.plugin... ]
Marco Ardito commented on TEIID-4354:
-------------------------------------
Ramesh, have you also checked forum thread post n.14?
https://developer.jboss.org/message/960646#960646
I tried removing jar and modules.xml reference, but in squirrel I still get a cxf related error...
Marco
> patch to CXF no longer needed with new version of the CXF in 9.0 series.
> -------------------------------------------…
[View More]-----------------------------
>
> Key: TEIID-4354
> URL: https://issues.jboss.org/browse/TEIID-4354
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.x
> Reporter: Marco Ardito
> Assignee: Ramesh Reddy
> Fix For: 9.1, 9.0.3
>
>
> Using oauth2 authentication for rest webservice in Teiid (issuing sql request through invokeHTTP method in dynamic VDB), fails with an error like:
> ERROR [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue61) P8QCt6jWv5/F Connector worker process failed for atomic-request=P8QCt6jWv5/F.7.4.35838: java.lang.NoClassDefFoundError: javax/ws/rs/client/ClientException
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:287)
> ...many more
> (see forum reference for more stack trace)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 8 months