[ https://issues.jboss.org/browse/TEIIDDES-1618?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-1618: --------------------------------------- I think the implementation to this could require a lot of work. Example, for each data source that is partitioned, the following information would possibly need to be tracked: - for each partition, what is the algorithm - depending on the algorithm, what columns and what criteria used - in designer, at import time, would need ask user if its partitioned and would need to know how to issue database specific commands to get stats per partition, and then store in the model. - server stat refresh would need to be able to refresh based on partition And the logic changes (I'm assuming here) related to cardinality optimization depending upon the criteria on the incoming query and using the corresponding cardinality according to how its partitioned. I think this request is doable, but will take some time to work out all the details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira