There are several modes in which Teiid Spring Boot is utilized:

• To create virtualizations via syndesis
• With a general DDL DB
• Operator based deployments (may support the first two, but is likely to focus on only the syndesis needs initially)
• Via annotations, with no VDB, in any spring boot application

The general vdb and annotation cases open things up to additional considerations that are not being handled given our primary focus on syndesis. This includes things like:

• https://developer.jboss.org/message/989586
• TEIIDSB-101
• The notion of a default schema for OData is ill-defined for the general VDB case.

One of the reasons to support general vdbs outside of what can be created with syndesis is the notion that they will be a better target for migration of existing customers. However there are quite a few mismatches to that approach - the primary being that all of the configuration information captured by the AS/WildFly runtime has no simple migration (especially customization, such as loginmodules, logging, etc.). The lack of support for VDB resources and a unified classpath make migration difficult for existing VDBs as you may end up with DDL that is quite large or classpath issues. Also the nature of VDB import support has changed.

In the interest of remaining focused on what is in product docs / tested, I'd propose at least tempering expectations around the possibility of automatic migration, and to not initially productize the annotation driven approach.