June 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3125) Netezza translator - add support for the LIKE_REGEX predicate.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3125?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3125. --------------------------------- > Netezza translator - add support for the LIKE_REGEX predicate. > -------------------------------------------------------------- > > Key: TEIID-3125 > URL: https://issues.jboss.org/browse/TEIID-3125 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.9 > > > With version 6 of Jboss DV the Netezza translator doesn't support the LIKE_REGEX predicate. > Netezza doesn't support regular expression by default, but with the installation of SQL Extensions toolkit this functionality is added. After installation Netezza provide the regular expression functions: > regexp_extract() > regexp_extract_all() > regexp_extract_all_sp() > regexp_extract_sp() > regexp_instr() > regexp_like() > regexp_match_count() > regexp_replace() > regexp_replace_sp() > IBM Netezza SQL Extensions toolkit is an optional package for IBM Netezza data warehouse appliances. > After installing this toolkit on Netezza and requires that regular expression in JBoss DV syntax are pushed down (delegated) to Netezza to prevent that filtering in the Jboss DV server most be done. > So please provide a configurable option in the Netezza translator of Jboss DV by which we can enable the LIKE_REGEX predicate for Netezza. This option when enabled will assume that the Netezza SQL extension toolkit is installed and the function regexp_like() is available. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3235) IndexOutOfBoundsException when using GROUP BY

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3235?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3235. --------------------------------- > IndexOutOfBoundsException when using GROUP BY > --------------------------------------------- > > Key: TEIID-3235 > URL: https://issues.jboss.org/browse/TEIID-3235 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.7.1, 8.10 > > Attachments: mongo-vdb.xml > > > Issuing the following queries that cause the IndexOutofBoundsException: > SELECT IntKey, SUM(IntNum) FROM BQT1.SmallA GROUP BY intKey > SELECT IntKey, IntNum FROM BQT1.SmallA GROUP BY IntKey, IntNum > Will attach VDB. > 0:07:04,905 ERROR [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue14) Connector worker process failed for atomic-request=XEIlvkzunTej.7.1.0: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1 > at java.util.ArrayList.rangeCheck(ArrayList.java:604) [rt.jar:1.7.0_25] > at java.util.ArrayList.get(ArrayList.java:382) [rt.jar:1.7.0_25] > at org.teiid.translator.mongodb.MongoDBQueryExecution.next(MongoDBQueryExecution.java:124) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:384) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:202) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:301) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3114) Add an option to not normalize salesforce names

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3114?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3114. --------------------------------- > Add an option to not normalize salesforce names > ----------------------------------------------- > > Key: TEIID-3114 > URL: https://issues.jboss.org/browse/TEIID-3114 > Project: Teiid > Issue Type: Enhancement > Components: Salesforce Connector > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > The normalization process for salesforce names can be non-obvious to follow. The only requirement is that column names don't contain a period - other than that we should have an option to allow the names to be imported more or less undisturbed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3009) perform projection minimization on with commands

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3009?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3009. --------------------------------- > perform projection minimization on with commands > ------------------------------------------------ > > Key: TEIID-3009 > URL: https://issues.jboss.org/browse/TEIID-3009 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > We currently treat the with clause as the creation of a temporary table at a query scope, but we can do projection minimization based upon the referenced columns. This is somewhat tricky with the current planning logic as we must first plan the with clause to determine if it's eligible for pushdown to then plan the main command. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 closed TEIID-3242. --------------------------------- > 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.9.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.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3237) Prevent processing cross joins with unknown cardinalities

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3237?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3237. --------------------------------- > Prevent processing cross joins with unknown cardinalities > --------------------------------------------------------- > > Key: TEIID-3237 > URL: https://issues.jboss.org/browse/TEIID-3237 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > The optimizer will select plans with cross joins (particularly with a parent dependent join) when the join is to be processed in Teiid and the cardinality of both sides of the join are unknown. > We should prefer non cross join plans in these scenarios. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3315) problem with function TRIM

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3315?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3315. --------------------------------- > problem with function TRIM > -------------------------- > > Key: TEIID-3315 > URL: https://issues.jboss.org/browse/TEIID-3315 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Labels: stringfunction > Fix For: 8.10 > > > I have a database that contains some columns with multiple values separated with comma . So I'm trying to use a combination of case, substring and trim to split these values into multiple colums. > The following statement part does not work: > case when pos2 = 0 then trim(substring(Description, pos1+1)) > end as bed > TEIID31100 Parsing error: Encountered "+1)[*])[*] end as" at line 3, column 68. > If I add ' ' FROM to the trim statement it does work and returns a correct result. > working statement: > case when pos2 = 0 then trim(' ' FROM substring(Description, pos1+1)) > end as bed -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3064) Sybase metadata loading fails

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3064?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3064. --------------------------------- > Sybase metadata loading fails > ----------------------------- > > Key: TEIID-3064 > URL: https://issues.jboss.org/browse/TEIID-3064 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Filip Elias > Assignee: Steven Hawkins > Attachments: server.log > > > Sybase metadata loading fails[1] when deploying dynamic vdb. > The problem is in JDBCMetdataProcessor.getForeignKeys. Method loads FKs from all tables, but it fails when it tries to load FKs from table sysquerymetrics. The problem seems to be that sysquerymetrics is not a system table, it is a view. > [1] Reason:TEIID11010 com.sybase.jdbc4.jdbc.SybSQLException: No such object or user exists in the database. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2990) MongoDB: Usage of lookup() function throws an exception

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2990?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2990. --------------------------------- > MongoDB: Usage of lookup() function throws an exception > ------------------------------------------------------- > > Key: TEIID-2990 > URL: https://issues.jboss.org/browse/TEIID-2990 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.8, 8.7.1 > > Attachments: server.log > > > Exception[1] is thrown when function lookup() is used in SQL query. > Mongo translator doesn't support selection of constants only, which causes the exception(select 1, select 'hi' from smalla). > {code} > [1] 3:59:20,997 ERROR [org.teiid.CONNECTOR] (Worker5_QueryProcessorQueue6) Connector worker process failed for atomic-request=Ef2Z7E0246by.1.5.3: com.mongodb.CommandFailureException: { "serverUsed" : "localhost/127.0.0.1:27017" , "errmsg" : "exception: $projection requires at least one output field" , "code" : 16403 , "ok" : 0.0} > at com.mongodb.CommandResult.getException(CommandResult.java:71) > {code} > Server log is in the attachment. > Sample query: > {code} > SELECT BQT1.SmallA.IntKey FROM BQT1.SmallA, BQT1.SmallB WHERE BQT1.SmallA.IntKey= lookup('BQT1.SmallB', 'IntKey', 'StringKey', BQT1.SmallA.StringKey) ORDER BY IntKey > {code} > Generated mongo commands: > {code} > { aggregate: "smalla", pipeline: [ { $project: { _m0: "$INTKEY", _m1: "$STRINGKEY" } } ] } > {code} > and > {code} > { aggregate: "smallb", pipeline: [ { $project: {} } ] } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3249) XMLCOMMENT missing validation

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3249?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3249. --------------------------------- > XMLCOMMENT missing validation > ----------------------------- > > Key: TEIID-3249 > URL: https://issues.jboss.org/browse/TEIID-3249 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.10 > > > XMLCOMMENT should check if the string contains -- or ends with - to ensure that the comment content is valid. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 June 2015