Known Limitations

Migration limitations of the esp_aml2ccl utility.

AleriML with module and cluster elements – AleriML with module and cluster elements is not migrated to CCL because it is represented by infrastructure elements instead.
```
<Cluster id="name of cluster">(Node)*</Cluster>
   	<Module id="name of module" >{Module | DataLocation | Store | Stream}*</Module>
```
Restrict access elements – The AleriML restrictAccess attribute and Stream element are not migrated to CCL because they are represented by infrastructure elements instead.
JoinStream migration – The Event Stream Processor compiler is more strict with joins than the Aleri compiler. Some cases may migrate but may not get compiled on the ESP Server. To successfully compile in such cases, manually configure the CCL for:
- JoinStream with FullOuter join.
  1. Ensure One-One mapping between participating streams and windows.
  2. Add firstnonnull() for primary keys.
- JoinStream with LeftOuter join with Many-Many cardinality.
  - Ensure One-One or Many-One mapping between participating streams and windows.
- JoinStream with InnerJoin with no One-One cardinality.
  - Ensure One-One mapping between participating streams and windows.
Note: Data models containing joins should be recompiled when migrating from ESP 5.0 to any subequent version of the product. Failure to do so may prevent the compiled data model from being loaded by the server. In the case that the model does load, the results produced will be incorrect.
Aleri element attributes that do not migrate to CCL –
- Stream – type, oldid, convdst, ofile, expiryTimeField
- Store – oldid
- SourceStream – convsrc
- Union stream – mergeKeys
Duplicate columns – AleriML allowed SPLASH code duplicate columns records with duplicate columns are not allowed in CCL. The esp_aml2ccl migration tool migrates SPLASH code to CCL SPLASH code as is. You may need to update the CCL manually if duplicate columns are present in the SPLASH record.