[
https://issues.jboss.org/browse/TEIIDDES-1244?page=com.atlassian.jira.plu...
]
Michael Walker commented on TEIIDDES-1244:
------------------------------------------
Of course, the new target datasource must have identical table structure to the previous
target, in order for this to completely succeed.
The business use case here is the ability to gather statistics against a development
database, and then update those statistics against a production database that has the same
structure, but different content. E.g. an unclassified database is typically used for
development work, whereas a classified database, with identical structure but different
content, is used in production.
A similar use case is simply if database connectivity info is changed over time, but the
database remains the same. E.g. a database is migrated to a new host / IP address /
hostname / port number / etc.
Modeling -> Update Source Data Statistics doesn't honor
changes to the Data Source
----------------------------------------------------------------------------------
Key: TEIIDDES-1244
URL:
https://issues.jboss.org/browse/TEIIDDES-1244
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.4.2
Reporter: Johnathon Lee
Modeling -> Update Source Data Statistics doesn't honor changes to the Data
Source. Steps to reproduce should clarify, the basic story is that feedback is given
that indicates modified resources will be used when Update Source Data Statistics is ran.
Based upon the changes made to create an invalid URL, this is not the case.
This originates with
https://issues.jboss.org/browse/JBEDSP-388 and the intention is to
allow cost statistics to be updated based upon a data source other than what was used for
the import.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira