December 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-145) Move the Spring Boot version 2.1.6.RELEASE to match for Syndesis

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-145?page=com.atlassian.jira.plugi... ] Van Halbert updated TEIIDSB-145: -------------------------------- Git Pull Request: https://github.com/syndesisio/syndesis/pull/7289, https://github.com/teiid/teiid-spring-boot/pull/147 (was: https://github.com/syndesisio/syndesis/pull/7289) > Move the Spring Boot version 2.1.6.RELEASE to match for Syndesis > ---------------------------------------------------------------- > > Key: TEIIDSB-145 > URL: https://issues.jboss.org/browse/TEIIDSB-145 > Project: Teiid Spring Boot > Issue Type: Task > Components: core > Reporter: Ramesh Reddy > Assignee: Van Halbert > Priority: Major > Fix For: 1.3.0 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > To match the version with Syndesis, move the Spring Boot to 2.1.6.RELEASE -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-145) Move the Spring Boot version 2.1.6.RELEASE to match for Syndesis

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-145?page=com.atlassian.jira.plugi... ] Van Halbert commented on TEIIDSB-145: ------------------------------------- [PR | https://github.com/teiid/teiid-spring-boot/pull/147] aligns teiid-spring-boot with 2.1.6.RELEASE > Move the Spring Boot version 2.1.6.RELEASE to match for Syndesis > ---------------------------------------------------------------- > > Key: TEIIDSB-145 > URL: https://issues.jboss.org/browse/TEIIDSB-145 > Project: Teiid Spring Boot > Issue Type: Task > Components: core > Reporter: Ramesh Reddy > Assignee: Van Halbert > Priority: Major > Fix For: 1.3.0 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > To match the version with Syndesis, move the Spring Boot to 2.1.6.RELEASE -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-146) Master branch fails to build due to expected results are have been reordered

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-146?page=com.atlassian.jira.plugi... ] Van Halbert closed TEIIDSB-146. ------------------------------- Resolution: Rejected Closing this request as it appears there is something that causes the ordering to be different when built locally. I'll work around the issue so that I can move on. > Master branch fails to build due to expected results are have been reordered > ---------------------------------------------------------------------------- > > Key: TEIIDSB-146 > URL: https://issues.jboss.org/browse/TEIIDSB-146 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Affects Versions: 1.3.0 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: 1.3.0 > > > Building master branch produced different expected results, which appear to be because schema info order has been changed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5857) Remove the modelauditfields execution property

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5857?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5857. ----------------------------------- Resolution: Done Updated the translator, docs, and release notes. > Remove the modelauditfields execution property > ---------------------------------------------- > > Key: TEIID-5857 > URL: https://issues.jboss.org/browse/TEIID-5857 > Project: Teiid > Issue Type: Quality Risk > Components: Salesforce Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Quite a while ago we added the import property modelAuditFields so that the execution property was no longer needed. It should be removed for clarity. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5859) Upgrade to wildfly 18

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5859: ------------------------------------- Summary: Upgrade to wildfly 18 Key: TEIID-5859 URL: https://issues.jboss.org/browse/TEIID-5859 Project: Teiid Issue Type: Task Components: Build/Kits, Server Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 13.1 We should pick up the latest wildfly 18+ -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5857) Remove the modelauditfields execution property

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5857?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5857: ---------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes Story Points: 0.5 (was: 1) > Remove the modelauditfields execution property > ---------------------------------------------- > > Key: TEIID-5857 > URL: https://issues.jboss.org/browse/TEIID-5857 > Project: Teiid > Issue Type: Quality Risk > Components: Salesforce Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Quite a while ago we added the import property modelAuditFields so that the execution property was no longer needed. It should be removed for clarity. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5762) Update security configuration to elytron

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5762?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5762: ---------------------------------- Fix Version/s: 13.1 (was: 13.0) > Update security configuration to elytron > ---------------------------------------- > > Key: TEIID-5762 > URL: https://issues.jboss.org/browse/TEIID-5762 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > > The Teiid configuration is based upon an out-dated version of the wildfly config. It should be brought up-to-date. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5856) Teiid generate wrong request to salesforce

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5856?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5856: --------------------------------------- > It is one request to salesforce. But i think references generation do not working in teiid now I don't know what you mean by references. > But need one Generally the salesforce translator will handle a single level of inner or left outer join as you expect. The one requirement is that there is a foreign key between the two tables - which should be inferred from the salesforce metadata. In this case you are performing a self-join of Product_License__c - there currently is no support for self-joins. That can certainly be captured as an issue/enhancement request. > I think do not working self references generation only. If i try to use SQL > Generated SOQL is > SELECT Account.BillingCountry__c, Account.Name FROM Contact LIMIT 1 I don't follow you. Are you saying that is the SOQL teiid is generating in that example or that is what you expect to be generated? That SOQL looks correct for the SQL query - it's just a child-to-parent query https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sos... > Another example: > wrong plan You'll have to clarify what you mean by wrong. Note that a limitation of the current salesforce translator is that only a single level of the relationship can be queried together. Introducing three entities will cause the pushdown to be split. Here again you can capture that as an enhancement request if you want. > Teiid generate wrong request to salesforce > ------------------------------------------ > > Key: TEIID-5856 > URL: https://issues.jboss.org/browse/TEIID-5856 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Environment: spring-boot teiid salesforce-connector > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > When i call request to salesforce teiid get very long wrong request and then OOM, because teiid request all data in salesforce object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-146) Master branch fails to build due to expected results are have been reordered

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-146?page=com.atlassian.jira.plugi... ] Van Halbert updated TEIIDSB-146: -------------------------------- Story Points: 1 > Master branch fails to build due to expected results are have been reordered > ---------------------------------------------------------------------------- > > Key: TEIIDSB-146 > URL: https://issues.jboss.org/browse/TEIIDSB-146 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Affects Versions: 1.3.0 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: 1.3.0 > > > Building master branch produced different expected results, which appear to be because schema info order has been changed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-146) Master branch fails to build due to expected results are have been reordered

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-146?page=com.atlassian.jira.plugi... ] Van Halbert updated TEIIDSB-146: -------------------------------- Git Pull Request: https://github.com/teiid/teiid-spring-boot/pull/146 > Master branch fails to build due to expected results are have been reordered > ---------------------------------------------------------------------------- > > Key: TEIIDSB-146 > URL: https://issues.jboss.org/browse/TEIIDSB-146 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Affects Versions: 1.3.0 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: 1.3.0 > > > Building master branch produced different expected results, which appear to be because schema info order has been changed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2019