July 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2982) Allow to change visibility to a model from imported vdb

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2982?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2982: ------------------------------------------- Bugzilla Update: (was: Perform) Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=1119522) > Allow to change visibility to a model from imported vdb > ------------------------------------------------------- > > Key: TEIID-2982 > URL: https://issues.jboss.org/browse/TEIID-2982 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Query Engine > Affects Versions: 8.7 > Reporter: Kenichi Takemura > Assignee: Steven Hawkins > Fix For: 8.9 > > > When a new vdb uses import-vdb, changing(override) visibility to a model from imported vdb would need to hide non-related model to the new vdb. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2982) Allow to change visibility to a model from imported vdb

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2982?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2982: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1119522 > Allow to change visibility to a model from imported vdb > ------------------------------------------------------- > > Key: TEIID-2982 > URL: https://issues.jboss.org/browse/TEIID-2982 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Query Engine > Affects Versions: 8.7 > Reporter: Kenichi Takemura > Assignee: Steven Hawkins > Fix For: 8.9 > > > When a new vdb uses import-vdb, changing(override) visibility to a model from imported vdb would need to hide non-related model to the new vdb. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2982) Allow to change visibility to a model from imported vdb

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2982?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2982: ------------------------------------------- Bugzilla Update: (was: Perform) Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=1027517) > Allow to change visibility to a model from imported vdb > ------------------------------------------------------- > > Key: TEIID-2982 > URL: https://issues.jboss.org/browse/TEIID-2982 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Query Engine > Affects Versions: 8.7 > Reporter: Kenichi Takemura > Assignee: Steven Hawkins > Fix For: 8.9 > > > When a new vdb uses import-vdb, changing(override) visibility to a model from imported vdb would need to hide non-related model to the new vdb. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2982) Allow to change visibility to a model from imported vdb

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2982?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2982: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1027517 > Allow to change visibility to a model from imported vdb > ------------------------------------------------------- > > Key: TEIID-2982 > URL: https://issues.jboss.org/browse/TEIID-2982 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Query Engine > Affects Versions: 8.7 > Reporter: Kenichi Takemura > Assignee: Steven Hawkins > Fix For: 8.9 > > > When a new vdb uses import-vdb, changing(override) visibility to a model from imported vdb would need to hide non-related model to the new vdb. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2700) Add CRUD support to Infinispan translator/connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2700?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2700: --------------------------------------- It's ok by me. you'll need user feedback to make further refinements. > Add CRUD support to Infinispan translator/connector > --------------------------------------------------- > > Key: TEIID-2700 > URL: https://issues.jboss.org/browse/TEIID-2700 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > > Add CRUD support to the Infinispan translator/connector to work with JDG 6.2. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Van Halbert (JIRA)

Van Halbert created TEIID-3033: ---------------------------------- Summary: Importing metadata thru Designer versus using dynamic VDB is different Key: TEIID-3033 URL: https://issues.jboss.org/browse/TEIID-3033 Project: Teiid Issue Type: Bug Security Level: Public (Everyone can see) Components: Misc. Connectors Affects Versions: 8.7.1, 8.9 Reporter: Van Halbert Assignee: Steven Hawkins The importing of metadata using JDBC importer (using ModeShape driver) returns tables as under Views and columns with underscore, like: nt_base but when using dynamic VDB, the tables show up under Tables and the columns have a colon, like:L nt:base and there require you to quote the columns in order to query ("nt:base") -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-3033: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The importing of metadata using JDBC importer (using ModeShape driver) returns tables as under Views and columns with underscore, like: nt_base > but when using dynamic VDB, the tables show up under Tables and the columns have a colon, like:L nt:base > and there require you to quote the columns in order to query ("nt:base") -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2700) Add CRUD support to Infinispan translator/connector

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2700?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2700: ------------------------------------ Added support for Insert, Update and Delete. However, there are limitations to Update and Delete: each doesn't support updating or deleting the container objects (i.e., 1-to-* relationship objects). I would like to consider this jira closed, and open up jira's for each of the above. Would that be ok? > Add CRUD support to Infinispan translator/connector > --------------------------------------------------- > > Key: TEIID-2700 > URL: https://issues.jboss.org/browse/TEIID-2700 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > > Add CRUD support to the Infinispan translator/connector to work with JDG 6.2. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3031) Database Logging: Problems with Oracle

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3031?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3031. --------------------------------- Assignee: Ramesh Reddy Fix Version/s: 8.7.1 Resolution: Done Changed the ID generation type from IDENTITY to AUTO based upon the discussion https://forum.hibernate.org/viewtopic.php?f=1&t=1000750 > Database Logging: Problems with Oracle > -------------------------------------- > > Key: TEIID-3031 > URL: https://issues.jboss.org/browse/TEIID-3031 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7.1 > > > Installed the teiid extension: database logging to use oracle, and get the following exception at startup: > Unable to build EntityManagerFactory > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:103) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Final-redhat-1] > Caused by: javax.persistence.PersistenceException: [PersistenceUnit: teiid-logger] Unable to build EntityManagerFactory > at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:924) > at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:899) > at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:76) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:200) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$600(PersistenceUnitServiceImpl.java:57) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:99) > ... 4 more > Caused by: org.hibernate.MappingException: org.hibernate.dialect.Oracle10gDialect does not support identity key generation > at org.hibernate.dialect.Dialect.getIdentityColumnString(Dialect.java:772) > at org.hibernate.dialect.Dialect.getIdentityColumnString(Dialect.java:762) > at org.hibernate.mapping.Table.sqlCreateString(Table.java:505) > at org.hibernate.cfg.Configuration.generateSchemaCreationScript(Configuration.java:1038) > at org.hibernate.tool.hbm2ddl.SchemaExport.<init>(SchemaExport.java:125) > at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:504) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1797) > at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:96) > at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:914) > ... 9 more -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3032) Database Logging: Problems with Microsoft

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3032?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3032. --------------------------------- Assignee: Ramesh Reddy Fix Version/s: 8.7.1 Resolution: Done Renamed the column to "queryplan" to avoid the reserved name conflict > Database Logging: Problems with Microsoft > ----------------------------------------- > > Key: TEIID-3032 > URL: https://issues.jboss.org/browse/TEIID-3032 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7.1 > > > Installed the teiid extension: database logging, and seeing the following errors: > 14:46:55,588 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB Logging.1 model "LoggingData" metadata failed to load. Reason:TEIID60013 Duplicate Table check_constraints > 14:46:55,844 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000227: Running hbm2ddl schema export > 14:46:56,119 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: drop table auditlog > 14:46:56,120 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Cannot drop the table 'auditlog', because it does not exist or you do not have permission. > 14:46:56,343 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: drop table commandlog > 14:46:56,343 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Cannot drop the table 'commandlog', because it does not exist or you do not have permission. > 14:46:56,857 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000389: Unsuccessful: create table commandlog (id bigint identity not null, applicationname varchar(255), executionid varchar(50), modelname varchar(255), plan varbinary(MAX), principal varchar(50), requestid varchar(50), rowcount int, sessionid varchar(50), sourcecommand bit, sourcerequestid bigint, sqlcmd varchar(MAX), eventtype varchar(10), logtime datetime2, transactionid varchar(100), translatorname varchar(50), vdbname varchar(255), vdbversion int, primary key (id)) > 14:46:56,858 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) Incorrect syntax near the keyword 'plan'. > 14:46:56,858 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 57) HHH000230: Schema export complete -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 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 July 2014