February 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3337) Netty exception related to close logged at warn level

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3337?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3337. ----------------------------------- Resolution: Done Addressed any message with close in it. > Netty exception related to close logged at warn level > ----------------------------------------------------- > > Key: TEIID-3337 > URL: https://issues.jboss.org/browse/TEIID-3337 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > An exception with the message "An existing connection was forcibly closed by the remote host" is still being logged at a warning level -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3342) Defining materialization in dynamic vdb when no staging table can be used, doesn't work

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3342?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3342: ------------------------------------- Assignee: (was: Steven Hawkins) The two possibilities here are to say that infinispan only supports incremental refresh or we would have to alter the logic for the full refresh strategy such that the swap was handled in the engine via some status from the source. > Defining materialization in dynamic vdb when no staging table can be used, doesn't work > --------------------------------------------------------------------------------------- > > Key: TEIID-3342 > URL: https://issues.jboss.org/browse/TEIID-3342 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > > When using JDG as a materialization target, there is not an option to use a staging table (because JDG doesn't support cache renaming). So, tried these 2 options (but didn't work) when defining materialization in a dynamic VDB: > - no staging table defined at all > - setting staging table to the same as the target table > Would like to change it so that a staging table isn't required. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3342) Defining materialization in dynamic vdb when no staging table can be used, doesn't work

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3342?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3342: ------------------------------- Description: When using JDG as a materialization target, there is not an option to use a staging table (because JDG doesn't support cache renaming). So, tried these 2 options (but didn't work) when defining materialization in a dynamic VDB: - no staging table defined at all - setting staging table to the same as the target table Would like to change it so that a staging table isn't required. was: When using JDG as a materialization target, there is not an option to use a staging table (because JDG doesn't support cache renaming). So, tried these 2 options (but didn't work): - no staging table defined at all - setting staging table to the same as the target table Would like to change it so that a staging table isn't required. > Defining materialization in dynamic vdb when no staging table can be used, doesn't work > --------------------------------------------------------------------------------------- > > Key: TEIID-3342 > URL: https://issues.jboss.org/browse/TEIID-3342 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > > When using JDG as a materialization target, there is not an option to use a staging table (because JDG doesn't support cache renaming). So, tried these 2 options (but didn't work) when defining materialization in a dynamic VDB: > - no staging table defined at all > - setting staging table to the same as the target table > Would like to change it so that a staging table isn't required. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3342) Defining materialization in dynamic vdb when no staging table can be used, doesn't work

by Van Halbert (JIRA)

Van Halbert created TEIID-3342: ---------------------------------- Summary: Defining materialization in dynamic vdb when no staging table can be used, doesn't work Key: TEIID-3342 URL: https://issues.jboss.org/browse/TEIID-3342 Project: Teiid Issue Type: Enhancement Components: Server Reporter: Van Halbert Assignee: Steven Hawkins When using JDG as a materialization target, there is not an option to use a staging table (because JDG doesn't support cache renaming). So, tried these 2 options (but didn't work): - no staging table defined at all - setting staging table to the same as the target table Would like to change it so that a staging table isn't required. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3320) Use alternative implementation to Spring in CXF

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3320?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3320. --------------------------------- Resolution: Won't Fix > Use alternative implementation to Spring in CXF > ----------------------------------------------- > > Key: TEIID-3320 > URL: https://issues.jboss.org/browse/TEIID-3320 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Van Halbert > Fix For: Open To Community > > > Use an alternative implementation to Spring in CXF -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3320) Use alternative implementation to Spring in CXF

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3320?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3320: ------------------------------------ I would vote to close this issue. And if/when there is a need to use an alternative, that a specific alternative would be known at that time, driving the need for a change. Instead of just waiting around for something to come around. > Use alternative implementation to Spring in CXF > ----------------------------------------------- > > Key: TEIID-3320 > URL: https://issues.jboss.org/browse/TEIID-3320 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Van Halbert > Fix For: Open To Community > > > Use an alternative implementation to Spring in CXF -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3339) Adding the multisource column does not work with variadic procedures

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3339?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3339. ----------------------------------- Resolution: Done Relaxed the validation to allow parameters after a variadic one - if they are all optional. However this means that to named parameters must be used if the source is to be specified. > Adding the multisource column does not work with variadic procedures > -------------------------------------------------------------------- > > Key: TEIID-3339 > URL: https://issues.jboss.org/browse/TEIID-3339 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > Adding the multi-source column as the last parameter to a variadic procedure results in a validation exception. Options to resolve this include adding the parameter as the second to last, not allowing the procedure to have a multi-source parameter, or choosing a different paradigm - such as call procname_source... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3320) Use alternative implementation to Spring in CXF

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3320?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3320: ------------------------------------- Issue Type: Quality Risk (was: Enhancement) Fix Version/s: Open To Community Assignee: (was: Ramesh Reddy) Moving to just an open to community issue, to see if we can make traction later. > Use alternative implementation to Spring in CXF > ----------------------------------------------- > > Key: TEIID-3320 > URL: https://issues.jboss.org/browse/TEIID-3320 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Van Halbert > Fix For: Open To Community > > > Use an alternative implementation to Spring in CXF -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3341) Metadata load failure between retries of multi-source models

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3341?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3341. ----------------------------------- Resolution: Done Resetting the metadatafactory after each load and making embedded exception handling the same as the server. > Metadata load failure between retries of multi-source models > ------------------------------------------------------------ > > Key: TEIID-3341 > URL: https://issues.jboss.org/browse/TEIID-3341 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.7 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.10 > > > The code will attempt to load from each source until one is successful. There is an issue however that the metadatafactory is not being reset, so the next load attempt will be against existing metadata. At the debug level this will be seen as "Failed to get metadata, trying next source." > From the forum post - If the metadata factories are chained like "NATIVE, DDL", with invalid DDL, a duplicate table issue is seen instead. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3341) Metadata load failure between retries of multi-source models

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3341?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3341: ---------------------------------- Description: The code will attempt to load from each source until one is successful. There is an issue however that the metadatafactory is not being reset, so the next load attempt will be against existing metadata. At the debug level this will be seen as "Failed to get metadata, trying next source." >From the forum post - If the metadata factories are chained like "NATIVE, DDL", with invalid DDL, a duplicate table issue is seen instead. was: The code will attempt to load from each source until one is successful. There is an issue however that the metadatafactory is not being reset, so the next load attempt will be against existing metadata. Hence the question about "Failed to get metadata, trying next source." It happens to be, if the metadata factories are chained like "NATIVE, DDL", in that case even the DDL schema must be valid, so that Teiid does not retry to load metadata from next source in line. Affects Version/s: 7.7 > Metadata load failure between retries of multi-source models > ------------------------------------------------------------ > > Key: TEIID-3341 > URL: https://issues.jboss.org/browse/TEIID-3341 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.7 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.10 > > > The code will attempt to load from each source until one is successful. There is an issue however that the metadatafactory is not being reset, so the next load attempt will be against existing metadata. At the debug level this will be seen as "Failed to get metadata, trying next source." > From the forum post - If the metadata factories are chained like "NATIVE, DDL", with invalid DDL, a duplicate table issue is seen instead. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2015