October 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5449) Infinispan: Update Infinispan translator to 9.3 version

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5449?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-5449 at 10/5/18 8:10 AM: ------------------------------------------------------------- After looking deeper at the code, the doc filtering is done by the teiid query evaluator. Which wouldn't it be better to apply the filter when the infinispan query is being issued, and push the filtering to the source? Yes, the infinispan query language is more limiting that what Teiid can evaluate, but I think that filtering (what infinispan doesn't support) could then be done in the translator. was (Author: van.halbert): [~rareddy] Does the marshaller that is registered in the client, is that logic performed on the client or pushed to the server? Reading the docs, its not clear, but seem to imply its done on the client, so I wasnt' sure if you have already made that determination. > Infinispan: Update Infinispan translator to 9.3 version > ------------------------------------------------------- > > Key: TEIID-5449 > URL: https://issues.jboss.org/browse/TEIID-5449 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Assignee: Van Halbert > Priority: Major > Fix For: 11.2 > > > Two changes observed > - The new cache create API changed, the old has been deprecated > - cache.get(key) now became Async operation, that means Thread Based serialization context no longer works. This needs to be removed, but there seem to be no better alternatives to support the Async threads. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5497) MetadataRepository can't be implemented

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5497?page=com.atlassian.jira.plugin... ] Work on TEIID-5497 started by Steven Hawkins. --------------------------------------------- > MetadataRepository can't be implemented > --------------------------------------- > > Key: TEIID-5497 > URL: https://issues.jboss.org/browse/TEIID-5497 > Project: Teiid > Issue Type: Enhancement > Affects Versions: 10.2.2 > Reporter: Don Krapohl > Assignee: Steven Hawkins > Priority: Major > Labels: metadata, teiid-engine > > I am unable to extend the MetadataRepository class as shown in the Teiid documentation. Per [~rareddy] the class is now abstract (public abstract class MetadataRepository<F,C>) and can't be implemented through the service loader. I'd like to see if you could implement a mechanism that allows custom metadata repositories again. > Ref: https://developer.jboss.org/thread/278855 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5498) Allow the pg layer to work for simple selects with the postgres_fdw

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5498?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5498: --------------------------------------- The initial commit is. I'll do more testing with a variety of types. We may also need to add enforcement of metadata constraints - such as string length - as to ensure proper results. That would be similar to existing logic in odata. This is also not a general purpose solution yet as including predicates can result in sql that isn't yet valid for us, such as using pg type names in casts 'a'::text - most of those issues would be easy to address though. > Allow the pg layer to work for simple selects with the postgres_fdw > ------------------------------------------------------------------- > > Key: TEIID-5498 > URL: https://issues.jboss.org/browse/TEIID-5498 > Project: Teiid > Issue Type: Sub-task > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > Another avenue for materialization support outlined in TEIID-4251 is to rely upon pg materialization, which would be easiest to setup through their foreign data wrapper. However it expects some additional support for: > start transaction syntax > abort transaction > automatic cleanup of portals/cursors at the end of a transaction > prepared cursors > Additionally this will have the same performance issue that we have with declare/fetch initially - that is a cursor requires a transaction, and our current strategy requires pre-buffering the results under a transaction. However since this would only be used for load/refresh that performance hit may be negligible - if now we'd need similar logic to effectively ignore the transaction wrapping. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5498) Allow the pg layer to work for simple selects with the postgres_fdw

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5498: ------------------------------------- Summary: Allow the pg layer to work for simple selects with the postgres_fdw Key: TEIID-5498 URL: https://issues.jboss.org/browse/TEIID-5498 Project: Teiid Issue Type: Sub-task Components: ODBC Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 11.2 Another avenue for materialization support outlined in TEIID-4251 is to rely upon pg materialization, which would be easiest to setup through their foreign data wrapper. However it expects some additional support for: start transaction syntax abort transaction automatic cleanup of portals/cursors at the end of a transaction prepared cursors Additionally this will have the same performance issue that we have with declare/fetch initially - that is a cursor requires a transaction, and our current strategy requires pre-buffering the results under a transaction. However since this would only be used for load/refresh that performance hit may be negligible - if now we'd need similar logic to effectively ignore the transaction wrapping. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5497) MetadataRepository can't be implemented

by Don Krapohl (Jira)

Don Krapohl created TEIID-5497: ---------------------------------- Summary: MetadataRepository can't be implemented Key: TEIID-5497 URL: https://issues.jboss.org/browse/TEIID-5497 Project: Teiid Issue Type: Enhancement Affects Versions: 10.2.2 Reporter: Don Krapohl Assignee: Steven Hawkins I am unable to extend the MetadataRepository class as shown in the Teiid documentation. Per [~rareddy] the class is now abstract (public abstract class MetadataRepository<F,C>) and can't be implemented through the service loader. I'd like to see if you could implement a mechanism that allows custom metadata repositories again. Ref: https://developer.jboss.org/thread/278855 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5449) Infinispan: Update Infinispan translator to 9.3 version

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5449?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5449: ------------------------------------ [~rareddy] Does the marshaller that is registered in the client, is that logic performed on the client or pushed to the server? Reading the docs, its not clear, but seem to imply its done on the client, so I wasnt' sure if you have already made that determination. > Infinispan: Update Infinispan translator to 9.3 version > ------------------------------------------------------- > > Key: TEIID-5449 > URL: https://issues.jboss.org/browse/TEIID-5449 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Assignee: Van Halbert > Priority: Major > Fix For: 11.2 > > > Two changes observed > - The new cache create API changed, the old has been deprecated > - cache.get(key) now became Async operation, that means Thread Based serialization context no longer works. This needs to be removed, but there seem to be no better alternatives to support the Async threads. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-4251 at 10/4/18 11:45 AM: ----------------------------------------------------------------- Issues with this approach: - fail fast? the fdw seems to hang if the remote server is not available, but that shouldn't really be a concern - expanded transaction statement support. the fdw expects more syntax for start transaction and abort transaction - import seems to succeed and the tables are visible in pg_class, but they are not resolvable -- using create foreign table... does create a querable table - but of course is not what I was going for It appears that the logic requires a local schema that matches the remote. Otherwise the query sent to the remote will be qualified with the wrong (local) schema name. It also fixes the import problem - so import ... "SYS" into sys is fine, but import ... "SYS" into public doesn't work. - the execution against a foreign table uses a prepared cursor syntax than we currently have support for - local names must match exactly, so quoted with case that matches Teiid - IMPORT FOREIGN SCHEMA "SYS" - as generated queries end up using predicates like name = '...' was (Author: shawkins): Issues with this approach: - fail fast? the fdw seems to hang if the remote server is not available, but that shouldn't really be a concern - expanded transaction statement support. the fdw expects more syntax for start transaction and abort transaction - import seems to succeed and the tables are visible in pg_class, but they are not resolvable -- using create foreign table... does create a querable table - but of course is not what I was going for - the execution against a foreign table uses a prepared cursor syntax than we currently have support for > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-4251 > URL: https://issues.jboss.org/browse/TEIID-4251 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like > - Creation of a common STATUS table > - Creation of the materilization targets (create views on dbms) > - On load, on undeploy and load scripts for all the materialization views > We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-4251 at 10/4/18 11:04 AM: ----------------------------------------------------------------- Issues with this approach: - fail fast? the fdw seems to hang if the remote server is not available, but that shouldn't really be a concern - expanded transaction statement support. the fdw expects more syntax for start transaction and abort transaction - import seems to succeed and the tables are visible in pg_class, but they are not resolvable -- using create foreign table... does create a querable table - but of course is not what I was going for - the execution against a foreign table uses a prepared cursor syntax than we currently have support for was (Author: shawkins): Issues with this approach: - fail fast? the fdw seems to hang if the remote server is not available, but that shouldn't really be a concern - expanded transaction statement support. the fdw expects more syntax for start transaction and abort transaction - import seems to succeed and the tables are visible in pg_class, but they are not resolvable -- using create foreign table... does create a querable table - but of course is not what I was going for - the execution against a foreign table uses a different declare cursor syntax than we currently have support for > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-4251 > URL: https://issues.jboss.org/browse/TEIID-4251 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like > - Creation of a common STATUS table > - Creation of the materilization targets (create views on dbms) > - On load, on undeploy and load scripts for all the materialization views > We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4251: --------------------------------------- Issues with this approach: - fail fast? the fdw seems to hang if the remote server is not available, but that shouldn't really be a concern - expanded transaction statement support. the fdw expects more syntax for start transaction and abort transaction - import seems to succeed and the tables are visible in pg_class, but they are not resolvable -- using create foreign table... does create a querable table - but of course is not what I was going for - the execution against a foreign table uses a different declare cursor syntax than we currently have support for > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-4251 > URL: https://issues.jboss.org/browse/TEIID-4251 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.2 > > > If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like > - Creation of a common STATUS table > - Creation of the materilization targets (create views on dbms) > - On load, on undeploy and load scripts for all the materialization views > We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5449) Infinispan: Update Infinispan translator to 9.3 version

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5449?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5449: ------------------------------------- [~van.halbert] Look at [1] the last parameter `DocumentFilter` which is part of the marshaller based on the query submitted not the table, but the name we have given is at Table level. There needs to be work done such that DocumentFilter is applied correctly with Entity/Table level Marshaller without conflict among two concurrent queries on the same table but with different criteria. I can take look at this, but right now I have other high priority items. [1] https://github.com/rareddy/teiid/blob/master/connectors/infinispan/infini... > Infinispan: Update Infinispan translator to 9.3 version > ------------------------------------------------------- > > Key: TEIID-5449 > URL: https://issues.jboss.org/browse/TEIID-5449 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Assignee: Van Halbert > Priority: Major > Fix For: 11.2 > > > Two changes observed > - The new cache create API changed, the old has been deprecated > - cache.get(key) now became Async operation, that means Thread Based serialization context no longer works. This needs to be removed, but there seem to be no better alternatives to support the Async threads. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2018