October 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5449) Infinispan: Update Infinispan translator to 9.3 version

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5449?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5449: ------------------------------------ 2 users using the same VDB, should be using a Marshaller that's based on the same structure that produces the same result. Not sure when the same tables in the same VDB would produce a different structure and therefore a different result. > Infinispan: Update Infinispan translator to 9.3 version > ------------------------------------------------------- > > Key: TEIID-5449 > URL: https://issues.jboss.org/browse/TEIID-5449 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Assignee: Van Halbert > Priority: Major > Fix For: 11.2 > > > Two changes observed > - The new cache create API changed, the old has been deprecated > - cache.get(key) now became Async operation, that means Thread Based serialization context no longer works. This needs to be removed, but there seem to be no better alternatives to support the Async threads. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5449) Infinispan: Update Infinispan translator to 9.3 version

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5449?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5449: ------------------------------------- It is not connections from Teiid vs outside. If there are two users using the same VDB with Infinispan translator, then their responses could be mangled using one's marshaller with another. > Infinispan: Update Infinispan translator to 9.3 version > ------------------------------------------------------- > > Key: TEIID-5449 > URL: https://issues.jboss.org/browse/TEIID-5449 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Assignee: Van Halbert > Priority: Major > Fix For: 11.2 > > > Two changes observed > - The new cache create API changed, the old has been deprecated > - cache.get(key) now became Async operation, that means Thread Based serialization context no longer works. This needs to be removed, but there seem to be no better alternatives to support the Async threads. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5449) Infinispan: Update Infinispan translator to 9.3 version

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5449?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5449: ------------------------------------ Lets make sure I'm understand the scope of connections and future direction here, because right now as I understand it, the resource-adapter is only used by Teiid. Is there a change such that the resource-adapter (and its connections) will be used by others outside Teiid? > Infinispan: Update Infinispan translator to 9.3 version > ------------------------------------------------------- > > Key: TEIID-5449 > URL: https://issues.jboss.org/browse/TEIID-5449 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Assignee: Van Halbert > Priority: Major > Fix For: 11.2 > > > Two changes observed > - The new cache create API changed, the old has been deprecated > - cache.get(key) now became Async operation, that means Thread Based serialization context no longer works. This needs to be removed, but there seem to be no better alternatives to support the Async threads. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5449) Infinispan: Update Infinispan translator to 9.3 version

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5449?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5449: ------------------------------------- [~rhn-engineering-vhalbert] As I mentioned above the Infinispan context where you registered marshaller is at global scope of all the connections in the pool, so registering a marshaller at that level will either overwrite or conflict with additional concurrent queries with the same name in the cache. This can lead to wrong results or errors in load. So, above commit is not sufficient. Either we need to * Create a new cache manager for each connection (very heavyweight, recommendation is to create one per VM) * Need to come with some way to non-conflict marshaller names based on connection * Ability to register marshallers at a different scope level in Infinispan API. The second bullet point will be my suggestion to implement. > Infinispan: Update Infinispan translator to 9.3 version > ------------------------------------------------------- > > Key: TEIID-5449 > URL: https://issues.jboss.org/browse/TEIID-5449 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Assignee: Van Halbert > Priority: Major > Fix For: 11.2 > > > Two changes observed > - The new cache create API changed, the old has been deprecated > - cache.get(key) now became Async operation, that means Thread Based serialization context no longer works. This needs to be removed, but there seem to be no better alternatives to support the Async threads. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5449) Infinispan: Update Infinispan translator to 9.3 version

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5449?page=com.atlassian.jira.plugin... ] Work on TEIID-5449 stopped by Van Halbert. ------------------------------------------ > Infinispan: Update Infinispan translator to 9.3 version > ------------------------------------------------------- > > Key: TEIID-5449 > URL: https://issues.jboss.org/browse/TEIID-5449 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Assignee: Van Halbert > Priority: Major > Fix For: 11.2 > > > Two changes observed > - The new cache create API changed, the old has been deprecated > - cache.get(key) now became Async operation, that means Thread Based serialization context no longer works. This needs to be removed, but there seem to be no better alternatives to support the Async threads. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5449) Infinispan: Update Infinispan translator to 9.3 version

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5449?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5449: ------------------------------------ I've been able to make the following changes in this [commit|https://github.com/vhalbert/teiid/commit/0bb92b90864e1cabee22cc37a...] that includes removing the thread based marshaller. The tests all pass. Not sure if this is what you expected, would like your review. > Infinispan: Update Infinispan translator to 9.3 version > ------------------------------------------------------- > > Key: TEIID-5449 > URL: https://issues.jboss.org/browse/TEIID-5449 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Assignee: Van Halbert > Priority: Major > Fix For: 11.2 > > > Two changes observed > - The new cache create API changed, the old has been deprecated > - cache.get(key) now became Async operation, that means Thread Based serialization context no longer works. This needs to be removed, but there seem to be no better alternatives to support the Async threads. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5470) Improve window function processing with order by over a literal

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5470?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5470. ----------------------------------- Resolution: Done Updated the logic to skip the initial sort in cases of sorting over literals. > Improve window function processing with order by over a literal > --------------------------------------------------------------- > > Key: TEIID-5470 > URL: https://issues.jboss.org/browse/TEIID-5470 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > We are sill processing the sort phase even when sorting over a literal. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5459) Support for large counts/ranks

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5459?page=com.atlassian.jira.plugin... ] Work on TEIID-5459 started by Steven Hawkins. --------------------------------------------- > Support for large counts/ranks > ------------------------------ > > Key: TEIID-5459 > URL: https://issues.jboss.org/browse/TEIID-5459 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.2 > > > Most databases implement analytical ranks/row_number as returning bigint - regardless of what type count returns. MS SQL introduced BIG_COUNT, and Postgresql switched everything to bigint in 7.2. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5470) Improve window function processing with order by over a literal

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5470?page=com.atlassian.jira.plugin... ] Work on TEIID-5470 started by Steven Hawkins. --------------------------------------------- > Improve window function processing with order by over a literal > --------------------------------------------------------------- > > Key: TEIID-5470 > URL: https://issues.jboss.org/browse/TEIID-5470 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.2 > > > We are sill processing the sort phase even when sorting over a literal. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4932) Support defining UDFs based upon a class and or function

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4932?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4932. ----------------------------------- Resolution: Done Added a UDF repository type and documented the use with xml and ddl metadata. In general it's more convienent via ddl as there could be multiple import options that make more sense by associating with the import statement. > Support defining UDFs based upon a class and or function > -------------------------------------------------------- > > Key: TEIID-4932 > URL: https://issues.jboss.org/browse/TEIID-4932 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.2 > > > With the new ddl support, we should allow an import to work against a class to define UDFs. > We should also in general support inferring arguments for UDFs and UDFs that are defined by a method. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2018