March 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2554) Enhance MERGE to support INSERT/UPDATE and DELETE

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-2554?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-2554. ----------------------------------- Fix Version/s: (was: 13.x) Resolution: Deferred > Enhance MERGE to support INSERT/UPDATE and DELETE > ------------------------------------------------- > > Key: TEIID-2554 > URL: https://issues.redhat.com/browse/TEIID-2554 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.4 > Reporter: Van Halbert > Priority: Major > > Add delete support to MERGE. Example is SQL Server: > MERGE <target_table> [AS TARGET] > USING <table_source> [AS SOURCE] > ON <search_condition> > [WHEN MATCHED > THEN <merge_matched> ] > [WHEN NOT MATCHED [BY TARGET] > THEN <merge_not_matched> ] > [WHEN NOT MATCHED BY SOURCE > THEN <merge_ matched> ]; -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1226) Reuse dynamic sql plans and allow for prepared statements in procedure logic

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-1226?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-1226. ----------------------------------- Fix Version/s: (was: 13.x) Resolution: Deferred Marking as deferred as there's been no customer/community request for this functionality. A quick alternative would be to develop prepared plans from dynamic sql when applicable. > Reuse dynamic sql plans and allow for prepared statements in procedure logic > ---------------------------------------------------------------------------- > > Key: TEIID-1226 > URL: https://issues.redhat.com/browse/TEIID-1226 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > > Dynamic sql plans (for dynamic sql statements, lookup, and matview refreshes) should allow for plan reuse. > Also procedure logic should have a mechanism to execute prepared statements for further plan reuse. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1096) Allow cost analysis tool to work against custom connectors

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-1096?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-1096: ---------------------------------- Parent: TEIID-992 Issue Type: Sub-task (was: Feature Request) > Allow cost analysis tool to work against custom connectors > ---------------------------------------------------------- > > Key: TEIID-1096 > URL: https://issues.redhat.com/browse/TEIID-1096 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Marc Shirley > Priority: Minor > Fix For: 13.x > > > case 5541 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-992) Improve update of source costing statistics

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-992?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-992: --------------------------------- Parent: (was: TEIID-245) Issue Type: Feature Request (was: Sub-task) > Improve update of source costing statistics > ------------------------------------------- > > Key: TEIID-992 > URL: https://issues.redhat.com/browse/TEIID-992 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Marc Shirley > Priority: Major > > It is very important that we support the ability to update source statistics at runtime. This is important due to the changing nature of read/write sources and differences between a development data source and a production data source. > The following options should be possible: > 1) Update model/source statistics on VDB deployment. > 2) Update model/source statistics on connector startup. > 3) Update model/source statistics on at a scheduled time. > 4) Update model/source statistics upon a manual request. > case 5920 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-245) Update costing metadata at runtime

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-245?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-245. ---------------------------------- Fix Version/s: (was: 13.x) Resolution: Duplicate Marking as a duplicate of the more general TEIID-992 > Update costing metadata at runtime > ---------------------------------- > > Key: TEIID-245 > URL: https://issues.redhat.com/browse/TEIID-245 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Reporter: Steven Hawkins > Priority: Minor > Attachments: OracleExecutionFactory.java.patch > > > Defect Tracker #24584: Cost analysis should be both a design-time activity and scheduled/feed during runtime. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5913) Assist with productization of the documentation

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5913?focusedWorklogId=12450520&pag... ] Steven Hawkins logged work on TEIID-5913: ----------------------------------------- Author: Steven Hawkins Created on: 14/Mar/20 9:55 PM Start Date: 14/Mar/20 9:55 PM Worklog Time Spent: 30 minutes Issue Time Tracking ------------------- Time Spent: 2 days, 2 hours (was: 2 days, 1 hour, 30 minutes) Worklog Id: (was: 12450520) > Assist with productization of the documentation > ----------------------------------------------- > > Key: TEIID-5913 > URL: https://issues.redhat.com/browse/TEIID-5913 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.x > > Original Estimate: 1 day, 2 hours > Time Spent: 2 days, 2 hours > Remaining Estimate: 0 minutes > > Assist the documentation team in merging changes and keeping the community docs building. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5876) MongoDB import name conflict issues

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5876?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5876. ----------------------------------- Resolution: Done Added and documented a new property to control if full embedded names are used. > MongoDB import name conflict issues > ----------------------------------- > > Key: TEIID-5876 > URL: https://issues.redhat.com/browse/TEIID-5876 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0 > > Original Estimate: 4 hours > Time Spent: 2 hours > Remaining Estimate: 2 hours > > There are two issues with the import logic and naming: > 1. There's an assumption that any table in the schema was created by the mongodb import. In general this is not true as other imports or ddl may have already run. > 2. If a child construct has a field name that matches an existing table, the two entities will get intertwined in the metadata, which is invalid. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5876) MongoDB import name conflict issues

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5876?focusedWorklogId=12450519&pag... ] Steven Hawkins logged work on TEIID-5876: ----------------------------------------- Author: Steven Hawkins Created on: 14/Mar/20 9:54 PM Start Date: 14/Mar/20 9:54 PM Worklog Time Spent: 1 hour, 30 minutes Issue Time Tracking ------------------- Remaining Estimate: 30 minutes (was: 2 hours) Time Spent: 3 hours, 30 minutes (was: 2 hours) Worklog Id: (was: 12450519) > MongoDB import name conflict issues > ----------------------------------- > > Key: TEIID-5876 > URL: https://issues.redhat.com/browse/TEIID-5876 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0 > > Original Estimate: 4 hours > Time Spent: 3 hours, 30 minutes > Remaining Estimate: 30 minutes > > There are two issues with the import logic and naming: > 1. There's an assumption that any table in the schema was created by the mongodb import. In general this is not true as other imports or ddl may have already run. > 2. If a child construct has a field name that matches an existing table, the two entities will get intertwined in the metadata, which is invalid. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5895) Review/create common mongodb logic

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5895?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5895: ---------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > Review/create common mongodb logic > ---------------------------------- > > Key: TEIID-5895 > URL: https://issues.redhat.com/browse/TEIID-5895 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Similar to the refactoring of infinispan connectivity, the logic should be shared between teiid and teiid spring boot. As well as a review of similar potential issues with the join filtering and TEIID-5876 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5895) Review/create common mongodb logic

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5895?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5895. ----------------------------------- Resolution: Done It looks like TEIID-5611 did all that is needed as there is no more common logic to capture in the connection impl - and no need at this time to switch to something other than the deprecated DB. When that happens we can revisit if a common base is needed. > Review/create common mongodb logic > ---------------------------------- > > Key: TEIID-5895 > URL: https://issues.redhat.com/browse/TEIID-5895 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0 > > > Similar to the refactoring of infinispan connectivity, the logic should be shared between teiid and teiid spring boot. As well as a review of similar potential issues with the join filtering and TEIID-5876 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2020