Import the connector and run a full crawl. Content in the FTP server should be crawled using the default settings. Instead, nothing is being crawled except that the "Index containers" option is getting the root item.
Configure the service using the Advance option (Weekly), save and close. Re-open the configuration. The controls do not display and the Schedule is set to Advance even if Minutes or Hourly were set.
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 no 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.
Field level help has been added for the special scope $record.
SharePoint 2010
On the Multiple URls drop-down, when the 'Site Discovery' option is set, the 'Set List View' option is removed.
Scan recursively was not working as expected.
SMB
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.
ConfigManager could log a debug message into {aspire.home}/logs/configmanager.log
A problem could occur when editing a custom application in the Admin UI
When stopping and restarting Aspire while the GroupDownload process was running, the group download did not start again
The LDAP Cache could report a MongoDB Duplicate key error
Aspider could stop with a MongoDB Duplicate key error
SharePoint Commons
An out of memory (OOM) exception could occur during large crawls
The AspireObject isEmpty method returned true even if the object had children
.The Mongo
Providerprovider 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 a 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.updating
Confluence
ACLs info appeared inside the hierarchy section
IBM Connections
A "NO-NAME" field could occur
SharePoint 2010
SharePoint 2013
KeyNotFoundException while trying to check attachments for list with lookup references deleted
The placeholder needed to be changed for the 'Seeds file' field
The connector was unable to crawl large lists
SharePoint 2016
An error could occur while crawling site
SharePoint Online
NPE crawling on distributed mode. Random NPE in the item complete callback
String index out of range while getting a List display url
Error while crawling after a crawl was stopped: Item parent wasn't assigned during crawl
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
Stager BDC Plugin could randomly fail during the crawls after setup
GCS Publisher
A resource config/application.xml was missing on the jar file
An error could occur when crawling and publishing to GCS
An error could be masked when running a non-batched job.
Validation needed to be added to the Time Rollover Threshold field.
Simultaneous crawls overlapped when used as a shared component.
It was not possible to publish to the staging repository using :app-publish-to-staging
.
TLS 1.2 support was needed for the SharePoint Security Pre Trimmer
Azure Group Expander could refuse to start.
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
Problems with LDAP-Cache component could include: reporting a duplicate key error twice, stopping with a duplicate error, taking too long, and refresh refusing to start. The connector could not look up ACL information in the LDAP-Cache component
You are now able to check the user’s cache for the Azure Group Expander via the Debug console
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
Pending required field validation for the 'Indexer Type' field