[JBoss JIRA] (TEIIDSB-215) Remove the amazon-s3 source
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-215:
--------------------------------------
Summary: Remove the amazon-s3 source
Key: TEIIDSB-215
URL: https://issues.redhat.com/browse/TEIIDSB-215
Project: Teiid Spring Boot
Issue Type: Sub-task
Components: datasource
Reporter: Steven Hawkins
Fix For: 1.6.0
Now that a proper s3 source has been added there's no reason to keep the existing amazon-s3 support in Teiid Spring Boot. We'll simply deprecate on the Teiid side.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (TEIID-5936) create an s3 file source
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5936?page=com.atlassian.jira.plugi... ]
Work on TEIID-5936 started by Steven Hawkins.
---------------------------------------------
> create an s3 file source
> -------------------------
>
> Key: TEIID-5936
> URL: https://issues.redhat.com/browse/TEIID-5936
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 15.0
>
>
> The existing s3 support is implemented as a translator / ws source combo. We instead need this to be just a source to allow for translators to utilize it (excel, parquet, avro).
> As an alternative to our existing support we should evaluate utilizing the sdk rather than providing our own processing logic. More than likely this will be a quicker path to things like s3 select support. However ceph seems to lag in s3 support (see TEIID-5935 and no s3 select support) so we'd have to compensate, make the metadata and/or the capabilities specific to the connection type.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (TEIID-5936) create an s3 file source
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5936?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIID-5936:
---------------------------------------
Just like with the hdfs work, I'll port the s3 logic from spring boot. It should be considerably easier this time given less dependency issues.
> create an s3 file source
> -------------------------
>
> Key: TEIID-5936
> URL: https://issues.redhat.com/browse/TEIID-5936
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 15.0
>
>
> The existing s3 support is implemented as a translator / ws source combo. We instead need this to be just a source to allow for translators to utilize it (excel, parquet, avro).
> As an alternative to our existing support we should evaluate utilizing the sdk rather than providing our own processing logic. More than likely this will be a quicker path to things like s3 select support. However ceph seems to lag in s3 support (see TEIID-5935 and no s3 select support) so we'd have to compensate, make the metadata and/or the capabilities specific to the connection type.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (TEIID-5979) how to create web service datasource for Google cloud APIs
by Nayan Bija (Jira)
[ https://issues.redhat.com/browse/TEIID-5979?page=com.atlassian.jira.plugi... ]
Nayan Bija updated TEIID-5979:
------------------------------
Description:
We need to create a web service data source to access google apis.
I followed the steps mentioned in the below document
[http://teiid.github.io/teiid-documents/master/content/admin/OAuth_Authent...]
But getting below error after entering the Access Token URL.
Could you please provide solution on it.
Error logs.
===========
WARNING: Default key managers cannot be initialized: Password must not be null
java.security.UnrecoverableKeyException: Password must not be null
at sun.security.provider.JavaKeyStore.engineGetKey(JavaKeyStore.java:124)
at sun.security.provider.JavaKeyStore$JKS.engineGetKey(JavaKeyStore.java:55)
at java.security.KeyStore.getKey(KeyStore.java:1011)
at sun.security.ssl.SunX509KeyManagerImpl.<init>(SunX509KeyManagerImpl.java:133)
at sun.security.ssl.KeyManagerFactoryImpl$SunX509.engineInit(KeyManagerFactoryImpl.java:70)
at javax.net.ssl.KeyManagerFactory.init(KeyManagerFactory.java:256)
at org.apache.cxf.configuration.jsse.SSLUtils.loadDefaultKeyManagers(SSLUtils.java:116)
at org.apache.cxf.configuration.jsse.SSLUtils.getDefaultKeyStoreManagers(SSLUtils.java:89)
at org.apache.cxf.transport.https.SSLUtils.getSSLContext(SSLUtils.java:75)
at org.apache.cxf.transport.https.HttpsURLConnectionFactory.decorateWithTLS(HttpsURLConnectionFactory.java:144)
at org.apache.cxf.transport.https.HttpsURLConnectionFactory.createConnection(HttpsURLConnectionFactory.java:101)
at org.apache.cxf.transport.http.URLConnectionHTTPConduit.createConnection(URLConnectionHTTPConduit.java:121)
at org.apache.cxf.transport.http.URLConnectionHTTPConduit.setupConnection(URLConnectionHTTPConduit.java:125)
at org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduit.setupConnection(AsyncHTTPConduit.java:190)
at org.apache.cxf.transport.http.HTTPConduit.prepare(HTTPConduit.java:505)
at org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:47)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at org.apache.cxf.jaxrs.client.AbstractClient.doRunInterceptorChain(AbstractClient.java:701)
at org.apache.cxf.jaxrs.client.WebClient.doChainedInvocation(WebClient.java:1086)
at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:932)
at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:901)
at org.apache.cxf.jaxrs.client.WebClient.form(WebClient.java:434)
at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:301)
at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:225)
at org.teiid.oauth.OAuthUtil.oauth20Flow(OAuthUtil.java:158)
at org.teiid.oauth.OAuthUtil.main(OAuthUtil.java:76)
at org.jboss.modules.Module.run(Module.java:352)
at org.jboss.modules.Module.run(Module.java:320)
at org.jboss.modules.Main.main(Main.java:593)
Exception in thread "main" org.apache.cxf.rs.security.oauth2.provider.OAuthServiceException: server_error
at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:323)
at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:225)
at org.teiid.oauth.OAuthUtil.oauth20Flow(OAuthUtil.java:158)
at org.teiid.oauth.OAuthUtil.main(OAuthUtil.java:76)
at org.jboss.modules.Module.run(Module.java:352)
at org.jboss.modules.Module.run(Module.java:320)
at org.jboss.modules.Main.main(Main.java:593)
Press any key to continue . . .
> how to create web service datasource for Google cloud APIs
> ----------------------------------------------------------
>
> Key: TEIID-5979
> URL: https://issues.redhat.com/browse/TEIID-5979
> Project: Teiid
> Issue Type: Feature Request
> Components: Common
> Reporter: Nayan Bija
> Assignee: Steven Hawkins
> Priority: Major
>
> We need to create a web service data source to access google apis.
> I followed the steps mentioned in the below document
> [http://teiid.github.io/teiid-documents/master/content/admin/OAuth_Authent...]
>
> But getting below error after entering the Access Token URL.
> Could you please provide solution on it.
>
> Error logs.
> ===========
> WARNING: Default key managers cannot be initialized: Password must not be null
> java.security.UnrecoverableKeyException: Password must not be null
> at sun.security.provider.JavaKeyStore.engineGetKey(JavaKeyStore.java:124)
> at sun.security.provider.JavaKeyStore$JKS.engineGetKey(JavaKeyStore.java:55)
> at java.security.KeyStore.getKey(KeyStore.java:1011)
> at sun.security.ssl.SunX509KeyManagerImpl.<init>(SunX509KeyManagerImpl.java:133)
> at sun.security.ssl.KeyManagerFactoryImpl$SunX509.engineInit(KeyManagerFactoryImpl.java:70)
> at javax.net.ssl.KeyManagerFactory.init(KeyManagerFactory.java:256)
> at org.apache.cxf.configuration.jsse.SSLUtils.loadDefaultKeyManagers(SSLUtils.java:116)
> at org.apache.cxf.configuration.jsse.SSLUtils.getDefaultKeyStoreManagers(SSLUtils.java:89)
> at org.apache.cxf.transport.https.SSLUtils.getSSLContext(SSLUtils.java:75)
> at org.apache.cxf.transport.https.HttpsURLConnectionFactory.decorateWithTLS(HttpsURLConnectionFactory.java:144)
> at org.apache.cxf.transport.https.HttpsURLConnectionFactory.createConnection(HttpsURLConnectionFactory.java:101)
> at org.apache.cxf.transport.http.URLConnectionHTTPConduit.createConnection(URLConnectionHTTPConduit.java:121)
> at org.apache.cxf.transport.http.URLConnectionHTTPConduit.setupConnection(URLConnectionHTTPConduit.java:125)
> at org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduit.setupConnection(AsyncHTTPConduit.java:190)
> at org.apache.cxf.transport.http.HTTPConduit.prepare(HTTPConduit.java:505)
> at org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:47)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at org.apache.cxf.jaxrs.client.AbstractClient.doRunInterceptorChain(AbstractClient.java:701)
> at org.apache.cxf.jaxrs.client.WebClient.doChainedInvocation(WebClient.java:1086)
> at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:932)
> at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:901)
> at org.apache.cxf.jaxrs.client.WebClient.form(WebClient.java:434)
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:301)
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:225)
> at org.teiid.oauth.OAuthUtil.oauth20Flow(OAuthUtil.java:158)
> at org.teiid.oauth.OAuthUtil.main(OAuthUtil.java:76)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Exception in thread "main" org.apache.cxf.rs.security.oauth2.provider.OAuthServiceException: server_error
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:323)
> at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:225)
> at org.teiid.oauth.OAuthUtil.oauth20Flow(OAuthUtil.java:158)
> at org.teiid.oauth.OAuthUtil.main(OAuthUtil.java:76)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Press any key to continue . . .
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (TEIID-5928) Allow External and Internal materialization of multi-source to fail/update individually
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5928?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIID-5928:
---------------------------------------
Here's the work in progress: https://github.com/teiid/teiid/pull/1295
It basically implements what is described above, but exposes the source names via a new procedure sysadmin.schemaSources - as the full source name list may not be generally known it's better to have this in sysadmin and it will be easier to work with than an array value: "select s.name from (exec sysadmin.schemaSources('schema name')) s"
> Allow External and Internal materialization of multi-source to fail/update individually
> ---------------------------------------------------------------------------------------
>
> Key: TEIID-5928
> URL: https://issues.redhat.com/browse/TEIID-5928
> Project: Teiid
> Issue Type: Enhancement
> Components: Common
> Affects Versions: 12.2.2
> Reporter: Rafael Sampaio
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 15.0
>
> Original Estimate: 0 minutes
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> Hi, all.
> First of all thanks in advance for your attention, and efforts on such a great product.
> Since I haven't found any docs or examples regarding my current usage (please if this already exists or there's a better way of doing this, disregard this request and advice) here goes my suggestion:
> It would be nice to have a way to gracefully update/fail per source, if a view that has Materialization enabled and target a multi-source source model, because things can get, messy if I have to create a view per source and Materialize each one and only then create a unified (UNION) view.
> Using this approach also obligates me to implement custom insert/update/delete/based on the discriminator column.
> Thanks again.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months