[ https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-3462 at 4/19/16 11:39 AM: ----------------------------------------------------------------- After looking at the changes for rest, I'm uneasy with the current state of things. It does seem to be a better option to just go ahead and introduce a breaking change so that the version field can be a string rather than an int. This would introduce a minor breaking change into: CommandLogMessage VDB Session EventListener VDBImport ExecutionContext MetadataRepository Duplicate methods on: EventDistributor Admin AdminShell could just accept Object for the version, rather than adding methods. Additionally materialization status tables would need the vdbversion column changed to string. This is much more logically consistent with the original intent of having the version field. was (Author: shawkins): After looking at the changes for rest, I'm uneasy with the current state of things. It does seem to be a better option to just go ahead and introduce a breaking change so that the version field can be a string rather than an int. This would introduce a minor breaking change into: CommandLogMessage VDB Session EventListener VDBImport ExecutionContext Duplicate methods on: EventDistributor MetadataRepository Admin AdminShell could just accept Object for the version, rather than adding methods. Additionally materialization status tables would need the vdbversion column changed to string. This is much more logically consistent with the original intent of having the version field. -- This message was sent by Atlassian JIRA (v6.4.11#64026)