DRAFT IN PROGRESS
The following are the NoSQL DB providers supported by the Aspire 3.3 release:
The supported version of Elasticsearch is 6.3.0
The supported version of StageR is 1.2
Below you can find a list of the updates for this version.
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.
Entitlements checking now longer checks missing components at every restart.
Time zones have been normalized for Aspire, including logs and statistics.
The ability to show Provider Information has been added.
Sharepoint 2010
On the Multiple Urls drop-down, when the 'Site Discovery' option is set, the 'Set List View' option is removed.
Scan recursively is working as expected.
When not in file configuration mode, the publisher can now be used without security.
Field level help has been added for the special scope $record.
The AspireObject isEmpty method returned true even if the object had children.
The Mongo Provider generated an invalid JSON object during document conversion.
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.
The "Loading Application" message could display whether a connector was loading or not.
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.
Confluence
ACLs info appeared inside the hierarchy section.
IBM Connections
A "NO-NAME" field could occur.
Sharepoint 2010
Sharepoint 2013
Sharepoint 2016
Sharepoint Online
Standalone Mode
A global variable was not working when configuring the server in the Staging Repository connector.
When crawling over multiple documents and publishing at two different scopes, the items published could be duplicated.
The Stager connection could be broken when running a full crawl.
DBC Plugin
GCS Publisher
An error could be masked when running a non-batched job.
Validation needed to be added to the Time Rollover Threshold field.
Sharepoint Security Pre Trimmer
Group Expansion failed if user data exceeded the Mongo Max Document Limit (16MB).
Services that were set up in an Aspire cluster were not synced up correctly.
Users were not being removed.
LDAP Cache Service
The controls did not display and the Schedule was set to Advanced even if Minutes or Hourly were set.
The "Send delete by query first" option could throw an exception.
Deleting files inside of an archive file was not handled properly for incremental crawls.
AVRO Extractor
During an incremental crawl, a "duplicate key error" message could display.
FTP