[ https://issues.jboss.org/browse/TEIID-4321?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4321: --------------------------------------- Actually no. ERROR logging is only for unexpected errors. Expected errors from user events are logged at a WARN level (otherwise it's very easy to fill up the logs with a failing query for example). If you want to make the case that this is an administrative operation and should logged at a higher level, then that could be considered. No. However updatablity of the matview doesn't correlate to a consideration about the materialization table. Here is what I would do for a change: - only check for fewer columns in the materialization table as that is obviously an issue - and as you have done don't require columns to be positionally the same {code} List<Column> matViewColumns = view.getColumns(); List<Column> tableColumns = table.getColumns(); if(tableColumns.size() < matViewColumns.size()) { metadataValidator.log(report, model, QueryPlugin.Util.gs(QueryPlugin.Event.TEIID31193, table.getFullName(), view.getFullName())); } else { for(int i = 0 ; i < matViewColumns.size() ; i ++) { Column matViewColumn = matViewColumns.get(i); Column tableColumn = table.getColumnByName(matViewColumn.getName()); if (tableColumn == null) { metadataValidator.log(report, model, QueryPlugin.Util.gs(QueryPlugin.Event.TEIID31203, table.getFullName(), matViewColumn.getName(), view.getFullName())); } else if(!matViewColumn.getDatatypeUUID().equals(tableColumn.getDatatypeUUID())){ metadataValidator.log(report, model, QueryPlugin.Util.gs(QueryPlugin.Event.TEIID31194, tableColumn.getName(), table.getFullName(), matViewColumn.getName(), view.getFullName())); } } } {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)