May 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5916) Add indexes in generated protobuf

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5916?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-5916: -------------------------------- Story Points: 0.5 (was: 1) > Add indexes in generated protobuf > --------------------------------- > > Key: TEIID-5916 > URL: https://issues.redhat.com/browse/TEIID-5916 > Project: Teiid > Issue Type: Enhancement > Components: Infinispan > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 14.0 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > The protobuf logic will mark an entire table as indexed, but that may not line up to what we need. > The usage of the Indexed annotation on the message indicates that custom IndexedField annotations will be used to selective enable indexes. > This is true whether the cache is marked as indexed (which would be specified in the cache template) or not. > If we auto-create an indexed cache, then all fields are automatically indexed and there's no need for the indexed annotation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5916) Add indexes in generated protobuf

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5916?focusedWorklogId=12450930&pag... ] Ramesh Reddy logged work on TEIID-5916: --------------------------------------- Author: Ramesh Reddy Created on: 01/May/20 9:35 AM Start Date: 01/May/20 9:35 AM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 2 hours Worklog Id: (was: 12450930) > Add indexes in generated protobuf > --------------------------------- > > Key: TEIID-5916 > URL: https://issues.redhat.com/browse/TEIID-5916 > Project: Teiid > Issue Type: Enhancement > Components: Infinispan > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 14.0 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > The protobuf logic will mark an entire table as indexed, but that may not line up to what we need. > The usage of the Indexed annotation on the message indicates that custom IndexedField annotations will be used to selective enable indexes. > This is true whether the cache is marked as indexed (which would be specified in the cache template) or not. > If we auto-create an indexed cache, then all fields are automatically indexed and there's no need for the indexed annotation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5916) Add indexes in generated protobuf

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5916?page=com.atlassian.jira.plugi... ] Work on TEIID-5916 started by Ramesh Reddy. ------------------------------------------- > Add indexes in generated protobuf > --------------------------------- > > Key: TEIID-5916 > URL: https://issues.redhat.com/browse/TEIID-5916 > Project: Teiid > Issue Type: Enhancement > Components: Infinispan > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 14.0 > > > The protobuf logic will mark an entire table as indexed, but that may not line up to what we need. > The usage of the Indexed annotation on the message indicates that custom IndexedField annotations will be used to selective enable indexes. > This is true whether the cache is marked as indexed (which would be specified in the cache template) or not. > If we auto-create an indexed cache, then all fields are automatically indexed and there's no need for the indexed annotation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5939) connection pool not destroyed after datasource deletion without server reload(java)

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5939?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5939: ---------------------------------- Fix Version/s: 14.0 > connection pool not destroyed after datasource deletion without server reload(java) > ----------------------------------------------------------------------------------- > > Key: TEIID-5939 > URL: https://issues.redhat.com/browse/TEIID-5939 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 11.1.2 > Reporter: Manoj Majumdar > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0 > > > Hi Team, > Connection pool is not removed after deletion of datasource using java code. > Teiid(Jboss) server reload required to reflect the deletion of connection pool from actual database(we are using mysql as database). > Until server reloads, connections in deleted datasource's connection pool remain in sleep mode. > *Pre-requisite* > * Connection is created with the mysql database using teiid > * Datasource is created in teiid. > * Delete the above created connection through java using code i.e by using AdminApiClientAccessor. > * That removed the datasource from teiid. > * Through below code I am able to delete the datasource. > *Java code* > {code:java} > import org.teiid.adminapi.Admin; > .. > private Admin admin; //assigned object to admin; > .. > .. > public void deleteDataSource(String datasourceName){ > try { > admin.deleteDataSource(datasourceName); > } catch (Exception e) { > logger.error(e); > } > } > {code} > datasourceName = name of the datasource created earlier. > *standalone-teiid.xml* > </xa-datasource> > .. > .. > <xa-pool> > <min-pool-size>3</min-pool-size> > <max-pool-size>10</max-pool-size> > <flush-strategy>IdleConnections</flush-strategy> > </xa-pool> > <validation> > <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/> > <background-validation>true</background-validation> > <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/> > </validation> > </xa-datasource> > *Issues :* > * Even though datasource removed, connection pool is not destroyed > * Able to see connection threads available on Mysql admin console using the command > > {code:java} > show processlist; > {code} > * Changes reflect only when the Teiid (jboss) server is reloaded. > * Once server reloads connections in connection pool is closed/removed from the database. > * 'Too many connection' issue facing on mysql server due to multiple connection threads remains in sleep mode even though datasource are already removed. > Please let us know : > * Is there any method to remove connection pool from actual database. > * Is server reload mandatory. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5946) condition support for masks needs restored

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5946?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5946: --------------------------------------- Any change would of course be backwards compatible. > condition support for masks needs restored > ------------------------------------------ > > Key: TEIID-5946 > URL: https://issues.redhat.com/browse/TEIID-5946 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0, 13.1.1 > > > Cleanup in TEIID-4770 TEIID-4771 removed the ability to set a condition with a mask - more than likely to avoid specifying whether the condition was a constraint. That should be added back. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5946) condition support for masks needs restored

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5946?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5946: --------------------------------------- A general issue here is that our syntax for column grants is pretty non-standard. It follows the old data roles paradigm of specifying a fully-qualified name, rather than separating out the table and column components. GRANT ... ON COLUMN x.y.z vs GRANT ... (z) ON TABLE x.y I'm not sure I'll address that yet. > condition support for masks needs restored > ------------------------------------------ > > Key: TEIID-5946 > URL: https://issues.redhat.com/browse/TEIID-5946 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0, 13.1.1 > > > Cleanup in TEIID-4770 TEIID-4771 removed the ability to set a condition with a mask - more than likely to avoid specifying whether the condition was a constraint. That should be added back. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5943) Status table not found when model is not visible

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5943?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5943: ---------------------------------- Original Estimate: 4 hours Story Points: 0.5 > Status table not found when model is not visible > ------------------------------------------------ > > Key: TEIID-5943 > URL: https://issues.redhat.com/browse/TEIID-5943 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0, 13.1.1, 8.0-tp1-13.1.x > > Original Estimate: 4 hours > Time Spent: 3 hours > Remaining Estimate: 0 minutes > > When materialization schema is hidden and the Materilization Status table is part of it, then references to it from Materialization scripts is not found and load auto management fails. > A workaround is simple to make model visible -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5943) Status table not found when model is not visible

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5943?focusedWorklogId=12450929&pag... ] Steven Hawkins logged work on TEIID-5943: ----------------------------------------- Author: Steven Hawkins Created on: 01/May/20 7:48 AM Start Date: 01/May/20 7:48 AM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Time Spent: 3 hours (was: 1 hour) Worklog Id: (was: 12450929) > Status table not found when model is not visible > ------------------------------------------------ > > Key: TEIID-5943 > URL: https://issues.redhat.com/browse/TEIID-5943 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0, 13.1.1, 8.0-tp1-13.1.x > > Time Spent: 3 hours > Remaining Estimate: 0 minutes > > When materialization schema is hidden and the Materilization Status table is part of it, then references to it from Materialization scripts is not found and load auto management fails. > A workaround is simple to make model visible -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5943) Status table not found when model is not visible

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5943?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5943. ----------------------------------- Fix Version/s: 8.0-tp1-13.1.x 14.0 13.1.1 Resolution: Done Addressed by adding a check of whether the current session is admin down in TransformationMetadata. > Status table not found when model is not visible > ------------------------------------------------ > > Key: TEIID-5943 > URL: https://issues.redhat.com/browse/TEIID-5943 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 8.0-tp1-13.1.x, 14.0, 13.1.1 > > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > When materialization schema is hidden and the Materilization Status table is part of it, then references to it from Materialization scripts is not found and load auto management fails. > A workaround is simple to make model visible -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5916) Add indexes in generated protobuf

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5916?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIID-5916: ------------------------------------- >From Infinispan Documentation NOTE {{@IndexedField}} is deprecated in Red Hat JBoss Data Grid 7.2. However, this version of JBoss Data Grid incorrectly throws a warning that the annotation is deprecated. You can ignore the warning and use @IndexedField. Alternatively, you can use the {{@Field}} annotation that replaces the {{@IndexedField}} annotation. However, this version of JBoss Data Grid does not support the analyze attribute for the {{@Field}} annotation. You can replace {{@IndexedField}} annotations with {{@Field}} annotations as follows: @IndexedField is equivalent to @Field(store=Store.YES) @IndexedField(store=false) is equivalent to @Field` @IndexedField(index=false, store=false) is equivalent to @Field(index=Index.NO) > Add indexes in generated protobuf > --------------------------------- > > Key: TEIID-5916 > URL: https://issues.redhat.com/browse/TEIID-5916 > Project: Teiid > Issue Type: Enhancement > Components: Infinispan > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 14.0 > > > The protobuf logic will mark an entire table as indexed, but that may not line up to what we need. > The usage of the Indexed annotation on the message indicates that custom IndexedField annotations will be used to selective enable indexes. > This is true whether the cache is marked as indexed (which would be specified in the cache template) or not. > If we auto-create an indexed cache, then all fields are automatically indexed and there's no need for the indexed annotation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2020