March 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3208) Remove outer join based solely on join predicates

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3208?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3208. --------------------------------- > Remove outer join based solely on join predicates > ------------------------------------------------- > > Key: TEIID-3208 > URL: https://issues.jboss.org/browse/TEIID-3208 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > We currently remove outer joins based upon where clause predicates, but won't necessarily detect when to remove the the outer join based solely on join predicates: > SELECT * from pm1.g1 inner join (pm1.g2 left outer join pm1.g3 on pm1.g2.e1=pm1.g3.e1) on pm1.g1.e1=pm1.g3.e1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3263) Invalid aggregate value

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3263?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3263. --------------------------------- > Invalid aggregate value > ----------------------- > > Key: TEIID-3263 > URL: https://issues.jboss.org/browse/TEIID-3263 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.9 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.9.1, 8.10 > > > There's a regression in TEIID-3119 - an incorrect aggregate value can be returned when using group/sort aggregation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3296) Some criteria are missing when indexes are used on the source tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3296?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3296. --------------------------------- > Some criteria are missing when indexes are used on the source tables > -------------------------------------------------------------------- > > Key: TEIID-3296 > URL: https://issues.jboss.org/browse/TEIID-3296 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.2 > Reporter: Salvatore R > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.10 > > > The following two tables are defined in two different datasources (PostgreSQL and MySQL): > {code:sql} > CREATE TABLE "pg"."tx1" > ( > a varchar(2147483647), > b varchar(2147483647), > c integer, > d integer, > e integer > ); > CREATE INDEX tx1_b ON "pg"."tx1"(b); > CREATE INDEX tx1_a ON "pg"."tx1"(a); > CREATE INDEX tx1_e ON "pg"."tx1"(e); > CREATE INDEX tx1_d ON "pg"."tx1"(d); > CREATE INDEX tx1_c ON "pg"."tx1"(c); > > CREATE TABLE "my"."tx2" > ( > a integer, > b integer, > c integer, > d integer, > e integer > ); > insert into tx1 VALUES(1,1,1,1,1) ; > insert into tx1 VALUES(1,2,2,2,2) ; > insert into tx1 VALUES(1,2,3,3,3) ; > insert into tx1 VALUES(1,2,3,4,4) ; > insert into tx1 VALUES(1,2,3,4,5) ; > insert into tx2 VALUES(1,2,3,4,5) ; > {code} > Running the following query: > {code:sql} > select tx1.* from pg.tx1 as tx1 join my.tx2 as tx2 on tx1.a=tx2.a and tx1.b=tx2.b and tx1.c=tx2.c and tx1.d=tx2.d and tx1.e!=tx2.e; > {code} > a wrong result is returned: > ||a||b||c||d||e|| > |1|2|2|2|2| > |1|2|3|3|3| > |1|2|3|4|4| > If indexes are removed from the source table, the expected result is correctly returned: > ||a||b||c||d||e|| > |1|2|3|4|4| -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3290) Auto generated REST WAR truncates the larger payloads

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3290?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3290. --------------------------------- > Auto generated REST WAR truncates the larger payloads > ----------------------------------------------------- > > Key: TEIID-3290 > URL: https://issues.jboss.org/browse/TEIID-3290 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Labels: Beta2 > Fix For: 8.7.1, 8.10 > > > Currently only query parameters are supported as the input parameters to the Teiid procedure in POST based call. > The POST BODY also needs to be supported to handle larger payloads in this situation as query parameters has size limitations. Currently string based query parameters are supported, but since they passed as is as strings on larger payloads the they will be subject 4000 string length restriction. > It should be possible to read metadata of the procedure and convert the string objects to respective objects before the query gets executed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3216) Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3216?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3216. --------------------------------- > Implement INSERT, UPDATE and DELETE support for google-spreadsheet connector > ---------------------------------------------------------------------------- > > Key: TEIID-3216 > URL: https://issues.jboss.org/browse/TEIID-3216 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Filip Elias > Assignee: Filip Elias > Fix For: 8.10 > > > Current plan is to use list-based feed of the Google Data API[1]. > There are three known issues: > performance - to delete/update 100 rows Teiid must generate 100 http requests > consistency - user wants to update 50 rows. After the 10th row is updated the connection could fail which would cause that 10 rows would be updated and 40 wouldn't. > headers - update, delete and and insert statements will be supported only for the spreadsheets that have a header for each column (headers are in the first row of a spreadsheet) > Select statement is implemented using Google Visualisation API, but this API doesn't support updates and doesn't return row numbers. > [1] https://developers.google.com/google-apps/spreadsheets/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2407) Support temporary table on commit behavior

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2407?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2407. --------------------------------- > Support temporary table on commit behavior > ------------------------------------------ > > Key: TEIID-2407 > URL: https://issues.jboss.org/browse/TEIID-2407 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Fix For: 8.10 > > > Now that our temporary tables are transactionally aware we should support the on commit clause. > Our current default for on commit is effectively "preserve rows", which is contrary to the sql specification. We should also offer delete rows and possible drop (similar to pg sql). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-991) Request for support of Sybase IQ as a supported data source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-991?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-991. -------------------------------- > Request for support of Sybase IQ as a supported data source > ----------------------------------------------------------- > > Key: TEIID-991 > URL: https://issues.jboss.org/browse/TEIID-991 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.10 > > > Per client: > We'd like the ability to have a built-in connector type for Sybase IQ, > just the same as Sybase ASE We have been getting inquiries and we've > had to decline one project because we didn't support Sybase IQ out of > the box. We foresee that Sybase IQ will be getting some play within > important Data Warehouses and Data Marts within the firm. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3209) Issues with mat view ttl

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3209?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3209. --------------------------------- > Issues with mat view ttl > ------------------------ > > Key: TEIID-3209 > URL: https://issues.jboss.org/browse/TEIID-3209 > Project: Teiid > Issue Type: Bug > Components: Documentation, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > The docs / code have matview_ttl as required, but the code will also prefer to use the cache hint ttl if it also supplied. I believe the cache hint should not be used in this case. > Generally there is also: TEIID-2194 which we should probably prefer properties over the cache hint because they are more targeted and can be more easily be manipulated at runtime. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2932) Datastax: fail to access PortfolioDemo (demo schema that provided by Datastax)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2932?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2932. --------------------------------- > Datastax: fail to access PortfolioDemo (demo schema that provided by Datastax) > ------------------------------------------------------------------------------- > > Key: TEIID-2932 > URL: https://issues.jboss.org/browse/TEIID-2932 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7 > Environment: Datastax with Teiid 8.7 CR > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Fix For: 8.10 > > > Fail to access PortfolioDemo (demo schema that provided by Datastax) and the the following exception: > java.lang.NullPointerException > at org.teiid.metadata.MetadataFactory.addColumn(MetadataFactory.java:204) > at org.teiid.translator.cassandra.CassandraMetadataProcessor.addColumnsToTable(CassandraMetadataProcessor.java:101) > at org.teiid.translator.cassandra.CassandraMetadataProcessor.addTable(CassandraMetadataProcessor.java:63) > at org.teiid.translator.cassandra.CassandraMetadataProcessor.process(CassandraMetadataProcessor.java:50) > at org.teiid.translator.cassandra.CassandraMetadataProcessor.process(CassandraMetadataProcessor.java:42) > at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:915) > at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73) > at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > at org.teiid.runtime.EmbeddedServer.loadMetadata(EmbeddedServer.java:685) > at org.teiid.runtime.AbstractVDBDeployer.loadMetadata(AbstractVDBDeployer.java:161) > at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:635) > at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:547) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3297) Possible NPE in WSConnectionImpl

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3297?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3297. --------------------------------- > Possible NPE in WSConnectionImpl > -------------------------------- > > Key: TEIID-3297 > URL: https://issues.jboss.org/browse/TEIID-3297 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > > {code} > ArrayList contentTypes = (ArrayList)this.responseContext.get("content-type"); //$NON-NLS-1$ > String contentType = contentTypes != null ? (String)contentTypes.get(0):"application/octet-stream"; //$NON-NLS-1$ > {code} > Looking at http://stackoverflow.com/questions/20392345/is-content-type-http-header-a... it is not always required but recommended. In the DV it is more required because, based on this it will to build the object of that type. What is missing is NPE handling there. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2015