• Created by Unknown User (nnavarro), last modified by user-1b188 on Apr 15, 2019

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 164 Next »

DRAFT

For version 4.0, Aspire requires a license file to run.

See Aspire Licensing for information on obtaining a license.


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

  • MongoDB version 3.6
  • HBase version 1.2.4

The supported version of Elasticsearch is 6.3.0

The supported version of StageR is 1.2  Note:  The latest version of Stager is v. 1.2 and it supports MongoDB v. 3.4.10 


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

On this page

Known Issues

Enhancements

Bug Fixes


Known Issues

Connectors 

  • Connectorname


Services

  • Servicename



New and Enhancements Features

Aspire Core and Framework Components

  • The Request log now contains the remote IP addresses for successful and failed logins
  • The following fields have been added for every record: 
    • “ingestionStart” (date time when a record was first created by the connector)
    • “ingestionEnd” (date time when a record was ingested into the search engine) 
    • “crawlStart” (date time when the crawl responsible for a record was started)

   For debugging, we can now identify which records were ingested when and what batches of records exist.  We can also more easily identify and remove orphans

  • An option has been added to the Aspire Parcel and Service to configure the Aspire log directory.
  • Connectors now have a concept of a “domain”
    • When creating or indexing ACLs, the search engine will include the domain, which defaults to the connector name (or ID)
    • The domain can be overridden
  • Improvements have been made to failed document handling
  • Aspire now works with Java 11
  • A message appears when adding a custom connector with ‘com.searchtechnologies.aspire’ Group ID
  • Aspire Parcel and Service – An option has been added to configure the Aspire log directory
  • The Aspire wiki has been updated to indicate that system properties can be configured in the settings.xml file for use in the Aspire UI.
    This is useful for connectors, services, workflow and can be applied to content sources and services to configure from the UI

Connectors

  • Connectorname


Publishers

  • Elasticsearch
  • HBase
    •  

Applications



Bug Fixes

Aspire Core and Framework Components

Aspire UI

Connectors

  • Aspider


  • Documentum
  • File System
  • Kafka


  • Standalone Mode

Publishers

  • Elasticsearch

  • Kafka


  • Publish to Avro


  • SharePoint 2013


  • SolrCloud
  • Solr
  • Publish to StageR


Services


Applications

  • Archive Extractor


  • AVRO Extractor




  • No labels