The following are the NoSQL DB providers supported by the Aspire 3.3 release:

• MongoDB version 3.4.10
• HBase version 1.2.4

Below you can find the list of the updates for this version.

Bug Fixes

Aspire Core and Framework Components

• The Aspire Archetype had repository and entitlement urls as "http" rather than "https".
• For components that were deploying twice to the Artifactory, the Maven Bundle Plugin has been updated to version 3.5.0 in the POM files. 
• For Aspire Distributed mode, Services in the master node were not starting automatically after saving changes.
• Errors to reflect failed Services were not being generated.

• AspireObject was casting an incorrect numeric type when created from JSON.

• The processDeletes (String) was missing a Status page.
• The Aspire Connector Framework was not using shouldScan during incremental crawls.

Aspire UI

• A Connector component might not show the actual state of a crawl.
• The link that points to the Confluence wiki has been updated.

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".

  • 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.

• Documentum
  
  • The SNAPSHOT could fail during Group Expansion.
• File System
  • Starting Directories in the File option was not working as expected.
• FTP
  
  • The connector was not always crawling the content.
• Jive

  • During an incremental crawl, a "No start token exception" could occur. 

• Kafka

  • A "NO-NAME" field could occur.

• ServiceNow

  • The sourceType field was missing from AspireObject.

• SharePoint 2016

  • Starting a full crawl, stopping, aborting and starting again could result in the connector neither crawling nor stopping.

• SMB2
  • An error could occur when loading the connector for the first time.

  • The placeholder for the Path to URLs file was not displaying.

Publishers

• Elasticsearch
  • DeleteByQuery was not working with Elasticsearch 6.1.1.
• Kafka

  • An error could be masked when running a non-batched job.

• Publish to Avro

  • Validation needed to be added to the Time Rollover Threshold field.

• Solr Cloud
  • A  component could not be added.
• Solr
  • An error could occur while installing or deploying the publisher.

Applications

• Archive Extractor

  • The 'Send delete by query first' option was throwing an exception.

  • Deleting files inside of an archive file were not handled properly for incremental crawls.

• AVRO Extractor

  • During an incremental crawl, a 'duplicate key error' message could display.

Enhancements

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.

Aspire UI

• To re-fetch entitled components (after deleting the Resources folder), an "Allow Refresh" button has been added.

Connectors

• Aspider

  • 
    

Publishers

Applications