[JBoss JIRA] (TEIID-5184) Clob not supported in dynamic VDB
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-5184?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated TEIID-5184:
---------------------------------
Fix Version/s: 8.12.14.6_4
> Clob not supported in dynamic VDB
> ---------------------------------
>
> Key: TEIID-5184
> URL: https://issues.jboss.org/browse/TEIID-5184
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: …
[View More]Aditi Patel
> Assignee: Steven Hawkins
> Fix For: 10.1, 9.3.6, 10.0.2, 8.12.14.6_4
>
>
> I have updated the Jconnect driver. The current version is 7.07. Still I am facing some differnt error.
>
> {color:red}07:47:01,145 INFO [org.teiid.CONNECTOR] (Worker10_async-teiid-threads10) SybaseExecutionFactory Commit=true;DatabaseProductName=Sybase IQ;DatabaseProductVersion=SAP IQ/16.1.020.528/10528/P/sp02/Sun_x64/OS 5.11/64bit/2017-07-14 13:57:25;DriverMajorVersion=7;DriverMajorVersion=0;DriverName=jConnect (TM) for JDBC (TM);DriverVersion=jConnect (TM) for JDBC(TM)/7.07 SP133 (Build 27244)/P/EBF24376/JDK 1.6.0/jdbcmain/DEBUG/Thu Mar 26 04:57:02 PDT 2015;IsolationLevel=1
> 07:47:02,529 INFO [org.teiid.RUNTIME] (Worker9_async-teiid-threads9) TEIID50030 VDB ST_VDB.1 model "SrcModel_6" metadata loaded. End Time: 12/14/17 7:47 AM
> 07:47:07,194 INFO [org.teiid.RUNTIME] (Worker8_async-teiid-threads8) TEIID50030 VDB ST_VDB.1 model "SrcModel_2" metadata loaded. End Time: 12/14/17 7:47 AM
> 07:47:58,354 INFO [org.teiid.RUNTIME] (Worker10_async-teiid-threads10) TEIID50030 VDB ST_VDB.1 model "SrcModel_4" metadata loaded. End Time: 12/14/17 7:47 AM
> 07:48:03,510 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker10_async-teiid-threads10) TEIID40003 VDB ST_VDB.1 is set to ACTIVE
>
> Error Log:
> 07:52:45,561 ERROR [org.teiid.PROCESSOR] (Worker7_QueryProcessorQueue425) Settto6t5XMi TEIID30019 Unexpected exception for request Settto6t5XMi.32: java.lang.NullPointerException
> at org.teiid.core.types.ClobImpl.<init>(ClobImpl.java:116)
> at org.teiid.common.buffer.LobManager.persistLob(LobManager.java:230)
> at org.teiid.common.buffer.LobManager.updateReferences(LobManager.java:141)
> at org.teiid.common.buffer.TupleBuffer.addTupleBatch(TupleBuffer.java:203)
> at org.teiid.query.processor.BatchCollector.flushBatchDirect(BatchCollector.java:230)
> at org.teiid.dqp.internal.process.RequestWorkItem$1.flushBatchDirect(RequestWorkItem.java:686)
> at org.teiid.query.processor.BatchCollector.flushBatch(BatchCollector.java:224)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:195)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:477)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:349)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:275)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {color}
> That looks to be a bug with the getSubString method of Sybase clobs. They are returning null when it is not expected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
6 years, 10 months
[JBoss JIRA] (TEIID-4756) Improve log messages when using an UDAF without the required classes defined in VDB
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-4756?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated TEIID-4756:
---------------------------------
Fix Version/s: 8.12.14.6_4
> Improve log messages when using an UDAF without the required classes defined in VDB
> -----------------------------------------------------------------------------------
>
> Key: TEIID-4756
> URL: https://issues.jboss.org/browse/TEIID-4756
> Project: …
[View More]Teiid
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 9.1.2
> Environment: * WildFly 10
> * Teiid 9.1.2
> * CentOs 7
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Fix For: 9.2, 8.12.14.6_4
>
>
> When using an _UDAF_ in a _VDB_, the required *JAVA_CLASS* and *JAVA_METHOD* are specified in the _VDB_.
> When for some reason the _JAVA_CLASS_ or _JAVA_METHOD_ do not exist in the library, the message from the system is quite imperceptible.
> In the following log excerpt, _GlobalTitleRangeCheck_ class does not exist in the _jar_ _rangecreator_. The model name that is defining the _VIRTUAL FUNCTION_ is _RangeGroupConcat_. The _VDB_ name is _CountryServiceListVDB_.
> {panel:title=Log excerpt}
> DEBUG [org.teiid.RUNTIME] (Worker53_async-teiid-threads203) TEIID50104 VDB CountryServiceListVDB.1 model "RangeGroupConcat" Using translator null and connection null to load metadata.
> ...
> INFO [org.teiid.RUNTIME] (Worker53_async-teiid-threads203) TEIID40073 The metadata for the VDB CountryServiceListVDB.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy.
> INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker53_async-teiid-threads203) TEIID40003 VDB CountryServiceListVDB.1 is set to FAILED
> {panel}
> As observed from the log excerpt, the only possible hint to know what the problem is with the _FAILED_ deploy might be:
> _model "RangeGroupConcat" Using translator null and connection null to load metadata._
> But this is a normal logging message that doesn't have nothing to do with the real problem.
> When putting the entire system logging _ALL_ levels, then is easy to see what the problem is:
> {panel:title=Log excerpt}
> DEBUG [org.teiid.RUNTIME] (Worker52_async-teiid-threads202) TEIID50104 VDB CountryServiceListVDB.1 model "RangeGroupConcat" Using translator null and connection null to load metadata.
> INFO [org.teiid.RUNTIME] (Worker52_async-teiid-threads202) TEIID50030 VDB CountryServiceListVDB.1 model "RangeGroupConcat" metadata loaded. End Time: 10/02/17 10:56
> TRACE [org.jboss.modules] (Worker52_async-teiid-threads202) Finding class com.truphone.teiid.udaf.GlobalTitleRangeCheck from Module "deployment.countryServiceList-vdb.xml:main" from Service Module Loader
> TRACE [org.jboss.modules] (Worker52_async-teiid-threads202) Finding local class com.truphone.teiid.udaf.GlobalTitleRangeCheck from Module "mnom.rangecreator:main" from local module loader @33e5ccce (finder: local module finder @5a42bbf4 (roots: /home/mnom/teiid/teiid-9.1.2/modules,/home/mnom/teiid/teiid-9.1.2/modules/system/layers/dv,/home/mnom/teiid/teiid-9.1.2/modules/system/layers/base))
> TRACE [org.jboss.modules] (Worker52_async-teiid-threads202) Loading class com.truphone.teiid.udaf.GlobalTitleRangeCheck locally from Module "mnom.rangecreator:main" from local module loader @33e5ccce (finder: local module finder @5a42bbf4 (roots: /home/mnom/teiid/teiid-9.1.2/modules,/home/mnom/teiid/teiid-9.1.2/modules/system/layers/dv,/home/mnom/teiid/teiid-9.1.2/modules/system/layers/base))
> TRACE [org.jboss.modules] (Worker52_async-teiid-threads202) No local specification found for class com.truphone.teiid.udaf.GlobalTitleRangeCheck in Module "mnom.rangecreator:main" from local module loader @33e5ccce (finder: local module finder @5a42bbf4 (roots: /home/mnom/teiid/teiid-9.1.2/modules,/home/mnom/teiid/teiid-9.1.2/modules/system/layers/dv,/home/mnom/teiid/teiid-9.1.2/modules/system/layers/base))
> TRACE [org.jboss.modules] (Worker52_async-teiid-threads202) Class com.truphone.teiid.udaf.GlobalTitleRangeCheck not found from Module "deployment.countryServiceList-vdb.xml:main" from Service Module Loader
> INFO [org.teiid.RUNTIME] (Worker52_async-teiid-threads202) TEIID40073 The metadata for the VDB CountryServiceListVDB.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy.
> INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker52_async-teiid-threads202) TEIID40003 VDB CountryServiceListVDB.1 is set to FAILED
> {panel}
> Here it is observable what the real problem is:
> _No local specification found for class com.truphone.teiid.udaf.GlobalTitleRangeCheck in Module "mnom.rangecreator:main"_
> So, to avoid unnecessarily losing time to investigate what the problem is, the message that is currently in *TRACE* level should be in, at least, *INFO* level.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
6 years, 10 months
[JBoss JIRA] (TEIID-5355) Allow for additional partitioning columns in multisource
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5355:
-------------------------------------
Summary: Allow for additional partitioning columns in multisource
Key: TEIID-5355
URL: https://issues.jboss.org/browse/TEIID-5355
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
In multi-source planning only the multi-source column is recognized as …
[View More]partitioned. It would be beneficial to allow other source columns to be seen as fully partitioned across their respective sources - even if we don't fully capture the partitioning scheme.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
6 years, 10 months
[JBoss JIRA] (TEIID-5354) Different results for a query with GROUP BY and SUM(1) (summation of the number 1) when there is a LEFT or INNER JOIN involved
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-5354?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-5354:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1584391
Bugzilla Update: Perform
> Different results for a query with GROUP BY and SUM(1) (summation of the number 1) when there is a LEFT or INNER JOIN involved
> ---------------------------------------------------------------------------------…
[View More]---------------------------------------------
>
> Key: TEIID-5354
> URL: https://issues.jboss.org/browse/TEIID-5354
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 10.2
> Environment: teiid-10.2.0 on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 11.0, 10.3.2, 10.2.3
>
> Attachments: address_pg.sql, stateprovince_mysql.sql
>
>
> Teiid returns different results for a query with GROUP BY and SUM(1) (summation of the number 1) when there is a LEFT or INNER JOIN involved.
> There are two problems: a) incorrect check in MergeJoinStrategy.compareToPrevious method which generates TEIID31202 exception and b) a bug in algorithm of join itself which leads to incorrect results.
> To reproduce the bug, please, run the following queries and compare theSum and theCount column values:
> {code:sql}
> select r.city,
> sum(1) as theSum
> ,count(*) as theCount
> from "dsp.address_pg" r
> left join "adventureworks.stateprovince" c on "r.stateprovinceid" = "c.stateprovinceid"
> group by r.city
> order by r.city ;;
> {code}
> {code:sql}
> select r.city,
> sum(1) as theSum
> ,count(*) as theCount
> from "dsp.address_pg" r
> inner join "adventureworks.stateprovince" c on "r.stateprovinceid" = "c.stateprovinceid"
> group by r.city
> order by r.city ;;
> {code}
> but the following queries return correct results:
> {code:sql}
> select r.city,
> sum(1) as theSum
> ,count(*) as theCount
> from "dsp.address_pg" r
> right join "adventureworks.stateprovince" c on "r.stateprovinceid" = "c.stateprovinceid"
> group by r.city
> order by r.city ;;
> {code}
> the second one is also correct (LEFT JOIN) but uses window function:
> {code:sql}
> select distinct city,
> sum(1) OVER (PARTITION BY city) as theSum
> ,count(*) OVER (PARTITION BY city) as theCount
> from "dsp.address_pg" r
> left join "adventureworks.stateprovince" c on "r.stateprovinceid" = "c.stateprovinceid"
> order by r.city ;;
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
6 years, 10 months
[JBoss JIRA] (TEIID-5354) Different results for a query with GROUP BY and SUM(1) (summation of the number 1) when there is a LEFT or INNER JOIN involved
by dalex dalex (JIRA)
[ https://issues.jboss.org/browse/TEIID-5354?page=com.atlassian.jira.plugin... ]
dalex dalex commented on TEIID-5354:
------------------------------------
[~shawkins] thx a lot for the quick fix, I've just checked it and these changes helped me.
> Different results for a query with GROUP BY and SUM(1) (summation of the number 1) when there is a LEFT or INNER JOIN involved
> -----------------------------------------------------------------------------------------------------------------…
[View More]-------------
>
> Key: TEIID-5354
> URL: https://issues.jboss.org/browse/TEIID-5354
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 10.2
> Environment: teiid-10.2.0 on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 11.0, 10.3.2, 10.2.3
>
> Attachments: address_pg.sql, stateprovince_mysql.sql
>
>
> Teiid returns different results for a query with GROUP BY and SUM(1) (summation of the number 1) when there is a LEFT or INNER JOIN involved.
> There are two problems: a) incorrect check in MergeJoinStrategy.compareToPrevious method which generates TEIID31202 exception and b) a bug in algorithm of join itself which leads to incorrect results.
> To reproduce the bug, please, run the following queries and compare theSum and theCount column values:
> {code:sql}
> select r.city,
> sum(1) as theSum
> ,count(*) as theCount
> from "dsp.address_pg" r
> left join "adventureworks.stateprovince" c on "r.stateprovinceid" = "c.stateprovinceid"
> group by r.city
> order by r.city ;;
> {code}
> {code:sql}
> select r.city,
> sum(1) as theSum
> ,count(*) as theCount
> from "dsp.address_pg" r
> inner join "adventureworks.stateprovince" c on "r.stateprovinceid" = "c.stateprovinceid"
> group by r.city
> order by r.city ;;
> {code}
> but the following queries return correct results:
> {code:sql}
> select r.city,
> sum(1) as theSum
> ,count(*) as theCount
> from "dsp.address_pg" r
> right join "adventureworks.stateprovince" c on "r.stateprovinceid" = "c.stateprovinceid"
> group by r.city
> order by r.city ;;
> {code}
> the second one is also correct (LEFT JOIN) but uses window function:
> {code:sql}
> select distinct city,
> sum(1) OVER (PARTITION BY city) as theSum
> ,count(*) OVER (PARTITION BY city) as theCount
> from "dsp.address_pg" r
> left join "adventureworks.stateprovince" c on "r.stateprovinceid" = "c.stateprovinceid"
> order by r.city ;;
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
6 years, 10 months
[JBoss JIRA] (TEIID-5354) Different results for a query with GROUP BY and SUM(1) (summation of the number 1) when there is a LEFT or INNER JOIN involved
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5354?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5354.
-----------------------------------
Fix Version/s: 10.2.3
11.0
10.3.2
Resolution: Done
Generalized the logic dealing with aggregates over literals with similar handling to the count star case.
> Different results for a query with GROUP BY and SUM(1) (summation of the number 1) when there is a LEFT or INNER JOIN involved
> …
[View More]------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-5354
> URL: https://issues.jboss.org/browse/TEIID-5354
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 10.2
> Environment: teiid-10.2.0 on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 10.2.3, 11.0, 10.3.2
>
> Attachments: address_pg.sql, stateprovince_mysql.sql
>
>
> Teiid returns different results for a query with GROUP BY and SUM(1) (summation of the number 1) when there is a LEFT or INNER JOIN involved.
> There are two problems: a) incorrect check in MergeJoinStrategy.compareToPrevious method which generates TEIID31202 exception and b) a bug in algorithm of join itself which leads to incorrect results.
> To reproduce the bug, please, run the following queries and compare theSum and theCount column values:
> {code:sql}
> select r.city,
> sum(1) as theSum
> ,count(*) as theCount
> from "dsp.address_pg" r
> left join "adventureworks.stateprovince" c on "r.stateprovinceid" = "c.stateprovinceid"
> group by r.city
> order by r.city ;;
> {code}
> {code:sql}
> select r.city,
> sum(1) as theSum
> ,count(*) as theCount
> from "dsp.address_pg" r
> inner join "adventureworks.stateprovince" c on "r.stateprovinceid" = "c.stateprovinceid"
> group by r.city
> order by r.city ;;
> {code}
> but the following queries return correct results:
> {code:sql}
> select r.city,
> sum(1) as theSum
> ,count(*) as theCount
> from "dsp.address_pg" r
> right join "adventureworks.stateprovince" c on "r.stateprovinceid" = "c.stateprovinceid"
> group by r.city
> order by r.city ;;
> {code}
> the second one is also correct (LEFT JOIN) but uses window function:
> {code:sql}
> select distinct city,
> sum(1) OVER (PARTITION BY city) as theSum
> ,count(*) OVER (PARTITION BY city) as theCount
> from "dsp.address_pg" r
> left join "adventureworks.stateprovince" c on "r.stateprovinceid" = "c.stateprovinceid"
> order by r.city ;;
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[View Less]
6 years, 10 months