February 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4758) Permanent materialization load failure is when JDG source goes down

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4758?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4758: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/903 > Permanent materialization load failure is when JDG source goes down > ------------------------------------------------------------------- > > Key: TEIID-4758 > URL: https://issues.jboss.org/browse/TEIID-4758 > Project: Teiid > Issue Type: Sub-task > Components: Server > Affects Versions: 8.12 > Reporter: Ramesh Reddy > Assignee: Van Halbert > Fix For: 9.3 > > > During the external materialization load, if the target cache database goes offline, the materialization job stops, but the {{Status}} table is left in {{LOADING}} state, which will never recover when the target cache database comes back up again. > This situation is observed when JDG is used in OpenShift along with JDV However, behavior can occur in standalone situations too. The system should resilient and must recover in this situation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4734) Restart during materialization load, does not update Materialized views anymore

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4734?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4734. --------------------------------- Resolution: Done Labels: Alpha1 (was: ) TEIID-4780 will handle for previous versions of Teiid, so this can be resolved for 9.3. > Restart during materialization load, does not update Materialized views anymore > ------------------------------------------------------------------------------- > > Key: TEIID-4734 > URL: https://issues.jboss.org/browse/TEIID-4734 > Project: Teiid > Issue Type: Sub-task > 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 > Labels: Alpha1 > Fix For: 9.3 > > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-4777) google package name misspelled

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4777?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4777. ----------------------------------- Resolution: Done Renamed back to google. > google package name misspelled > ------------------------------ > > Key: TEIID-4777 > URL: https://issues.jboss.org/browse/TEIID-4777 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Affects Versions: 9.0, 8.13.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3 > > > With TEIID-4070 the google package name was inadvertently changed to goole. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4776) Issues with array type metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4776?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4776. ----------------------------------- Resolution: Done Updated the logic to preserve the array dimensions. > Issues with array type metadata > ------------------------------- > > Key: TEIID-4776 > URL: https://issues.jboss.org/browse/TEIID-4776 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0.6, 9.3, 9.2.1, 9.1.4 > > > If cached metadata (typically from Designer) is used, then on cached usage our logic to use the canonical datatype reference will reset the array dimension to 0 on array type columns. > There is also an issue with Designer vdbs in that an array type cannot be conveyed as we are only looking at the datatype uuid and not at the runtime type name, which would contain the array dimensions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4734) Restart during materialization load, does not update Materialized views anymore

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4734?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4734: ------------------------------- Fix Version/s: (was: 8.12.9.6_3) > Restart during materialization load, does not update Materialized views anymore > ------------------------------------------------------------------------------- > > Key: TEIID-4734 > URL: https://issues.jboss.org/browse/TEIID-4734 > Project: Teiid > Issue Type: Sub-task > 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 > Fix For: 9.3 > > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2820) Support Couchbase as a resource

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-2820?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-2820: ------------------------------------ I would like to write a summary and difficults that I have met so far, after some investigation of Couchbase documents and samples. * The big difficults that block me so far is that it's hard to get the metadata of a specific document. In a Couchbase *Cluster*(same as a Database in RDBMS), there are lots of *Bucket*(same as Keyspace in NoSQL, or Table in RDBMS), each *Bucket* can contains lots of *Document*. These documents are JSON, use _a self-describing format, flexible Data Model, dynamic schemas_, and each document can have different attributes, can not get the attributes' name and data type in my investigation. * Community version can test limit features, Couchbase has 2 version: Community version and Enterprise version, the Enterprise version seems have full rights to access all features and a better documents, [1] hints there are SQL can infer the metadata(a JSON schema as [2]) of documents in a keyspace, for example the structure of documents, data types of various attributes, sample values, and so on, but The INFER statement is only supported in the Enterprise Edition. * Another approach to integrate with JDBC way is to define the metadata, mapping the documents in Bucket/keyspace to several Tables, including define data columns/data types, etc, An example is Simba JDBC Drivers, [3] is how schema definition in Simba. Any suggests and advices? [1] https://developer.couchbase.com/documentation/server/4.6/n1ql/n1ql-langua... [2] http://json-schema.org/documentation.html [3] http://cdn.simba.com/products/Couchbase/doc/JDBC_InstallGuide/content/jdb... > Support Couchbase as a resource > ------------------------------- > > Key: TEIID-2820 > URL: https://issues.jboss.org/browse/TEIID-2820 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Kim Palko > Assignee: Kylin Soong > Priority: Blocker > Labels: data_source > Fix For: 9.3 > > > Support Couchbase as a data source in Teiid. This requires resource adapter and translater development -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4734) Restart during materialization load, does not update Materialized views anymore

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4734?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4734: ------------------------------- Fix Version/s: 8.12.9.6_3 > Restart during materialization load, does not update Materialized views anymore > ------------------------------------------------------------------------------- > > Key: TEIID-4734 > URL: https://issues.jboss.org/browse/TEIID-4734 > Project: Teiid > Issue Type: Sub-task > 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 > Fix For: 9.3, 8.12.9.6_3 > > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-4780) Clone TEIID-4734 (Backwards compatible solution)

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4780?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4780: -------------------------------- Attachment: (was: StatusTableAfterStop.csv) > Clone TEIID-4734 (Backwards compatible solution) > ------------------------------------------------ > > Key: TEIID-4780 > URL: https://issues.jboss.org/browse/TEIID-4780 > Project: Teiid > Issue Type: Sub-task > Components: Common > Affects Versions: 9.1.2 > Reporter: Pedro Inácio > Assignee: Ramesh Reddy > Fix For: 9.2.1 > > > This is clone of TEIID-4734, however the solution provided through it is a breaking change. This JIRA is logged to provide a non-breaking change for released Teiid versions based on comments from TEIID-4734 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4780) Clone TEIID-4734 (Backwards compatible solution)

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4780?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4780: -------------------------------- Description: This is clone of TEIID-4734, however the solution provided through it is a breaking change. This JIRA is logged to provide a non-breaking change for released Teiid versions based on comments from TEIID-4734 (was: 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. ) Fix Version/s: 9.2.1 (was: 9.3) Summary: Clone TEIID-4734 (Backwards compatible solution) (was: Restart during materialization load, does not update Materialized views anymore) Environment: (was: * Wildfly 10 * MySQL 5.6.32 * Teiid Server 9.1.2) > Clone TEIID-4734 (Backwards compatible solution) > ------------------------------------------------ > > Key: TEIID-4780 > URL: https://issues.jboss.org/browse/TEIID-4780 > Project: Teiid > Issue Type: Sub-task > Components: Common > Affects Versions: 9.1.2 > Reporter: Pedro Inácio > Assignee: Ramesh Reddy > Fix For: 9.2.1 > > > This is clone of TEIID-4734, however the solution provided through it is a breaking change. This JIRA is logged to provide a non-breaking change for released Teiid versions based on comments from TEIID-4734 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4780) Clone TEIID-4734 (Backwards compatible solution)

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4780?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4780: -------------------------------- Attachment: (was: StatusTableAfterStart.csv) > Clone TEIID-4734 (Backwards compatible solution) > ------------------------------------------------ > > Key: TEIID-4780 > URL: https://issues.jboss.org/browse/TEIID-4780 > Project: Teiid > Issue Type: Sub-task > Components: Common > Affects Versions: 9.1.2 > Reporter: Pedro Inácio > Assignee: Ramesh Reddy > Fix For: 9.2.1 > > > This is clone of TEIID-4734, however the solution provided through it is a breaking change. This JIRA is logged to provide a non-breaking change for released Teiid versions based on comments from TEIID-4734 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2017