January 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4676) PrestoDB translator - convert/cast is not properly translated/pushed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4676?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4676. ----------------------------------- Fix Version/s: 9.2 (was: 9.2.1) Resolution: Done Merged the pull request. > PrestoDB translator - convert/cast is not properly translated/pushed > -------------------------------------------------------------------- > > Key: TEIID-4676 > URL: https://issues.jboss.org/browse/TEIID-4676 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.8.6_3 > Reporter: Juraj Duráni > Assignee: Kylin Soong > Fix For: 9.2 > > > Convert/cast in query \[1\] is not pushed to PrestoDB. > In come cases Teiid acts like it was pushed (reads integer instead of String) and throws exception \[2\] while reading result from PrestoDB. Source-specific command \[3\]. > In other scenario, not-traslated convert causes exception - query \[4\], processing query \[5\], source-specific command \[6\], exception \[7\]. > {code:sql|title=\[1\] Query} > SELECT convert(stringnum, integer) FROM bqt1.smalla > {code} > {code:plain|title=\[2\] Exception} > 12:20:10,727 WARN [org.teiid.PROCESSOR] (Worker4_QueryProcessorQueue41) TEIID30020 Processing exception for request A7WqBzZhsyYM.6 'TEIID30504 Source: Unexpected exception while translating results: Value is not a number: java.lang.String'. Originally TeiidProcessingException PrestoResultSet.java:1727.: org.teiid.core.TeiidProcessingException: TEIID30504 Source: Unexpected exception while translating results: Value is not a number: java.lang.String > at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:401) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:161) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:391) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_92] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_92] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_92] > Caused by: org.teiid.translator.TranslatorException: Unexpected exception while translating results: Value is not a number: java.lang.String > at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:351) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:434) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:234) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_92] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_92] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_92] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_92] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at com.sun.proxy.$Proxy48.more(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:309) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_92] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > ... 6 more > Caused by: java.sql.SQLException: Value is not a number: java.lang.String > at com.facebook.presto.jdbc.PrestoResultSet.toNumber(PrestoResultSet.java:1727) > at com.facebook.presto.jdbc.PrestoResultSet.getInt(PrestoResultSet.java:212) > at org.jboss.jca.adapters.jdbc.WrappedResultSet.getInt(WrappedResultSet.java:1052) > at org.teiid.translator.jdbc.JDBCExecutionFactory.retrieveValue(JDBCExecutionFactory.java:997) > at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:344) > ... 19 more > {code} > {code:sql|title=\[3\] Command} > SELECT g_0.stringnum FROM smalla AS g_0 > {code} > {code:sql|title=\[4\] User query} > SELECT BooleanValue, (BooleanValue+1) AS BooleanValuePlus2 FROM BQT1.SmallA > {code} > {code:sql|title=\[5\] Teiid query} > SELECT g_0.BooleanValue, (convert(g_0.BooleanValue, integer) + 1) FROM Source.SmallA AS g_0 > {code} > {code:sql|title=\[6\] Source-specific command} > SELECT g_0.booleanvalue, (g_0.booleanvalue + 1) FROM smalla AS g_0 > {code} > {code:plain|title=\[7\] Exception} > 12:41:46,974 WARN [org.teiid.CONNECTOR] (Worker15_QueryProcessorQueue70) Connector worker process failed for atomic-request=A7WqBzZhsyYM.18.0.16: org.teiid.translator.jdbc.JDBCExecutionException: 1 TEIID11008:TEIID11004 Error executing statement(s): [SQL: SELECT g_0.booleanvalue, (g_0.booleanvalue + 1) FROM smalla AS g_0] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) > at sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source) [:1.8.0_92] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_92] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_92] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy48.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_92] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_92] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_92] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_92] > Caused by: java.sql.SQLException: Query failed (#20170106_114146_04086_k4ss5): line 1:44: '+' cannot be applied to boolean, integer > at com.facebook.presto.jdbc.PrestoResultSet.resultsException(PrestoResultSet.java:1799) > at com.facebook.presto.jdbc.PrestoResultSet.getColumns(PrestoResultSet.java:1747) > at com.facebook.presto.jdbc.PrestoResultSet.<init>(PrestoResultSet.java:125) > at com.facebook.presto.jdbc.PrestoStatement.execute(PrestoStatement.java:212) > at com.facebook.presto.jdbc.PrestoStatement.executeQuery(PrestoStatement.java:69) > at org.jboss.jca.adapters.jdbc.WrappedStatement.executeQuery(WrappedStatement.java:344) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:119) [translator-jdbc-8.12.5.redhat-8.jar:8.12.5.redhat-8] > ... 17 more > Caused by: com.facebook.presto.sql.analyzer.SemanticException: line 1:44: '+' cannot be applied to boolean, integer > at com.facebook.presto.sql.analyzer.ExpressionAnalyzer$Visitor.getOperator(ExpressionAnalyzer.java:1138) > at com.facebook.presto.sql.analyzer.ExpressionAnalyzer$Visitor.visitArithmeticBinary(ExpressionAnalyzer.java:560) > at com.facebook.presto.sql.analyzer.ExpressionAnalyzer$Visitor.visitArithmeticBinary(ExpressionAnalyzer.java:254) > at com.facebook.presto.sql.tree.ArithmeticBinaryExpression.accept(ArithmeticBinaryExpression.java:82) > at com.facebook.presto.sql.tree.StackableAstVisitor.process(StackableAstVisitor.java:26) > at com.facebook.presto.sql.analyzer.ExpressionAnalyzer$Visitor.process(ExpressionAnalyzer.java:273) > at com.facebook.presto.sql.analyzer.ExpressionAnalyzer.analyze(ExpressionAnalyzer.java:230) > at com.facebook.presto.sql.analyzer.ExpressionAnalyzer.analyzeExpression(ExpressionAnalyzer.java:1416) > at com.facebook.presto.sql.analyzer.StatementAnalyzer.analyzeExpression(StatementAnalyzer.java:1791) > at com.facebook.presto.sql.analyzer.StatementAnalyzer.analyzeSelect(StatementAnalyzer.java:1613) > at com.facebook.presto.sql.analyzer.StatementAnalyzer.visitQuerySpecification(StatementAnalyzer.java:785) > at com.facebook.presto.sql.analyzer.StatementAnalyzer.visitQuerySpecification(StatementAnalyzer.java:187) > at com.facebook.presto.sql.tree.QuerySpecification.accept(QuerySpecification.java:125) > at com.facebook.presto.sql.tree.AstVisitor.process(AstVisitor.java:27) > at com.facebook.presto.sql.analyzer.StatementAnalyzer.visitQuery(StatementAnalyzer.java:549) > at com.facebook.presto.sql.analyzer.StatementAnalyzer.visitQuery(StatementAnalyzer.java:187) > at com.facebook.presto.sql.tree.Query.accept(Query.java:92) > at com.facebook.presto.sql.tree.AstVisitor.process(AstVisitor.java:27) > at com.facebook.presto.sql.analyzer.Analyzer.analyze(Analyzer.java:67) > at com.facebook.presto.sql.analyzer.Analyzer.analyze(Analyzer.java:59) > at com.facebook.presto.execution.SqlQueryExecution.doAnalyzeQuery(SqlQueryExecution.java:285) > at com.facebook.presto.execution.SqlQueryExecution.analyzeQuery(SqlQueryExecution.java:271) > at com.facebook.presto.execution.SqlQueryExecution.start(SqlQueryExecution.java:229) > at com.facebook.presto.execution.QueuedExecution.lambda$start$1(QueuedExecution.java:62) > ... 3 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4690) Displayed javascript source in documentation

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4690?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4690: --------------------------------------- Yes, this is likely something that we can't resolve. It will need to be raised as an issue with github. > Displayed javascript source in documentation > -------------------------------------------- > > Key: TEIID-4690 > URL: https://issues.jboss.org/browse/TEIID-4690 > Project: Teiid > Issue Type: Bug > Reporter: Miroslava Voglova > Assignee: Kylin Soong > > Javascript source is displayed in [data sources|https://teiid.gitbooks.io/documents/content/reference/Data_Sources.html] page. > Element script has style="display: block;" when inspecting element (checked in Firefox). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4686) PrestoDB translator - ordering of joined tables fails

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4686?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4686: ------------------------------------- [~jdurani] I do not think there is a way to disable ORDER BY only in JOIN situations through capabilities. Also there is seems to be specific when there are multiple columns in the ORDER BY. I would suggest making this as translator override and adding a note in the document about it, that way we can leave it for the user configuration. > PrestoDB translator - ordering of joined tables fails > ----------------------------------------------------- > > Key: TEIID-4686 > URL: https://issues.jboss.org/browse/TEIID-4686 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.8.6_3 > Reporter: Juraj Duráni > Assignee: Kylin Soong > Fix For: 9.2.1 > > > Issuing query like \[1\] causes an exception in PrestoDB. This seems to be PrestoDB issue. I found similar issue \[2\], but that one should be fixed. I have created a new issue \[3\]. Removing one column from ORDER BY, query returns correct result. > Not sure if we can do something about it without avoiding pushing JOIN. > I suggest either to fix this (if simple enough) or add a note to the documentation. > \[1\] > {code:sql} > SELECT a.intkey, b.intkey FROM BQT1.SmallA AS a INNER JOIN BQT1.SmallB AS b on a.intkey = b.intkey ORDER BY 1, 2 > {code} > \[2\] https://github.com/prestodb/presto/issues/1621 > \[3\] https://github.com/prestodb/presto/issues/7010 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4702) Clarify that JDG is what's supported, not infinispan

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4702?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4702: ------------------------------------ Changed the resource adapters to reference JDG, instead of Infinispan. > Clarify that JDG is what's supported, not infinispan > ---------------------------------------------------- > > Key: TEIID-4702 > URL: https://issues.jboss.org/browse/TEIID-4702 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > > The documentation related to supporting Infinispan as a data source should be clarified that its JDG that is supported. Referencing Infinispan when its not really the intention of the data source integration, causes confusion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4702) Clarify that JDG is what's supported, not infinispan

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4702?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4702: ------------------------------- Git Pull Request: https://github.com/teiid/teiid-documents/pull/90 > Clarify that JDG is what's supported, not infinispan > ---------------------------------------------------- > > Key: TEIID-4702 > URL: https://issues.jboss.org/browse/TEIID-4702 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > > The documentation related to supporting Infinispan as a data source should be clarified that its JDG that is supported. Referencing Infinispan when its not really the intention of the data source integration, causes confusion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4702) Clarify that JDG is what's supported, not infinispan

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4702?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-4702: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Clarify that JDG is what's supported, not infinispan > ---------------------------------------------------- > > Key: TEIID-4702 > URL: https://issues.jboss.org/browse/TEIID-4702 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > > The documentation related to supporting Infinispan as a data source should be clarified that its JDG that is supported. Referencing Infinispan when its not really the intention of the data source integration, causes confusion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4702) Clarify that JDG is what's supported, not infinispan

by Van Halbert (JIRA)

Van Halbert created TEIID-4702: ---------------------------------- Summary: Clarify that JDG is what's supported, not infinispan Key: TEIID-4702 URL: https://issues.jboss.org/browse/TEIID-4702 Project: Teiid Issue Type: Enhancement Components: Documentation Affects Versions: 9.2 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor The documentation related to supporting Infinispan as a data source should be clarified that its JDG that is supported. Referencing Infinispan when its not really the intention of the data source integration, causes confusion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4701) Create a quick start/embedded examples to demonstrate PrestoDB as a datasource

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4701?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-4701: ------------------------------------- Is it worth of it? Do we need a QS for "standard-JDBC-ds-usage" demonstration? > Create a quick start/embedded examples to demonstrate PrestoDB as a datasource > ------------------------------------------------------------------------------ > > Key: TEIID-4701 > URL: https://issues.jboss.org/browse/TEIID-4701 > Project: Teiid > Issue Type: Task > Components: Quick Starts > Affects Versions: 9.2 > Reporter: Kylin Soong > Assignee: Van Halbert > > a quick start/embedded examples to demonstrate PrestoDB as a datasource -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4686) PrestoDB translator - ordering of joined tables fails

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4686?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-4686: ------------------------------------- [~kylin] I do not. Setting up a PrestoDB instance consuming e.g. MySQL is pretty simple. Following [PrestoDB documentation|https://prestodb.io/docs/current/], it's simple. Regarding quickstart - is it worth of it? PrestoDB uses standard JDBC driver so there is really nothing special in connecting and consuming it. > PrestoDB translator - ordering of joined tables fails > ----------------------------------------------------- > > Key: TEIID-4686 > URL: https://issues.jboss.org/browse/TEIID-4686 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.8.6_3 > Reporter: Juraj Duráni > Assignee: Kylin Soong > Fix For: 9.2.1 > > > Issuing query like \[1\] causes an exception in PrestoDB. This seems to be PrestoDB issue. I found similar issue \[2\], but that one should be fixed. I have created a new issue \[3\]. Removing one column from ORDER BY, query returns correct result. > Not sure if we can do something about it without avoiding pushing JOIN. > I suggest either to fix this (if simple enough) or add a note to the documentation. > \[1\] > {code:sql} > SELECT a.intkey, b.intkey FROM BQT1.SmallA AS a INNER JOIN BQT1.SmallB AS b on a.intkey = b.intkey ORDER BY 1, 2 > {code} > \[2\] https://github.com/prestodb/presto/issues/1621 > \[3\] https://github.com/prestodb/presto/issues/7010 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4701) Create a quick start/embedded examples to demonstrate PrestoDB as a datasource

by Kylin Soong (JIRA)

Kylin Soong created TEIID-4701: ---------------------------------- Summary: Create a quick start/embedded examples to demonstrate PrestoDB as a datasource Key: TEIID-4701 URL: https://issues.jboss.org/browse/TEIID-4701 Project: Teiid Issue Type: Task Components: Quick Starts Affects Versions: 9.2 Reporter: Kylin Soong Assignee: Van Halbert a quick start/embedded examples to demonstrate PrestoDB as a datasource -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2017