June 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4957) Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4957?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4957: ------------------------------------- To make this work, I think we need to replace whole caching with overlay stuff as in updating web.xml in war files. Looks like WildFly reads the configuration from master node. Right now they are applied after deployment based on disk contents, needs to be in the configuration. > Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-4957 > URL: https://issues.jboss.org/browse/TEIID-4957 > Project: Teiid > Issue Type: Bug > Components: VDB > Affects Versions: 8.12.10.6_3 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Fix For: 10.0 > > > After deploying a VDB to a managed server group, set the Connection type to anything but the default of By_Version, so None or Any. Now restart the server and you'll see the Connection type is reset to the default. > What I see is that when the change is made a vdb.xml with that new connection-type is written to the /DVserverhome/domain/servers/server-two/data/teiid-data/SampleVDB_1 folder, this folder is deleted upon a restart though so the change is not kept. > This only happens in Domain mode, running in Standalone mode saves the change because the teiid-data is not deleted on a restart. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4957) Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4957?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4957: ------------------------------------- Fix Version/s: 10.0 Assignee: Ramesh Reddy (was: Barry LaFond) > Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-4957 > URL: https://issues.jboss.org/browse/TEIID-4957 > Project: Teiid > Issue Type: Bug > Components: VDB > Affects Versions: 8.12.10.6_3 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Fix For: 10.0 > > > After deploying a VDB to a managed server group, set the Connection type to anything but the default of By_Version, so None or Any. Now restart the server and you'll see the Connection type is reset to the default. > What I see is that when the change is made a vdb.xml with that new connection-type is written to the /DVserverhome/domain/servers/server-two/data/teiid-data/SampleVDB_1 folder, this folder is deleted upon a restart though so the change is not kept. > This only happens in Domain mode, running in Standalone mode saves the change because the teiid-data is not deleted on a restart. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4847) Google translator ClientLogin not supported

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4847?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4847: ------------------------------------------------ David Le Sage <dlesage(a)redhat.com> changed the Status of [bug 1439668|https://bugzilla.redhat.com/show_bug.cgi?id=1439668] from ASSIGNED to ON_QA > Google translator ClientLogin not supported > ------------------------------------------- > > Key: TEIID-4847 > URL: https://issues.jboss.org/browse/TEIID-4847 > Project: Teiid > Issue Type: Bug > Components: Documentation > Affects Versions: 9.2 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Fix For: 9.3 > > > Documentation for both DV 6.3 [1] and teiid 9 [2] says "Authentication to your google account may be done in two ways. ClientLogin (requires login and password) or OAuth...", however only OAuth is supported already - SpreadsheetConnectionImpl.java throws exception for method other than OAuth with message "provide_auth=Only OAuth2 is allowed for the AuthMethod." > [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_data_virtuali... > [2] https://teiid.gitbooks.io/documents/content/admin/Google_Spreadsheet_Data... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4962) 9.3 teiid-standalone-mode-install.cli gives an error on startup

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4962?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4962. --------------------------------- Fix Version/s: 9.2.5 10.0 9.3.1 Assignee: Ramesh Reddy (was: Steven Hawkins) Resolution: Done > 9.3 teiid-standalone-mode-install.cli gives an error on startup > --------------------------------------------------------------- > > Key: TEIID-4962 > URL: https://issues.jboss.org/browse/TEIID-4962 > Project: Teiid > Issue Type: Bug > Reporter: Mike Higgins > Assignee: Ramesh Reddy > Fix For: 9.2.5, 10.0, 9.3.1 > > > Using the commands from the standalone cli file, the wildfly server gives an error that it cannot load the module org.jboss.teiid.translator.hbase. In the other cli files, this translator module has been renamed to phoenix. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4962) 9.3 teiid-standalone-mode-install.cli gives an error on startup

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4962?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4962: -------------------------------- Component/s: Build/Kits > 9.3 teiid-standalone-mode-install.cli gives an error on startup > --------------------------------------------------------------- > > Key: TEIID-4962 > URL: https://issues.jboss.org/browse/TEIID-4962 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Reporter: Mike Higgins > Assignee: Ramesh Reddy > Fix For: 10.0, 9.3.1, 9.2.5 > > > Using the commands from the standalone cli file, the wildfly server gives an error that it cannot load the module org.jboss.teiid.translator.hbase. In the other cli files, this translator module has been renamed to phoenix. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4959) VDB Resource usage restriction options

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4959?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4959. ----------------------------------- Resolution: Duplicate Issue See TEIID-4557 for a discussion of what was added. > VDB Resource usage restriction options > -------------------------------------- > > Key: TEIID-4959 > URL: https://issues.jboss.org/browse/TEIID-4959 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.12.10.6_3 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > It would be very useful to have configurable options to limit resource usage (CPU, RAM, disk...) by user, query or connection. This would prevent any one user or query from consuming all/disproportionate system resources. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4962) 9.3 teiid-standalone-mode-install.cli gives an error on startup

by Mike Higgins (JIRA)

Mike Higgins created TEIID-4962: ----------------------------------- Summary: 9.3 teiid-standalone-mode-install.cli gives an error on startup Key: TEIID-4962 URL: https://issues.jboss.org/browse/TEIID-4962 Project: Teiid Issue Type: Bug Reporter: Mike Higgins Assignee: Steven Hawkins Using the commands from the standalone cli file, the wildfly server gives an error that it cannot load the module org.jboss.teiid.translator.hbase. In the other cli files, this translator module has been renamed to phoenix. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4961) External Materialized View With State Loaded but 0 Cardinality

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4961?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4961: ------------------------------------- This is no different than TEIID-4960, when you're ON_ERROR_ACTION flag set to ignore, this will be is the result. > External Materialized View With State Loaded but 0 Cardinality > -------------------------------------------------------------- > > Key: TEIID-4961 > URL: https://issues.jboss.org/browse/TEIID-4961 > Project: Teiid > Issue Type: Bug > Affects Versions: 9.3 > Environment: * Teiid 9.3.0 > * MySQL 5.7.18 > * Wildfly 10 > Reporter: Pedro Inácio > Assignee: Steven Hawkins > Attachments: server.log > > > *Scenario*: Having several views that depend on others (ex: V1-> V2->V3, where V3 depends on V2 and V2 depends on V1), all with external materialization. > Although all views LoadState is *LOADED *even after failures due to the dependent ones being loaded, in the end some views have zero (0) of cardinality, when there are actually records. Running the queries by hand return records. > Log attached. > Example: > {panel} > 2017-06-14 17:14:39,521 INFO [org.teiid.MATVIEWS] (Worker63_QueryProcessorQueue19799) WDpoyHmXlkvS Materialization of view VodafoneNlBaseSource.vodafone_nl_base_source completed. Rows updated = 0 Load Number = 1 > {panel} > After forcing the view update: > {panel} > 2017-06-14 17:23:38,042 INFO [org.teiid.MATVIEWS] (Worker65_QueryProcessorQueue27597) +IbRaNRtrZ1K Materialization of view VodafoneNlBaseSource.vodafone_nl_base_source completed. Rows updated = 1816 Load Number = 2 > {panel} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4960) Problems when using External Materialized Views

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4960?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4960: ------------------------------------- >What you are affirming is that Teiid does not support a view that depends on another view that is Materialized (Internal or external)? Because there is no coordination logic. I would think this works fine if one view is already loaded, otherwise, if both views in loading stage and one depends on another, we are seeing above exception. Now, one could argue with default value "teiid_rel:MATVIEW_ONERROR_ACTION" to "WAIT", the dependency chain gets satisfied, but we are not seeing that. Maybe we can use this JIRA to fix the behavior. I understand your need for the materialized views, I am only questioning the need to depend on one mat view over other. The second one could be just a simple view. > Problems when using External Materialized Views > ----------------------------------------------- > > Key: TEIID-4960 > URL: https://issues.jboss.org/browse/TEIID-4960 > Project: Teiid > Issue Type: Bug > Affects Versions: 9.3 > Environment: * Teiid Server 9.3.0 > * Wildfly 10 > * Mysql 5.7.18 > Reporter: Pedro Inácio > Assignee: Steven Hawkins > Attachments: server.log > > > The following problem occurs when, apparently, we have two views where one depend on another, and also we use External Materialization. > The dependent view is never updated due to a "Transaction already associated with request." exception. > Logs attached. > The error: > {panel:title=The exception in logs} > 2017-06-14 13:51:51,753 WARN [org.teiid.MATVIEWS] (Worker14_QueryProcessorQueue365) Hlbq3jmDWXNl org.teiid.jdbc.TeiidSQLException: TEIID30328 Unable to evaluate mvstatus('NumberingPlan', 'numbering_plan'): TEIID30384 Error while evaluating function mvstatus > 2017-06-14 13:52:51,803 INFO [org.teiid.MATVIEWS] (Worker14_QueryProcessorQueue368) XAtcLA8RBrLm Materialization of view NumberingPlanRaw.numbering_plan_raw started. > 2017-06-14 13:52:51,867 ERROR [org.teiid.PROCESSOR] (Worker14_QueryProcessorQueue372) XAtcLA8RBrLm TEIID30019 Unexpected exception for request XAtcLA8RBrLm.-2514910280603581440: java.lang.AssertionError: Transaction already associated with request. > {panel} > The VDB: > {code:xml} > <model name="MnomMaterialized" type="PHYSICAL"> > <property name="importer.useFullSchemaName" value="false"/> > <property name="query-timeout" value="600000"/> > <source name="MnomMaterializedView" translator-name="mysql-override" connection-jndi-name="java:/mnomDs"/> > </model> > > <model name="NumberingPlanCsvData"> > <source name="numberingPlanCsv-connector" translator-name="file" connection-jndi-name="java:/numberingPlanCsvDs"/> > </model> > <model name="NumberingPlan" type="VIRTUAL"> > <metadata type="DDL"><![CDATA[ > CREATE VIEW numbering_plan ( > id integer PRIMARY KEY, > global_title varchar(20) > ) > OPTIONS( > MATERIALIZED 'TRUE', > UPDATABLE 'TRUE', > MATERIALIZED_TABLE 'MnomMaterialized.numbering_plan_cache', > "teiid_rel:MATVIEW_TTL" 86400000, > "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true', > "teiid_rel:MATVIEW_LOADNUMBER_COLUMN" 'LoadNumber', > "teiid_rel:MATVIEW_STATUS_TABLE" 'MnomMaterialized.status' > ) > AS > SELECT ROW_NUMBER() OVER (ORDER BY cns) as id, > cns > FROM (EXEC NumberingPlanCsvData.getTextFiles('NumberingPlan.csv')) AS f, > TEXTTABLE(f.file COLUMNS cns string DELIMITER ';' SKIP 1) AS A; > > ]]> > </metadata> > </model> > > <model name="NumberingPlanRaw" type="VIRTUAL"> > <metadata type="DDL"> > <![CDATA[ > CREATE VIEW numbering_plan_raw ( > id integer PRIMARY KEY, > global_title varchar(20) > ) > OPTIONS( > MATERIALIZED 'TRUE', > UPDATABLE 'FALSE', > MATERIALIZED_TABLE 'MnomMaterialized.numbering_plan_raw_cache', > "teiid_rel:MATVIEW_TTL" 86400000, > "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true', > "teiid_rel:MATVIEW_LOADNUMBER_COLUMN" 'LoadNumber', > "teiid_rel:MATVIEW_STATUS_TABLE" 'MnomMaterialized.status' > ) > AS > SELECT ROW_NUMBER() OVER (ORDER BY network) as id, > global_title > FROM numbering_plan np; > > ]]> > </metadata> > </model> > </model> > {code} > The Materialized table: > {code:sql} > CREATE TABLE status ( > VDBName VARCHAR(50) NOT NULL, > VDBVersion VARCHAR(50) NOT NULL, > SchemaName VARCHAR(50) NOT NULL, > Name VARCHAR(256) NOT NULL, > TargetSchemaName VARCHAR(50), > TargetName VARCHAR(256) NOT NULL, > Valid BOOLEAN NOT NULL, > LoadState VARCHAR(25) NOT NULL, > Cardinality BIGINT, > Updated TIMESTAMP NOT NULL, > LoadNumber BIGINT NOT NULL, > NodeName varchar(25) not null, > StaleCount BIGINT, > PRIMARY KEY (VDBName , VDBVersion , SchemaName , Name) > ); > CREATE TABLE numbering_plan_cache ( > id integer, > global_title varchar(20), > LoadNumber BIGINT, > PRIMARY KEY(id) > ); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4960) Problems when using External Materialized Views

by Pedro Inácio (JIRA)

[ https://issues.jboss.org/browse/TEIID-4960?page=com.atlassian.jira.plugin... ] Pedro Inácio commented on TEIID-4960: ------------------------------------- What you are affirming is that Teiid does not support a view that depends on another view that is Materialized (Internal or external)? We are using external materialization due to the high volume of data and to avoid parsing over and over again the same CSV files. >From my point of view materialization is only a way to improve performance. > Problems when using External Materialized Views > ----------------------------------------------- > > Key: TEIID-4960 > URL: https://issues.jboss.org/browse/TEIID-4960 > Project: Teiid > Issue Type: Bug > Affects Versions: 9.3 > Environment: * Teiid Server 9.3.0 > * Wildfly 10 > * Mysql 5.7.18 > Reporter: Pedro Inácio > Assignee: Steven Hawkins > Attachments: server.log > > > The following problem occurs when, apparently, we have two views where one depend on another, and also we use External Materialization. > The dependent view is never updated due to a "Transaction already associated with request." exception. > Logs attached. > The error: > {panel:title=The exception in logs} > 2017-06-14 13:51:51,753 WARN [org.teiid.MATVIEWS] (Worker14_QueryProcessorQueue365) Hlbq3jmDWXNl org.teiid.jdbc.TeiidSQLException: TEIID30328 Unable to evaluate mvstatus('NumberingPlan', 'numbering_plan'): TEIID30384 Error while evaluating function mvstatus > 2017-06-14 13:52:51,803 INFO [org.teiid.MATVIEWS] (Worker14_QueryProcessorQueue368) XAtcLA8RBrLm Materialization of view NumberingPlanRaw.numbering_plan_raw started. > 2017-06-14 13:52:51,867 ERROR [org.teiid.PROCESSOR] (Worker14_QueryProcessorQueue372) XAtcLA8RBrLm TEIID30019 Unexpected exception for request XAtcLA8RBrLm.-2514910280603581440: java.lang.AssertionError: Transaction already associated with request. > {panel} > The VDB: > {code:xml} > <model name="MnomMaterialized" type="PHYSICAL"> > <property name="importer.useFullSchemaName" value="false"/> > <property name="query-timeout" value="600000"/> > <source name="MnomMaterializedView" translator-name="mysql-override" connection-jndi-name="java:/mnomDs"/> > </model> > > <model name="NumberingPlanCsvData"> > <source name="numberingPlanCsv-connector" translator-name="file" connection-jndi-name="java:/numberingPlanCsvDs"/> > </model> > <model name="NumberingPlan" type="VIRTUAL"> > <metadata type="DDL"><![CDATA[ > CREATE VIEW numbering_plan ( > id integer PRIMARY KEY, > global_title varchar(20) > ) > OPTIONS( > MATERIALIZED 'TRUE', > UPDATABLE 'TRUE', > MATERIALIZED_TABLE 'MnomMaterialized.numbering_plan_cache', > "teiid_rel:MATVIEW_TTL" 86400000, > "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true', > "teiid_rel:MATVIEW_LOADNUMBER_COLUMN" 'LoadNumber', > "teiid_rel:MATVIEW_STATUS_TABLE" 'MnomMaterialized.status' > ) > AS > SELECT ROW_NUMBER() OVER (ORDER BY cns) as id, > cns > FROM (EXEC NumberingPlanCsvData.getTextFiles('NumberingPlan.csv')) AS f, > TEXTTABLE(f.file COLUMNS cns string DELIMITER ';' SKIP 1) AS A; > > ]]> > </metadata> > </model> > > <model name="NumberingPlanRaw" type="VIRTUAL"> > <metadata type="DDL"> > <![CDATA[ > CREATE VIEW numbering_plan_raw ( > id integer PRIMARY KEY, > global_title varchar(20) > ) > OPTIONS( > MATERIALIZED 'TRUE', > UPDATABLE 'FALSE', > MATERIALIZED_TABLE 'MnomMaterialized.numbering_plan_raw_cache', > "teiid_rel:MATVIEW_TTL" 86400000, > "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true', > "teiid_rel:MATVIEW_LOADNUMBER_COLUMN" 'LoadNumber', > "teiid_rel:MATVIEW_STATUS_TABLE" 'MnomMaterialized.status' > ) > AS > SELECT ROW_NUMBER() OVER (ORDER BY network) as id, > global_title > FROM numbering_plan np; > > ]]> > </metadata> > </model> > </model> > {code} > The Materialized table: > {code:sql} > CREATE TABLE status ( > VDBName VARCHAR(50) NOT NULL, > VDBVersion VARCHAR(50) NOT NULL, > SchemaName VARCHAR(50) NOT NULL, > Name VARCHAR(256) NOT NULL, > TargetSchemaName VARCHAR(50), > TargetName VARCHAR(256) NOT NULL, > Valid BOOLEAN NOT NULL, > LoadState VARCHAR(25) NOT NULL, > Cardinality BIGINT, > Updated TIMESTAMP NOT NULL, > LoadNumber BIGINT NOT NULL, > NodeName varchar(25) not null, > StaleCount BIGINT, > PRIMARY KEY (VDBName , VDBVersion , SchemaName , Name) > ); > CREATE TABLE numbering_plan_cache ( > id integer, > global_title varchar(20), > LoadNumber BIGINT, > PRIMARY KEY(id) > ); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2017