[JBoss JIRA] (TEIID-4730) Problem with Import VDB with Materialized View (external)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4730?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4730:
---------------------------------------
> So, I can settle for option (1).
So you want to warn, and then also prevent the materialization logic from engaging in the planner correct? It is pretty straight-forward to check if a schema comes from an imported vdb.
> 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 10:15 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>
{code}
- the username/password have to be added to the JDG server
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:
{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 edited comment on TEIID-4709 at 2/1/17 10:15 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:
{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.
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:
<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>
Teiid config:
The following are the new settings on the RA to configure
<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>
- 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:
------------------------------------
Initial testing scenarios of 8.12.x against JDG 6.6:
1) specifying username/password on RA, for the materialization use case
JDG config:
<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>
Teiid config:
The following are the new settings on the RA to configure
<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>
- 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-4727) Aggregation is performed incorrectly for JOIN queries
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4727?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4727:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1418075, https://bugzilla.redhat.com/show_bug.cgi?id=1418076
Bugzilla Update: Perform
> Aggregation is performed incorrectly for JOIN queries
> -----------------------------------------------------
>
> Key: TEIID-4727
> URL: https://issues.jboss.org/browse/TEIID-4727
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.0.3
> Environment: teiid-9.0.3 on WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 9.0.6, 9.2, 9.1.3
>
>
> Aggregation is performed incorrectly for JOIN queries, like this
> {code:sql}
> select count(v2.b) from views.v1 right join views.v2 on true group by v1.b;
> select count(v2.b) from views.v1 join (call procs.pr()) v2 on true group by v1.b;
> select count(v2.b) from views.v1 left join (call procs.pr()) v2 on true group by v1.b;
> select count(v2.b) from views.v1 right join (call procs.pr()) v2 on true group by v1.b;
> {code}
> showing as a result:
> {code}
> 1
> 1
> 1
> {code}
> though these ones work correctly:
> {code:sql}
> select count(v2.b) from views.v1 join views.v2 on true group by v1.b;
> select count(v2.b) from views.v1 left join views.v2 on true group by v1.b;
> {code}
> showing
> {code}
> 1
> 1
> 2
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4713) HANA translator evaluates > as >=
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIID-4713?page=com.atlassian.jira.plugin... ]
Lucie Fabrikova resolved TEIID-4713.
------------------------------------
Resolution: Rejected
> HANA translator evaluates > as >=
> ---------------------------------
>
> Key: TEIID-4713
> URL: https://issues.jboss.org/browse/TEIID-4713
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.2
> Reporter: Lucie Fabrikova
> Assignee: Ted Jones
> Fix For: 9.2
>
> Attachments: sap-hana_crud-vdb.xml
>
>
> HANA translator evaluates > as >= in following query:
> DELETE FROM SmallA WHERE FloatNum > 11814.4
> I observed rows where FloatNum = 11814.4 were also deleted.
> Next observations:
> - query DELETE FROM SmallA WHERE FloatNum = 11814.4 deleted no rows.
> - <= was evaluated as <
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4713) HANA translator evaluates > as >=
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIID-4713?page=com.atlassian.jira.plugin... ]
Lucie Fabrikova commented on TEIID-4713:
----------------------------------------
I re-tested query both directly against Hana and via sap hana translator, and in both cases both > and >= worked as expected (ie > didn't delete also = rows).
I am sorry, there seems to be problem only in our test data...
> HANA translator evaluates > as >=
> ---------------------------------
>
> Key: TEIID-4713
> URL: https://issues.jboss.org/browse/TEIID-4713
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.2
> Reporter: Lucie Fabrikova
> Assignee: Ted Jones
> Fix For: 9.2
>
> Attachments: sap-hana_crud-vdb.xml
>
>
> HANA translator evaluates > as >= in following query:
> DELETE FROM SmallA WHERE FloatNum > 11814.4
> I observed rows where FloatNum = 11814.4 were also deleted.
> Next observations:
> - query DELETE FROM SmallA WHERE FloatNum = 11814.4 deleted no rows.
> - <= was evaluated as <
--
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 Pedro Inácio (JIRA)
[ https://issues.jboss.org/browse/TEIID-4730?page=com.atlassian.jira.plugin... ]
Pedro Inácio commented on TEIID-4730:
-------------------------------------
[~rareddy] Changing in _numberingPlan-vdb.xml_ to _teiid_rel:MATVIEW_SHARE_SCOPE" '*SCHEMA*'_ solves the problem.
> 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-4713) HANA translator evaluates > as >=
by Juraj Duráni (JIRA)
[ https://issues.jboss.org/browse/TEIID-4713?page=com.atlassian.jira.plugin... ]
Juraj Duráni commented on TEIID-4713:
-------------------------------------
[~shawkins] In this case I think it's not a problem. FloatNum is of type float, i.e. floating point number. So _FloatNum = 11814.4_ might not be evaluated to true for any value even if respective value seems to be in the table.
We will check this again and let you know.
> HANA translator evaluates > as >=
> ---------------------------------
>
> Key: TEIID-4713
> URL: https://issues.jboss.org/browse/TEIID-4713
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.2
> Reporter: Lucie Fabrikova
> Assignee: Ted Jones
> Fix For: 9.2
>
> Attachments: sap-hana_crud-vdb.xml
>
>
> HANA translator evaluates > as >= in following query:
> DELETE FROM SmallA WHERE FloatNum > 11814.4
> I observed rows where FloatNum = 11814.4 were also deleted.
> Next observations:
> - query DELETE FROM SmallA WHERE FloatNum = 11814.4 deleted no rows.
> - <= was evaluated as <
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4627) High-level event handling
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4627?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4627:
---------------------------------------
A future is now being returned if work is started as a result of the call. If it's successful that represents a "best effort" completion as failures of any individual trigger will simply be logged. If there is a failure that would represent a component or other unexpected exception and would be an "in doubt" situation, where you are not guaranteed success even if the event were replayed.
> 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