December 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3875) Many info messages upon startup that start with: TEIID31173 Inherent

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3875?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3875: ------------------------------------ When I see the following message in the log: 18:43:23,705 INFO [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 1) TEIID31173 Inherent Multiple failures occurred during validation:The updatable view query has a FROM clause that is not a single table, pass-through processing will not be used for UPDATE/DELETE operations., The updatable view has no valid target for UPDATEs. against UPDATE has the following issues: VDB_Lineage.Model_Tables So the user expectation here is that the view can't be used for simple INSERT/UPDATE/DELETE, and that a trigger must be defined to specifically map the tables/columns. > Many info messages upon startup that start with: TEIID31173 Inherent > --------------------------------------------------------------------- > > Key: TEIID-3875 > URL: https://issues.jboss.org/browse/TEIID-3875 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.12.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Attachments: server.log > > > See that attached server log that shows a page full of the following similar message: > [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 1) TEIID31173 Inherent Multiple failures occurred .. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3875) Many info messages upon startup that start with: TEIID31173 Inherent

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3875?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3875: --------------------------------------- Yes, this comes from TEIID-3740. Before that we were not noting the underlying causes as to why the views were not inherently updatable. > Many info messages upon startup that start with: TEIID31173 Inherent > --------------------------------------------------------------------- > > Key: TEIID-3875 > URL: https://issues.jboss.org/browse/TEIID-3875 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.12.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Attachments: server.log > > > See that attached server log that shows a page full of the following similar message: > [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 1) TEIID31173 Inherent Multiple failures occurred .. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3873) Need 8.x Release PDF documentation

by Surendhar T (JIRA)

[ https://issues.jboss.org/browse/TEIID-3873?page=com.atlassian.jira.plugin... ] Surendhar T commented on TEIID-3873: ------------------------------------ Thanks a lot Ramesh & Steven Regards, Surendhar T > Need 8.x Release PDF documentation > ---------------------------------- > > Key: TEIID-3873 > URL: https://issues.jboss.org/browse/TEIID-3873 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Surendhar T > Assignee: Steven Hawkins > Priority: Blocker > Labels: release_notes > > Need 8.x Release PDF documentation > Reference Guide > Developer's Guide > Client Developer's Guide > Admin Guide > Caching Guide > Quick Start > Security Guide > API Docs -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3873) Need 8.x Release PDF documentation

by Surendhar T (JIRA)

[ https://issues.jboss.org/browse/TEIID-3873?page=com.atlassian.jira.plugin... ] Surendhar T edited comment on TEIID-3873 at 12/18/15 12:04 AM: --------------------------------------------------------------- Thanks a lot Ramesh & Steven, I exported as pdf. Regards, Surendhar T was (Author: surendhar.1): Thanks a lot Ramesh & Steven Regards, Surendhar T > Need 8.x Release PDF documentation > ---------------------------------- > > Key: TEIID-3873 > URL: https://issues.jboss.org/browse/TEIID-3873 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Surendhar T > Assignee: Steven Hawkins > Priority: Blocker > Labels: release_notes > > Need 8.x Release PDF documentation > Reference Guide > Developer's Guide > Client Developer's Guide > Admin Guide > Caching Guide > Quick Start > Security Guide > API Docs -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3725) In the JDG translators, enable named cache swapping so that materialization can be supported

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3725?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3725: ------------------------------- Attachment: (was: server.log) > In the JDG translators, enable named cache swapping so that materialization can be supported > -------------------------------------------------------------------------------------------- > > Key: TEIID-3725 > URL: https://issues.jboss.org/browse/TEIID-3725 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Van Halbert > Assignee: Van Halbert > > The JDG translators, that in order to support materialization, will need to enable the named cache that's referenced by the connection, to be swapped. This is due to JDG doesn't currently support renaming a cache (i.e., like table rename in JDBC). And because of that, it limits how the cache can be refreshed (don't want to clear it before re-loading). > Ideas are: > 1. configure translator with the 2 cache names to use (a) initial cache to read from and (b) the staging cache to use > perform materialize load > call SYSADMIN.setProperty to trigger the swapping of the cache names > 2 ??? > Note: because there's no persistence in Teiid so that any cache name changes will outlive a server restart, when a restart occurs, the translator will read from the cache identified as the initial cache to read from. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3875) Many info messages upon startup that start with: TEIID31173 Inherent

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3875?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3875: ------------------------------- Attachment: server.log > Many info messages upon startup that start with: TEIID31173 Inherent > --------------------------------------------------------------------- > > Key: TEIID-3875 > URL: https://issues.jboss.org/browse/TEIID-3875 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.12.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Attachments: server.log > > > See that attached server log that shows a page full of the following similar message: > [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 1) TEIID31173 Inherent Multiple failures occurred .. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3875) Many info messages upon startup that start with: TEIID31173 Inherent

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3875?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3875: ------------------------------- Description: See that attached server log that shows a page full of the following similar message: [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 1) TEIID31173 Inherent Multiple failures occurred .. was: See that attached server log that shows a page full of the following similar message: [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 1) TEIID31173 Inherent .... > Many info messages upon startup that start with: TEIID31173 Inherent > --------------------------------------------------------------------- > > Key: TEIID-3875 > URL: https://issues.jboss.org/browse/TEIID-3875 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.12.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > > See that attached server log that shows a page full of the following similar message: > [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 1) TEIID31173 Inherent Multiple failures occurred .. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3725) In the JDG translators, enable named cache swapping so that materialization can be supported

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3725?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3725: ------------------------------- Attachment: server.log > In the JDG translators, enable named cache swapping so that materialization can be supported > -------------------------------------------------------------------------------------------- > > Key: TEIID-3725 > URL: https://issues.jboss.org/browse/TEIID-3725 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Van Halbert > Assignee: Van Halbert > Attachments: server.log > > > The JDG translators, that in order to support materialization, will need to enable the named cache that's referenced by the connection, to be swapped. This is due to JDG doesn't currently support renaming a cache (i.e., like table rename in JDBC). And because of that, it limits how the cache can be refreshed (don't want to clear it before re-loading). > Ideas are: > 1. configure translator with the 2 cache names to use (a) initial cache to read from and (b) the staging cache to use > perform materialize load > call SYSADMIN.setProperty to trigger the swapping of the cache names > 2 ??? > Note: because there's no persistence in Teiid so that any cache name changes will outlive a server restart, when a restart occurs, the translator will read from the cache identified as the initial cache to read from. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3875) Many info messages upon startup that start with: TEIID31173 Inherent

by Van Halbert (JIRA)

Van Halbert created TEIID-3875: ---------------------------------- Summary: Many info messages upon startup that start with: TEIID31173 Inherent Key: TEIID-3875 URL: https://issues.jboss.org/browse/TEIID-3875 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 8.12.2 Reporter: Van Halbert Assignee: Steven Hawkins See that attached server log that shows a page full of the following similar message: [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 1) TEIID31173 Inherent .... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3874) Invalid source query for subquery referencing a common table

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3874?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3874: --------------------------------- Fix Version/s: 8.7.2.6_2 > Invalid source query for subquery referencing a common table > ------------------------------------------------------------ > > Key: TEIID-3874 > URL: https://issues.jboss.org/browse/TEIID-3874 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.2.6_2, 8.12.3 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.7.2.6_2, 8.13, 8.12.4 > > Attachments: withclause.tar.gz > > > TeiidProcessingException when using a With Clause requiring semi-join optimization and having a cross-source with clause subquery. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2015