December 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3675) Remove JwtBearerGrant CXF classes

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3675?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3675: ------------------------------------- CXF version in WildFly 9.0.1.Final does not yet have the fix > Remove JwtBearerGrant CXF classes > --------------------------------- > > Key: TEIID-3675 > URL: https://issues.jboss.org/browse/TEIID-3675 > Project: Teiid > Issue Type: Sub-task > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 9.0 > > > When CXF version > 3.0.4 remove JwtBearerGrant related CXF classes, and use ones from CXF -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3718) Add Log4j 2 Logger Adapter

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3718?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3718: --------------------------------------- By default we're picking up the Wildfly 9.0.x version of JBoss Logging, so that is currently 3.2.1. > Add Log4j 2 Logger Adapter > -------------------------- > > Key: TEIID-3718 > URL: https://issues.jboss.org/browse/TEIID-3718 > Project: Teiid > Issue Type: Sub-task > Components: Embedded > Affects Versions: 8.11.4 > Environment: Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T04:57:37-07:00) > Maven home: C:\Java\apache-maven-3.3.3 > Java version: 1.7.0_79, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.7.0_79\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > Reporter: Gary Gregory > Assignee: Kylin Soong > Fix For: 8.13 > > Attachments: Log4j2LoggerAdapter.java > > > Add a Log4j 2 Logger Adapter. See attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3718) Add Log4j 2 Logger Adapter

by Gary Gregory (JIRA)

[ https://issues.jboss.org/browse/TEIID-3718?page=com.atlassian.jira.plugin... ] Gary Gregory commented on TEIID-3718: ------------------------------------- Thank you for the update Steven. Any reason JBoss Logging 3.2.1 is used instead of 3.3.0.Final? Gary > Add Log4j 2 Logger Adapter > -------------------------- > > Key: TEIID-3718 > URL: https://issues.jboss.org/browse/TEIID-3718 > Project: Teiid > Issue Type: Sub-task > Components: Embedded > Affects Versions: 8.11.4 > Environment: Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T04:57:37-07:00) > Maven home: C:\Java\apache-maven-3.3.3 > Java version: 1.7.0_79, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.7.0_79\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > Reporter: Gary Gregory > Assignee: Kylin Soong > Fix For: 8.13 > > Attachments: Log4j2LoggerAdapter.java > > > Add a Log4j 2 Logger Adapter. See attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3286) Deprecate the support for Client JDK 1.5, to be removed in v9

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3286?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3286. ----------------------------------- Resolution: Done The code has been removed, and the build has been updated. The community site advises people to use an older release 1.4/1.5 jar to connect instead. > Deprecate the support for Client JDK 1.5, to be removed in v9 > -------------------------------------------------------------- > > Key: TEIID-3286 > URL: https://issues.jboss.org/browse/TEIID-3286 > Project: Teiid > Issue Type: Task > Components: JDBC Driver > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.0 > > > Deprecate the support for the Client JDK 1.5 support, which should be removed in v9. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3675) Remove JwtBearerGrant CXF classes

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3675?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3675: --------------------------------------- Should this be bumped up to 8.13? > Remove JwtBearerGrant CXF classes > --------------------------------- > > Key: TEIID-3675 > URL: https://issues.jboss.org/browse/TEIID-3675 > Project: Teiid > Issue Type: Sub-task > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 9.0 > > > When CXF version > 3.0.4 remove JwtBearerGrant related CXF classes, and use ones from CXF -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3718) Add Log4j 2 Logger Adapter

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3718?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3718. ----------------------------------- Fix Version/s: 8.13 Resolution: Done With the latest changes we now depend on JBoss Logging 3.2.1 with Log4j 2 support. The attached class can still be used if desired to cut out the additional abstraction layer. > Add Log4j 2 Logger Adapter > -------------------------- > > Key: TEIID-3718 > URL: https://issues.jboss.org/browse/TEIID-3718 > Project: Teiid > Issue Type: Sub-task > Components: Embedded > Affects Versions: 8.11.4 > Environment: Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T04:57:37-07:00) > Maven home: C:\Java\apache-maven-3.3.3 > Java version: 1.7.0_79, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.7.0_79\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > Reporter: Gary Gregory > Assignee: Kylin Soong > Fix For: 8.13 > > Attachments: Log4j2LoggerAdapter.java > > > Add a Log4j 2 Logger Adapter. See attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3519) Produce a wildfly kit

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3519?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3519: ---------------------------------- Fix Version/s: (was: 9.0) > Produce a wildfly kit > --------------------- > > Key: TEIID-3519 > URL: https://issues.jboss.org/browse/TEIID-3519 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.13 > > > Ahead of the 9 release it would be good to provide an option for an 8.x kit on wildfly. See also http://teiid.blogspot.com/2015/06/teiid-811-beta3-posted.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3541) Remove the Teiid embedded kit

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3541?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3541: --------------------------------------- Are we ready for this in 8.13, or do we want to keep things consistent there with 8.12? > Remove the Teiid embedded kit > ----------------------------- > > Key: TEIID-3541 > URL: https://issues.jboss.org/browse/TEIID-3541 > Project: Teiid > Issue Type: Task > Components: Embedded > Reporter: Ramesh Reddy > Assignee: Kylin Soong > Fix For: 9.0 > > > There is no reason to keep a separate embedded kit supplied by Teiid. The scripts that are building the kit needs to be removed from build. > All the required jar files for the "embedded" examples will be available from the "teiid-embedded-examples". Here we need to focus on documentation, but that is separate effort -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3489) Can a function be added to filter certain ASCII chars below 31 and above 127 out of an XML Document

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3489?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3489. ----------------------------------- Resolution: Done Teiid 9 adds support for clobs as well, so that it can be used for larger docs: regexp_Replace(doc, '[^\x09\x0A\x0D\x20-\x7E]', '', 'g') > Can a function be added to filter certain ASCII chars below 31 and above 127 out of an XML Document > --------------------------------------------------------------------------------------------------- > > Key: TEIID-3489 > URL: https://issues.jboss.org/browse/TEIID-3489 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Debbie Steigner > Priority: Minor > Fix For: 9.0 > > > Add a function in Teiid to filter off all ASCII chars below 31 and above 127. > web service data source that contains control characters due to data entered by copy and paste the text from another system. > The characters in this instance were the print control chars ASCII 28 and 29, File Separator and Group Separator respectively. These are used for formatting in older systems. Unfortunately, the XML standard prohibits the processing of all ASCII characters below 31 apart from Tab, Line Feed and Carriage Return which are permissible. Also, ASCII chars above 127 to 255 will also cause XML parsers to crash. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3849) Writes using Cassandra connector are very slow

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3849?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3849: --------------------------------------- We are trying to keep 8.13 free of additional feature work, but if this is deemed necessary for 8.12.x it will be pulled into 8.13 as well. > Writes using Cassandra connector are very slow > ---------------------------------------------- > > Key: TEIID-3849 > URL: https://issues.jboss.org/browse/TEIID-3849 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Pranav K > Assignee: Steven Hawkins > Fix For: 9.0 > > > The connector seems to execute the insert queries one by one rather than using batched approach, also the API used is the synchronous one instead of the future based async API [session.executeAsync()] > Cassandra writes are generally very fast, but it was noted in one scenario that on a single node Cassandra setup inserting a set 50k records and 3 columns took more than 25 mins. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2015