April 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5937) Union All followed by except returns wrong results

by Dmitrii Pogorelov (Jira)

Dmitrii Pogorelov created TEIID-5937: ---------------------------------------- Summary: Union All followed by except returns wrong results Key: TEIID-5937 URL: https://issues.redhat.com/browse/TEIID-5937 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 13.1 Reporter: Dmitrii Pogorelov Assignee: Steven Hawkins The following queries return wrong results: {code:sql} -- <null> though should return 1 select * from views.test2 except select * from views.test1 UNION ALL select * from views.test1 except select * from views.test2 ;; -- <null> though should return 1 (select * from views.test2 except select * from views.test1 UNION ALL select * from views.test1) except select * from views.test2 ;; {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5935) S3 support for ceph

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5935?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5935: --------------------------------------- After looking over rpm and manual install options, I switched to https://rook.io/docs/rook/v1.3/ceph-quickstart.html which unfortunately has it's own hurdles https://rook.io/docs/rook/v1.3/k8s-pre-reqs.html so long story short, it's a bit of a slog to get this running quickly / locally. > S3 support for ceph > ------------------- > > Key: TEIID-5935 > URL: https://issues.redhat.com/browse/TEIID-5935 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0 > > > We need to validate ceph support against the changes in TEIID-5927. The most immediate issue appears to be that ceph does not support the v2 listing of bucket contents and would need to use an older list method. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-190) REST with request payload throws an error

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-190?page=com.atlassian.jira.plug... ] Steven Hawkins reassigned TEIIDSB-190: -------------------------------------- Assignee: Steven Hawkins (was: Ramesh Reddy) > REST with request payload throws an error > ----------------------------------------- > > Key: TEIIDSB-190 > URL: https://issues.redhat.com/browse/TEIIDSB-190 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Reporter: Sadhana Nandakumar > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > > TEIID spring boot is expecting the payload to be a bean, and hence throws an error. POST without request body works fine without any issues. > CREATE VIEW StockPrice ( > symbol string PRIMARY KEY, > price double > ) AS > SELECT p.symbol, y.price > FROM accounts.PRODUCT as p, TABLE(call invokeHttp(action=>'POST', endpoint=>QUERYSTRING('predict'), headers=>jsonObject('application/json' as "Content-Type"), request=>jsonObject('PLATINUM' as "customerClass"))) as x, > JSONTABLE(JSONPARSE(x.result,true), '$' COLUMNS price double path '@.data.segment') as y > No errors on build, when I query the odata endpoint, I see the following error. > <error xmlns="http://docs.oasis-open.org/odata/ns/metadata"> > <code>TEIID30504</code> > <message> > TEIID30504 quotesvc: No bean named '{"customerClass":"PLATINUM"}' available > </message> > </error> -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-192) Document migration for alias names

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-192: ------------------------------------ Summary: Document migration for alias names Key: TEIIDSB-192 URL: https://issues.redhat.com/browse/TEIIDSB-192 Project: Teiid Spring Boot Issue Type: Task Components: documentation Reporter: Ramesh Reddy Translators like salesforce and actian-vector has new name in the spring boot, we need to either document or switch back to original names. Also if we are updating migration utilities we can build in smarts into it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-191) Build annotation based ExternalSource for JDBC sources

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-191: ------------------------------------ Summary: Build annotation based ExternalSource for JDBC sources Key: TEIIDSB-191 URL: https://issues.redhat.com/browse/TEIIDSB-191 Project: Teiid Spring Boot Issue Type: Enhancement Components: core Reporter: Ramesh Reddy All the JDBC based sources need to be converted to individual projects such that dependencies can be captured correctly and these also fall into the naming convention like other "spring-data-xxxx" sources. Then we can consider removing the external json file in the Operator to solely depend on the naming convention even for JDBC. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-186) Fix to use only use alias name from ExternalSource

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-186?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIIDSB-186. ---------------------------------- Resolution: Done Documentation and JDBC based external sources will be handled in separate JIRA > Fix to use only use alias name from ExternalSource > -------------------------------------------------- > > Key: TEIIDSB-186 > URL: https://issues.redhat.com/browse/TEIIDSB-186 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > Time Spent: 4 days, 2 hours > Remaining Estimate: 0 minutes > > As the code progressed the usage of translator name and alias name from ExternalSource class is interchangeably used. This is leading to confusion in terms of development and documents. > Need to fix all the places where the translator name used to use alias name with Spring Boot engine. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-187) Change the Operator around ExternalSource

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-187?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIIDSB-187. ---------------------------------- Resolution: Done Added the external connection_factories.json file to drive all the connection management and also parse the VDB for the name and types of data sources rather than string lookups. > Change the Operator around ExternalSource > ----------------------------------------- > > Key: TEIIDSB-187 > URL: https://issues.redhat.com/browse/TEIIDSB-187 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > Time Spent: 2 days > Remaining Estimate: 0 minutes > > Consider externalizing ExternalSource information into a "json" configuration file, then this can be then used in Operator code load and enforce dependencies and pom file generation and property generation from a single location. Right now all this looks very hacky as it spread out across projects. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-187) Change the Operator around ExternalSource

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-187?focusedWorklogId=12450842&pa... ] Ramesh Reddy logged work on TEIIDSB-187: ---------------------------------------- Author: Ramesh Reddy Created on: 16/Apr/20 4:12 PM Start Date: 16/Apr/20 4:11 PM Worklog Time Spent: 2 days Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 2 days Worklog Id: (was: 12450842) > Change the Operator around ExternalSource > ----------------------------------------- > > Key: TEIIDSB-187 > URL: https://issues.redhat.com/browse/TEIIDSB-187 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > Time Spent: 2 days > Remaining Estimate: 0 minutes > > Consider externalizing ExternalSource information into a "json" configuration file, then this can be then used in Operator code load and enforce dependencies and pom file generation and property generation from a single location. Right now all this looks very hacky as it spread out across projects. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-187) Change the Operator around ExternalSource

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-187?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-187: --------------------------------- Description: Consider externalizing ExternalSource information into a "json" configuration file, then this can be then used in Operator code load and enforce dependencies and pom file generation and property generation from a single location. Right now all this looks very hacky as it spread out across projects. was: The prefix of the source like "org.spring.teiid.data.xxx" kind of property patterns are defined in the ConnectionFactory classes, this needs to be pulled into ExternalSource class, then this can be one central place everything about translator and source is managed. Consider externalizing ExternalSource information into a "json" configuration file, then this can be then used in Operator code load and enforce dependencies and pom file generation and property generation from a single location. Right now all this looks very hacky as it spread out across projects. > Change the Operator around ExternalSource > ----------------------------------------- > > Key: TEIIDSB-187 > URL: https://issues.redhat.com/browse/TEIIDSB-187 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > > Consider externalizing ExternalSource information into a "json" configuration file, then this can be then used in Operator code load and enforce dependencies and pom file generation and property generation from a single location. Right now all this looks very hacky as it spread out across projects. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-187) Change the Operator around ExternalSource

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-187?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-187: --------------------------------- Summary: Change the Operator around ExternalSource (was: Need to pull out the "property prefix" to ExternalSource) > Change the Operator around ExternalSource > ----------------------------------------- > > Key: TEIIDSB-187 > URL: https://issues.redhat.com/browse/TEIIDSB-187 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > > The prefix of the source like "org.spring.teiid.data.xxx" kind of property patterns are defined in the ConnectionFactory classes, this needs to be pulled into ExternalSource class, then this can be one central place everything about translator and source is managed. > Consider externalizing ExternalSource information into a "json" configuration file, then this can be then used in Operator code load and enforce dependencies and pom file generation and property generation from a single location. Right now all this looks very hacky as it spread out across projects. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2020