May 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-199) Teiid logging level env vars are not supported

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-199?focusedWorklogId=12451029&pa... ] Ramesh Reddy logged work on TEIIDSB-199: ---------------------------------------- Author: Ramesh Reddy Created on: 13/May/20 1:41 PM Start Date: 13/May/20 1:41 PM Worklog Time Spent: 3 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 3 hours Worklog Id: (was: 12451029) > Teiid logging level env vars are not supported > ---------------------------------------------- > > Key: TEIIDSB-199 > URL: https://issues.redhat.com/browse/TEIIDSB-199 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > Time Spent: 3 hours > Remaining Estimate: 0 minutes > > There are two undocumented env vars to enable source query logging, {{LOGGING_LEVEL_ORG_TEIID_COMMAND_LOG}} and {{LOGGING_LEVEL_ORG_TEIID_COMMAND_LOG_SOURCE}} . These should be documented to allow debugging of query-level issues. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5928) Allow External and Internal materialization of multi-source to fail/update individually

by Rafael Sampaio (Jira)

[ https://issues.redhat.com/browse/TEIID-5928?page=com.atlassian.jira.plugi... ] Rafael Sampaio commented on TEIID-5928: --------------------------------------- Yes, you nailed it... That's what I think it should happen on a refresh. My situation a true multi-source source table, and a Materialized view on top that with discriminator column in the view. I believe that if the multi-source table could be materialized would be a nice approach, due to the problem you stated which is not easy to detect the multi-source nature of the underlying tables used to build the view. Thanks for your quick response. > Allow External and Internal materialization of multi-source to fail/update individually > --------------------------------------------------------------------------------------- > > Key: TEIID-5928 > URL: https://issues.redhat.com/browse/TEIID-5928 > Project: Teiid > Issue Type: Enhancement > Components: Common > Affects Versions: 12.2.2 > Reporter: Rafael Sampaio > Assignee: Steven Hawkins > Priority: Major > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > > Hi, all. > First of all thanks in advance for your attention, and efforts on such a great product. > Since I haven't found any docs or examples regarding my current usage (please if this already exists or there's a better way of doing this, disregard this request and advice) here goes my suggestion: > It would be nice to have a way to gracefully update/fail per source, if a view that has Materialization enabled and target a multi-source source model, because things can get, messy if I have to create a view per source and Materialize each one and only then create a unified (UNION) view. > Using this approach also obligates me to implement custom insert/update/delete/based on the discriminator column. > Thanks again. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5928) Allow External and Internal materialization of multi-source to fail/update individually

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5928?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5928: --------------------------------------- So basically this is a request to automate the approach above - on a refresh instead of a full snapshot, walk through or in parallel issue the individual refreshes to update each source partition. That may be possible, but it will likely need some restrictions. Is this a situation where you've partitioned the view manually? Or is this a true multi-source scenario where you've added a materialized view directly above a source multi-source table and the discriminator column is still exposed? The latter case can be more complicated for us to deal with if we have to detect the multi-source nature through multiple layers of views. If that is the case, something that we've talked about before was allowing source tables to be marked as materialized which would further simplify this detection. > Allow External and Internal materialization of multi-source to fail/update individually > --------------------------------------------------------------------------------------- > > Key: TEIID-5928 > URL: https://issues.redhat.com/browse/TEIID-5928 > Project: Teiid > Issue Type: Enhancement > Components: Common > Affects Versions: 12.2.2 > Reporter: Rafael Sampaio > Assignee: Steven Hawkins > Priority: Major > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > > Hi, all. > First of all thanks in advance for your attention, and efforts on such a great product. > Since I haven't found any docs or examples regarding my current usage (please if this already exists or there's a better way of doing this, disregard this request and advice) here goes my suggestion: > It would be nice to have a way to gracefully update/fail per source, if a view that has Materialization enabled and target a multi-source source model, because things can get, messy if I have to create a view per source and Materialize each one and only then create a unified (UNION) view. > Using this approach also obligates me to implement custom insert/update/delete/based on the discriminator column. > Thanks again. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5928) Allow External and Internal materialization of multi-source to fail/update individually

by Rafael Sampaio (Jira)

[ https://issues.redhat.com/browse/TEIID-5928?page=com.atlassian.jira.plugi... ] Rafael Sampaio reopened TEIID-5928: ----------------------------------- Hello, Steven. Since I didn't get noticed of your previous comment, I was not able to answer you in proper time, so please accept my apologies. I have a multi-source externally materialized view whose update is controlled by Teiid. When the update runs and, for instance, one of the sources is not available, it fails completely, not by each source. So this update process, IMO, should run and fail, by source allowing the available data to be updated to its materialization. Hopefully I made myself clear. Kindly Rafael Sampaio > Allow External and Internal materialization of multi-source to fail/update individually > --------------------------------------------------------------------------------------- > > Key: TEIID-5928 > URL: https://issues.redhat.com/browse/TEIID-5928 > Project: Teiid > Issue Type: Enhancement > Components: Common > Affects Versions: 12.2.2 > Reporter: Rafael Sampaio > Assignee: Steven Hawkins > Priority: Major > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > > Hi, all. > First of all thanks in advance for your attention, and efforts on such a great product. > Since I haven't found any docs or examples regarding my current usage (please if this already exists or there's a better way of doing this, disregard this request and advice) here goes my suggestion: > It would be nice to have a way to gracefully update/fail per source, if a view that has Materialization enabled and target a multi-source source model, because things can get, messy if I have to create a view per source and Materialize each one and only then create a unified (UNION) view. > Using this approach also obligates me to implement custom insert/update/delete/based on the discriminator column. > Thanks again. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5944) Infinispan protobuf generation fails to validate name with "-" in them

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5944?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIID-5944: ------------------------------------- > So for Teiid this could be a documentation issue or we need to add logic to correct or throw an exception during import that generates protobuf. > Teiid is the one writing the protobuf in the case where it is not supplied from the source schema. Correction logic is added for materialization generation, but not for native DDL -> proto, so we could add more logic there or move the logic. The exception is little cryptic from Infinispan side as it fails the registration of the protobuf file. If we want to add any meaningful exception, we probably need to write some validation logic for protobuf file itself during the import. > Infinispan protobuf generation fails to validate name with "-" in them > ---------------------------------------------------------------------- > > Key: TEIID-5944 > URL: https://issues.redhat.com/browse/TEIID-5944 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When the name of the view contains like "mat-example_vix" the protobuf generation seems to succeed however the validation of it by the Infinispan seems to fail. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5944) Infinispan protobuf generation fails to validate name with "-" in them

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5944?page=com.atlassian.jira.plugi... ] Steven Hawkins edited comment on TEIID-5944 at 5/13/20 10:35 AM: ----------------------------------------------------------------- I'm not trying to capture all issues... It wasn't clear from the description/resolution what exactly was the behavior you were seeing with Teiid. I'm just trying to make sure there aren't any follow-ups that are being missed. > as one writing the Protobuf not according to spec it will fail Teiid is the one writing the protobuf in the case where it is not supplied from the source schema. As long as the infinispan exception makes it clear that the user needs to rename their source table, then I don't think we need to do anything. was (Author: shawkins): I'm not trying to capture all issues... It wasn't clear from the description/resolution what exactly was the behavior you were seeing with Teiid. I'm just trying to make sure there aren't any follow-ups that are being missed. > Infinispan protobuf generation fails to validate name with "-" in them > ---------------------------------------------------------------------- > > Key: TEIID-5944 > URL: https://issues.redhat.com/browse/TEIID-5944 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When the name of the view contains like "mat-example_vix" the protobuf generation seems to succeed however the validation of it by the Infinispan seems to fail. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5944) Infinispan protobuf generation fails to validate name with "-" in them

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5944?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5944: --------------------------------------- I'm not trying to capture all issues... It wasn't clear from the description/resolution what exactly was the behavior you were seeing with Teiid. I'm just trying to make sure there aren't any follow-ups that are being missed. > Infinispan protobuf generation fails to validate name with "-" in them > ---------------------------------------------------------------------- > > Key: TEIID-5944 > URL: https://issues.redhat.com/browse/TEIID-5944 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When the name of the view contains like "mat-example_vix" the protobuf generation seems to succeed however the validation of it by the Infinispan seems to fail. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5944) Infinispan protobuf generation fails to validate name with "-" in them

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5944?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIID-5944: ------------------------------------- Infinispan already throws an exception, IMO we do not really need to document this, as one writing the Protobuf not according to spec it will fail, we can not capture all issues. > Infinispan protobuf generation fails to validate name with "-" in them > ---------------------------------------------------------------------- > > Key: TEIID-5944 > URL: https://issues.redhat.com/browse/TEIID-5944 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When the name of the view contains like "mat-example_vix" the protobuf generation seems to succeed however the validation of it by the Infinispan seems to fail. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5944) Infinispan protobuf generation fails to validate name with "-" in them

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5944?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5944: --------------------------------------- So for Teiid this could be a documentation issue or we need to add logic to correct or throw an exception during import. > Infinispan protobuf generation fails to validate name with "-" in them > ---------------------------------------------------------------------- > > Key: TEIID-5944 > URL: https://issues.redhat.com/browse/TEIID-5944 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When the name of the view contains like "mat-example_vix" the protobuf generation seems to succeed however the validation of it by the Infinispan seems to fail. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5944) Infinispan protobuf generation fails to validate name with "-" in them

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5944?page=com.atlassian.jira.plugi... ] Steven Hawkins edited comment on TEIID-5944 at 5/13/20 10:21 AM: ----------------------------------------------------------------- So for Teiid this could be a documentation issue or we need to add logic to correct or throw an exception during import that generates protobuf. was (Author: shawkins): So for Teiid this could be a documentation issue or we need to add logic to correct or throw an exception during import. > Infinispan protobuf generation fails to validate name with "-" in them > ---------------------------------------------------------------------- > > Key: TEIID-5944 > URL: https://issues.redhat.com/browse/TEIID-5944 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > When the name of the view contains like "mat-example_vix" the protobuf generation seems to succeed however the validation of it by the Infinispan seems to fail. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 May 2020