August 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4981) Support Amazon S3 Transaltor

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4981?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4981: ------------------------------------ Thanks Ramesh. > Support Amazon S3 Transaltor > ---------------------------- > > Key: TEIID-4981 > URL: https://issues.jboss.org/browse/TEIID-4981 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 10.0, 8.12.x-6.4 > > > Support Amazon S3 access from Teiid. Typically this is viewed as file-based access? however handling the security is key here. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4981) Support Amazon S3 Transaltor

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4981?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4981: -------------------------------- Fix Version/s: 8.12.x-6.4 > Support Amazon S3 Transaltor > ---------------------------- > > Key: TEIID-4981 > URL: https://issues.jboss.org/browse/TEIID-4981 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 10.0, 8.12.x-6.4 > > > Support Amazon S3 access from Teiid. Typically this is viewed as file-based access? however handling the security is key here. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4844) Google translator unexpected behavior for comparison with time

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4844?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4844: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1460484|https://bugzilla.redhat.com/show_bug.cgi?id=1460484] from NEW to MODIFIED > Google translator unexpected behavior for comparison with time > -------------------------------------------------------------- > > Key: TEIID-4844 > URL: https://issues.jboss.org/browse/TEIID-4844 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.10.6_3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Fix For: 9.3, 8.12.x-6.4, 9.2.2 > > > Comparison operators <, <=, >, >=, =, <> work unexpectedly for 'time' datatype, foreign table has column 'timevalue time OPTIONS (NATIVE_TYPE 'TIMEOFDAY')'. > I created view with column 'TimeValue time', inserted data in format '10:57:23'. > I run queries like 'DELETE FROM smalla WHERE TimeValue < {t '10:57:23'}' > * <, <>, <= deletes all rows, including rows that should be left > * >, >=, = deletes no rows -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4964) AWS S3 Connector

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4964?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4964: ------------------------------- Fix Version/s: 8.12.x-6.4 > AWS S3 Connector > ---------------- > > Key: TEIID-4964 > URL: https://issues.jboss.org/browse/TEIID-4964 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Chandra Akkinepalli > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 10.0, 8.12.x-6.4 > > > I would like to request a feature for a new connector to access files in AWS S3 via JDV and be able to use SQL to query them. > It would be great to have the ability to use AWS KMS for accessing the SSE-KMS encrypted objects on AWS S3 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4080) Prevent expired client/server certificates from being accepted

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4080?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4080: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1318154, https://bugzilla.redhat.com/show_bug.cgi?id=1481709 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1318154) > Prevent expired client/server certificates from being accepted > -------------------------------------------------------------- > > Key: TEIID-4080 > URL: https://issues.jboss.org/browse/TEIID-4080 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > Attachments: keystore_client.jks, keystore_server_root_expired.jks, truststore.jks, truststore_expired.jks > > > If SSL is enabled (1-way or 2-way) server provides to the client certificate which must be signed by valid certificate of trusted CA. > If server provides certificate which is signed by certificate of root CA which already expired client accepts this certificate. Client should not accept such certificate. > This affects 1-way and 2-way authentication modes. > On the client side, paths are set using teiid-specific properties: > {code:java} > System.setProperty("org.teiid.ssl.keyStore", clientKeystorePath); > System.setProperty("org.teiid.ssl.keyStorePassword", "keystorepswd"); > System.setProperty("org.teiid.ssl.keyAlias", "client"); > System.setProperty("org.teiid.ssl.keyPassword", "keystorepswd"); > System.setProperty("org.teiid.ssl.trustStore", clientTruststorePath); > System.setProperty("org.teiid.ssl.trustStorePassword", "truststorepswd"); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4700) Google translator inconsistent behavior for DELETE and SELECT for null values

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4700?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4700: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1460483|https://bugzilla.redhat.com/show_bug.cgi?id=1460483] from NEW to MODIFIED > Google translator inconsistent behavior for DELETE and SELECT for null values > ----------------------------------------------------------------------------- > > Key: TEIID-4700 > URL: https://issues.jboss.org/browse/TEIID-4700 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.2 > Environment: 9.2.0.Alpha2 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Fix For: 9.2, 9.1.3, 8.12.x-6.4 > > > In teiid I observed following inconsistent behavior: > Q1: select intnum, intkey from smalla where intnum > -10 AND intnum < 20 > Q2: delete from smalla where intnum > -10 AND intnum < 20 > Q1 returns rows without null values for intnum, but Q2 deletes also rows with null values for intnum. > I observed that if I remove the lower boundary (ie. Q3: select intnum, intkey from smalla where intnum < 20 and similarly for delete), both selected and deleted rows contain null values, so the result is consistent. > The server.log is empty, so I didn't attach it... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5020) Join query results in NullPointerException

by Debbie Steigner (JIRA)

Debbie Steigner created TEIID-5020: -------------------------------------- Summary: Join query results in NullPointerException Key: TEIID-5020 URL: https://issues.jboss.org/browse/TEIID-5020 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 9.3.2, 8.12.11.6_3 Reporter: Debbie Steigner Assignee: Steven Hawkins Running Join query results in NPE: 10:36:06,836 ERROR [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue17) TEIID30019 Unexpected exception for request KuTljjNz7YSM.1: java.lang.NullPointerException at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:423) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:415) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:491) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:399) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:276) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:223) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:243) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:186) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.<init>(ConnectorWorkItem.java:176) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.datamgr.ConnectorManager.registerRequest(ConnectorManager.java:203) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.process.DataTierManagerImpl.registerRequest(DataTierManagerImpl.java:997) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:179) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:497) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.relational.AccessNode.openInternal(AccessNode.java:265) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:168) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.relational.UnionAllNode.open(UnionAllNode.java:123) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.relational.JoinStrategy.openRight(JoinStrategy.java:105) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:231) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.relational.LimitNode.nextBatchDirect(LimitNode.java:102) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:150) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5014) Unable to use parameterized query with node pg module and Teiid/JBoss VDB

by Brian M (JIRA)

[ https://issues.jboss.org/browse/TEIID-5014?page=com.atlassian.jira.plugin... ] Brian M commented on TEIID-5014: -------------------------------- Great! Thank you so much again, Steven! > Unable to use parameterized query with node pg module and Teiid/JBoss VDB > ------------------------------------------------------------------------- > > Key: TEIID-5014 > URL: https://issues.jboss.org/browse/TEIID-5014 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.7.11.6_2 > Environment: Teiid runtime 8.7.11 > JBoss Data Virtualization 6.10 > NodeJS 6.9.4 > node pg 6.4.1 > Mac OSX 10.11.6 > Reporter: Brian M > Assignee: Steven Hawkins > Fix For: 10.0, 9.2.6, 9.3.3 > > > When using node pg 6.4.1 in a node application to connect to a JBoss VDB with Teiid, we are unable to successfully return data with a parameterized query. > Example from node js application (failure): > client.query("SELECT * FROM records WHERE recordType = $1", ['TYPE1'], function(err, result) { done(); }) > The above code will actually retrieve rows of data, but the connection will be terminated unexpectedly from the JBoss side, thus resulting in a failure. We can confirm though that the parameter is properly inserted into the variable, and rows of data can be retrieved without issue. > Also, we have confirmed that when sending a static query, we are able to successfully return data without JBoss terminating the connection. We found this approach from the Teiid blog: http://teiid.blogspot.com/2013/02/access-teiid-from-nodejs.html > Example from node js application (success): > client.query("SELECT * FROM records WHERE recordType = 'TYPE1'", function(err, result) { done(); }) > Is there something different about a parameterized query vs. a static query that may cause this issue? > Are you aware of other individuals who have successfully used parameterized queries with the node pg module and Teiid/JBoss VDB? > Is it possible that how the ODBC settings for Teiid are configured may have an impact on parameterized queries vs. static queries? > Link: https://teiid.gitbooks.io/documents/content/client-dev/ODBC_Support.html > Thank you so much for all your help! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5014) Unable to use parameterized query with node pg module and Teiid/JBoss VDB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5014?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5014: --------------------------------------- > Does this mean that we can apply your fix in 9.3.3? It's already on the 9.3.x branch for inclusion into 9.3.3. > Unable to use parameterized query with node pg module and Teiid/JBoss VDB > ------------------------------------------------------------------------- > > Key: TEIID-5014 > URL: https://issues.jboss.org/browse/TEIID-5014 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.7.11.6_2 > Environment: Teiid runtime 8.7.11 > JBoss Data Virtualization 6.10 > NodeJS 6.9.4 > node pg 6.4.1 > Mac OSX 10.11.6 > Reporter: Brian M > Assignee: Steven Hawkins > Fix For: 10.0, 9.2.6, 9.3.3 > > > When using node pg 6.4.1 in a node application to connect to a JBoss VDB with Teiid, we are unable to successfully return data with a parameterized query. > Example from node js application (failure): > client.query("SELECT * FROM records WHERE recordType = $1", ['TYPE1'], function(err, result) { done(); }) > The above code will actually retrieve rows of data, but the connection will be terminated unexpectedly from the JBoss side, thus resulting in a failure. We can confirm though that the parameter is properly inserted into the variable, and rows of data can be retrieved without issue. > Also, we have confirmed that when sending a static query, we are able to successfully return data without JBoss terminating the connection. We found this approach from the Teiid blog: http://teiid.blogspot.com/2013/02/access-teiid-from-nodejs.html > Example from node js application (success): > client.query("SELECT * FROM records WHERE recordType = 'TYPE1'", function(err, result) { done(); }) > Is there something different about a parameterized query vs. a static query that may cause this issue? > Are you aware of other individuals who have successfully used parameterized queries with the node pg module and Teiid/JBoss VDB? > Is it possible that how the ODBC settings for Teiid are configured may have an impact on parameterized queries vs. static queries? > Link: https://teiid.gitbooks.io/documents/content/client-dev/ODBC_Support.html > Thank you so much for all your help! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5014) Unable to use parameterized query with node pg module and Teiid/JBoss VDB

by Brian M (JIRA)

[ https://issues.jboss.org/browse/TEIID-5014?page=com.atlassian.jira.plugin... ] Brian M commented on TEIID-5014: -------------------------------- Hi Steven! Thank you so much for the resolution! We really appreciate your speed in fixing this! Thank you! Does this mean that we can apply your fix in 9.3.3? > Unable to use parameterized query with node pg module and Teiid/JBoss VDB > ------------------------------------------------------------------------- > > Key: TEIID-5014 > URL: https://issues.jboss.org/browse/TEIID-5014 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.7.11.6_2 > Environment: Teiid runtime 8.7.11 > JBoss Data Virtualization 6.10 > NodeJS 6.9.4 > node pg 6.4.1 > Mac OSX 10.11.6 > Reporter: Brian M > Assignee: Steven Hawkins > Fix For: 10.0, 9.2.6, 9.3.3 > > > When using node pg 6.4.1 in a node application to connect to a JBoss VDB with Teiid, we are unable to successfully return data with a parameterized query. > Example from node js application (failure): > client.query("SELECT * FROM records WHERE recordType = $1", ['TYPE1'], function(err, result) { done(); }) > The above code will actually retrieve rows of data, but the connection will be terminated unexpectedly from the JBoss side, thus resulting in a failure. We can confirm though that the parameter is properly inserted into the variable, and rows of data can be retrieved without issue. > Also, we have confirmed that when sending a static query, we are able to successfully return data without JBoss terminating the connection. We found this approach from the Teiid blog: http://teiid.blogspot.com/2013/02/access-teiid-from-nodejs.html > Example from node js application (success): > client.query("SELECT * FROM records WHERE recordType = 'TYPE1'", function(err, result) { done(); }) > Is there something different about a parameterized query vs. a static query that may cause this issue? > Are you aware of other individuals who have successfully used parameterized queries with the node pg module and Teiid/JBoss VDB? > Is it possible that how the ODBC settings for Teiid are configured may have an impact on parameterized queries vs. static queries? > Link: https://teiid.gitbooks.io/documents/content/client-dev/ODBC_Support.html > Thank you so much for all your help! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2017