[JBoss JIRA] (TEIID-5153) RAND function gives same results in view
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5153?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5153.
-----------------------------------
Fix Version/s: 9.3.5
10.1
10.0.1
Resolution: Done
Expanded the logic that sets the eval flag to false to also consider functions appearing in subquery from clause and with clause locations.
> RAND function gives same results in view
> ----------------------------------------
>
> Key: TEIID-5153
> URL: https://issues.jboss.org/browse/TEIID-5153
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.4
> Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 9.3.5, 10.1, 10.0.1
>
>
> When using patched PostgreSQLExecutionFactory class to push down RAND function it starts to give the same values in a view. I wanted to push down RAND function in PostgreSQL for a while and noticed the bug related to identical values when using RAND function through a select in a view.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5153) RAND function gives same results in view
by dalex dalex (JIRA)
[ https://issues.jboss.org/browse/TEIID-5153?page=com.atlassian.jira.plugin... ]
dalex dalex commented on TEIID-5153:
------------------------------------
[~shawkins] do you mean to create a corresponding issue to add the random support for postgresql?
> RAND function gives same results in view
> ----------------------------------------
>
> Key: TEIID-5153
> URL: https://issues.jboss.org/browse/TEIID-5153
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.4
> Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Critical
>
> When using patched PostgreSQLExecutionFactory class to push down RAND function it starts to give the same values in a view. I wanted to push down RAND function in PostgreSQL for a while and noticed the bug related to identical values when using RAND function through a select in a view.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5153) RAND function gives same results in view
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5153?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5153:
---------------------------------------
Can you log an issue to add random support to postgresql as well?
> RAND function gives same results in view
> ----------------------------------------
>
> Key: TEIID-5153
> URL: https://issues.jboss.org/browse/TEIID-5153
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.4
> Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Critical
>
> When using patched PostgreSQLExecutionFactory class to push down RAND function it starts to give the same values in a view. I wanted to push down RAND function in PostgreSQL for a while and noticed the bug related to identical values when using RAND function through a select in a view.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5007) Changes to reduce Teiid in the cloud footprint
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5007?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5007:
---------------------------------------
I'm not finding good guidelines around ephemeral disk usage. You can put limits based upon image and node usage, but there doesn't seem to be an a priori way of automatically determining a limit for a single container - https://docs.openshift.com/container-platform/3.6/admin_guide/out_of_reso...
As is things like the logs, temp files (buffer manager, deployment related), etc. just go to their default location. For the server log the console is probably sufficient. Concerns such locations for heap and other dumps should they be needed should be looked at (Burr has material on this and I'm not sure what we're planning on baking into the base java image).
Options:
- fully read-only image and manage all disk usage through volumes (seems unnecessary as we don't need persistence)
- add more parameters, in particular buffermanager disk consumption to the templates (or even useDisk=false)
- something else?
> Changes to reduce Teiid in the cloud footprint
> ----------------------------------------------
>
> Key: TEIID-5007
> URL: https://issues.jboss.org/browse/TEIID-5007
> Project: Teiid
> Issue Type: Quality Risk
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.1
>
>
> A Teiid instance even as swarm or springboot needs additional considerations to minimize the runtime footprint. This includes:
> * container aware auto-sizing. Detection of the number of cpus and available memory need refined - there are experimental settings being considered for containerized vms to better report these values and there is logic in WildFly and other projects that attempts better auto-detection. We also need to utilize the memory buffer space more and probably as off-heap space (and ideally direct operations on the serialized data)
> * Subsystems required include JTA, webserver, security, which could be satisfied by slimmer alternative versions - especially if we make new assumptions, such as not utilizing xa transactions.
> * Engine dependencies could be application specific - removing xml/xsl support, geometry support, etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5154) Missing default method for IsDistinct
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5154:
-------------------------------------
Summary: Missing default method for IsDistinct
Key: TEIID-5154
URL: https://issues.jboss.org/browse/TEIID-5154
Project: Teiid
Issue Type: Quality Risk
Components: Connector API
Affects Versions: 10.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.1, 10.0.1
TEIID-4711 missed adding the default method in AbstractLanguageVisitor
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5150) JDG source model with 'v' letter at beginning of a name doesn't work.
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/TEIID-5150?page=com.atlassian.jira.plugin... ]
Adrian Nistor commented on TEIID-5150:
--------------------------------------
Yes, known lexer issue, caused by antlr 3. I've just linked the ISPN issue, which is still unsolved.
> JDG source model with 'v' letter at beginning of a name doesn't work.
> ---------------------------------------------------------------------
>
> Key: TEIID-5150
> URL: https://issues.jboss.org/browse/TEIID-5150
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector
> Affects Versions: 8.12.x-6.4
> Environment: Fedora 26
> Mac OS 10.12
> Reporter: Matej Kralik
> Assignee: Ramesh Reddy
> Priority: Critical
> Attachments: BookMat-vdb.xml
>
>
> When the name of a JDG source model starts with 'v' letter, after run query at the materialized table (BooksMatView.viewBooks in attached VDB), the server shows exception:
> {code:java}
> 14:29:19,383 WARN [org.infinispan.client.hotrod.impl.protocol.Codec21] (Worker3_QueryProcessorQueue176) ISPN004005: Error received from the server: java.lang.IllegalArgumentException: Message descriptor not found : endorBookJDGSource.viewBooks
> 14:29:19,384 ERROR [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue176) Connector worker process failed for atomic-request=X6jNnAMTIgyp.0.6.248: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=551 returned server error (status=0x85): java.lang.IllegalArgumentException: Message descriptor not found : endorBookJDGSource.viewBooks
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:363) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:152) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:138) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:68) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:30) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:57) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.executeQuery(RemoteQuery.java:68) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.list(RemoteQuery.java:53) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.teiid.translator.infinispan.hotrod.InfinispanResponse.fetchNextBatch(InfinispanResponse.java:76) [translator-infinispan-hotrod-8.12.11.6_4-redhat-7.jar:8.12.11.6_4-redhat-7]
> at org.teiid.translator.infinispan.hotrod.InfinispanResponse.getNextRow(InfinispanResponse.java:92) [translator-infinispan-hotrod-8.12.11.6_4-redhat-7.jar:8.12.11.6_4-redhat-7]
> at org.teiid.translator.infinispan.hotrod.InfinispanQueryExecution.next(InfinispanQueryExecution.java:142) [translator-infinispan-hotrod-8.12.11.6_4-redhat-7.jar:8.12.11.6_4-redhat-7]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:433) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:236) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at sun.reflect.GeneratedMethodAccessor167.invoke(Unknown Source) [:1.8.0_65]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_65]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_65]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at com.sun.proxy.$Proxy42.more(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:309) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_65]
> 14:29:19,389 WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue177) TEIID30020 Processing exception for request X6jNnAMTIgyp.0 'TEIID30504 vendorBookJDGSource: java.lang.IllegalArgumentException: Message descriptor not found : endorBookJDGSource.viewBooks'. Originally TeiidProcessingException Codec20.java:363. Enable more detailed logging to see the entire stacktrace.
> {code}
> JDG source model has name *vendorBookJDGSource*.
> However, the name of JDG source model in the exception doesn't contain first 'v' letter ( Message descriptor not found : *endorBookJDGSource*.viewBooks ).
> Jdg server doesn't show any exception. I use DV 6.4.0 ER3, JDG 7.1 server and JDG 7.1.1 CR2 EAP module.
> In the attachments, I upload my VDB. Remove 'v' letter fix the issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5150) JDG source model with 'v' letter at beginning of a name doesn't work.
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/TEIID-5150?page=com.atlassian.jira.plugin... ]
Tristan Tarrant commented on TEIID-5150:
----------------------------------------
My hunch is that this is caused by the lexer not understand the escape sequence for a vertical tab '\v' and just removing the v as whitespace... /cc [~adriannistor]
> JDG source model with 'v' letter at beginning of a name doesn't work.
> ---------------------------------------------------------------------
>
> Key: TEIID-5150
> URL: https://issues.jboss.org/browse/TEIID-5150
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector
> Affects Versions: 8.12.x-6.4
> Environment: Fedora 26
> Mac OS 10.12
> Reporter: Matej Kralik
> Assignee: Ramesh Reddy
> Priority: Critical
> Attachments: BookMat-vdb.xml
>
>
> When the name of a JDG source model starts with 'v' letter, after run query at the materialized table (BooksMatView.viewBooks in attached VDB), the server shows exception:
> {code:java}
> 14:29:19,383 WARN [org.infinispan.client.hotrod.impl.protocol.Codec21] (Worker3_QueryProcessorQueue176) ISPN004005: Error received from the server: java.lang.IllegalArgumentException: Message descriptor not found : endorBookJDGSource.viewBooks
> 14:29:19,384 ERROR [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue176) Connector worker process failed for atomic-request=X6jNnAMTIgyp.0.6.248: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=551 returned server error (status=0x85): java.lang.IllegalArgumentException: Message descriptor not found : endorBookJDGSource.viewBooks
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:363) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:152) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:138) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:68) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:30) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:57) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.executeQuery(RemoteQuery.java:68) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.list(RemoteQuery.java:53) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.teiid.translator.infinispan.hotrod.InfinispanResponse.fetchNextBatch(InfinispanResponse.java:76) [translator-infinispan-hotrod-8.12.11.6_4-redhat-7.jar:8.12.11.6_4-redhat-7]
> at org.teiid.translator.infinispan.hotrod.InfinispanResponse.getNextRow(InfinispanResponse.java:92) [translator-infinispan-hotrod-8.12.11.6_4-redhat-7.jar:8.12.11.6_4-redhat-7]
> at org.teiid.translator.infinispan.hotrod.InfinispanQueryExecution.next(InfinispanQueryExecution.java:142) [translator-infinispan-hotrod-8.12.11.6_4-redhat-7.jar:8.12.11.6_4-redhat-7]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:433) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:236) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at sun.reflect.GeneratedMethodAccessor167.invoke(Unknown Source) [:1.8.0_65]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_65]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_65]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at com.sun.proxy.$Proxy42.more(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:309) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_65]
> 14:29:19,389 WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue177) TEIID30020 Processing exception for request X6jNnAMTIgyp.0 'TEIID30504 vendorBookJDGSource: java.lang.IllegalArgumentException: Message descriptor not found : endorBookJDGSource.viewBooks'. Originally TeiidProcessingException Codec20.java:363. Enable more detailed logging to see the entire stacktrace.
> {code}
> JDG source model has name *vendorBookJDGSource*.
> However, the name of JDG source model in the exception doesn't contain first 'v' letter ( Message descriptor not found : *endorBookJDGSource*.viewBooks ).
> Jdg server doesn't show any exception. I use DV 6.4.0 ER3, JDG 7.1 server and JDG 7.1.1 CR2 EAP module.
> In the attachments, I upload my VDB. Remove 'v' letter fix the issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5153) RAND function gives same results in view
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5153?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5153:
---------------------------------------
The logic isn't appropriately differentiating between scalar subqueries and inline views. In the former you do want to preevaluate "select (select random()) from test_a", but not the latter.
> RAND function gives same results in view
> ----------------------------------------
>
> Key: TEIID-5153
> URL: https://issues.jboss.org/browse/TEIID-5153
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.4
> Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Critical
>
> When using patched PostgreSQLExecutionFactory class to push down RAND function it starts to give the same values in a view. I wanted to push down RAND function in PostgreSQL for a while and noticed the bug related to identical values when using RAND function through a select in a view.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5153) RAND function gives same results in view
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5153?page=com.atlassian.jira.plugin... ]
Work on TEIID-5153 started by Steven Hawkins.
---------------------------------------------
> RAND function gives same results in view
> ----------------------------------------
>
> Key: TEIID-5153
> URL: https://issues.jboss.org/browse/TEIID-5153
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.4
> Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Critical
>
> When using patched PostgreSQLExecutionFactory class to push down RAND function it starts to give the same values in a view. I wanted to push down RAND function in PostgreSQL for a while and noticed the bug related to identical values when using RAND function through a select in a view.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month