March 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5291) MongoDB Java driver in JDV 6.4 is out of date

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5291?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-5291: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1558585 Bugzilla Update: Perform > MongoDB Java driver in JDV 6.4 is out of date > --------------------------------------------- > > Key: TEIID-5291 > URL: https://issues.jboss.org/browse/TEIID-5291 … [View More]

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5290) NOW() function returns the same value for each call in BEGIN...END block

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5290?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5290: --------------------------------------- > But what about backward compatibility? The change to fully non-deterministic will alter the planning behavior for user queries and potentially lead to performance issues due to lack of evaluation and pushdown. You are correct that in a stored procedure context you were relying on the non-deterministic implementation. … [View More]

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5290) NOW() function returns the same value for each call in BEGIN...END block

by dalex dalex (JIRA)

[ https://issues.jboss.org/browse/TEIID-5290?page=com.atlassian.jira.plugin... ] dalex dalex commented on TEIID-5290: ------------------------------------ But what about backward compatibility? For example, we have many stored procedures where we suppose non-deterministic behavior of the now() function. I don't say about another users of the platform, there are I think tons of stored procedures which should be rewritten. > NOW() function returns the same value for each call in BEGIN...… [View More]

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5290) NOW() function returns the same value for each call in BEGIN...END block

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5290?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5290: --------------------------------------- On 2 - prior to TEIID-5204 the function was non-deterministic, but planned as if it were command deterministic. That was not desirable as the behavior was not consistent, but most of the time it meant that a single value per user command was used. Post TEIID-5204 it's fully command deterministic. Thinking about this more it's … [View More]

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5291) MongoDB Java driver in JDV 6.4 is out of date

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5291?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5291: ---------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/1072 There's now a pull request with with original code change and a further upgrade to 3.6.3. > MongoDB Java driver in JDV 6.4 is out of date > --------------------------------------------- > > Key: TEIID-5291 > URL: https://issues.jboss.… [View More]

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5290) NOW() function returns the same value for each call in BEGIN...END block

by dalex dalex (JIRA)

[ https://issues.jboss.org/browse/TEIID-5290?page=com.atlassian.jira.plugin... ] dalex dalex commented on TEIID-5290: ------------------------------------ [~shawkins] I totally agree with [~rareddy], actually we got the problem related to now() behavior because of the TEIID-5204 issue. Let's consider the 2. option. > NOW() function returns the same value for each call in BEGIN...END block > ------------------------------------------------------------------------ > > … [View More]

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5291) MongoDB Java driver in JDV 6.4 is out of date

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5291?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5291: --------------------------------------- This was addressed originally by TEIID-4781 to the 3.4.2 driver version. We can resolve this as a duplicate or leave it open to further upgrade to 3.6. > MongoDB Java driver in JDV 6.4 is out of date > --------------------------------------------- > > Key: TEIID-5291 > URL: https://… [View More]

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5290) NOW() function returns the same value for each call in BEGIN...END block

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5290?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5290: ------------------------------------- I think since the new behavior is introduced recently wouldn't it be better if we did option (2) to change it back to non-deterministic and then introduce another deterministic function for TEIID-5204 purposes? > NOW() function returns the same value for each call in BEGIN...END block > ---------------------------------------------… [View More]

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5290) NOW() function returns the same value for each call in BEGIN...END block

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5290?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5290: --------------------------------------- This is mostly about the function definition for now/current_timestamp - it is defined as command deterministic, which as per TEIID-5204 means that it should have a single value for the scope of the user command. There is no difference in the behavior in this case between using "declare timestamp ts2 = now()" and "declare timestamp … [View More]ts2 = (select now())" as we are still only looking for the command level value. getdate and clock_timestamp are the fully non-deterministic timestamp functions for sql server and postgresql respectively. Postgresql actually offers: transaction_timestamp() - same as pg now() statement_timestamp() clock_timestamp() Our current behavior for now / current_timestamp matches pg statement_timestamp. If you use now() in the postgresql example above, it will produce the same value for each timestamp. It appears that SQL Server and postgresql disagree on the meaning of current_timestamp - it's fully non-deterministc for SQL Server and it matches transaction_timetstamp for postgresql. The spec does not seem to fully specify what current means. Our choices here are: 1. leave the Teiid current_timestamp / now functions as command deterministic as per TEIID-5204 and introduce a new fully non-deterministic timestamp function. 2. change the Teiid current_timestamp / now functions back to the non-determinisic implementation and update the metadata to indicate it is fully non-deterministic. Do you have a preference as to the resolution? > NOW() function returns the same value for each call in BEGIN...END block > ------------------------------------------------------------------------ > > Key: TEIID-5290 > URL: https://issues.jboss.org/browse/TEIID-5290 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 10.1 > Environment: teiid-10.1.0 on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Fix For: 10.2 > > > Run the following queries: > {code:sql} > BEGIN > declare timestamp ts1 = select now(); > DECLARE integer c = 20000; > WHILE (c > 0) > BEGIN > c= c-1; > END > declare timestamp ts2 = select now(); > select ts1, ts2; > END ;; > {code} > and > {code:sql} > BEGIN > DECLARE integer c = 20000; > create local temporary table #tem(ts timestamp); > WHILE (c > 0) > BEGIN > INSERT INTO #tem VALUES((select NOW())); > c= c-1; > END > select * from #tem; > END ;; > {code} > NOW() function returns the same value for each call in BEGIN...END block and it doesn't matter if it is atomic or not. -- This message was sent by Atlassian JIRA (v7.5.0#75005) [View Less]

7 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5291) MongoDB Java driver in JDV 6.4 is out of date

by Jan Martiska (JIRA)

Jan Martiska created TEIID-5291: ----------------------------------- Summary: MongoDB Java driver in JDV 6.4 is out of date Key: TEIID-5291 URL: https://issues.jboss.org/browse/TEIID-5291 Project: Teiid Issue Type: Bug Components: Misc. Connectors Reporter: Jan Martiska Assignee: Steven Hawkins Priority: Critical JDV 6.4 contains MongoDB Java driver 2.13.1. If we want to start … [View More]

7 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2018