[JBoss JIRA] Updated: (TEIID-196) Support creation of temp tables on physical sources.
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-196?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIID-196:
---------------------------------
Fix Version/s: 7.0
(was: 6.3.0)
> Support creation of temp tables on physical sources.
> ----------------------------------------------------
>
> Key: TEIID-196
> URL: https://jira.jboss.org/jira/browse/TEIID-196
> Project: Teiid
> Issue Type: Feature Request
> Components: Connector API, Query Engine
> Affects Versions: 6.0.0
> Reporter: Ken Johnson
> Fix For: 7.0
>
>
> This is a multi-part request.
> First, the system should support creation of temporary tables using a physical backing store rather than buffer manger. Given multi-pass SQL's heavy use of temp tables, buffer manager can easily be overloaded with large interim results stored in temp tables.
> Second, this should be a user-configurable behavior. For example, user might be able to choose a system-level or session-level default from among:
> -- memory/cache
> -- a source represented by a connector binding
> -- a distinct temp source defined with it's own connection parameters (possibly another schema in the repository DB instance)
> Ideally default selectoin should be override-able at temp table creation time through a DDL extension
> In the case where multiple temp tables have been created on a source via connector, the query planner should recognize this and leverage pushdown to the temp store when later query passes access multiple temp tables.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 6 months
[JBoss JIRA] Created: (TEIID-729) Default keystore may lead to confusion or provide false sense of security in encrypting passwords
by Ramesh Reddy (JIRA)
Default keystore may lead to confusion or provide false sense of security in encrypting passwords
-------------------------------------------------------------------------------------------------
Key: TEIID-729
URL: https://jira.jboss.org/jira/browse/TEIID-729
Project: Teiid
Issue Type: Bug
Components: Common
Affects Versions: 6.1.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.2.0
Currently Teiid source code contains a default "teiid.keystore", which is then used by any component (connector binding) in encrypting password. Designer does use this to encrypt the password as it does not have it's own private keystore. This poses
1) False sense of security, as this is mere obfuscation as "keystore" available to anybody.
2) If the Designer provides a keystore of its own, now it becomes the burden on the user to share this same keystore on the runtime environment to enable decrypting the password. Currently this major issue in connector binding as not starting, or somebody imports previous configuration where the passwords are encrypted with different keystore.
The simple solution is not provide a "default" keystore. If Designer does not provide a private keystore, then passwords in plain text in the connector binding properties. That will seamlessly run in Teiid runtime, if user does not care about having clear text passwords. That may be situation in DEV environments. In production environments during runtime (if required) Teiid will provide tools and instructions as to how to encrypt passwords.
If the user does provide keystore in the Designer then it is user responsibility to share this keystore with runtime environment, that they work in sync in encrypting and decrypting the password.
Users will be provided with scripts to generate a keystore with Teiid kit, with which they can use to encrypt the passwords. So, this will make the encryption as an option rather than requirement in the Teiid system.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 6 months