February 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4785) Add options through alter table in DDL does not work.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4785?page=com.atlassian.jira.plugin... ] Work on TEIID-4785 started by Steven Hawkins. --------------------------------------------- > Add options through alter table in DDL does not work. > ----------------------------------------------------- > > Key: TEIID-4785 > URL: https://issues.jboss.org/browse/TEIID-4785 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.2 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Fix For: 9.3, 9.2.1 > > > A command like the one below fails > ALTER TABLE "teiidtest" options (add cardinality 1); > This fails with message: > This complains that the "group" teiidtest could not be found. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4626) Add a full snapshot refresh strategy based upon table modifications

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4626?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4626: --------------------------------------- Here's some possible refinements: https://github.com/shawkins/teiid/commit/6f8b67d097f9293802c9548bc0c117ec... - discover a unique set of contributing tables - remove the need for refresh type property - allow for both ttl and staleness to be used at the same time - refined the staleness calculation to account for cardinality 0 and to be based upon a percentage of the square root rather than just the percentage. So a likely recommendation would be 10 which would mean 1 update for a 100 row matview, 100 updates for a million row matview, 1000 updates for a 100 million row matview, etc. > Add a full snapshot refresh strategy based upon table modifications > ------------------------------------------------------------------- > > Key: TEIID-4626 > URL: https://issues.jboss.org/browse/TEIID-4626 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.3 > > > using the existing full materialization refresh logic we can trigger a refresh based upon a notion of how dirty a table is based upon a proportion of rows updated to the rows in the table. This would also require some change to the status table to capture the number of transitive row updates. This could then be hooked up to debezium as the event source. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4789) OData - Allow reading/writing messages in GZIP format

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4789?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-4789: ------------------------------------- Yes, I was thinking about native support. Some application servers do support this (e.g. for Tomcat, all you need to do is set a property). Even WildFly do support this. E.g. for JAX-RS, you just set 'Content-Encoding' header for your response and server will take care for gzipping. Similarly for request body. But I am not sure whether there similar mechanism for servlets (at least I did not find any). Moreover, with this solution it will work out-of-the-box on any application server (of course there are issues with teiid-related dependencies but that is different question). > OData - Allow reading/writing messages in GZIP format > ----------------------------------------------------- > > Key: TEIID-4789 > URL: https://issues.jboss.org/browse/TEIID-4789 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Juraj Duráni > Assignee: Juraj Duráni > Priority: Minor > > Allow writing and reading messages in GZIP format for OData interfaces. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4789) OData - Allow reading/writing messages in GZIP format

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4789?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4789: ------------------------------------- Agreed, browsers are much more smart about this (not sure about smoke signals :) ) than individual applications that are based on OData. As long this is not impede that, it should be OK. Frankly, these kind of cross cutting concerns should be supported natively from web-server itself IMO. > OData - Allow reading/writing messages in GZIP format > ----------------------------------------------------- > > Key: TEIID-4789 > URL: https://issues.jboss.org/browse/TEIID-4789 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Juraj Duráni > Assignee: Juraj Duráni > Priority: Minor > > Allow writing and reading messages in GZIP format for OData interfaces. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4789) OData - Allow reading/writing messages in GZIP format

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4789?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-4789: ------------------------------------- Regarding why - it will reduce amount of data transfered between client and server. > OData - Allow reading/writing messages in GZIP format > ----------------------------------------------------- > > Key: TEIID-4789 > URL: https://issues.jboss.org/browse/TEIID-4789 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Juraj Duráni > Assignee: Juraj Duráni > Priority: Minor > > Allow writing and reading messages in GZIP format for OData interfaces. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4789) OData - Allow reading/writing messages in GZIP format

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4789?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-4789: ------------------------------------- Regarding specification - I do not believe there is need for (OData) specification for this. It could be covered by specification of HTTP headers. OData specification specifies format of the message - JSON, XML. It does not say anything about format in which we transfer it to client - GZIP, ZIP, smoke signals :). > OData - Allow reading/writing messages in GZIP format > ----------------------------------------------------- > > Key: TEIID-4789 > URL: https://issues.jboss.org/browse/TEIID-4789 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Juraj Duráni > Assignee: Juraj Duráni > Priority: Minor > > Allow writing and reading messages in GZIP format for OData interfaces. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4789) OData - Allow reading/writing messages in GZIP format

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4789?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-4789 at 2/27/17 12:29 PM: --------------------------------------------------------------- [~jdurani] I am not asking how it works, but asking why? We can not do any enhancements outside the OData specification, if we do that our solution will no longer be inter-operable. If specification allows it then yes. was (Author: rareddy): [~jdurani] I am not asking how it works, but asking why? We can not do any enhancements outside the OData specification, if we do that will, we solution will no longer be inter-operable. If specification allows it then yes. > OData - Allow reading/writing messages in GZIP format > ----------------------------------------------------- > > Key: TEIID-4789 > URL: https://issues.jboss.org/browse/TEIID-4789 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Juraj Duráni > Assignee: Juraj Duráni > Priority: Minor > > Allow writing and reading messages in GZIP format for OData interfaces. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4789) OData - Allow reading/writing messages in GZIP format

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4789?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4789: ------------------------------------- [~jdurani] I am not asking how it works, but asking why? We can not do any enhancements outside the OData specification, if we do that will, we solution will no longer be inter-operable. If specification allows it then yes. > OData - Allow reading/writing messages in GZIP format > ----------------------------------------------------- > > Key: TEIID-4789 > URL: https://issues.jboss.org/browse/TEIID-4789 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Juraj Duráni > Assignee: Juraj Duráni > Priority: Minor > > Allow writing and reading messages in GZIP format for OData interfaces. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4789) OData - Allow reading/writing messages in GZIP format

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4789?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-4789: ------------------------------------- The way how to make client aware of the compression is via standard HTTP header 'Content-Encoding'. The basic idea is: Iff client send HTTP request header 'Accept-Encoding' with value 'gzip' (e.g Firefox sends 'Accept-Encoding: gzip,deflate'), then server will encode output as a GZIP and send it along with HTTP response header 'Content-Encoding: gzip'. Otherwise response body will not be inflated. I.e. we will inflate it only if user is capable of handling it (which he/she states so with setting 'Accept-Encoding' header) Similary for request body. If client sends HTTP request header 'Content-Encoding: gzip', then we expect input to be inflated and we will deflate if before passing to the application. > OData - Allow reading/writing messages in GZIP format > ----------------------------------------------------- > > Key: TEIID-4789 > URL: https://issues.jboss.org/browse/TEIID-4789 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Juraj Duráni > Assignee: Juraj Duráni > Priority: Minor > > Allow writing and reading messages in GZIP format for OData interfaces. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4719) Add a ddl equivalent to the metadata tag

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4719?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-4719 at 2/27/17 12:21 PM: --------------------------------------------------------------- Looks like I added an example, but missed the BNF definition in the document. Corrected it now in 9.3 documents was (Author: rareddy): Looks like I added an example, but missed the BNF definition in the document. Corrected it now. > Add a ddl equivalent to the metadata tag > ---------------------------------------- > > Key: TEIID-4719 > URL: https://issues.jboss.org/browse/TEIID-4719 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 9.2 > > > Generally we'll need something that is equivalent to the metadata tag - that can specify a repo and options. In a zip deployment this will allow splitting the ddl over multiple files. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2017