June 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3294) dynamic vdb imports nvarchar2 as object

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3294?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3294. --------------------------------- > dynamic vdb imports nvarchar2 as object > --------------------------------------- > > Key: TEIID-3294 > URL: https://issues.jboss.org/browse/TEIID-3294 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.6 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > A regression with TEIID-2644 causes nvarchar/nvarchar2 to import as object. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3072) SOLR: Make the Id named field as PK

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3072?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3072. --------------------------------- > SOLR: Make the Id named field as PK > ----------------------------------- > > Key: TEIID-3072 > URL: https://issues.jboss.org/browse/TEIID-3072 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.7.1, 8.9 > > > When using dynamic metadata retrieval, there is no way query the system if a field is unique. By default the schema.xml in SOLR defines "id" as unique key, so SOLR translator needs to use this as PK. > Having a PK is essential during the delete operation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3137) Change infinispan-cache translator to support JDG 6 and no longer support pre 6.0 infinispan

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3137?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3137. --------------------------------- > Change infinispan-cache translator to support JDG 6 and no longer support pre 6.0 infinispan > -------------------------------------------------------------------------------------------- > > Key: TEIID-3137 > URL: https://issues.jboss.org/browse/TEIID-3137 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7.1, 8.10 > > > Change the infinispan-cache translator to support JDG 6 using library mode. Also, remove support for infinispan v.5. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2249) Enable the use of temporary tables for those data sources that support them instead of IN criteria for EDS

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2249?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2249. --------------------------------- > Enable the use of temporary tables for those data sources that support them instead of IN criteria for EDS > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-2249 > URL: https://issues.jboss.org/browse/TEIID-2249 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.5 > > > Our proposal is to allow for the more efficient use of large ad-hoc result-sets by rather than creating a long 'IN' list, inserting them in to a temporary table - for example a # table in Sybase and SQL Server - and then generating an SQL join to that instead. > One of the difference to materialized views (or at least my understanding), is that this work happens at a data-source rather than within the Teiid server. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3557) Can't reload VDB in domain mode

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3557?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3557: ---------------------------------- Fix Version/s: 8.11.1 > Can't reload VDB in domain mode > ------------------------------- > > Key: TEIID-3557 > URL: https://issues.jboss.org/browse/TEIID-3557 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1.6_2, 8.12, 8.11.1 > > > Can't reload VDB in domain mode, get the following error: > Server throws the following exception: > [Server:server-one] 12:26:45,678 ERROR [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40088 Could not replicate object org.teiid.query.tempdata.GlobalTableStoreImpl@4e6c9a30: java.lang.IllegalStateException: cluster 'ModeShape.1' is already connected to singleton transport: [dummy-1435055090515, loopback.1, ModeShape.1, loopback-dynamic.1, $TEIID_BM$, dummy-1435055090188, dummy-1435055205654, $TEIID_ED$, teiid-cache, ddl2-vdb.1] > [Server:server-one] at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:919) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.jgroups.JChannel.startStack(JChannel.java:827) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.jgroups.JChannel._preConnect(JChannel.java:525) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.jgroups.JChannel.connect(JChannel.java:277) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.jgroups.JChannel.connect(JChannel.java:268) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.teiid.replication.jgroups.JGroupsObjectReplicator.replicate(JGroupsObjectReplicator.java:563) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.deployers.CompositeGlobalTableStore.createInstance(CompositeGlobalTableStore.java:57) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.jboss.VDBService$1.finishedDeployment(VDBService.java:156) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.deployers.VDBRepository.notifyFinished(VDBRepository.java:352) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.deployers.VDBRepository.finishDeployment(VDBRepository.java:308) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.runtime.AbstractVDBDeployer.metadataLoaded(AbstractVDBDeployer.java:202) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.jboss.VDBService.access$1100(VDBService.java:85) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.jboss.VDBService$6.run(VDBService.java:411) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > [Server:server-one] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:122) > VDB reload works fine in standalone mode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3558) Duplicate records being for formed for Internal Materialized View cluster

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3558?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3558. ----------------------------------- Resolution: Done Adding the missing page iteration to the replication. > Duplicate records being for formed for Internal Materialized View cluster > ------------------------------------------------------------------------- > > Key: TEIID-3558 > URL: https://issues.jboss.org/browse/TEIID-3558 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Pranav K > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7.1.6_2, 8.12, 8.11.1 > > > -On running a query over one of the nodes of a cluster (say node A) to fetch 25000 records (with internal materialization switched on), the cache gets formed on node A and presumably gets synced using the JgroupsObjectReplicator. > -On running the same query on the cache formed in the other node (node B), I noticed that I was getting 25600 records. > -On analysis the records, I saw there were only 1024 distinct records each of which repeated 25 times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3418) Allow positional group by for odbc

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3418?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3418: --------------------------------- Fix Version/s: 8.7.4 > Allow positional group by for odbc > ---------------------------------- > > Key: TEIID-3418 > URL: https://issues.jboss.org/browse/TEIID-3418 > Project: Teiid > Issue Type: Quality Risk > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.11, 8.7.4 > > > A remaining item for TEIID-3073 was that since tableau assumes we are postgresql they will use the pg specific positional group by references. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3418) Allow positional group by for odbc

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3418?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3418: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1227487|https://bugzilla.redhat.com/show_bug.cgi?id=1227487] from NEW to MODIFIED > Allow positional group by for odbc > ---------------------------------- > > Key: TEIID-3418 > URL: https://issues.jboss.org/browse/TEIID-3418 > Project: Teiid > Issue Type: Quality Risk > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.11 > > > A remaining item for TEIID-3073 was that since tableau assumes we are postgresql they will use the pg specific positional group by references. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3558) Duplicate records being for formed for Internal Materialized View cluster

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3558?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3558: ---------------------------------- Fix Version/s: 8.7.1.6_2 8.12 8.11.1 Affects Version/s: 8.0 (was: 8.11) Component/s: Query Engine (was: Embedded) > Duplicate records being for formed for Internal Materialized View cluster > ------------------------------------------------------------------------- > > Key: TEIID-3558 > URL: https://issues.jboss.org/browse/TEIID-3558 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Pranav K > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7.1.6_2, 8.12, 8.11.1 > > > -On running a query over one of the nodes of a cluster (say node A) to fetch 25000 records (with internal materialization switched on), the cache gets formed on node A and presumably gets synced using the JgroupsObjectReplicator. > -On running the same query on the cache formed in the other node (node B), I noticed that I was getting 25600 records. > -On analysis the records, I saw there were only 1024 distinct records each of which repeated 25 times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3558) Duplicate records being for formed for Internal Materialized View cluster

by Pranav K (JIRA)

[ https://issues.jboss.org/browse/TEIID-3558?page=com.atlassian.jira.plugin... ] Pranav K updated TEIID-3558: ---------------------------- Description: -On running a query over one of the nodes of a cluster (say node A) to fetch 25000 records (with internal materialization switched on), the cache gets formed on node A and presumably gets synced using the JgroupsObjectReplicator. -On running the same query on the cache formed in the other node (node B), I noticed that I was getting 25600 records. -On analysis the records, I saw there were only 1024 distinct records each of which repeated 25 times. was: On running a query over one of the nodes of a cluster (say node A) to fetch 25000 records (with internal materialization switched on), the cache gets formed on node A and presumably gets synced using the JgroupsObjectReplicator. On running the same query on the cache formed in the other node (node B), I noticed that I was getting 25600 records. On analysis the records, I saw there were only 1024 distinct records each of which repeated 25 times > Duplicate records being for formed for Internal Materialized View cluster > ------------------------------------------------------------------------- > > Key: TEIID-3558 > URL: https://issues.jboss.org/browse/TEIID-3558 > Project: Teiid > Issue Type: Bug > Components: Embedded > Affects Versions: 8.11 > Reporter: Pranav K > Assignee: Steven Hawkins > Priority: Critical > > -On running a query over one of the nodes of a cluster (say node A) to fetch 25000 records (with internal materialization switched on), the cache gets formed on node A and presumably gets synced using the JgroupsObjectReplicator. > -On running the same query on the cache formed in the other node (node B), I noticed that I was getting 25600 records. > -On analysis the records, I saw there were only 1024 distinct records each of which repeated 25 times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2015