December 2016 - teiid-issues - Jboss List Archives

[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 resolved TEIID-3243. ----------------------------------- Resolution: Done Marking the original as resolved with the additional property issue captured as TEIID-4645 > 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 (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4647) Add Kerberos support to the MongoDB

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4647?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4647: ------------------------------------ It wasn't targeted for any specific version, but I think QE was trying to pick up all mongo related features and see where they were. And the biggest hurdle to all this is purchasing a required license in order to test Kerberos, and that will be dependent on when QE can obtain theirs. So I would defer this until QE gets their license, and at that point this can be scheduled for work. > Add Kerberos support to the MongoDB > ------------------------------------ > > Key: TEIID-4647 > URL: https://issues.jboss.org/browse/TEIID-4647 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > > Add support for kerberos in MongoDB resource adapter. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4647) Add Kerberos support to the MongoDB

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4647?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4647: ------------------------------------- No, also we do not have Enterprise MongoDB to test with. > Add Kerberos support to the MongoDB > ------------------------------------ > > Key: TEIID-4647 > URL: https://issues.jboss.org/browse/TEIID-4647 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > > Add support for kerberos in MongoDB resource adapter. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4647) Add Kerberos support to the MongoDB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4647?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4647: ------------------------------------- Assignee: (was: Steven Hawkins) [~vhalbert2] Is this being requested for 9.2, or can it be deferred until 10? [~rareddy] is the scope of work known here? > Add Kerberos support to the MongoDB > ------------------------------------ > > Key: TEIID-4647 > URL: https://issues.jboss.org/browse/TEIID-4647 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > > Add support for kerberos in MongoDB resource adapter. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4543) Rewrite parse/format of standard formats to cast instead

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4543?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4543: --------------------------------- Fix Version/s: 8.7.10.6_2 > Rewrite parse/format of standard formats to cast instead > -------------------------------------------------------- > > Key: TEIID-4543 > URL: https://issues.jboss.org/browse/TEIID-4543 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.10.6_2, 9.2 > > > Since parse/format functions have limited pushdown support, it would be better to treat the standard formats as casts instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4656) parseTimestamp issue with Oracle

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4656?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4656: --------------------------------- Fix Version/s: 8.7.10.6_2 > parseTimestamp issue with Oracle > -------------------------------- > > Key: TEIID-4656 > URL: https://issues.jboss.org/browse/TEIID-4656 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector, Query Engine > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.10.6_2, 9.2 > > > parseTimestamp is pushed as to_timestamp. However TO_TIMESTAMP is not generally valid unless the format string covers the entire string input value otherwise there is an exception about the picture ending. > This means in general that we cannot pushdown the parseDate/Time/Timestamp operations to oracle as that is behavioral different with the java format routines, which will process just to the end of the format string. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4519) JDG prevent execution of delete or update on child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4519?page=com.atlassian.jira.plugin... ] Van Halbert resolved TEIID-4519. -------------------------------- Resolution: Done > JDG prevent execution of delete or update on child objects > ---------------------------------------------------------- > > Key: TEIID-4519 > URL: https://issues.jboss.org/browse/TEIID-4519 > Project: Teiid > Issue Type: Bug > Components: JDG Connector > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 8.12.7.6_3 > > > When using JDG and complex pojos, delete query issued against child tables end with error. > * 1-1 relation: > When deleting a child object, whole parent object is deleted > * 1-n relation: > An exception is thrown: > {code:plain} > 13:31:28,926 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue91) Connector worker process failed for atomic-request=rKsoeHUfbaAW.21.0.21: org.teiid.translator.TranslatorException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:388) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.executeUpdate(ObjectUpdateExecution.java:137) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.execute(ObjectUpdateExecution.java:100) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:402) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) [:1.8.0_102] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_102] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at com.sun.proxy.$Proxy81.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_102] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_102] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_102] > Caused by: javax.script.ScriptException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectScriptEngine$1.eval(ObjectScriptEngine.java:144) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:372) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > ... 20 more > {code} > These two cases should be handled. Given the lack of DELETE support, all the DELETE queries on child entities should throw exception instead. > The DELETE on parent should be enabled though. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4519) JDG prevent execution of delete or update on child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4519?page=com.atlassian.jira.plugin... ] Van Halbert closed TEIID-4519. ------------------------------ These were only for 8.12.x > JDG prevent execution of delete or update on child objects > ---------------------------------------------------------- > > Key: TEIID-4519 > URL: https://issues.jboss.org/browse/TEIID-4519 > Project: Teiid > Issue Type: Bug > Components: JDG Connector > Affects Versions: 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 8.12.7.6_3 > > > When using JDG and complex pojos, delete query issued against child tables end with error. > * 1-1 relation: > When deleting a child object, whole parent object is deleted > * 1-n relation: > An exception is thrown: > {code:plain} > 13:31:28,926 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue91) Connector worker process failed for atomic-request=rKsoeHUfbaAW.21.0.21: org.teiid.translator.TranslatorException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:388) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.executeUpdate(ObjectUpdateExecution.java:137) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.execute(ObjectUpdateExecution.java:100) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:402) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) [:1.8.0_102] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_102] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at com.sun.proxy.$Proxy81.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_102] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_102] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_102] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_102] > Caused by: javax.script.ScriptException: TEIID31111 No such accessible property/method number on class java.util.ArrayList. > at org.teiid.translator.object.ObjectScriptEngine$1.eval(ObjectScriptEngine.java:144) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:372) [translator-object-8.12.6.6_3.jar:8.12.6.6_3] > ... 20 more > {code} > These two cases should be handled. Given the lack of DELETE support, all the DELETE queries on child entities should throw exception instead. > The DELETE on parent should be enabled though. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4543) Rewrite parse/format of standard formats to cast instead

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4543?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4543. ----------------------------------- Resolution: Done Added conversions to cast for parse/format date/time using the standard formats 'yyyy-MM-dd' and 'hh:mm:ss'. Timestamp was not handled yet as there isn't a specific convention for how the fractional seconds need to be formated/parsed - but that could be expanded upon later if needed. > Rewrite parse/format of standard formats to cast instead > -------------------------------------------------------- > > Key: TEIID-4543 > URL: https://issues.jboss.org/browse/TEIID-4543 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2 > > > Since parse/format functions have limited pushdown support, it would be better to treat the standard formats as casts instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4622) Adding new data quality functions from osDQ

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4622?page=com.atlassian.jira.plugin... ] Kylin Soong resolved TEIID-4622. -------------------------------- Resolution: Done Set to resolve due to documentation finished > Adding new data quality functions from osDQ > ------------------------------------------- > > Key: TEIID-4622 > URL: https://issues.jboss.org/browse/TEIID-4622 > Project: Teiid > Issue Type: Feature Request > Components: Common > Affects Versions: Open To Community > Environment: osdq-core and its dependency simmetric 3.0.0 is needed to run these functions > maven central location > http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22osdq-core%22 > Reporter: vivek singh > Assignee: Kylin Soong > Fix For: Open To Community > > Attachments: DateUtil.java, NumberUtil.java, StringUtil.java > > > Following functions have been added into osdq-core for integration with teiid. > String functions : > // Encrypting a string using key and AES encryption > String encrypt ( String val, String key) > String decrypt ( String val, String key) > // Fuzzy distance - similarity between two strings > float levestheindistance ( String a, String b) > float jarowinklerdistance( String a , String b) > float cosinedistance (String a, String b) > // Format check for PII ( personal information) > boolean isCreditCardFormat(String a) > boolean isSSNFormat(String a) > boolean isPhoneFormat(String a) > boolean isEmailFormat(String a) > boolean hasWhiteSpace(String a ) > Date Functions > // converting date into universal recognized format > long dateToEpoch(java.util.Date date) > Date epochToDate(long epoch) > Date epochToDate(long epoch, String TimeZone) > long diffInSec(date a, date b) > String convertToFormat ( Date a, String Format) > Numerical Functions > // Statistical functions > double stdDev(Number[] numSeries) > double range(Number[] numSeries) > double median(Number[] numSeries) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2016