[JBoss JIRA] (TEIID-3725) In the JDG translators, enable named cache swapping so that materialization can be supported
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3725?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3725:
---------------------------------------
Just wanted to check what you mean by the resource adapter will know the name of what is being truncated/swapped. Can there only be a single materialization per resource adapter?
> 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)
10 years, 2 months
[JBoss JIRA] (TEIID-3870) Add ability to properly qualify package objects
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3870?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3870:
---------------------------------------
> Can you explain how to use the JDBC api database metadata to get objects in packages?
The DatabaseMetaData doesn't have this concern. As long as the package is in the schema(s) you are importing against the procedures will be reported in the getProcedures method - just with a catalog name as the package name.
> Add ability to properly qualify package objects
> -----------------------------------------------
>
> Key: TEIID-3870
> URL: https://issues.jboss.org/browse/TEIID-3870
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector
> Affects Versions: 8.7.1.6_2
> Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3,
> JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157
> 64-bit Windows 7 environment
> Reporter: Steve Tran
> Assignee: Steven Hawkins
> Fix For: 8.13, 8.12.4
>
>
> Even if the catalog name pattern matches package names, there is no option or recognition that contained procedures should be qualified as <package / catalog>.<name>.
> We need this because at least in Oracle, procedures may be encapsulated in Oracle Packages that are used as catalog names in the DatabaseMetaData. When trying to import these into Teiid, the "Name in Source" field does not allow me to specify the Package name, so I can't call those procedures.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3870) Add ability to properly qualify package objects
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3870?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3870:
------------------------------------
Can you explain how to use the JDBC api database metadata to get objects in packages?
To my knowledge, there is no current way, using the JDBC api metadata, to get a list of packages and then obtain of list of objects within each package. To do this, you must query the system tables.
> Add ability to properly qualify package objects
> -----------------------------------------------
>
> Key: TEIID-3870
> URL: https://issues.jboss.org/browse/TEIID-3870
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector
> Affects Versions: 8.7.1.6_2
> Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3,
> JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157
> 64-bit Windows 7 environment
> Reporter: Steve Tran
> Assignee: Steven Hawkins
> Fix For: 8.13, 8.12.4
>
>
> Even if the catalog name pattern matches package names, there is no option or recognition that contained procedures should be qualified as <package / catalog>.<name>.
> We need this because at least in Oracle, procedures may be encapsulated in Oracle Packages that are used as catalog names in the DatabaseMetaData. When trying to import these into Teiid, the "Name in Source" field does not allow me to specify the Package name, so I can't call those procedures.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3871) moving documentation from confluence to gitbook
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3871?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3871:
-------------------------------------
[~kylin]I am not sure what webhook to add, so I gave you admin permission to the repo, so you can add it.
> moving documentation from confluence to gitbook
> -------------------------------------------------
>
> Key: TEIID-3871
> URL: https://issues.jboss.org/browse/TEIID-3871
> Project: Teiid
> Issue Type: Task
> Components: Documentation
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.x
>
>
> From Teiid DV 7 F2F Notes,
> " In the Teiid 9.x timeframe we should look toward moving everything to gitbook / markdown. We should start by migrating the documentation and solicit help with the website if possible."
> This issue will address this.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3871) moving documentation from confluence to gitbook
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3871?page=com.atlassian.jira.plugin... ]
Kylin Soong edited comment on TEIID-3871 at 1/14/16 5:03 AM:
-------------------------------------------------------------
h2. Quick Overview
Quick overview: [https://teiid.gitbooks.io/documents/content/index.html]
Sources Content link: [https://github.com/teiid/teiid-documents]
h2.Document Migration Status
||Name||Status||link||
|Embedded Guide |Done |[https://www.gitbook.com/book/teiid/embedded-guide/details] |
|Security Guide |Done |[https://www.gitbook.com/book/teiid/security-guide/details] |
|Caching Guide |Done |[https://www.gitbook.com/book/teiid/caching-guide/details] |
|Administrator's Guide |Pending |- |
|Client Developer's Guide |Pending |- |
|Developer's Guide |Pending |- |
|Reference Guide |Scheduled |- |
{color:#d04437}*Note that*{color}: Once a doc in '*Done*' status, please update doc via submit to Github, rather than edit Conference pages.
was (Author: kylin):
h2.Document Migration Status
||Name||Status||link||
|Embedded Guide |Done |[https://www.gitbook.com/book/teiid/embedded-guide/details] |
|Security Guide |Done |[https://www.gitbook.com/book/teiid/security-guide/details] |
|Caching Guide |Done |[https://www.gitbook.com/book/teiid/caching-guide/details] |
|Administrator's Guide |Pending |- |
|Client Developer's Guide |Pending |- |
|Developer's Guide |Pending |- |
|Reference Guide |Scheduled |- |
{color:#d04437}Note that{color}: Once a doc in '*Done*' status, please update doc via submit to Github, rather than edit Conference pages.
> moving documentation from confluence to gitbook
> -------------------------------------------------
>
> Key: TEIID-3871
> URL: https://issues.jboss.org/browse/TEIID-3871
> Project: Teiid
> Issue Type: Task
> Components: Documentation
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.x
>
>
> From Teiid DV 7 F2F Notes,
> " In the Teiid 9.x timeframe we should look toward moving everything to gitbook / markdown. We should start by migrating the documentation and solicit help with the website if possible."
> This issue will address this.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3871) moving documentation from confluence to gitbook
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3871?page=com.atlassian.jira.plugin... ]
Kylin Soong edited comment on TEIID-3871 at 1/14/16 4:39 AM:
-------------------------------------------------------------
h2.Document Migration Status
||Name||Status||link||
|Embedded Guide |Done |[https://www.gitbook.com/book/teiid/embedded-guide/details] |
|Security Guide |Done |[https://www.gitbook.com/book/teiid/security-guide/details] |
|Caching Guide |Done |[https://www.gitbook.com/book/teiid/caching-guide/details] |
|Administrator's Guide |Pending |- |
|Client Developer's Guide |Pending |- |
|Developer's Guide |Pending |- |
|Reference Guide |Scheduled |- |
{color:#d04437}Note that{color}: Once a doc in '*Done*' status, please update doc via submit to Github, rather than edit Conference pages.
was (Author: kylin):
h2.Document Migration Status
||Name||Status||link||
|Embedded Guide |Done |[https://www.gitbook.com/book/teiid/embedded-guide/details] |
|Security Guide |Done |[https://www.gitbook.com/book/teiid/security-guide/details] |
|Caching Guide |Pending |- |
|Administrator's Guide |Pending |- |
|Client Developer's Guide |Pending |- |
|Developer's Guide |Pending |- |
|Reference Guide |Scheduled |- |
{color:#d04437}Note that{color}: Once a doc in '*Done*' status, please update doc via submit to Github, rather than edit Conference pages.
> moving documentation from confluence to gitbook
> -------------------------------------------------
>
> Key: TEIID-3871
> URL: https://issues.jboss.org/browse/TEIID-3871
> Project: Teiid
> Issue Type: Task
> Components: Documentation
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.x
>
>
> From Teiid DV 7 F2F Notes,
> " In the Teiid 9.x timeframe we should look toward moving everything to gitbook / markdown. We should start by migrating the documentation and solicit help with the website if possible."
> This issue will address this.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3871) moving documentation from confluence to gitbook
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3871?page=com.atlassian.jira.plugin... ]
Kylin Soong edited comment on TEIID-3871 at 1/14/16 1:51 AM:
-------------------------------------------------------------
h2.Document Migration Status
||Name||Status||link||
|Embedded Guide |Done |[https://www.gitbook.com/book/teiid/embedded-guide/details] |
|Security Guide |Done |[https://www.gitbook.com/book/teiid/security-guide/details] |
|Caching Guide |Pending |- |
|Administrator's Guide |Pending |- |
|Client Developer's Guide |Pending |- |
|Developer's Guide |Pending |- |
|Reference Guide |Scheduled |- |
{color:#d04437}Note that{color}: Once a doc in '*Done*' status, please update doc via submit to Github, rather than edit Conference pages.
was (Author: kylin):
h2.Document Migration Status
||Name||Status||link||
|Embedded Guide |Done |[https://www.gitbook.com/book/teiid/embedded-guide/details] |
|Security Guide |Pending |[https://www.gitbook.com/book/teiid/security-guide/details] |
|Caching Guide |Pending |- |
|Administrator's Guide |Pending |- |
|Client Developer's Guide |Scheduled |- |
|Developer's Guide |Scheduled |- |
|Reference Guide |Scheduled |- |
{color:#d04437}Note that{color}: Once a doc in '*Done*' status, please update doc via submit to Github, rather than edit Conference pages.
> moving documentation from confluence to gitbook
> -------------------------------------------------
>
> Key: TEIID-3871
> URL: https://issues.jboss.org/browse/TEIID-3871
> Project: Teiid
> Issue Type: Task
> Components: Documentation
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.x
>
>
> From Teiid DV 7 F2F Notes,
> " In the Teiid 9.x timeframe we should look toward moving everything to gitbook / markdown. We should start by migrating the documentation and solicit help with the website if possible."
> This issue will address this.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months