The following are the NoSQL DB providers supported by the Aspire 3.3 release:
Below you can find the list of the updates for this version.
AspireObject was casting an incorrect numeric type when created from JSON.
The Mongo Provider generated an invalid JSON object during document conversion.
For AIP integration, the logout action was not being logged.
Headless browser was not executing Post requests.
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".
An Aspider 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.
During an incremental crawl, a "No start token" exception could occur.
A "NO-NAME" field could occur.
The sourceType field was missing from AspireObject.
Starting a full crawl, stopping, aborting and starting again could result in the connector neither crawling nor stopping.
The "Path to URLs file" placeholder was not being displayed.
An error could be masked when running a non-batched job.
Validation needed to be added to the Time Rollover Threshold field.
Services that were set up in an Aspire cluster were not synced up correctly.
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.
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 ability to show Provider Information has been added.
URLs and site collections can now be specified with 'Add New' functionality.
Field level help has been added for the special scope $record.