November 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2223) Compiled Groovy cannot deploy a dynamic VDB, using AdminShell methods, that is recognized as ACTIVE by the Groovy script

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2223. ----------------------------------- Resolution: Out of Date Marking as out of date as there has been no movement in two years. > Compiled Groovy cannot deploy a dynamic VDB, using AdminShell methods, that is recognized as ACTIVE by the Groovy script > ------------------------------------------------------------------------------------------------------------------------ > > Key: TEIID-2223 > URL: https://issues.jboss.org/browse/TEIID-2223 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 7.7.2 > Reporter: Paul Nittel > Assignee: Johnathon Lee > Priority: Optional > Fix For: Open To Community > > Attachments: CrummyWeather.groovy, ShortWeatherNoTest.groovy, weather-vdb.xml > > > This is a weird case. If I deploy a dynamic VDB from a compiled Groovy script, it is not seen as ACTIVE by the script. The server log shows it is active. > If I use a non-compiled Groovy script, it all works fine. > To add to the intrigue, if the compiled script periodically polls to see if the VDB is active, and I go to the Virtual Databases display in RHQ, the script magically sees the VDB as ACTIVE. > I'm attaching the materials used in this test. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3223) An issue with time in WHERE clause - SQLServer

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3223?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3223: --------------------------------------- With SQL Server 2008+ and without this fix, the following will not work: source type, Teiid type, driver datetime, time, sql server - incorrect results time, time, sql server - exception So without the fix, you would have to use the JTDS driver or with a source type of datetime use a Teiid type of timestamp (which is what the dynamic vdbs were doing). > An issue with time in WHERE clause - SQLServer > ---------------------------------------------- > > Key: TEIID-3223 > URL: https://issues.jboss.org/browse/TEIID-3223 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: oracle 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.10 > > > Teiid is not able to manage WHERE clause with time value. > translator: sqlserver > base DB: SQL Server 2012/2008/2005 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3215) External Materialization ON_VDB_START_SCRIPT invocation issues

by Jan Stastny (JIRA)

[ https://issues.jboss.org/browse/TEIID-3215?page=com.atlassian.jira.plugin... ] Jan Stastny updated TEIID-3215: ------------------------------- Attachment: mat-views-vdb.xml The attached vdb should demonstrate the issue. Below are schemas of required tables. CREATE TABLE check_table( id VARCHAR(50) PRIMARY KEY, vdb_create INT DEFAULT 0, vdb_drop INT DEFAULT 0, before_load INT DEFAULT 0, after_load INT DEFAULT 0 ) CREATE TABLE IF NOT EXISTS status(VDBName varchar(50) not null, VDBVersion integer 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 long, Updated timestamp not null, LoadNumber long not null, PRIMARY KEY (VDBName, VDBVersion, SchemaName, Name)); CREATE TABLE IF NOT EXISTS mat_view(customer_id INT NOT NULL,total_amount INT);ALTER TABLE mat_view ADD CONSTRAINT pk_customer_id PRIMARY KEY (customer_id); CREATE TABLE IF NOT EXISTS mat_view_stage(customer_id INT NOT NULL,total_amount INT);ALTER TABLE mat_view_stage ADD CONSTRAINT pk_customer_stage_id PRIMARY KEY (customer_id); > External Materialization ON_VDB_START_SCRIPT invocation issues > -------------------------------------------------------------- > > Key: TEIID-3215 > URL: https://issues.jboss.org/browse/TEIID-3215 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7 > Reporter: Jan Stastny > Assignee: Ramesh Reddy > Labels: Final > Fix For: 8.7.1, 8.9 > > Attachments: mat-views-vdb.xml > > > With materialized view I have set teiid_rel:ON_VDB_START_SCRIPT property for the external matview table. (Simple query to increment a column in table to count invocations.) > Invocation of the script is dependent upon the way the vdb is deployed. The first case (A) doesn't invoke the script, the second (B) does. > A - 1. Copy the vdbname-vdb.xml into deployments folder > 2. Start the server > B - 1. Start the server > 2. Copy the vdbname-vdb.xml into deployments folder > That means that after server stop (maintenance) the script is not invoked on start, which can cause problems when the script is used to initialize running environment (clear table, create temporary table,...) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3223) An issue with time in WHERE clause - SQLServer

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3223?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-3223: ------------------------------------- So, your suggestion is to change the type to 'time' (without changing static vdb)? > An issue with time in WHERE clause - SQLServer > ---------------------------------------------- > > Key: TEIID-3223 > URL: https://issues.jboss.org/browse/TEIID-3223 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: oracle 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.10 > > > Teiid is not able to manage WHERE clause with time value. > translator: sqlserver > base DB: SQL Server 2012/2008/2005 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3219) Excel Translator Wrong Result From Columns With Interleaved Null Values

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3219?page=com.atlassian.jira.plugin... ] Kylin Soong updated TEIID-3219: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/361 > Excel Translator Wrong Result From Columns With Interleaved Null Values > ----------------------------------------------------------------------- > > Key: TEIID-3219 > URL: https://issues.jboss.org/browse/TEIID-3219 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Jan Stastny > Assignee: Kylin Soong > Attachments: artifacts.zip > > > When querying a column which has a null value somewhere in it, the result set is missing all the rows under the null value in the xlsx file. When querying more columns, the result set is missing some values only if there is a row, where both columns contains null value. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3219) Excel Translator Wrong Result From Columns With Interleaved Null Values

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3219?page=com.atlassian.jira.plugin... ] Kylin Soong reassigned TEIID-3219: ---------------------------------- Assignee: Kylin Soong (was: Steven Hawkins) > Excel Translator Wrong Result From Columns With Interleaved Null Values > ----------------------------------------------------------------------- > > Key: TEIID-3219 > URL: https://issues.jboss.org/browse/TEIID-3219 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Jan Stastny > Assignee: Kylin Soong > Attachments: artifacts.zip > > > When querying a column which has a null value somewhere in it, the result set is missing all the rows under the null value in the xlsx file. When querying more columns, the result set is missing some values only if there is a row, where both columns contains null value. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2831) Add a full ddl example to the ldap translator docs

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-2831?page=com.atlassian.jira.plugin... ] Kylin Soong closed TEIID-2831. ------------------------------ Resolution: Done > Add a full ddl example to the ldap translator docs > -------------------------------------------------- > > Key: TEIID-2831 > URL: https://issues.jboss.org/browse/TEIID-2831 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Steven Hawkins > Assignee: Kylin Soong > > It would be helpful to have a full example of LDAP metadata. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3170) Change build to include spring framework jar dependencies for WS translator

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3170?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3170: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/340, https://github.com/teiid/teiid/pull/362 (was: https://github.com/teiid/teiid/pull/340) > Change build to include spring framework jar dependencies for WS translator > --------------------------------------------------------------------------- > > Key: TEIID-3170 > URL: https://issues.jboss.org/browse/TEIID-3170 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > Fix For: 8.7.1 > > > The "org.springframework.spring" module and dependent jars will be added to the kit. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3170) Change build to include spring framework jar dependencies for WS translator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3170?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3170: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1151047|https://bugzilla.redhat.com/show_bug.cgi?id=1151047] from MODIFIED to ASSIGNED > Change build to include spring framework jar dependencies for WS translator > --------------------------------------------------------------------------- > > Key: TEIID-3170 > URL: https://issues.jboss.org/browse/TEIID-3170 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > Fix For: 8.7.1 > > > The "org.springframework.spring" module and dependent jars will be added to the kit. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3170) Change build to include spring framework jar dependencies for WS translator

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3170?page=com.atlassian.jira.plugin... ] Van Halbert reopened TEIID-3170: -------------------------------- More jars from the spring frame work is needed. The module needed to be the following in order to start the server when configured to use: <module xmlns="urn:jboss:module:1.1" name="org.springframework.spring"> <resources> <resource-root path="spring-beans-3.0.7.RELEASE.jar"/> <resource-root path="spring-context-3.0.7.RELEASE.jar"/> <resource-root path="spring-core-3.0.7.RELEASE.jar"/> <resource-root path="spring-asm-3.0.7.RELEASE.jar"/> <resource-root path="spring-expression-3.0.7.RELEASE.jar"/> <resource-root path="spring-aop-3.0.7.RELEASE.jar"/> <resource-root path="spring-tx-3.0.7.RELEASE.jar"/> </resources> <dependencies> <module name="javax.api"/> <module name="org.apache.commons.logging"/> </dependencies> </module> > Change build to include spring framework jar dependencies for WS translator > --------------------------------------------------------------------------- > > Key: TEIID-3170 > URL: https://issues.jboss.org/browse/TEIID-3170 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > Fix For: 8.7.1 > > > The "org.springframework.spring" module and dependent jars will be added to the kit. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2014