[JBoss JIRA] (TEIID-4734) Under some circumstances after restart Teiid Server does not update Materialized views anymore
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4734?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-4734:
--------------------------------
Git Pull Request: https://github.com/teiid/teiid/pull/889
> Under some circumstances after restart Teiid Server does not update Materialized views anymore
> ----------------------------------------------------------------------------------------------
>
> Key: TEIID-4734
> URL: https://issues.jboss.org/browse/TEIID-4734
> Project: Teiid
> Issue Type: Bug
> Components: Common
> Affects Versions: 9.1.2
> Environment: * Wildfly 10
> * MySQL 5.6.32
> * Teiid Server 9.1.2
> Reporter: Pedro Inácio
> Assignee: Ramesh Reddy
> Attachments: StatusTableAfterStart.csv, StatusTableAfterStop.csv
>
>
> Under some circumstances, start and stop the server several times at different points, some Materialized Views are not being updated by the server.
> It is observable that in status table some views are no longer updated. In server log are being printed lots of INFO lines.
> Waited more than 15 minutes and the server was not capable of recovering.
> See the _StatusTableAfterStop.csv_ file to observe the status table content after stopping the server.
> See the _StatusTableAfterStart.csv_ file to observe the status table content after approximately 15 minutes after restart.
> Check _server.log_ for the Teiid Server log.
> See that hundreds of lines similar to the following occur
> {panel:title=Server.log}
> 2017-01-31 13:06:34,597 INFO [org.teiid.COMMAND_LOG] (Teiid Timer0) JfGY9cInAbrb START USER COMMAND: startTime=2017-01-31 13:06:34.597 requestID=JfGY9cInAbrb.0 txID=null sessionID=JfGY9cInAbrb applicationName=internal principal=embedded-async vdbName=CountryServiceListVDB vdbVersion=1 sql=execute SYSADMIN.matViewStatus('NumberingPlan', 'numbering_plan')
> {panel}
> The server cannot continue to load materialized views.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4734) Under some circumstances after restart Teiid Server does not update Materialized views anymore
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4734?page=com.atlassian.jira.plugin... ]
Ramesh Reddy reassigned TEIID-4734:
-----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> Under some circumstances after restart Teiid Server does not update Materialized views anymore
> ----------------------------------------------------------------------------------------------
>
> Key: TEIID-4734
> URL: https://issues.jboss.org/browse/TEIID-4734
> Project: Teiid
> Issue Type: Bug
> Components: Common
> Affects Versions: 9.1.2
> Environment: * Wildfly 10
> * MySQL 5.6.32
> * Teiid Server 9.1.2
> Reporter: Pedro Inácio
> Assignee: Ramesh Reddy
> Attachments: StatusTableAfterStart.csv, StatusTableAfterStop.csv
>
>
> Under some circumstances, start and stop the server several times at different points, some Materialized Views are not being updated by the server.
> It is observable that in status table some views are no longer updated. In server log are being printed lots of INFO lines.
> Waited more than 15 minutes and the server was not capable of recovering.
> See the _StatusTableAfterStop.csv_ file to observe the status table content after stopping the server.
> See the _StatusTableAfterStart.csv_ file to observe the status table content after approximately 15 minutes after restart.
> Check _server.log_ for the Teiid Server log.
> See that hundreds of lines similar to the following occur
> {panel:title=Server.log}
> 2017-01-31 13:06:34,597 INFO [org.teiid.COMMAND_LOG] (Teiid Timer0) JfGY9cInAbrb START USER COMMAND: startTime=2017-01-31 13:06:34.597 requestID=JfGY9cInAbrb.0 txID=null sessionID=JfGY9cInAbrb applicationName=internal principal=embedded-async vdbName=CountryServiceListVDB vdbVersion=1 sql=execute SYSADMIN.matViewStatus('NumberingPlan', 'numbering_plan')
> {panel}
> The server cannot continue to load materialized views.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4627) High-level event handling
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIID-4627?page=com.atlassian.jira.plugin... ]
Barry LaFond reassigned TEIID-4627:
-----------------------------------
Assignee: Steven Hawkins (was: Barry LaFond)
> High-level event handling
> -------------------------
>
> Key: TEIID-4627
> URL: https://issues.jboss.org/browse/TEIID-4627
> Project: Teiid
> Issue Type: Enhancement
> Components: Grammar, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> We should look into high-level plugability of event handling at a row level. This could even be handled at the language level with new trigger semantics for source tables: create trigger on tbl on cdc (insert|update...) - which could potentially even specify the topic mapping other details. There is complexity for multi-source models here though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4627) High-level event handling
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIID-4627?page=com.atlassian.jira.plugin... ]
Barry LaFond updated TEIID-4627:
--------------------------------
Summary: High-level event handling (was: Add after-trigger feature for materialization)
> High-level event handling
> -------------------------
>
> Key: TEIID-4627
> URL: https://issues.jboss.org/browse/TEIID-4627
> Project: Teiid
> Issue Type: Enhancement
> Components: Grammar, Query Engine
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Fix For: 9.2
>
>
> We should look into high-level plugability of event handling at a row level. This could even be handled at the language level with new trigger semantics for source tables: create trigger on tbl on cdc (insert|update...) - which could potentially even specify the topic mapping other details. There is complexity for multi-source models here though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4627) Add after-trigger feature for materialization
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIID-4627?page=com.atlassian.jira.plugin... ]
Barry LaFond reassigned TEIID-4627:
-----------------------------------
Assignee: Barry LaFond (was: Steven Hawkins)
> Add after-trigger feature for materialization
> ---------------------------------------------
>
> Key: TEIID-4627
> URL: https://issues.jboss.org/browse/TEIID-4627
> Project: Teiid
> Issue Type: Enhancement
> Components: Grammar, Query Engine
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Fix For: 9.2
>
>
> We should look into high-level plugability of event handling at a row level. This could even be handled at the language level with new trigger semantics for source tables: create trigger on tbl on cdc (insert|update...) - which could potentially even specify the topic mapping other details. There is complexity for multi-source models here though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4627) Add after-trigger feature for materialization
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIID-4627?page=com.atlassian.jira.plugin... ]
Barry LaFond updated TEIID-4627:
--------------------------------
Summary: Add after-trigger feature for materialization (was: High-level event handling)
> Add after-trigger feature for materialization
> ---------------------------------------------
>
> Key: TEIID-4627
> URL: https://issues.jboss.org/browse/TEIID-4627
> Project: Teiid
> Issue Type: Enhancement
> Components: Grammar, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> We should look into high-level plugability of event handling at a row level. This could even be handled at the language level with new trigger semantics for source tables: create trigger on tbl on cdc (insert|update...) - which could potentially even specify the topic mapping other details. There is complexity for multi-source models here though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4730) Problem with Import VDB with Materialized View (external)
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4730?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4730:
-------------------------------------
Ok, if you agree, I will add a check and send pull for your review.
> Problem with Import VDB with Materialized View (external)
> ---------------------------------------------------------
>
> Key: TEIID-4730
> URL: https://issues.jboss.org/browse/TEIID-4730
> Project: Teiid
> Issue Type: Bug
> Components: Common
> Affects Versions: 9.1.2
> Environment: * Teiid 9.1.2
> * CentOs 7
> * WildFly 10
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Attachments: externalMaterializationOrderProblem-vdb.xml, numberingPlan-vdb.xml
>
>
> Having defined a VDB which contains a Model that has External Materialization, when importing this VDB into another that also uses External Materialization, Teiid Server is searching in the wrong place for the view status.
> Example:
> ..
> <import-vdb name="CountryServiceListVDB" version="1" import-data-policies="true"/>
> ...
> <model name="MyView" type="VIRTUAL">
> ...
> SELECT cns,
> country_code
> FROM NumberingPlan.numbering_plan;
> ....
> </metadata>
> </model>
> *NumberingPlan.numbering_plan is defined in the imported VDB, and is also Materialized.*
> *Warning in Logs: *
> 17:51:45,161 WARN [org.teiid.MATVIEWS] (Worker8_QueryProcessorQueue10653) n9M6de3y5xHM org.teiid.jdbc.TeiidSQLException: TEIID30328 Unable to evaluate (SELECT mvstatus('NumberingPlan', 'numbering_plan', Valid, LoadState, 'THROW_EXCEPTION') FROM (SELECT 1) AS x LEFT OUTER JOIN NumberingPlanMaterialized.status ON VDBName = 'ExternalMaterializationOrderProblem' AND VDBVersion = '1' AND SchemaName = 'NumberingPlan' AND Name = 'numbering_plan' LIMIT 2): TEIID30328 Unable to evaluate mvstatus('NumberingPlan', 'numbering_plan', Valid, LoadState, 'THROW_EXCEPTION'): TEIID30384 Error while evaluating function mvstatus
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4709) Enable JDG resource adapter to pass the username/password to HotRod Client
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4709?page=com.atlassian.jira.plugin... ]
Van Halbert edited comment on TEIID-4709 at 2/1/17 11:47 AM:
-------------------------------------------------------------
Initial testing scenarios of 8.12.x against JDG 6.6:
1) specifying username/password on RA, for the materialization use case
JDG config: swapped out the default hotrod-connector with the following:
{code}
<hotrod-connector socket-binding="hotrod" cache-container="clustered">
<topology-state-transfer lazy-retrieval="false" lock-timeout="1000" replication-timeout="5000"/>
<authentication security-realm="ApplicationRealm">
<sasl server-name="myhotrodserver" mechanisms="DIGEST-MD5" qop="auth" />
</authentication>
</hotrod-connector>
{code}
Teiid config:
The following are the new settings on the RA to configure
{code}
<config-property name="AuthServerName">
myhotrodserver
</config-property>
<config-property name="AuthApplicationRealm">
ApplicationRealm
</config-property>
<config-property name="AuthSASLMechanism">
DIGEST-MD5
</config-property>
<config-property name="AuthUserName">
teiidUser
</config-property>
<config-property name="AuthPassword">
redhat1!
</config-property>
<config-property name="AdminUserName">
teiidUser
</config-property>
<config-property name="AdminPassword">
redhat1!
</config-property>
{code}
- admin username/password is required
- the auth username/password is optional
confirmed this works with the upcoming changes.
was (Author: van.halbert):
Initial testing scenarios of 8.12.x against JDG 6.6:
1) specifying username/password on RA, for the materialization use case
JDG config: swapped out the default hotrod-connector with the following:
{code}
<hotrod-connector socket-binding="hotrod" cache-container="clustered">
<topology-state-transfer lazy-retrieval="false" lock-timeout="1000" replication-timeout="5000"/>
<authentication security-realm="ApplicationRealm">
<sasl server-name="myhotrodserver" mechanisms="DIGEST-MD5" qop="auth" />
</authentication>
</hotrod-connector>
{code}
Teiid config:
The following are the new settings on the RA to configure
{code}
<config-property name="AuthServerName">
myhotrodserver
</config-property>
<config-property name="AuthApplicationRealm">
ApplicationRealm
</config-property>
<config-property name="AuthSASLMechanism">
DIGEST-MD5
</config-property>
<config-property name="AuthUserName">
teiidUser
</config-property>
<config-property name="AuthPassword">
redhat1!
</config-property>
{code}
- the username/password have to be added to the JDG server
confirmed this works with the upcoming changes.
> Enable JDG resource adapter to pass the username/password to HotRod Client
> --------------------------------------------------------------------------
>
> Key: TEIID-4709
> URL: https://issues.jboss.org/browse/TEIID-4709
> Project: Teiid
> Issue Type: Feature Request
> Components: JDG Connector
> Affects Versions: 9.3
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 9.3, 8.12.9.6_3
>
>
> Enable the JDG resource adapter to pass the username/password to the JDG hot rod client.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4709) Enable JDG resource adapter to pass the username/password to HotRod Client
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4709?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-4709:
------------------------------------
On small challenge when using a VDB that doesn't define the source metadata, but expects it to be derived from the translator. The metadata processor requires the connection in order to get the schema from the cache. And that is done before a user is asking for a query. So it means an "admin" user will have to be defined in order to derive the metadata. So additional properties will need to configure "admin". So the following will be the scenarios:
- always require the "admin" and password, which will need the _schema_manager role in JDG
- optional provide the authUsername/authPassword, when not provided, the logic will be pulling the Subject to use to create the RemoteCacheManager.
JDG RemoteCacheManager has 2 options for setting the user when its created:
1) username/password
2) Subject
> Enable JDG resource adapter to pass the username/password to HotRod Client
> --------------------------------------------------------------------------
>
> Key: TEIID-4709
> URL: https://issues.jboss.org/browse/TEIID-4709
> Project: Teiid
> Issue Type: Feature Request
> Components: JDG Connector
> Affects Versions: 9.3
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 9.3, 8.12.9.6_3
>
>
> Enable the JDG resource adapter to pass the username/password to the JDG hot rod client.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months