[teiid-designer-issues] [JBoss JIRA] Commented: (TEIIDDES-921) Issue during importing of Oracle metadata when the schema is partitioned
[
https://issues.jboss.org/browse/TEIIDDES-921?page=com.atlassian.jira.plug...
]
Van Halbert commented on TEIIDDES-921:
--------------------------------------
When using the JDBC importer, and on the step where the Foreign keys, indexes and table
types are selected. If "indexes" are selected to be imported, the
"Approximations Allowed" option should be selected by default. This is so the
current stats on the indexes are used by default. Therefore, requiring the user to
de-select that option if they want to trigger the database to perform an ANALYSE (in
oracles case) and could be long running depending on how the schema is setup and how much
data is in the tables.
Issue during importing of Oracle metadata when the schema is
partitioned
------------------------------------------------------------------------
Key: TEIIDDES-921
URL: https://issues.jboss.org/browse/TEIIDDES-921
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.1.1
Reporter: Debbie Steigner
Assignee: Barry LaFond
Fix For: 7.4
The Table is BIG ! - The Oracle table that we're importing is partitioned by date
with 5 million rows per day and 2 years worth of data.
The problem is that it takes longer than 2 hours because it issues an ANALYSE table
command.
Would it be possible to create an option (perhaps a checkbox) that would allow the meta
data to be created quiclky and defer the ANALYSE to runtime?
create an option (perhaps a checkbox) on Import from JDBC that would allow the metadata
to be created quickly and defer the ANALYSE to runtime. Also, it was indicated that the
ANALYSE call is an old Oracle command, that there is a newer command. Also, consider
running the stats only only the requested partition.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira