Aspire 3.2 – Big Data Release (the first Aspire release as part of Accenture
) includes the successful integration of Aspire into the Hadoop ecosystem as a Cloudera parcel with Accenture AIP. However,
you can still
use Aspire in stand-alone mode or as a parcel inside of Cloudera.
Find more information on the Cloudera parcel configuration at Aspire Parcel and Service for Cloudera.
When importing a content source from 3.1.1 x into 3.2, the following error will may occur and the . The content source will may show up in with a red "Failed" status:.
Code Block |
---|
Error message: Unable to start appBundle: com.searchtechnologies.aspire:app-rap-connector Caused by: com.searchtechnologies.aspire.services.AspireException: Failed to register components from appBundle: CONTENT_SOURCE_NAME (Parent: <null>) at com.searchtechnologies.aspire.application.AspireApplicationImpl.registerAppBundleComponents(AspireApplicationImpl.java:945) at com.searchtechnologies.aspire.application.AspireApplicationImpl.registerAppBundle(AspireApplicationImpl.java:980) at com.searchtechnologies.aspire.application.AspireApplicationComponent.loadApplication(AspireApplicationComponent.java:696) at com.searchtechnologies.aspire.application.AspireApplicationComponent.loadApplication(AspireApplicationComponent.java:692) at com.searchtechnologies.aspire.configuration.ConfigurationManager.reloadApplication(ConfigurationManager.java:697) at com.searchtechnologies.aspire.configuration.ContentSourcesModule.processSyncUnitUpdate(ContentSourcesModule.java:309) at com.searchtechnologies.aspire.configuration.SynchronizedModule.run(SynchronizedModule.java:289) at java.lang.Thread.run(Thread.java:748) Caused by: com.searchtechnologies.aspire.services.AspireException: The value ("${waitForWfApps}") of element <waitForWfApps> is improperly formatted for a boolean - must be either "true" or "false" at com.searchtechnologies.aspire.framework.ComponentImpl.getBooleanFromConfig(ComponentImpl.java:2634) at com.searchtechnologies.aspire.connector.framework.controller.CrawlControllerImpl.initialize(CrawlControllerImpl.java:260) at com.searchtechnologies.aspire.framework.ComponentFactoryImpl.registerComponent(ComponentFactoryImpl.java:446) at com.searchtechnologies.aspire.application.ComponentManagerImpl.registerComponents(ComponentManagerImpl.java:328) at com.searchtechnologies.aspire.application.ComponentManagerImpl.initialize(ComponentManagerImpl.java:93) at com.searchtechnologies.aspire.application.PipelineManagerImpl.initialize(PipelineManagerImpl.java:75) at com.searchtechnologies.aspire.framework.ComponentFactoryImpl.registerComponent(ComponentFactoryImpl.java:446) at com.searchtechnologies.aspire.application.ComponentManagerImpl.registerComponents(ComponentManagerImpl.java:328) at com.searchtechnologies.aspire.application.ComponentManagerImpl.initialize(ComponentManagerImpl.java:93) at com.searchtechnologies.aspire.framework.ComponentFactoryImpl.registerComponent(ComponentFactoryImpl.java:446) at com.searchtechnologies.aspire.application.AspireApplicationImpl.registerAppBundleComponents(AspireApplicationImpl.java:941) |
This happens could happen because the Aspire 3.2 connectors contains several new contain configuration options that the "content source to import does not have." lack. To fix this error:
By doing this Aspire will generate generates the new options and save saves them into the configuration files.
Any migration from Aspire 3.1.1 x requires a Full Crawl of all content sources since there was a major refactor on the MongoDB provider component. In specific the following tables changed:
Collection | Fields in 3.1.1x | Fields in 3.2 | Compatible |
---|---|---|---|
audit |
|
| Yes |
errors |
|
| No |
hierarchy |
|
| No |
processQueue and scanQueue |
|
| Yes |
snapshot |
|
| No |
statistics |
|
| No |
status |
|
| No |
*These fields were available in Aspire 3.1