[JBoss JIRA] (TEIID-3937) Multiplying two columns in CASE statement overrides pushdown (Impala)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3937?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3937:
---------------------------------------
We don't have a type mapping for bigdecimal unless impala reports version 2 or greater. What version of impala are you using?
If it's an older version of impala we could add an option to map bigdecimal to double.
> Multiplying two columns in CASE statement overrides pushdown (Impala)
> ---------------------------------------------------------------------
>
> Key: TEIID-3937
> URL: https://issues.jboss.org/browse/TEIID-3937
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.4
> Environment: Ubuntu Trusty
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
>
> In the Impala translator, pushdown doesn't happen when two columns are multiplied in the THEN portion of a CASE statement with bigdecimal data type.
> //this should push down but does not
> CASE WHEN column1 IS NOT NULL
> THEN column1 * column2
> ELSE column3 END
> //but you can multiply the columns by a constant and it will push down
> CASE WHEN column1 IS NOT NULL
> THEN column1 * 34567
> ELSE column3 END
> //or
> CASE WHEN column1 IS NOT NULL
> THEN 34567 * column2
> ELSE column3 END
> //or casting to consistent datatypes with BIGDECIMAL output
> CASE WHEN column1 IS NOT NULL
> THEN cast(column1 as BIGDECIMAL ) * cast(column2 as BIGDECIMAL )
> ELSE cast(column3 as BIGDECIMAL ) END
> //BUT output it as double with the cast statement above changed and it does push down (so floating point works)
> CASE WHEN column1 IS NOT NULL
> THEN cast(column1 as double ) * cast(column2 as double)
> ELSE cast(column3 as double) END
> Source data types:
> Column1 is BIGDECIMAL
> Column2 is BIGINT/LONG
> Column3 is BIGDECIMAL
> Output column is BIGDECIMAL
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3747) Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3747?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3747:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1270336|https://bugzilla.redhat.com/show_bug.cgi?id=1270336] from NEW to MODIFIED
> Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates
> ---------------------------------------------------------------------------------------
>
> Key: TEIID-3747
> URL: https://issues.jboss.org/browse/TEIID-3747
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.12
>
>
> deployed a dynamic vdb using CLI: deploy teiidfiles/vdb/portfolio-vdb.xml
> then in Designer, tried to deploy the same named VDB, but as a .vdb and the deployment fails with errors indicating duplicate service:
> 11:26:31,301 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."Portfolio.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Portfolio.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "Portfolio.vdb"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.teiid.ds-listener.Portfolio.1./accounts-ds is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3793) Push Teiid function LOCATE() to SQL Server
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3793?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3793.
---------------------------------
> Push Teiid function LOCATE() to SQL Server
> ------------------------------------------
>
> Key: TEIID-3793
> URL: https://issues.jboss.org/browse/TEIID-3793
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Connector
> Affects Versions: 8.7.1.6_2
> Environment: JBOSS DV 6.2
> Microsoft SQL Server 10.50.1600.1
> Reporter: Jean-Pierre Matsumoto
> Assignee: Steven Hawkins
> Fix For: 8.12.2, 8.13
>
>
> We have some Teiid views with query similar to:
> SELECT col1
> FROM tableA
> WHERE SUBSTRING(col1, 1, LOCATE(' ', col1)) = 'PREFIX'
> SQL Server receives a full scan of col1 table without WHERE:
> SELECT col1
> FROM tableA
> Because Teiid LOCATE() function is not translated to CHARINDEX() SQL Server function (SUBSTRING is translated).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months