Versions Compared

Old Version 162

changes.mady.by.user user-1b188

Saved on

compared with

New Version 163

changes.mady.by.user user-1b188

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status
colourYellow
titleDRAFT

Info

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.4.10
  • HBase version 1.2.4


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

On this page

Known Issues

Enhancements

Bug Fixes


Anchor
knownissues
knownissues
Known Issues

Anchor
connectorknown
connectorknown
Connectors 

  • FTP 

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

  • Connectorname


Anchor
servicesknown
servicesknown
Services

  • ServicenameLDAP Cache Service
    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.



Anchor
enhancements
enhancements
Enhancements

Anchor
AspireCoreEnhance
AspireCoreEnhance
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.
  • Improvements have been added to Job usage.
  • Updates have been made to the ExtractText default configuration limit for text extracted from a stream.

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

    Anchor
    connectorEnhance
    connectorEnhance
    Connectors

    • Aspider
      • Added a Headless browser for rendering dynamically generated pages (client side JavaScript pages).
    • Publish to StageR

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

    • Connectorname


    Anchor
    publisherEnhance
    publisherEnhance
    Publishers

    • Elasticsearch
      • Case sensitive index names can be handled properly now.
      Google Cloud SearchA new Google Cloud Search publisher receives content from Aspire connectors and uses the Java Client library to index the content into Cloud Search.
    • HBase
      • Content can now be deleted.
      • During a full crawl, the publisher now defaults to clean.
      • When not in file configuration mode, the publisher can now be used without security. 

    Anchor
    AppEnhance
    AppEnhance
    Applications

    The Entitlements Admin application has been updated.



    Anchor
    bugfixes
    bugfixes
    Bug Fixes

    Anchor
    AspireCorebugs
    AspireCorebugs
    Aspire Core and Framework Components

  • The Aspire Archetype had "http" rather than "https" repository and entitlement URLs.

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

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

  • Extract Text
    • Use the Apache Tika SAX Parser for Microsoft documents.
  • Scheduler
    • The option to create a Cache Groups scheduler was not being displayed.

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

    Anchor
    connectorsbugs
    connectorsbugs
    Connectors

    • Aspider

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


    • Documentum
      Exception was being thrown during Group Expansion.
    • File SystemStarting Directories in the File option was not working as expected.
    • Kafka

      • A "NO-NAME" field could occur.


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

    Anchor
    publishersbugs
    publishersbugs
    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.


    • SolrCloud
      A component could not be added.
    • SolrAn 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.


    Anchor
    servicesbugs
    servicesbugs
    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.


    Anchor
    appbugs
    appbugs
    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.