December 2014 - teiid-issues - Jboss List Archives

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3216?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3216: ---------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/377 > 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-3244) XML Choice is not being evaluated as expected

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3244?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-3244 at 12/5/14 10:58 AM: ----------------------------------------------------------------- This may also be due to logic in Designer in setting the choice criteria. was (Author: shawkins): This may also be due to logic in Designer in setting the choice criteria. It may also not get worked since xml document models as they currently exist shouldn't make it to Teiid 8. > XML Choice is not being evaluated as expected > --------------------------------------------- > > Key: TEIID-3244 > URL: https://issues.jboss.org/browse/TEIID-3244 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Debbie Steigner > Priority: Minor > Fix For: Open To Community > > > We have an XML View model, built on a schema that includes choice nodes. We've used the choice editor to define a default choice; however, no data comes back for any of these choices, despite the fact that data does exist. > It appears that MMX is not executing the queries under the default choice nodes. > As a second test, we tried setting criteria that would always be true. Still, the choice nodes were not executed. > Finally, we tried setting criteria that would never be true, and told the choice editor to throw an exception if the criteria was not met. No exception was thrown. This seems to indicate that MMX simply isn't evaluating this part of the document. > Finally, I have an theory about what could be the source of the problem, based on what I did differently during the rebuild. If you click on the "Subject" mapping class, notice that "choice" gets highlighted. In my rebuild, when I click on "Subject", the "category" gets highlighted, but the choice above it does not. The behavior is problematic in the first case, but works as expected in the second case. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3244) XML Choice is not being evaluated as expected

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3244?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3244: ---------------------------------- Assignee: (was: Steven Hawkins) > XML Choice is not being evaluated as expected > --------------------------------------------- > > Key: TEIID-3244 > URL: https://issues.jboss.org/browse/TEIID-3244 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Debbie Steigner > Priority: Minor > Fix For: Open To Community > > > We have an XML View model, built on a schema that includes choice nodes. We've used the choice editor to define a default choice; however, no data comes back for any of these choices, despite the fact that data does exist. > It appears that MMX is not executing the queries under the default choice nodes. > As a second test, we tried setting criteria that would always be true. Still, the choice nodes were not executed. > Finally, we tried setting criteria that would never be true, and told the choice editor to throw an exception if the criteria was not met. No exception was thrown. This seems to indicate that MMX simply isn't evaluating this part of the document. > Finally, I have an theory about what could be the source of the problem, based on what I did differently during the rebuild. If you click on the "Subject" mapping class, notice that "choice" gets highlighted. In my rebuild, when I click on "Subject", the "category" gets highlighted, but the choice above it does not. The behavior is problematic in the first case, but works as expected in the second case. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3244) XML Choice is not being evaluated as expected

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3244?page=com.atlassian.jira.plugin... ] Steven Hawkins moved JBEDSP-1238 to TEIID-3244: ----------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-3244 (was: JBEDSP-1238) Component/s: Query Engine (was: Server) Fix Version/s: Open To Community (was: Future Versions) > XML Choice is not being evaluated as expected > --------------------------------------------- > > Key: TEIID-3244 > URL: https://issues.jboss.org/browse/TEIID-3244 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Minor > Fix For: Open To Community > > > We have an XML View model, built on a schema that includes choice nodes. We've used the choice editor to define a default choice; however, no data comes back for any of these choices, despite the fact that data does exist. > It appears that MMX is not executing the queries under the default choice nodes. > As a second test, we tried setting criteria that would always be true. Still, the choice nodes were not executed. > Finally, we tried setting criteria that would never be true, and told the choice editor to throw an exception if the criteria was not met. No exception was thrown. This seems to indicate that MMX simply isn't evaluating this part of the document. > Finally, I have an theory about what could be the source of the problem, based on what I did differently during the rebuild. If you click on the "Subject" mapping class, notice that "choice" gets highlighted. In my rebuild, when I click on "Subject", the "category" gets highlighted, but the choice above it does not. The behavior is problematic in the first case, but works as expected in the second case. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3242?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3242. ----------------------------------- Resolution: Done Removed the initial create permission check to ensure that we get the proper message. Also corrected the checks of foreign temp tables against their respective permissions. > 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 commented on TEIID-3241: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1170583|https://bugzilla.redhat.com/show_bug.cgi?id=1170583] from NEW to ASSIGNED > 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 > Fix For: 8.7.1 > > > 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: ------------------------------- Fix Version/s: 8.7.1 > 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 > Fix For: 8.7.1 > > > 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 resolved TEIID-3241. -------------------------------- Resolution: Done > 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 > Fix For: 8.7.1 > > > 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-3243) MongoDB: doens't support more than 1 aggregation in SQL

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3243?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3243: ---------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) I think there was an issue with MongoDB only supporting count(*), so there is only limited support for a general count aggregate. > MongoDB: doens't support more than 1 aggregation in SQL > -------------------------------------------------------- > > Key: TEIID-3243 > URL: https://issues.jboss.org/browse/TEIID-3243 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.8 > Environment: MongoDB with Teiid > Reporter: Ivan Chan > Assignee: Ramesh Reddy > > Got exception if I have more than 1 aggregation in SQL for MongoDB: > Original SQL > SELECT COUNT(MongoNestedDocDS.addresst.age) AS c_0, SUM(MongoNestedDocDS.addres > st.age) AS c_1 FROM MongoNestedDocDS.addresst LIMIT 1000 > Got exception: > Caused by: org.teiid.jdbc.TeiidSQLException: TEIID30504 -1880007235: TEIID18024 multiple aggregate symbols are not sup > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135) > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71) > at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:667) > at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:63) > at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:515) > at org.teiid.client.util.ResultsFuture.addCompletionListener(ResultsFuture.java:148) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:511) > at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261) > at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java:233) > Can we consider to use in memory engine instead if more than 1 aggregation? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3243) MongoDB: doens't support more than 1 aggregation in SQL

by Ivan Chan (JIRA)

Ivan Chan created TEIID-3243: -------------------------------- Summary: MongoDB: doens't support more than 1 aggregation in SQL Key: TEIID-3243 URL: https://issues.jboss.org/browse/TEIID-3243 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.8 Environment: MongoDB with Teiid Reporter: Ivan Chan Assignee: Steven Hawkins Got exception if I have more than 1 aggregation in SQL for MongoDB: Original SQL SELECT COUNT(MongoNestedDocDS.addresst.age) AS c_0, SUM(MongoNestedDocDS.addres st.age) AS c_1 FROM MongoNestedDocDS.addresst LIMIT 1000 Got exception: Caused by: org.teiid.jdbc.TeiidSQLException: TEIID30504 -1880007235: TEIID18024 multiple aggregate symbols are not sup at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135) at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71) at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:667) at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:63) at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:515) at org.teiid.client.util.ResultsFuture.addCompletionListener(ResultsFuture.java:148) at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:511) at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261) at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java:233) Can we consider to use in memory engine instead if more than 1 aggregation? -- 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