[JBoss JIRA] (TEIID-3793) Push Teiid function LOCATE() to SQL Server
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3793?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3793:
----------------------------------
Fix Version/s: 8.12.2
8.13
Thanks Jean-Pierre, we'll get this change in soon.
> Push Teiid function LOCATE() to SQL Server
> ------------------------------------------
>
> Key: TEIID-3793
> URL: https://issues.jboss.org/browse/TEIID-3793
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Connector
> Affects Versions: 8.7.1.6_2
> Environment: JBOSS DV 6.2
> Microsoft SQL Server 10.50.1600.1
> Reporter: Jean-Pierre Matsumoto
> Assignee: Steven Hawkins
> Fix For: 8.13, 8.12.2
>
>
> We have some Teiid views with query similar to:
> SELECT col1
> FROM tableA
> WHERE SUBSTRING(col1, 1, LOCATE(' ', col1)) = 'PREFIX'
> SQL Server receives a full scan of col1 table without WHERE:
> SELECT col1
> FROM tableA
> Because Teiid LOCATE() function is not translated to CHARINDEX() SQL Server function (SUBSTRING is translated).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-1942) Add the support for accessing Coherence
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1942?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-1942:
---------------------------------------
> At this point, unless there's another reason to keep this jira open, I would suggest closing this. And I will open new jira's as enhancements are targeted.
You'll want to leave this open until the branch is merged. Or is this something that is product only and will be built separately?
> Add the support for accessing Coherence
> ---------------------------------------
>
> Key: TEIID-1942
> URL: https://issues.jboss.org/browse/TEIID-1942
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.10
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.12.x
>
>
> Add the support for using the Coherence
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3140) Add getVDBType() method to the VDB interface
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3140?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3140.
-----------------------------------
Fix Version/s: (was: 8.12.1)
Resolution: Out of Date
We already set the deployment-name property on VDBs. That can be used to determine if it's an xml or a zip deployment. That seems sufficient for now.
> Add getVDBType() method to the VDB interface
> --------------------------------------------
>
> Key: TEIID-3140
> URL: https://issues.jboss.org/browse/TEIID-3140
> Project: Teiid
> Issue Type: Enhancement
> Components: AdminApi
> Reporter: Barry LaFond
> Assignee: Steven Hawkins
>
> Because Teiid supports mutliple VDB types, any tooling designed to interact (edit, deploy, undeploy, display etc...) with the runtime VDBs will need to be able to easilly distinguish what each VDB type is.
> Currently Teiid Designer utilizes PREVIEW and defeault VDBs with *vdb* file extensions and there are 2 types of dynamic VDBs, *xml* and *zip* files backed by DDL model metadata definitions.
> The current VDB interface currently doesn't provide a type.
> Request adding something like:
> {code}
> public enum VDBType {DEFAULT, PREVIEW, XML, DDL}
> /**
> * @return the vdb type
> */
> public VDBType getVDBType();
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-2476) Exclude hidden tables/columns from metadata
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2476?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2476:
----------------------------------
Fix Version/s: 9.0
> Exclude hidden tables/columns from metadata
> -------------------------------------------
>
> Key: TEIID-2476
> URL: https://issues.jboss.org/browse/TEIID-2476
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Driver, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.0
>
>
> We should offer or possibly default to filtering tables/columns that can not accessed out of the user metadata. This should be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it is easier to add filters to the DatabaseMetadata (and ideally pg) metadata queries.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3725) In the JDG translators, enable named cache swapping so that materialization can be supported
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3725?page=com.atlassian.jira.plugin... ]
Work on TEIID-3725 started by Van Halbert.
------------------------------------------
> In the JDG translators, enable named cache swapping so that materialization can be supported
> --------------------------------------------------------------------------------------------
>
> Key: TEIID-3725
> URL: https://issues.jboss.org/browse/TEIID-3725
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.12
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> The JDG translators, that in order to support materialization, will need to enable the named cache that's referenced by the connection, to be swapped. This is due to JDG doesn't currently support renaming a cache (i.e., like table rename in JDBC). And because of that, it limits how the cache can be refreshed (don't want to clear it before re-loading).
> Ideas are:
> 1. configure translator with the 2 cache names to use (a) initial cache to read from and (b) the staging cache to use
> perform materialize load
> call SYSADMIN.setProperty to trigger the swapping of the cache names
> 2 ???
> Note: because there's no persistence in Teiid so that any cache name changes will outlive a server restart, when a restart occurs, the translator will read from the cache identified as the initial cache to read from.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3790) Restrict any authenticated roles
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3790?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3790.
-----------------------------------
Resolution: Done
Removed role assignment for unauthenticated sessions.
> Restrict any authenticated roles
> --------------------------------
>
> Key: TEIID-3790
> URL: https://issues.jboss.org/browse/TEIID-3790
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.x
>
>
> A local connection with the pass-through flag set will allow any connection if no security domain is set (the 8.x default). Beyond that the role assignment logic will any authenticated roles to those users. We need to restrict any-authenticated roles to only properly authenticated users.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months