December 2015 - teiid-issues - Jboss List Archives

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3541?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3541: -------------------------------- Fix Version/s: 8.13 (was: 9.0) > 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: Ramesh Reddy > Fix For: 8.13 > > > 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)

8 years, 5 months

1
0
0 / 0

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

by Pranav K (JIRA)

[ https://issues.jboss.org/browse/TEIID-3849?page=com.atlassian.jira.plugin... ] Pranav K commented on TEIID-3849: --------------------------------- Yes (if possible) it would be great to have this earlier in 8.13, as in a few of our scenario we were getting constrained due to Cassandra performance. > 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)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3861) re-done embedded examples in terms of their build

by Kylin Soong (JIRA)

Kylin Soong created TEIID-3861: ---------------------------------- Summary: re-done embedded examples in terms of their build Key: TEIID-3861 URL: https://issues.jboss.org/browse/TEIID-3861 Project: Teiid Issue Type: Task Reporter: Kylin Soong Assignee: Kylin Soong The embedded examples needs to be re-done in terms of their build. I will be removing the embedded kit in next release of Teiid 8.13. That means all the examples you have just need to depend upon maven pom files and their dependencies for building them. IMO you do not need to provide any run.sh kind of scripts, just provide the code that can compiled with right dependencies. Each example MUST be independent, i.e no parent POM brings a bucket of dependencies. Have example documented clearly what dependencies it takes to compile and execute. Then have the parent readme.md file documented with all different types of translators, and their maven dependency xml code fragment. See this as example https://github.com/wildfly-swarm/wildfly-swarm-examples/tree/master/datas... this is the format we need to follow. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3725) In the JDG translators, enable named cache swapping so that materialization can be supported

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3725?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3725: ------------------------------------ Based on the latest conference call, it was decided that the teiid translator will be changed to use a second JDG cache for managing the cache names. The key:value pairs will be used to refer to: cache alias name: cache name The cache alias names will be assigned accordingly: modelName.tableName : jdgCacheNameA modelName.tableName.stage : jdgCacheNameB The translator will be changed to support native query, so that a specific native query can be issued as part of the materialization process to handle pre-processing and post-processing (swapping jdgCacheNameA/B). There is more usability work to be done to assist with reverse engineering the view table into a pojo object. Will start looking at that once the translator logic is done and in the product build. > In the JDG translators, enable named cache swapping so that materialization can be supported > -------------------------------------------------------------------------------------------- > > Key: TEIID-3725 > URL: https://issues.jboss.org/browse/TEIID-3725 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Van Halbert > Assignee: Van Halbert > > The JDG translators, that in order to support materialization, will need to enable the named cache that's referenced by the connection, to be swapped. This is due to JDG doesn't currently support renaming a cache (i.e., like table rename in JDBC). And because of that, it limits how the cache can be refreshed (don't want to clear it before re-loading). > Ideas are: > 1. configure translator with the 2 cache names to use (a) initial cache to read from and (b) the staging cache to use > perform materialize load > call SYSADMIN.setProperty to trigger the swapping of the cache names > 2 ??? > Note: because there's no persistence in Teiid so that any cache name changes will outlive a server restart, when a restart occurs, the translator will read from the cache identified as the initial cache to read from. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3725) In the JDG translators, enable named cache swapping so that materialization can be supported

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3725?page=com.atlassian.jira.plugin... ] Work on TEIID-3725 started by Van Halbert. ------------------------------------------ > In the JDG translators, enable named cache swapping so that materialization can be supported > -------------------------------------------------------------------------------------------- > > Key: TEIID-3725 > URL: https://issues.jboss.org/browse/TEIID-3725 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Van Halbert > Assignee: Van Halbert > > The JDG translators, that in order to support materialization, will need to enable the named cache that's referenced by the connection, to be swapped. This is due to JDG doesn't currently support renaming a cache (i.e., like table rename in JDBC). And because of that, it limits how the cache can be refreshed (don't want to clear it before re-loading). > Ideas are: > 1. configure translator with the 2 cache names to use (a) initial cache to read from and (b) the staging cache to use > perform materialize load > call SYSADMIN.setProperty to trigger the swapping of the cache names > 2 ??? > Note: because there's no persistence in Teiid so that any cache name changes will outlive a server restart, when a restart occurs, the translator will read from the cache identified as the initial cache to read from. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3801) Upgrade Infinispan translator to support 6.4.x version (JDG 6.6)

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3801?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3801: ------------------------------------ This has been upgraded to 6.5, but waiting for JDG 6.6. > Upgrade Infinispan translator to support 6.4.x version (JDG 6.6) > ---------------------------------------------------------------- > > Key: TEIID-3801 > URL: https://issues.jboss.org/browse/TEIID-3801 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.12.x, 9.x > Reporter: Van Halbert > Assignee: Van Halbert > > Upgrade Infinispan translator to support version 6.4 (JDG 6.6). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3677) Update the Teiid Community Home Page to show all the types of data sources being supported

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3677?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-3677: ---------------------------------- Assignee: (was: Van Halbert) > Update the Teiid Community Home Page to show all the types of data sources being supported > ------------------------------------------------------------------------------------------ > > Key: TEIID-3677 > URL: https://issues.jboss.org/browse/TEIID-3677 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Reporter: Van Halbert > Attachments: dvover.png, teiid_architecture.png > > > With all the new types of data sources being supported by Teiid, it would be nice to indicate those on the Teiid Community home page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

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: --------------------------------------- The working plan right now is to have Teiid 9.0 released against Wildfly 9 as well. Wildfly 10 support will come in Teiid 9.x unless it introduces breaking changes. > 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)

8 years, 5 months

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: ------------------------------------- Roger that, thanks. What is the longer term plan WRT Wildfly 10? I am looking to sync up with Apache CXF which is at the 3.1 level in WF 10 it looks like. > 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)

8 years, 5 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3541?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3541: ------------------------------------- Yes, I did not update the embedded distributions, so we are good get rid of this now. > 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)

8 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2015