Info |
---|
For version 4.0, Aspire requires a license file to run. |
The following are the NoSQL DB providers supported by the Aspire 4.0 release:
- Elasticsearch version 7.1.1
- MongoDB version 3. 4.100
HBase
The supported version of StageR is 1.2 and it works with MongoDB v. 3.4.10.
Below you can find the list of the updates for included in this version.
New and Enhanced Features
Anchor |
---|
| AspireCoreEnhance |
---|
| AspireCoreEnhance |
---|
|
Aspire Core and Framework Components
- New Elasticsearch as a NoSQL provider.
- All Publishers are using the new Publisher Framework.
- Updates to the Listener service (push updates).
- Cluster Mode improvements (Zookeeper stability).
- Implemented the FIFOQueue for the MongoDB Provider.
- New options for the Extract Text configuration and new Throttling section in Advanced Configuration for connectors.
- Background processing.
- Saga natural language processing is available as an Aspire plug-in and can be used to perform NLP as part of Aspire workflow.
Aspire UI
- Import/Export System configuration.
Log Browser.
Anchor |
---|
| connectorEnhance |
---|
| connectorEnhance |
---|
|
Connectors
Anchor |
---|
| publisherEnhance |
---|
| publisherEnhance |
---|
|
Publishers
Applications- Amazon S3.
- Background Queue.
- Azure Search.
Plugins
- Stager BDC Plugin.
- Now supports Sharepoint 2019.
Services
Framework ComponentsBug Fixes
Anchor |
---|
| AspireCorebugs |
---|
| AspireCorebugs |
---|
|
Aspire Core and Framework Components
The Aspire Archetype had "http" rather than "https" repository and entitlement URLs.AspireObject was casting an incorrect numeric type when created from JSON.
The AspireObject isEmpty method returned true even if the object had children.
The processDeletes (String) was missing a Status page.The Aspire Connector Framework was not using shouldScan during incremental crawls.When running a full crawl, a "Provider 'encrypted' not installed" message could occur.The Mongo Provider generated an invalid JSON object during document conversion.
Audit logs were incomplete.For AIP integration, the logout action was not being logged.
Publisher framework retryDelay, retryDelayMultiplier and maxRetryDelay properties were not supported by Dynamic XML Forms (DFX).
The Aspire-Services jar file was missing noSQL package.
- Missing headers on OAuth classes.
- Wrong URL info for the Aspire UI Authentication documentation in settings.xml file.
- Master password ssh file not working on Centos OS.
- Errors processing failed documents with the Exception Patterns option.
- Components on Workflow not saved if the content source was not saved first.
- Invalid entitlements host caused missing workflow applications.
- Double click ignored on disabled workflow item.
- NPE after shutting down 2 Aspire instances in distributed mode.
- Java 1.8 Error when name of the Application and name of Publish was the same.
- Aspire not starting in shell mode on Centos OS.
- Publisher added to the workflow not being unpacked into cache folder so they were unavailable and not working.
- Error installing Aspire as a service in Windows.
- Status not displayed in Aspire after a crawl was aborted.
- NPE scheduling the "cacheGroups" option without the GEM configured.
- Two different entries in status collection being generated for the same crawl ID.
- NPE having Artifactory user with not entitlements assigned.
- Mongo database name limit exceeded by the Aspire Database name.
- NPE with the Non Text Document Filter and Open Data Stream options enabled.
- NPE using encrypted password at the SSL settings in settings.xml file.
- NPE pausing a crawl with MongoDB and Zookeeper in distributed mode.
- Error trying to import a Service since some services do not have a workflow associated.
- Previous crawl errors displayed when current crawl was running.
- Crawls on distributed mode not populating correctly ancestor ID and ACLs.
- Error uninstalling Aspire as a service.
- Aspire not getting alert if Elasticsearch provider is not running.
- Crawl statistics not reflecting the deletes if there were adds/updates.
- NPE after an authentication method configured in the settings.xml file.
- NPE displayed while stopping a crawl after it just started.
- Some Aspire UI settings configured in settings.xml file being ignored.
- Out of Memory error using a very big number in Hierarchy Cache Size option.
- Every time a groovy script was updated, a blank line was added at the beginning of the script.
- Invalid characters validation in the Extension List option of the Non Text Document filter.
Applications
- Archive Extractor
- Using Select/Deselect All option closed the Configuration window.
- AVRO Extractor
- ASPIRE-8112/ASPIRE-8113 Routing section options not displaying correctly.
- Hierarchy Extractor
- The User/Group field on ACLs section is now required
The "Loading Application" message could display whether a connector was loading or notA Connector component might not show the actual state of a crawl.- Typos on Accenture license information.
- UI refreshing stacks over and over while changing between the Cards View and the List View.
- Aspire DXF not accepting Windows relative paths.
- The word "content sources" displayed in the Service Group control.
- Navigation controls at the bottom overlapping the footer.
- Fixed special characters allowed in the connector's name
The link that points to the Confluence wiki has been updated Anchor |
---|
| connectorsbugs |
---|
| connectorsbugs |
---|
|
Connectors
- Aspider
Headless browser was not executing Post requests.
- An authentication form error could occur indicating "Target host is not specified while crawling".
Neither NTLM nor ADFS authentication was occurring when a host was specified in the Credentials.
On any port, the Port field was not working correctly with any value except "-1".
A crawl could cause a warning about duplicate IDs in MongoDB.
To indicate that the Gateway was not working, the exception message in ADFS needed updating.
Aspider needed to be able to crawl dynamically rendered pages.
- Documentum
- Exception was being thrown during Group Expansion.
- File System
- Starting Directories in the File option was not working as expected.
- Kafka
- Standalone Mode
- When a user added a custom connector, feedback needed to be provided by the Aspire UI.
Anchor |
---|
publishersbugs | publishersbugs | Publishers- Elasticsearch
- DeleteByQuery was not being used with Elasticsearch 6.1.1.
- Kafka
- Publish to Avro
- SharePoint 2013
- SolrCloud
- A component could not be added.
- Solr
- An error could occur while installing or deploying the publisher.
- Publish to StageR
Anchor |
---|
servicesbugs | servicesbugs | Services Anchor |
---|
appbugs | appbugs | Applications- Archive Extractor
AVRO Extractor
Anchor |
---|
componentsbugs | componentsbugs | Framework Components- Extract Text
- Use the Apache Tika SAX Parser for Microsoft documents.
- Scheduler
- The option to create a Cache Groups scheduler was not being displayed.
Known Issues
Anchor |
---|
| connectorknown |
---|
| connectorknown |
---|
|
Aspire Core and Framework Components
- Completed items not being removed from the process queue.
- Crawl time execution still running after pause it.
- Felix startup warning using Java version 11.
- Connectors/publishers saved twice when Aspire components are still downloading.
- HttpFeeder - Servlet added with the same name of another servlet is not notified in the UI.
- Error validating field Maximum size on Extract Text
Anchor |
---|
| connectorknown |
---|
| connectorknown |
---|
|
Publishers
- Elasticsearch: Error publishing hierarchy information to the index using the Lotus connector. This will be fixed for Aspire 4.0.1. Meanwhile and as workaround change the transform.groovy file in the line 225 to the following line:
- ancestors?.getChildren().each() { ancestor ->
Anchor |
---|
| techLimitations |
---|
| techLimitations |
---|
|
External Technical Limitations
- Aspire Core and Framework Components
Publisher
Anchor |
---|
enhancements | enhancements | Enhancements Anchor |
---|
AspireCoreEnhance | AspireCoreEnhance | Aspire Core and Framework Components- Salted Challenge Response Authentication Mechanism (SCRAM) support has been added to the MongoDB used with Aspire.
- The ability to dynamically load jar files has been added to Aspire with Java 9.
- When starting Aspire either normally or in debug mode, the debug line in the
settings.xml
file is handled appropriately. A section has been added to the settings.xml
file for HBase information.
Logging of remote IP addresses for successful or failed logins will now occur.
- The Mongo Provider now encrypts/hashes IDs.
- Record fields have been improved.
Entitlements checking now longer checks missing components at every restart.
Time zones have been normalized for Aspire, including logs and statistics.
- The documentation has been updated for Keytab/Kerberos.
Anchor |
---|
UIEnhance | UIEnhance | Aspire UI Anchor |
---|
connectorEnhance | connectorEnhance | Connectors Anchor |
---|
publisherEnhance | publisherEnhance | Publishers- Elasticsearch
- Case sensitive index names can be handled properly now.
- HBase
Anchor |
---|
AppEnhance | AppEnhance | Applications- The Entitlements Admin application has been updated.
Anchor |
---|
componentEnhance | componentEnhance | Framework ComponentsImprovements have been added to Job usage.Extract TextUpdates have been made to the ExtractText default configuration limit for text extracted from a stream.