October 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5460) Update Teiid docker example

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5460?page=com.atlassian.jira.plugin... ] Work on TEIID-5460 started by Steven Hawkins. --------------------------------------------- > Update Teiid docker example > --------------------------- > > Key: TEIID-5460 > URL: https://issues.jboss.org/browse/TEIID-5460 > Project: Teiid > Issue Type: Sub-task > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > The Teiid docker example is somewhat out of date - https://developer.jboss.org/wiki/QuickstartExampleWithDockerizedTeiid > It should be updated or fully subsumed into the formal docs that were started with the parent issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5480) Add geography support

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5480?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5480. ----------------------------------- Resolution: Done Marking the initial support as resolved. It is modeled after the existing geometry support with the same limitations - however there is a subtask for providing full function support. > Add geography support > --------------------- > > Key: TEIID-5480 > URL: https://issues.jboss.org/browse/TEIID-5480 > Project: Teiid > Issue Type: Feature Request > Components: OData, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > Geometry support should be expanded to the geography type. If we rely on additional libraries, we could also investigate 3 dimensional support at that time. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5490) Make long analytical results the default

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5490: ------------------------------------- Summary: Make long analytical results the default Key: TEIID-5490 URL: https://issues.jboss.org/browse/TEIID-5490 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.0 We should switch the default for org.teiid.longRanks to true as that better matches the behavior of most platforms. -- 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... ] Steven Hawkins updated TEIID-5459: ---------------------------------- Description: Most databases implement analytical ranks/row_number as returning bigint - regardless of what type count returns. MS SQL introduced COUNT_BIG, and Postgresql switched everything to bigint in 7.2. (was: 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.) > 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 > Priority: Major > Fix For: 11.2 > > > Most databases implement analytical ranks/row_number as returning bigint - regardless of what type count returns. MS SQL introduced COUNT_BIG, and Postgresql switched everything to bigint in 7.2. -- 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... ] Steven Hawkins resolved TEIID-5459. ----------------------------------- Resolution: Done The initial work focuses solely on the functions with integer return values - rank, dense_rank, and row_number. Additional work would be needed to allow the inner working of cume_dist and percent_rank to use long instead of integer - that can be worked later if it becomes an issue. COUNT_BIG was introduced, but is generally pushed as COUNT instead. > 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 > Priority: Major > 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.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: ------------------------------------ Good point, query level dynamic marshalling would introduce a challenge. I need to understand that more. > 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: ------------------------------------- Yes, that is true for the default Infinispan behaviour. What Teiid has dynamic marshallers. Need to check we were building at table or query level. I remember at query level but could be at table level. > 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 edited comment on TEIID-5449 at 10/2/18 3:55 PM: ------------------------------------------------------------- Change that, that doesn't make sense, because infinispan only requires the registration of the marshaller 1 time for it to be used for all subsequent queries. And that doesn't cause an issue. Docs: The next relevant part is the registration of per entity marshallers for our domain model types. They must be provided by the user for each type or marshalling will fail. Writing marshallers is a simple process. The BookMarshaller example should get you started. The most important thing you need to consider is they need to be stateless and threadsafe as a single instance of them is being used. was (Author: van.halbert): Change that, that doesn't make sense, because infinispan only requires the registration of the marshaller 1 time for it to be used for all subsequent queries. And that doesn't cause an issue. > 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: ------------------------------------ Change that, that doesn't make sense, because infinispan only requires the registration of the marshaller 1 time for it to be used for all subsequent queries. And that doesn't cause an issue. > 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: ------------------------------------ Ok, think I just realized what you are saying, in that the marshaller instance isn't thread safe. > 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2018