December 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2407) Support temporary table on commit behavior

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2407?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2407: --------------------------------------- This will be done in part for TEIID-3073, which uses an explicit on commit clause. At this time we'll just add support for PRESERVE ROWS, which is our default behavior. DROP as mentioned above is not standard and is probably not needed given that we already do block scoping. DELETE ROWS is somewhat difficult to implement as requires a commit hook on TempTableStore that doesn't currently exist (we just have the usage based synchronization). > Support temporary table on commit behavior > ------------------------------------------ > > Key: TEIID-2407 > URL: https://issues.jboss.org/browse/TEIID-2407 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Fix For: 8.10 > > > Now that our temporary tables are transactionally aware we should support the on commit clause. > Our current default for on commit is effectively "preserve rows", which is contrary to the sql specification. We should also offer delete rows and possible drop (similar to pg sql). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2407) Support temporary table on commit behavior

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2407?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2407: ---------------------------------- Fix Version/s: 8.10 > Support temporary table on commit behavior > ------------------------------------------ > > Key: TEIID-2407 > URL: https://issues.jboss.org/browse/TEIID-2407 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Fix For: 8.10 > > > Now that our temporary tables are transactionally aware we should support the on commit clause. > Our current default for on commit is effectively "preserve rows", which is contrary to the sql specification. We should also offer delete rows and possible drop (similar to pg sql). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-999) Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-999?page=com.atlassian.jira.plugin.... ] Steven Hawkins resolved TEIID-999. ---------------------------------- Resolution: Out of Date There is now both an excel-odbc and and excel translator. > Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors > --------------------------------------------------------------------------------- > > Key: TEIID-999 > URL: https://issues.jboss.org/browse/TEIID-999 > Project: Teiid > Issue Type: Sub-task > Components: Misc. Connectors > Environment: MS Excel 2003 > Reporter: Larry O'Leary > Fix For: Open To Community > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Create a capabilities set that can be used by the MS Access and MS Excel connectors. We currently offer the MS Excel connector which is using the generic JDBC capabilities and translators and the MS Access connector which is using its own capabilities and translators but they do not reflect MS Access. > The replacement connector types should work very much like the current ones but reflect the base capabilities offered by MS JET 4 and specific capabilities as defined by the MS Excel and MS Access limitations to the MS JET 4 implementation. At bare minimum we should support push-down of all currently defined capabilities and remove any current ones that are not valid for MS JET/MS Access/MS Excel. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1741) Record level audit trail in teiid log files

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1741?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1741: ---------------------------------- Fix Version/s: 8.10 Component/s: Connector API Query Engine As much as this seems like it will lead to data retention issues with voluminous logs, this issues keeps cropping up as a custom request. We should look at adding a built-in trace logger or an extension of the command logger for this. > Record level audit trail in teiid log files > ------------------------------------------- > > Key: TEIID-1741 > URL: https://issues.jboss.org/browse/TEIID-1741 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Reporter: Monika Ahuja > Fix For: 8.10, Open To Community > > > In order to track the audit trail for patient identified information access, we would like to track the executed queries, results as well as the timestamps for each user's query and its result. Essentially we need a report providing the list of Medical Record Numbers accessed by each user id and I think we can use the Logs to track that (unless you suggest a better way). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2194) Allow the mat view cache hint to be specified via a property

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2194?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2194. ----------------------------------- Resolution: Done Added and documented extension based support for internal materialization properties. We'll want to keep bringing features/functionality from each of the materialization approaches together - such as having a proactive ttl refresh for internal like is done for external. > Allow the mat view cache hint to be specified via a property > ------------------------------------------------------------ > > Key: TEIID-2194 > URL: https://issues.jboss.org/browse/TEIID-2194 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > Setting the mat cache hint via a property is useful so that it can be changed independently of the view definition. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 3 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3243?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3243. --------------------------------- Labels: Alpha2 (was: ) Fix Version/s: 8.10 Resolution: Done Provided support to allow multiple aggregation functions in the select statement, that are based on same column or different columns. For ex: {code:sql} SELECT COUNT(intnum) AS c_0, SUM(intnum) AS c_1 FROM bqt1.smalla SELECT COUNT(intkey) AS c_0, SUM(intnum) AS c_1 FROM bqt1.smalla {code} Also provided way to turn off "count(key)" capability in translator properties "SupportsAggregateCount" > 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 > Labels: Alpha2 > Fix For: 8.10 > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2194) Allow the mat view cache hint to be specified via a property

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2194?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2194: --------------------------------------- The ttl property already exists. The new properties would be prefer memory and updatable. > Allow the mat view cache hint to be specified via a property > ------------------------------------------------------------ > > Key: TEIID-2194 > URL: https://issues.jboss.org/browse/TEIID-2194 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > Setting the mat cache hint via a property is useful so that it can be changed independently of the view definition. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3209) Issues with mat view ttl

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3209?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3209. ----------------------------------- Fix Version/s: 8.10 Resolution: Done Made TTL optional and prefers the property if the cache hint is present. And made on error action optional defaulting to WAIT. > Issues with mat view ttl > ------------------------ > > Key: TEIID-3209 > URL: https://issues.jboss.org/browse/TEIID-3209 > Project: Teiid > Issue Type: Bug > Components: Documentation, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > The docs / code have matview_ttl as required, but the code will also prefer to use the cache hint ttl if it also supplied. I believe the cache hint should not be used in this case. > Generally there is also: TEIID-2194 which we should probably prefer properties over the cache hint because they are more targeted and can be more easily be manipulated at runtime. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2194) Allow the mat view cache hint to be specified via a property

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2194?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2194: ---------------------------------- Fix Version/s: 8.10 > Allow the mat view cache hint to be specified via a property > ------------------------------------------------------------ > > Key: TEIID-2194 > URL: https://issues.jboss.org/browse/TEIID-2194 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > Setting the mat cache hint via a property is useful so that it can be changed independently of the view definition. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3209) Issues with mat view ttl

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3209?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3209: --------------------------------------- I would go further to make ttl and on error action optional. > Issues with mat view ttl > ------------------------ > > Key: TEIID-3209 > URL: https://issues.jboss.org/browse/TEIID-3209 > Project: Teiid > Issue Type: Bug > Components: Documentation, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > The docs / code have matview_ttl as required, but the code will also prefer to use the cache hint ttl if it also supplied. I believe the cache hint should not be used in this case. > Generally there is also: TEIID-2194 which we should probably prefer properties over the cache hint because they are more targeted and can be more easily be manipulated at runtime. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 3 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