April 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3434) Ability to enable/disable caching by table and/or source

by Burak Serdar (JIRA)

[ https://issues.jboss.org/browse/TEIID-3434?page=com.atlassian.jira.plugin... ] Burak Serdar updated TEIID-3434: -------------------------------- Is there a way to control result set caching as well? For tables containing real time data, we'd like to execute the same statement repeatedly, but expect to see different data. ----- Original Message ----- > Ability to enable/disable caching by table and/or source > -------------------------------------------------------- > > Key: TEIID-3434 > URL: https://issues.jboss.org/browse/TEIID-3434 > Project: Teiid > Issue Type: Feature Request > Reporter: Burak Serdar > Assignee: Steven Hawkins > > We need to be able to enable/disable caching by table and/or source. Some of our tables have real-time data, and we do not want to cache those, and some other tables can use cached data. It is not sufficient to use SQL options to turn caching on or off, because we're using 3rd party tools, and we don't have control over the SQL they generate. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3434) Ability to enable/disable caching by table and/or source

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3434?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3434: ------------------------------------- Setting the "materialization=true" flag does what you looking for. Is that not sufficient? When you do not want to use cache you can always supply OPTION NOCACHE in the query. > Ability to enable/disable caching by table and/or source > -------------------------------------------------------- > > Key: TEIID-3434 > URL: https://issues.jboss.org/browse/TEIID-3434 > Project: Teiid > Issue Type: Feature Request > Reporter: Burak Serdar > Assignee: Steven Hawkins > > We need to be able to enable/disable caching by table and/or source. Some of our tables have real-time data, and we do not want to cache those, and some other tables can use cached data. It is not sufficient to use SQL options to turn caching on or off, because we're using 3rd party tools, and we don't have control over the SQL they generate. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3434) Ability to enable/disable caching by table and/or source

by Burak Serdar (JIRA)

Burak Serdar created TEIID-3434: ----------------------------------- Summary: Ability to enable/disable caching by table and/or source Key: TEIID-3434 URL: https://issues.jboss.org/browse/TEIID-3434 Project: Teiid Issue Type: Feature Request Reporter: Burak Serdar Assignee: Steven Hawkins We need to be able to enable/disable caching by table and/or source. Some of our tables have real-time data, and we do not want to cache those, and some other tables can use cached data. It is not sufficient to use SQL options to turn caching on or off, because we're using 3rd party tools, and we don't have control over the SQL they generate. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3429) Provide hooks to interrogate metadata prior to full import

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3429?page=com.atlassian.jira.plugin... ] Work on TEIID-3429 started by Steven Hawkins. --------------------------------------------- > Provide hooks to interrogate metadata prior to full import > ----------------------------------------------------------- > > Key: TEIID-3429 > URL: https://issues.jboss.org/browse/TEIID-3429 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > To support the Desinger we should offer the ability to interrogate metadata prior to full import. > Exploring metadata is effectively an entirely different mode of operation with respect to the current metadata processing logic on the Teiid side. Also partial metadata isn't something that would neatly be expressed through DDL - tables without columns, a list of schema names, etc. > Ways around that would be to expose source procedures for metadata interrogation: > > getTableNames - which would probably give both the Teiid name and the name in source and consider the current translator metadata settings > getProcedureNames > And importer specific info such as for JDBC getTableTypes, getCatalogNames, getSchemaNames > > I'd want to keep it fairly high level though. Getting column or key information I'd expect would be done through the normal full import. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3218) Translator for MarkLogic

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIID-3218?page=com.atlassian.jira.plugin... ] Andrej Šmigala reassigned TEIID-3218: ------------------------------------- Assignee: Andrej Šmigala > Translator for MarkLogic > ------------------------ > > Key: TEIID-3218 > URL: https://issues.jboss.org/browse/TEIID-3218 > Project: Teiid > Issue Type: Feature Request > Components: Connector API > Reporter: Tom Johnston > Assignee: Andrej Šmigala > Fix For: Open To Community > > > Full Crud support for MarkLogic... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3433) Teiid designer DDL importer fails to import file exported using the exporter

by Burak Serdar (JIRA)

Burak Serdar created TEIID-3433: ----------------------------------- Summary: Teiid designer DDL importer fails to import file exported using the exporter Key: TEIID-3433 URL: https://issues.jboss.org/browse/TEIID-3433 Project: Teiid Issue Type: Bug Reporter: Burak Serdar Assignee: Steven Hawkins Attachments: sfexport.ddl Exporting a salesforce model to DDL and importing it back fails because of a parse error in the importer. If I remove all primary key and foreign key constraints, it imports the tables without any columns. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3433) Teiid designer DDL importer fails to import file exported using the exporter

by Burak Serdar (JIRA)

[ https://issues.jboss.org/browse/TEIID-3433?page=com.atlassian.jira.plugin... ] Burak Serdar updated TEIID-3433: -------------------------------- Attachment: sfexport.ddl The failing DDL file. > Teiid designer DDL importer fails to import file exported using the exporter > ---------------------------------------------------------------------------- > > Key: TEIID-3433 > URL: https://issues.jboss.org/browse/TEIID-3433 > Project: Teiid > Issue Type: Bug > Reporter: Burak Serdar > Assignee: Steven Hawkins > Attachments: sfexport.ddl > > > Exporting a salesforce model to DDL and importing it back fails because of a parse error in the importer. > If I remove all primary key and foreign key constraints, it imports the tables without any columns. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3425) Pass-through kerberos authentication on IBM JDK - principal is not passed to MSSQL driver

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3425?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3425: ---------------------------------- Fix Version/s: 8.12 > Pass-through kerberos authentication on IBM JDK - principal is not passed to MSSQL driver > ----------------------------------------------------------------------------------------- > > Key: TEIID-3425 > URL: https://issues.jboss.org/browse/TEIID-3425 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: Fedora 20 > java: IBM JDK 1.7 > arch: x86_64 > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Fix For: 8.12 > > Attachments: set-up-mssql-ibm.cli, sql2012krb-static-vdb.xml, sql2012krb-vdb.xml > > > I have configured a datasource for MSSQL database. The datasource uses PassthroughIdentityLoginModule. I have also created a VDB which requires kerberos authentication. I am trying to pass credentials used for authentication CLIENT <=> TEIID to datasource so they can be used for authentication TEIID <=> MSSQL. > Method getConnection(..) (record in server log) is called with correct credentials, but SQLServerDriver throws an exception: > initAuthInit failed privileged exception:-java.security.PrivilegedActionException: org.ietf.jgss.GSSException, major code: 13, minor code: 0 > major string: Invalid credentials > minor string: Cannot get credential from JAAS Subject for principal: default principal > Some ideas, but I am only guessing: > 1. I have seen same exception (on client side) if system property "javax.security.auth.useSubjectCredsOnly" is set to false on client side. As this property is set to true in the server config (<property name="javax.security.auth.useSubjectCredsOnly" value="true"/>), it is probably not passed to the driver (or is being ignored). > 2. SQLServerDriver sets two system properties by default (if no kerberos configuration file is specified) useDefaultCcache = true moduleBanner = false - see https://msdn.microsoft.com/en-us/library/gg558122%28v=sql.110%29.aspx - ibm kerberos login module will try to get TGT from ticket cache > I have tried static kerberos configuration for same DS and there was no problem with it. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3432) support: MongoDB 3.0

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3432?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3432: ------------------------------------- [~ichanjasper] would it be possible for you to see what are the changes required and submit a patch? I am guessing it should be straight forward patch. > support: MongoDB 3.0 > --------------------- > > Key: TEIID-3432 > URL: https://issues.jboss.org/browse/TEIID-3432 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.10 > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Fix For: 8.11 > > > According latest documentation for MongoDB 3.0 (Driver Compatibility Changes[1]) the minimum driver version required is 2.13. Currently Teiid 8.10 is using 2.12 > http://docs.mongodb.org/manual/release-notes/3.0-compatibility/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3432) support: MongoDB 3.0

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3432?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3432: ----------------------------------- Assignee: Ramesh Reddy > support: MongoDB 3.0 > --------------------- > > Key: TEIID-3432 > URL: https://issues.jboss.org/browse/TEIID-3432 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.10 > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Fix For: 8.11 > > > According latest documentation for MongoDB 3.0 (Driver Compatibility Changes[1]) the minimum driver version required is 2.13. Currently Teiid 8.10 is using 2.12 > http://docs.mongodb.org/manual/release-notes/3.0-compatibility/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2015