Converting the Extraction Plan after migrating to InfoSphere BigInsights Version 2 (all releases) Eclipse development environment

When a Version 2 (all releases) InfoSphere® BigInsights™ Text Analytics project is imported to the InfoSphere BigInsights Version 2 (all releases) Eclipse development environment, and the Extraction Plan is opened in the BigInsights Text Analytics Workflow Perspective, the Extraction Plan is automatically converted to the new design. However, the AQL source code of the project is still in Version 1 (all releases) and must be manually migrated to Version 2 (all releases). For more information about the migration process, see Migrating Text Analytics extractors from AQL 1.x to modular AQL.

There are three types of objects in an extraction plan:
Label
When a root label is created, four modules are created automatically:
  • <LabelName>_BasicFeatures
  • <LabelName>_CandidateGeneration
  • <LabelName>_FilterConsolidate
  • <LabelName>_Finals
When migrating AQL code from Version 1 (all releases) to Version 2 (all releases), it is recommended to organize AQL code by following this concept. Create the modules with those names and move the AQL scripts to the appropriate module. In v2.x, labels can be inside the groups BasicFeatures, CandidateGeneration, FilterConsolidate, and Finals. To take advantage of this feature, group the sublabels and their related AQL views together.
Example
For this type of object, if the referenced document is also imported into the InfoSphere BigInsights Eclipse workspace at the same location, the examples are still valid and no further action is necessary. You can check if the examples are still valid by double-clicking the examples to see if the right documents are loaded and the examples are highlighted correctly. If the examples are not correctly linked to the documents, move the referenced document to the same location as before or re-create the examples.
AQL element
After migrating projects to InfoSphere BigInsights Version 2 (all releases), the AQL files might no longer be in the same location. As a result, the AQL views in the Extraction Plan are not linked with their definition in the AQL files. You must manually fix each of the AQL views in the extraction plan. There are two ways to fix the linkage.
Double-click
InfoSphere BigInsights Tools for Eclipse report that the view cannot be found and ask you to manually set its new location. Enter the information about its module and AQL file. The new location information is preserved even when the AQL view object is moved to a different place in the extraction plan.
Drag-and-drop
After you locate the definition in the AQL editor of an existing AQL view in the extraction plan, delete it and then highlight its name in the definition. Drag it into the extraction plan to create an AQL view object.