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 "http" rather than "https" repository and entitlement urls.
• 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. 

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

• The "Loading Application" message could display whether a connector was loading or not.

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

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

• Box

  • Extract text problems occurred when impersonate user functionality was used.  

• Confluence
  • Page parent ACLs needed an update.

  • Fetcher authenticated continuously.

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

  • Validation was not occurring for the "Sub job timeout" field when a value was not entered.
• Kafka

  • A "NO-NAME" field could occur.

• Parquet Extractor
  • Validation was not occurring for the "Sub job timeout" field when a value was not entered.
• RDB via Snapshots

  • A string ID that starts with a space could not be processed.

• 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 "Path to URLs file" placeholder was not being displayed.

• Standalone Mode
  • When a user added a custom connector, feedback needed to be provided by the Aspire UI. 

Publishers

• Elasticsearch
  • DeleteByQuery was not being used 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.

• Sharepoint 2013

  • Simultaneous crawls overlapped when used as a shared component.

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

  • It was not possible to publish to the staging repository using :app-publish-to-staging.

Services

• Group Expansion failed if user data exceeded the Mongo Max Document Limit (16MB).

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

• Services that were set up in an Aspire cluster were not synced up correctly.

• Azure Active Directory Group Expander

  • Users were not being removed.

• Group Expansion Service
  • The userGroupCache map was accessed when the Group Expansion Service was running.

Applications

• Archive Extractor

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

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.

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

Aspire UI

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

• The ability to show Provider Information has been added.

Connectors

• Sharepoint

  • URLs and site collections can now be specified with 'Add New' functionality.

• Publish to StageR

  • Field level help has been added for the special scope $record.

Publishers

• Elasticsearch
  • Case sensitive index names can be handled properly now.
    
• HBase
  • Content can now be deleted.
  • During a full crawl, the publisher now default to clean.
    

  • When not in file configuration mode, the publisher can now be used without security. 

Applications

• The Entitlements Admin application has been updated.

Framework Components

• Improvements have been added to Job usage.
• Extract Text
  • Updates have been made to the ExtractText default configuration limit for text extracted from a stream.