October 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5102) add INSTR function similar to that of Oracle

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5102?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-5102: ------------------------------------- Component/s: Query Engine (was: Server) Fix Version/s: Open To Community Assignee: (was: Steven Hawkins) > add INSTR function similar to that of Oracle > -------------------------------------------- > > Key: TEIID-5102 > URL: https://issues.jboss.org/browse/TEIID-5102 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Tom Johnston > Fix For: Open To Community > > > Add Function INSTR with functionality such as Oracle (https://docs.oracle.com/cd/B19306_01/server.102/b14200/functions068.htm) > Though it is similar to locate it allows for position and occurrence. > Obviously the oracle translator would push down this function if implemented. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5103) ManagedConnectionFactory hashCode/equals

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5103: ------------------------------------- Summary: ManagedConnectionFactory hashCode/equals Key: TEIID-5103 URL: https://issues.jboss.org/browse/TEIID-5103 Project: Teiid Issue Type: Quality Risk Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.0 There's been some drift with config properties that aren't reflected in several resource adapters. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5101) .vdb with JDG data source, with NATIVE defined, throws exception

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5101?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5101: ------------------------------------- Metadata tags or schema are new constructs with dynamic VDB notion, .vdb there is always guarantee that all the required metadata is already available in the VDB, which is not true in this case. We should write this up KI and force the use of Dynamic VDB in this case. Ramesh.. > .vdb with JDG data source, with NATIVE defined, throws exception > ---------------------------------------------------------------- > > Key: TEIID-5101 > URL: https://issues.jboss.org/browse/TEIID-5101 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > > When a .vdb (created in designer), and the internal vdb.xml contains the <metadata type="NATIVE"></metadata>, the vdb will not deploy. > However, it will work if the .vdb is exported to vdb xml, because the DDL and the NATIVE tags are there. > Guessing that the translator doesn't know how to handle a .vdb file. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5096) Using /*+ MAKEDEP */ blocks the deploy proces when using DDL based vdb

by Bram Gadeyne (JIRA)

[ https://issues.jboss.org/browse/TEIID-5096?page=com.atlassian.jira.plugin... ] Bram Gadeyne commented on TEIID-5096: ------------------------------------- Oh Sorry, I forgot to mention this error message when I use jboss cli to deploy. Failed to add the deployment content to the repository: java.util.concurrent.CancellationException: Operation was cancelled. I've increased the log level to DEBUG but this does not show anything more. Should I set it to something else? > Using /*+ MAKEDEP */ blocks the deploy proces when using DDL based vdb > ---------------------------------------------------------------------- > > Key: TEIID-5096 > URL: https://issues.jboss.org/browse/TEIID-5096 > Project: Teiid > Issue Type: Bug > Affects Versions: 9.3.3 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: threaddump.txt > > > Hi, > I've created a vdb that is depoyed using a vdb-ddl.ddl file. > The deployment just stops and returned no error message when adding the SQL part below. Subsequent deployments are not handles. It seems like the deployment process just hangs. The only way to resolve this was to stop the wildfly server, remove the latest added content from the standalone/data/content directory and restart wildfly. > {code:sql} > CREATE VIEW tv_retrieve_monvals( > admissionid integer not null, > VariableID integer not null, > Datetime timestamp not null, > Entertime timestamp not null, > varvalue double not null, > primary key (admissionid, VariableID, Datetime) > ) > AS > SELECT v.PatientID AS admissionid, v.VariableID, v.Datetime, v.Entertime, v."Value" AS varvalue > FROM ( > SELECT mv.PatientID, mv.VariableID, mv.Datetime, mv.Entertime, mv."Value", > ROW_NUMBER() OVER (PARTITION BY mv.PatientID, mv.VariableID, mv.Datetime ORDER BY mv.Entertime DESC) AS rang > FROM izisprod.P_GeneralData AS gd > INNER JOIN /*+ MAKEDEP */ izisprod.P_MonVals AS mv ON > gd.PatientID = mv.PatientID AND > bitand(mv.Status, 8) = 8 AND > bitand(mv.Status, 2) <> 2 > WHERE gd.Status = 1 OR (gd.Status >= 4 AND gd.Status <> 5) > UNION > SELECT mv.PatientID, mv.VariableID, mv.Datetime, mv.Entertime, mv."Value", > ROW_NUMBER() OVER (PARTITION BY mv.PatientID, mv.VariableID, mv.Datetime ORDER BY mv.Entertime DESC) AS rang > FROM iziswh.P_GeneralData AS gd > INNER JOIN /*+ MAKEDEP */ iziswh.P_MonVals AS mv ON > gd.PatientID = mv.PatientID AND > bitand(mv.Status, 8) = 8 AND > bitand(mv.Status, 2) <> 2 > ) AS v > WHERE v.rang = 1; > {code} > Removing the /*+ MAKDEP */ references resolves the issue. > I've tried creating a small ddl script that uses /*+ MAKEDEP */ to reproduce this issue but this script does deploy so currently I can not make a small example. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5096) Using /*+ MAKEDEP */ blocks the deploy proces when using DDL based vdb

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5096?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5096: --------------------------------------- Unfortunately there isn't anything that seems off about that thread dump. There are what appears to be the daemon threads for Teiid and for WildFly that handle deployment scans - although that's just by comparing stacks the actual thread names are not shown in this dump. We can have you try increasing the logging level to trace or work towards a reproducer. > Using /*+ MAKEDEP */ blocks the deploy proces when using DDL based vdb > ---------------------------------------------------------------------- > > Key: TEIID-5096 > URL: https://issues.jboss.org/browse/TEIID-5096 > Project: Teiid > Issue Type: Bug > Affects Versions: 9.3.3 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: threaddump.txt > > > Hi, > I've created a vdb that is depoyed using a vdb-ddl.ddl file. > The deployment just stops and returned no error message when adding the SQL part below. Subsequent deployments are not handles. It seems like the deployment process just hangs. The only way to resolve this was to stop the wildfly server, remove the latest added content from the standalone/data/content directory and restart wildfly. > {code:sql} > CREATE VIEW tv_retrieve_monvals( > admissionid integer not null, > VariableID integer not null, > Datetime timestamp not null, > Entertime timestamp not null, > varvalue double not null, > primary key (admissionid, VariableID, Datetime) > ) > AS > SELECT v.PatientID AS admissionid, v.VariableID, v.Datetime, v.Entertime, v."Value" AS varvalue > FROM ( > SELECT mv.PatientID, mv.VariableID, mv.Datetime, mv.Entertime, mv."Value", > ROW_NUMBER() OVER (PARTITION BY mv.PatientID, mv.VariableID, mv.Datetime ORDER BY mv.Entertime DESC) AS rang > FROM izisprod.P_GeneralData AS gd > INNER JOIN /*+ MAKEDEP */ izisprod.P_MonVals AS mv ON > gd.PatientID = mv.PatientID AND > bitand(mv.Status, 8) = 8 AND > bitand(mv.Status, 2) <> 2 > WHERE gd.Status = 1 OR (gd.Status >= 4 AND gd.Status <> 5) > UNION > SELECT mv.PatientID, mv.VariableID, mv.Datetime, mv.Entertime, mv."Value", > ROW_NUMBER() OVER (PARTITION BY mv.PatientID, mv.VariableID, mv.Datetime ORDER BY mv.Entertime DESC) AS rang > FROM iziswh.P_GeneralData AS gd > INNER JOIN /*+ MAKEDEP */ iziswh.P_MonVals AS mv ON > gd.PatientID = mv.PatientID AND > bitand(mv.Status, 8) = 8 AND > bitand(mv.Status, 2) <> 2 > ) AS v > WHERE v.rang = 1; > {code} > Removing the /*+ MAKDEP */ references resolves the issue. > I've tried creating a small ddl script that uses /*+ MAKEDEP */ to reproduce this issue but this script does deploy so currently I can not make a small example. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5101) .vdb with JDG data source, with NATIVE defined, throws exception

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5101?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5101: ------------------------------------ I wonder if its possible, that in designer, the xmi model can have a "Native" construct so that its generated into the .index file. > .vdb with JDG data source, with NATIVE defined, throws exception > ---------------------------------------------------------------- > > Key: TEIID-5101 > URL: https://issues.jboss.org/browse/TEIID-5101 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > > When a .vdb (created in designer), and the internal vdb.xml contains the <metadata type="NATIVE"></metadata>, the vdb will not deploy. > However, it will work if the .vdb is exported to vdb xml, because the DDL and the NATIVE tags are there. > Guessing that the translator doesn't know how to handle a .vdb file. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5025) Improve BufferManagerCleaner shutdown

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5025?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5025: ---------------------------------- Fix Version/s: 9.3.3 > Improve BufferManagerCleaner shutdown > ------------------------------------- > > Key: TEIID-5025 > URL: https://issues.jboss.org/browse/TEIID-5025 > Project: Teiid > Issue Type: Quality Risk > Components: Embedded > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.3 > > > When running an embedded example the static timer used for the buffer cleaner is a daemon thread that isn't otherwise shutdown and will cause a delay/warning. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5096) Using /*+ MAKEDEP */ blocks the deploy proces when using DDL based vdb

by Bram Gadeyne (JIRA)

[ https://issues.jboss.org/browse/TEIID-5096?page=com.atlassian.jira.plugin... ] Bram Gadeyne commented on TEIID-5096: ------------------------------------- Hi Steven, I've created a threaddump using the command sudo /usr/lib/jvm/jdk1.8.0_121/bin/jstack -F -l 30699 > threaddump.txt. I hope this is what you expected. With kind regards > Using /*+ MAKEDEP */ blocks the deploy proces when using DDL based vdb > ---------------------------------------------------------------------- > > Key: TEIID-5096 > URL: https://issues.jboss.org/browse/TEIID-5096 > Project: Teiid > Issue Type: Bug > Affects Versions: 9.3.3 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: threaddump.txt > > > Hi, > I've created a vdb that is depoyed using a vdb-ddl.ddl file. > The deployment just stops and returned no error message when adding the SQL part below. Subsequent deployments are not handles. It seems like the deployment process just hangs. The only way to resolve this was to stop the wildfly server, remove the latest added content from the standalone/data/content directory and restart wildfly. > {code:sql} > CREATE VIEW tv_retrieve_monvals( > admissionid integer not null, > VariableID integer not null, > Datetime timestamp not null, > Entertime timestamp not null, > varvalue double not null, > primary key (admissionid, VariableID, Datetime) > ) > AS > SELECT v.PatientID AS admissionid, v.VariableID, v.Datetime, v.Entertime, v."Value" AS varvalue > FROM ( > SELECT mv.PatientID, mv.VariableID, mv.Datetime, mv.Entertime, mv."Value", > ROW_NUMBER() OVER (PARTITION BY mv.PatientID, mv.VariableID, mv.Datetime ORDER BY mv.Entertime DESC) AS rang > FROM izisprod.P_GeneralData AS gd > INNER JOIN /*+ MAKEDEP */ izisprod.P_MonVals AS mv ON > gd.PatientID = mv.PatientID AND > bitand(mv.Status, 8) = 8 AND > bitand(mv.Status, 2) <> 2 > WHERE gd.Status = 1 OR (gd.Status >= 4 AND gd.Status <> 5) > UNION > SELECT mv.PatientID, mv.VariableID, mv.Datetime, mv.Entertime, mv."Value", > ROW_NUMBER() OVER (PARTITION BY mv.PatientID, mv.VariableID, mv.Datetime ORDER BY mv.Entertime DESC) AS rang > FROM iziswh.P_GeneralData AS gd > INNER JOIN /*+ MAKEDEP */ iziswh.P_MonVals AS mv ON > gd.PatientID = mv.PatientID AND > bitand(mv.Status, 8) = 8 AND > bitand(mv.Status, 2) <> 2 > ) AS v > WHERE v.rang = 1; > {code} > Removing the /*+ MAKDEP */ references resolves the issue. > I've tried creating a small ddl script that uses /*+ MAKEDEP */ to reproduce this issue but this script does deploy so currently I can not make a small example. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5096) Using /*+ MAKEDEP */ blocks the deploy proces when using DDL based vdb

by Bram Gadeyne (JIRA)

[ https://issues.jboss.org/browse/TEIID-5096?page=com.atlassian.jira.plugin... ] Bram Gadeyne updated TEIID-5096: -------------------------------- Attachment: threaddump.txt > Using /*+ MAKEDEP */ blocks the deploy proces when using DDL based vdb > ---------------------------------------------------------------------- > > Key: TEIID-5096 > URL: https://issues.jboss.org/browse/TEIID-5096 > Project: Teiid > Issue Type: Bug > Affects Versions: 9.3.3 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: threaddump.txt > > > Hi, > I've created a vdb that is depoyed using a vdb-ddl.ddl file. > The deployment just stops and returned no error message when adding the SQL part below. Subsequent deployments are not handles. It seems like the deployment process just hangs. The only way to resolve this was to stop the wildfly server, remove the latest added content from the standalone/data/content directory and restart wildfly. > {code:sql} > CREATE VIEW tv_retrieve_monvals( > admissionid integer not null, > VariableID integer not null, > Datetime timestamp not null, > Entertime timestamp not null, > varvalue double not null, > primary key (admissionid, VariableID, Datetime) > ) > AS > SELECT v.PatientID AS admissionid, v.VariableID, v.Datetime, v.Entertime, v."Value" AS varvalue > FROM ( > SELECT mv.PatientID, mv.VariableID, mv.Datetime, mv.Entertime, mv."Value", > ROW_NUMBER() OVER (PARTITION BY mv.PatientID, mv.VariableID, mv.Datetime ORDER BY mv.Entertime DESC) AS rang > FROM izisprod.P_GeneralData AS gd > INNER JOIN /*+ MAKEDEP */ izisprod.P_MonVals AS mv ON > gd.PatientID = mv.PatientID AND > bitand(mv.Status, 8) = 8 AND > bitand(mv.Status, 2) <> 2 > WHERE gd.Status = 1 OR (gd.Status >= 4 AND gd.Status <> 5) > UNION > SELECT mv.PatientID, mv.VariableID, mv.Datetime, mv.Entertime, mv."Value", > ROW_NUMBER() OVER (PARTITION BY mv.PatientID, mv.VariableID, mv.Datetime ORDER BY mv.Entertime DESC) AS rang > FROM iziswh.P_GeneralData AS gd > INNER JOIN /*+ MAKEDEP */ iziswh.P_MonVals AS mv ON > gd.PatientID = mv.PatientID AND > bitand(mv.Status, 8) = 8 AND > bitand(mv.Status, 2) <> 2 > ) AS v > WHERE v.rang = 1; > {code} > Removing the /*+ MAKDEP */ references resolves the issue. > I've tried creating a small ddl script that uses /*+ MAKEDEP */ to reproduce this issue but this script does deploy so currently I can not make a small example. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4835) Implement column level incoming dependencies

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4835?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4835: ------------------------------- Fix Version/s: 8.12.x-6.4 > Implement column level incoming dependencies > -------------------------------------------- > > Key: TEIID-4835 > URL: https://issues.jboss.org/browse/TEIID-4835 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3, 8.12.x-6.4 > > > The original implementation of the usage table did not implement the ElementName column. Additional logic will be needed in the metadatavalidator to determine what contributes to the column. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 October 2017