April 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5725) Please improve documentation on definition of stored procedures, virtual functions and virtual procedures

by Christoph John (Jira)

[ https://issues.jboss.org/browse/TEIID-5725?page=com.atlassian.jira.plugin... ] Christoph John edited comment on TEIID-5725 at 4/22/19 3:52 PM: ---------------------------------------------------------------- Hello Steven, I came up with a further question regarding virtual procedures. The question is related to transactions. Let's say I have multiple Teiid instances running which access the same mysql database, or alternatively other clients with direct access to the mysql database. Do I explicitly have to wrap my virtual procedures and functions which I write in the ddl file into a transaction? And how would the command syntax for this look like? Further question regarding visibility of stored procedures and functions. I learned from a discussion with Ramesh, that there is a visibility attribute which I can set on the entire schema to set all tables and functions inaccessible. However, in that case I would have to wrap each table I like to export to odata into a view, which seems like odd extra work for me. My thinking is the following. If I have a stored procedure or function in the source database, I would like to use it within my virtual procedures but at the same time would not like to allow access via odata. Would it be possible to add a visibility option to the procedure definition in the dll definition? Or does something similar already exist? was (Author: cjohn001): Hello Steven, I came up with a further question regarding virtual procedures. The question is related to transactions. Let's say I have multiple Teiid instances running which access the same mysql database, or alternatively other clients with direct access to the mysql database. Do I explicitly have to wrap my virtual procedures and functions which I write in the ddl file into a transaction? And how would the command syntax for this look like? > Please improve documentation on definition of stored procedures, virtual functions and virtual procedures > --------------------------------------------------------------------------------------------------------- > > Key: TEIID-5725 > URL: https://issues.jboss.org/browse/TEIID-5725 > Project: Teiid > Issue Type: Enhancement > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Critical > > I refer to the discussion with Ramesh in > https://developer.jboss.org/message/989048#989048 and would like to ask for a more detailed explanation on how to write virtual procedures and functions. > -Especially, how are OUT and INOUT params set and how can they be obtained via odata. > - How is the return value of a virtual function set? > - How are collections and arrays of collections returned? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5725) Please improve documentation on definition of stored procedures, virtual functions and virtual procedures

by Christoph John (Jira)

[ https://issues.jboss.org/browse/TEIID-5725?page=com.atlassian.jira.plugin... ] Christoph John commented on TEIID-5725: --------------------------------------- Hello Steven, I came up with a further question regarding virtual procedures. The question is related to transactions. Let's say I have multiple Teiid instances running which access the same mysql database, or alternatively other clients with direct access to the mysql database. Do I explicitly have to wrap my virtual procedures and functions which I write in the ddl file into a transaction? And how would the command syntax for this look like? > Please improve documentation on definition of stored procedures, virtual functions and virtual procedures > --------------------------------------------------------------------------------------------------------- > > Key: TEIID-5725 > URL: https://issues.jboss.org/browse/TEIID-5725 > Project: Teiid > Issue Type: Enhancement > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Critical > > I refer to the discussion with Ramesh in > https://developer.jboss.org/message/989048#989048 and would like to ask for a more detailed explanation on how to write virtual procedures and functions. > -Especially, how are OUT and INOUT params set and how can they be obtained via odata. > - How is the return value of a virtual function set? > - How are collections and arrays of collections returned? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5725) Please improve documentation on definition of stored procedures, virtual functions and virtual procedures

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5725?page=com.atlassian.jira.plugin... ] Work on TEIID-5725 started by Steven Hawkins. --------------------------------------------- > Please improve documentation on definition of stored procedures, virtual functions and virtual procedures > --------------------------------------------------------------------------------------------------------- > > Key: TEIID-5725 > URL: https://issues.jboss.org/browse/TEIID-5725 > Project: Teiid > Issue Type: Enhancement > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Critical > > I refer to the discussion with Ramesh in > https://developer.jboss.org/message/989048#989048 and would like to ask for a more detailed explanation on how to write virtual procedures and functions. > -Especially, how are OUT and INOUT params set and how can they be obtained via odata. > - How is the return value of a virtual function set? > - How are collections and arrays of collections returned? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5720) PSQL client fails to report the metadata

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5720?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5720: --------------------------------------- \d \dt \dS - now work \dd fails since the reserved word object is being used as an alias \df \dy \dD \dg \du fails as we don't like the array constructor ARRAY( and we don't define pg_catalog.array_to_string \dL fails as we don't define a pg_catalog.pg_language \dT fails since we don't support the two argument pg_catalog.obj_description \da fails since we don't support pg_catalog.text as an alias in that context - we have added some support for aliases with ., so this is just another case not yet covered. \db fails since we don't define pg_tablesspace \dC fails since we don't define pg_cast \dl fails since we don't define pg_largeobject \do fails since we don't define pg_operator \dp fails since we don't define the relacl column This also highlights that we'll need to move our reported server version consistently ahead in the near future to 8.4+. 8.2 is not 13 years old and many of the \d commands don't work against that old of a version. I'll tack on a fix for the lowest hanging fruit above and we can document the other limitations. > PSQL client fails to report the metadata > ---------------------------------------- > > Key: TEIID-5720 > URL: https://issues.jboss.org/browse/TEIID-5720 > Project: Teiid > Issue Type: Bug > Components: ODBC > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When using psql client and issuing the "\dt" command I see this exception instead of returning the table names. > {code} > WARN: TEIID30020 Processing exception for request grF9mx6fyMfD.1 'TEIID30082 Expected value of type 'char' but '''' is of type 'string' and no implicit conversion is available.'. Originally QueryResolverException ResolverUtil.java:230. > org.teiid.api.exception.query.QueryResolverException: TEIID30082 Expected value of type 'char' but '''' is of type 'string' and no implicit conversion is available. > at org.teiid.query.resolver.util.ResolverUtil.convertExpression(ResolverUtil.java:230) > at org.teiid.query.resolver.util.ResolverVisitor.resolveSetCriteria(ResolverVisitor.java:1203) > at org.teiid.query.resolver.util.ResolverVisitor.visit(ResolverVisitor.java:294) > at org.teiid.query.sql.lang.SetCriteria.acceptVisitor(SetCriteria.java:96) > at org.teiid.query.sql.navigator.AbstractNavigator.visitVisitor(AbstractNavigator.java:50) > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.postVisitVisitor(PreOrPostOrderNavigator.java:57) > at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.postVisitVisitor(SimpleQueryResolver.java:229) > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:345) > at org.teiid.query.sql.lang.SetCriteria.acceptVisitor(SetCriteria.java:96) > at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:59) > at org.teiid.query.sql.navigator.AbstractNavigator.visitNodes(AbstractNavigator.java:72) > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:135) > at org.teiid.query.sql.lang.CompoundCriteria.acceptVisitor(CompoundCriteria.java:231) > at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:59) > at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:244) > at org.teiid.query.resolver.command.SimpleQueryResolver.resolveCommand(SimpleQueryResolver.java:66) > at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:178) > at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:120) > at org.teiid.dqp.internal.process.Request.resolveCommand(Request.java:282) > at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:418) > at org.teiid.dqp.internal.process.Request.processRequest(Request.java:486) > at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:672) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:351) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:43) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:285) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:281) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:124) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$2.run(ThreadReuseExecutor.java:212) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-54) Provide Salesforce source support

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-54?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIIDSB-54: ------------------------------------- yeah, we pulled the refresh-token negotiation outside in oauth-util.sh then apply to any resource-adapter, but never went back to fix the google one to this approach. > Provide Salesforce source support > --------------------------------- > > Key: TEIIDSB-54 > URL: https://issues.jboss.org/browse/TEIIDSB-54 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Affects Versions: 1.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Salesforce data source needs to be supported. Should support the same authentication as the Syndesis -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-54) Provide Salesforce source support

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-54?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-54: --------------------------------------- I was thinking of how we built refresh token support into the google resource adapter. I forgot about the login module approach... > Provide Salesforce source support > --------------------------------- > > Key: TEIIDSB-54 > URL: https://issues.jboss.org/browse/TEIIDSB-54 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Affects Versions: 1.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Salesforce data source needs to be supported. Should support the same authentication as the Syndesis -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-54) Provide Salesforce source support

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-54?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIIDSB-54: ------------------------------------- see here http://teiid.github.io/teiid-documents/master/content/admin/Salesforce_Da... for "OAuth Security with "Refresh Token"" looks like documentation has error in showing the title correctly. > Provide Salesforce source support > --------------------------------- > > Key: TEIIDSB-54 > URL: https://issues.jboss.org/browse/TEIIDSB-54 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Affects Versions: 1.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Salesforce data source needs to be supported. Should support the same authentication as the Syndesis -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-54) Provide Salesforce source support

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-54?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-54: --------------------------------------- Would that be directly configured through CXF? The resource adapter only handles username/password and propogation of OAuth and username/password. > Provide Salesforce source support > --------------------------------- > > Key: TEIIDSB-54 > URL: https://issues.jboss.org/browse/TEIIDSB-54 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Affects Versions: 1.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Salesforce data source needs to be supported. Should support the same authentication as the Syndesis -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-54) Provide Salesforce source support

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-54?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIIDSB-54: ------------------------------------- Do you mean for WildFly? There is similar support there. > Provide Salesforce source support > --------------------------------- > > Key: TEIIDSB-54 > URL: https://issues.jboss.org/browse/TEIIDSB-54 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Affects Versions: 1.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Salesforce data source needs to be supported. Should support the same authentication as the Syndesis -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-54) Provide Salesforce source support

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-54?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-54: --------------------------------------- Should we add refresh token support to the resource adapter as well? > Provide Salesforce source support > --------------------------------- > > Key: TEIIDSB-54 > URL: https://issues.jboss.org/browse/TEIIDSB-54 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Affects Versions: 1.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Salesforce data source needs to be supported. Should support the same authentication as the Syndesis -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2019