December 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3242) issues with data roles and foreign temp tables

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3242: ------------------------------------- Summary: issues with data roles and foreign temp tables Key: TEIID-3242 URL: https://issues.jboss.org/browse/TEIID-3242 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.3 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.10 With data roles enabled we require create on the target schema, but will output a message saying that create temp tables is required. We will also not appropriately check the columns as there name is not reported as relative to the target schema. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3241) Audit/Command Logging handler names do not match web console handler names

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3241?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3241: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1170583 > Audit/Command Logging handler names do not match web console handler names > -------------------------------------------------------------------------- > > Key: TEIID-3241 > URL: https://issues.jboss.org/browse/TEIID-3241 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > > When changing configuration of Audit and Command logging via Web Management, an exception is thrown in specific usecase, see the steps to reproduce below. > Then even after server restart logging doesn't work. No changes noticed in standalone.xml during the configuration. > Version-Release number of selected component (if applicable): > DV 6.1.0 ER4 > How reproducible: > Once after installation (further on the logging simply doesn't work) > Steps to Reproduce: > 1.Install DV with audit/command logging enabled > 2.Start DV with bin/standalone.sh, check that logging works > 3.Access http://localhost:9990/console/App.html#teiid-audit and unselect selected options > 4.Apply > 5.Select the previously deselected options again > 6.Apply > 7.See the server log in console > 8.When there is server reload between unselecting and reselecting the options, then the exception is not raised, but the logging doesn't work afterwards. > Actual results: > java.lang.IllegalArgumentException: Handler "TEIID_AUDIT_LOG" is not found > or > java.lang.IllegalArgumentException: Handler "TEIID_COMMAND_LOG" is not found > Expected results: > Logging configured again -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3241) Audit/Command Logging handler names do not match web console handler names

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3241?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3241: ------------------------------- Git Pull Request: https://github.com/teiid/teiid-extensions/pull/11 > Audit/Command Logging handler names do not match web console handler names > -------------------------------------------------------------------------- > > Key: TEIID-3241 > URL: https://issues.jboss.org/browse/TEIID-3241 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > > When changing configuration of Audit and Command logging via Web Management, an exception is thrown in specific usecase, see the steps to reproduce below. > Then even after server restart logging doesn't work. No changes noticed in standalone.xml during the configuration. > Version-Release number of selected component (if applicable): > DV 6.1.0 ER4 > How reproducible: > Once after installation (further on the logging simply doesn't work) > Steps to Reproduce: > 1.Install DV with audit/command logging enabled > 2.Start DV with bin/standalone.sh, check that logging works > 3.Access http://localhost:9990/console/App.html#teiid-audit and unselect selected options > 4.Apply > 5.Select the previously deselected options again > 6.Apply > 7.See the server log in console > 8.When there is server reload between unselecting and reselecting the options, then the exception is not raised, but the logging doesn't work afterwards. > Actual results: > java.lang.IllegalArgumentException: Handler "TEIID_AUDIT_LOG" is not found > or > java.lang.IllegalArgumentException: Handler "TEIID_COMMAND_LOG" is not found > Expected results: > Logging configured again -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3241) Audit/Command Logging handler names do not match web console handler names

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3241?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3241: ------------------------------------ Change the teiid-extension cli script that configures logging > Audit/Command Logging handler names do not match web console handler names > -------------------------------------------------------------------------- > > Key: TEIID-3241 > URL: https://issues.jboss.org/browse/TEIID-3241 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > > When changing configuration of Audit and Command logging via Web Management, an exception is thrown in specific usecase, see the steps to reproduce below. > Then even after server restart logging doesn't work. No changes noticed in standalone.xml during the configuration. > Version-Release number of selected component (if applicable): > DV 6.1.0 ER4 > How reproducible: > Once after installation (further on the logging simply doesn't work) > Steps to Reproduce: > 1.Install DV with audit/command logging enabled > 2.Start DV with bin/standalone.sh, check that logging works > 3.Access http://localhost:9990/console/App.html#teiid-audit and unselect selected options > 4.Apply > 5.Select the previously deselected options again > 6.Apply > 7.See the server log in console > 8.When there is server reload between unselecting and reselecting the options, then the exception is not raised, but the logging doesn't work afterwards. > Actual results: > java.lang.IllegalArgumentException: Handler "TEIID_AUDIT_LOG" is not found > or > java.lang.IllegalArgumentException: Handler "TEIID_COMMAND_LOG" is not found > Expected results: > Logging configured again -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3241) Audit/Command Logging handler names do not match web console handler names

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3241?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3241: ------------------------------- Summary: Audit/Command Logging handler names do not match web console handler names (was: JBoss Web Management Audit/Command Logging handler not found ) > Audit/Command Logging handler names do not match web console handler names > -------------------------------------------------------------------------- > > Key: TEIID-3241 > URL: https://issues.jboss.org/browse/TEIID-3241 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > > When changing configuration of Audit and Command logging via Web Management, an exception is thrown in specific usecase, see the steps to reproduce below. > Then even after server restart logging doesn't work. No changes noticed in standalone.xml during the configuration. > Version-Release number of selected component (if applicable): > DV 6.1.0 ER4 > How reproducible: > Once after installation (further on the logging simply doesn't work) > Steps to Reproduce: > 1.Install DV with audit/command logging enabled > 2.Start DV with bin/standalone.sh, check that logging works > 3.Access http://localhost:9990/console/App.html#teiid-audit and unselect selected options > 4.Apply > 5.Select the previously deselected options again > 6.Apply > 7.See the server log in console > 8.When there is server reload between unselecting and reselecting the options, then the exception is not raised, but the logging doesn't work afterwards. > Actual results: > java.lang.IllegalArgumentException: Handler "TEIID_AUDIT_LOG" is not found > or > java.lang.IllegalArgumentException: Handler "TEIID_COMMAND_LOG" is not found > Expected results: > Logging configured again -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3241) JBoss Web Management Audit/Command Logging handler not found

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3241?page=com.atlassian.jira.plugin... ] Van Halbert moved TEIIDWEBCN-11 to TEIID-3241: ---------------------------------------------- Project: Teiid (was: Teiid Web Console) Key: TEIID-3241 (was: TEIIDWEBCN-11) Affects Version/s: 8.7.1 (was: 1.2.0) Component/s: Tools (was: Server) > JBoss Web Management Audit/Command Logging handler not found > ------------------------------------------------------------- > > Key: TEIID-3241 > URL: https://issues.jboss.org/browse/TEIID-3241 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > > When changing configuration of Audit and Command logging via Web Management, an exception is thrown in specific usecase, see the steps to reproduce below. > Then even after server restart logging doesn't work. No changes noticed in standalone.xml during the configuration. > Version-Release number of selected component (if applicable): > DV 6.1.0 ER4 > How reproducible: > Once after installation (further on the logging simply doesn't work) > Steps to Reproduce: > 1.Install DV with audit/command logging enabled > 2.Start DV with bin/standalone.sh, check that logging works > 3.Access http://localhost:9990/console/App.html#teiid-audit and unselect selected options > 4.Apply > 5.Select the previously deselected options again > 6.Apply > 7.See the server log in console > 8.When there is server reload between unselecting and reselecting the options, then the exception is not raised, but the logging doesn't work afterwards. > Actual results: > java.lang.IllegalArgumentException: Handler "TEIID_AUDIT_LOG" is not found > or > java.lang.IllegalArgumentException: Handler "TEIID_COMMAND_LOG" is not found > Expected results: > Logging configured again -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3216) Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector

by Filip Elias (JIRA)

[ https://issues.jboss.org/browse/TEIID-3216?page=com.atlassian.jira.plugin... ] Filip Elias commented on TEIID-3216: ------------------------------------ Steven, I created a pull request, but I am not sure how to link it with this JIRA. > Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector > ---------------------------------------------------------------------------- > > Key: TEIID-3216 > URL: https://issues.jboss.org/browse/TEIID-3216 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Filip Elias > Assignee: Filip Elias > Fix For: Open To Community > > > Current plan is to use list-based feed of the Google Data API[1]. > There are three known issues: > performance - to delete/update 100 rows Teiid must generate 100 http requests > consistency - user wants to update 50 rows. After the 10th row is updated the connection could fail which would cause that 10 rows would be updated and 40 wouldn't. > headers - update, delete and and insert statements will be supported only for the spreadsheets that have a header for each column (headers are in the first row of a spreadsheet) > Select statement is implemented using Google Visualisation API, but this API doesn't support updates and doesn't return row numbers. > [1] https://developers.google.com/google-apps/spreadsheets/ -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3179) To support AS 7.4.0 requires changes to jboss-integration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3179?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3179: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1153703|https://bugzilla.redhat.com/show_bug.cgi?id=1153703] from ON_QA to VERIFIED > To support AS 7.4.0 requires changes to jboss-integration > --------------------------------------------------------- > > Key: TEIID-3179 > URL: https://issues.jboss.org/browse/TEIID-3179 > Project: Teiid > Issue Type: Enhancement > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > Fix For: 8.7.1 > > > When upgrading to use the BOM version 13, from 10, the jboss-integration breaks due to changes in the jboss as controller. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3240) Tranlator archetype creation: -Dversion option sets the version of parent

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3240?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3240: ------------------------------------- This is using old arch-type, I know we fixed bunch of version related stuff to accurately point which is arch-type version, which is teiid-version, which is translator version in the new code. See example here https://docs.jboss.org/author/display/TEIID/Archetype+Template+Translator... > Tranlator archetype creation: -Dversion option sets the version of parent > ------------------------------------------------------------------------- > > Key: TEIID-3240 > URL: https://issues.jboss.org/browse/TEIID-3240 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Juraj Duráni > Assignee: Van Halbert > > If new translator is created using command line, -Dversion option is set as version of parent project instead of version of actual translator. > pom file: > <parent> > <groupId>org.jboss.teiid</groupId> > <artifactId>connectors</artifactId> > <version>0.0.1</version> > </parent> > ... > <groupId>org.jboss.teiid.test.translator</groupId> > <artifactId>test-translator</artifactId> >  > <packaging>jar</packaging> > ... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2978) using LIKE on columns causes no results though they indeed exist

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2978?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2978: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1122976|https://bugzilla.redhat.com/show_bug.cgi?id=1122976] from ON_QA to VERIFIED > using LIKE on columns causes no results though they indeed exist > ---------------------------------------------------------------- > > Key: TEIID-2978 > URL: https://issues.jboss.org/browse/TEIID-2978 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Tom Johnston > Assignee: Van Halbert > Labels: modeshape, teiid > > Use of LIKE doesn't appear to work when querying modeshape through JDBC. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 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 December 2014