The following are the NoSQL DB providers supported by Aspire 3.2 release:
- MongoDB version 3.4.10
- HBase version 1.2.4
Below you can find the list
This page maintains a list of all version 3.2 of Aspire.New Features
Brand new Connector Framework (for more information check here)
Several connectors refactored and migrated to the new framework.
Refactored Group Expansion to use MongoDB.
Improved and redesigned User Interface.
- Added the creationDate filter option and Progressive Retries for Jive Source Connector.
New applications: Archive and PST Extractor.
- New Connector: Documentum DQL
Bug Fixes
Aspire Core
Fixed issue on DXF with the escapeValue flag.
Workflow - Validation allows to re-save a workflow rule.
Workflow - Component with a DXF text field is now saved.
Workflow - Deleting Components now works properly.
Scheduler General Tab - Content Source configuration saved is now being displayed in the UI.
UI - Deleting references do not delete application if shared.
Failover - After a single instance full crawl it's possible to run another one.
Aspire Framework crashing when include/exclude pattern is left empty.
Hierarchy Extractor - Fixed NPE.
Workflow - Rules are editable even if disabled.
General Auditing fixes.
Applications
Multiple Source Mappings not updating correctly.
Connectors
Extension List option and Open Data Stream not working with the Groovy script.
JiveACLs not fetching when the option is checked.Fixed Non-text Document Filtering issues.Include/exclude patterns not working at all.Hierarchy is not being updated after moving document to a different place.Adds/Deletes reported for the same Places.Group Expansion not retrieving all users.Security plugin being used even when selecting Entitlements API option.Some unused metadata info being retrieved.Multiple Public groups in Jive ACLs.Some minor UI issues.this version.
New Features
- NoSQL DB Provider
- AIP Integration related features (Aspire Cloudera Parcel mode)
- Audit Logs
- Log Aspire actions via Jetty.
- Cloudera Parcel updated.
- Licensing
- Licensing to build entitlements for AIP
- Licensing to Access Aspire Application: Annual, Perpetual and Trial.
- Log Tika errors as warnings.
- Logging improvements .
- Added processes and scripts to delete old logs.
- Security Access Control Configuration.
- User Role Authentication with LDAP.
- Security
- Access to file system/APIs via groovy.
To Be Released
- Connectors
- Publishers
- CDH Hadoop
- Elasticsearch in Azure
- Web HDFS
- Services
- Azure Group Expansion
- HTTP Listener
- HTTP Service
External Technical Limitations
- HBase: When running Aspire with long-term, large ingestion (with HBASE as the underlying HBase libraries may eventually stop returning results without throwing any error back, degrading the crawl performance down until it stalls completely. When this happens the only solution is to restart the affected aspire servers so the underlying HBase library threads get to connect from scratch.
- SalesForce connector: Due to SalesForce API limitations, the connector has the following limitations:
- For incremental crawls, the getUpdated and getDeleted methods are used, but when an attachment is updated from any item, that action will not be processed by the methods mentioned.
- Security and incremental related limitations:
- In security, we are only supporting 'Supported elements'.
- For sharing related incremental crawling, unsharing of Salesforce item is not working.
- For incremental crawling of Salesforce task items, we are only supporting tasks based on accounts.
- If removal of sharing occurs for a item (e.g., removing sharing of an account), it is not reflect in the incremental crawl.
- Pricebook sharing ACLs are not supported.
- We are only supporting Tasks that are based on accounts for incremental crawling.
- Chatter security
- Chatter ACLs only will be retrieved if the “Filter TrackedChange feeds” option is checked.
- Chatter ACLs are only supported for items that were created by a User or a Group, otherwise no ACL will be generated for the item.
- The public chatter groups will have two ACLs, one for the public group and a PUBLIC:ALL ACL.
- Private and Unlisted chatter groups will have one ACL for the group.
- The followers of a chatter user will be treated as a private group called “<username>’s followers”, all the feed items created by a user to their followers will have this ACL.
- The chatter item attachments will inherit the parent item ACLs.
- Reducing the users retrieval scope might lead to a loss of ACLs, since no ACLs won’t be generated for followers of users outside the scope of the user retrieval.
- Salesforce Compatibility limitation
- Every 3 months Salesforce releases a new version of their API and, sometimes makes changes to the data structures, after each update there is a possibility that the compatibility between the connector and Salesforce will break.
Anchor |
---|
| ItemDeprecate |
---|
| ItemDeprecate |
---|
|
Items Deprecated on Aspire 3.2
Applications
- Archive Extractor
- Deletes are not handled properly for incremental crawls.
- Delete by query option is not working for ElasticSearch versions greater than 5.0. Ask to the Core Engineering team for a workaround if you need it.
Aspire Core
- Loading Application message trying to add connector but it does not load.
- Intermittent black screen showing in the UI for less than a second (flickering screen).
- Failover:
- Triple instance full crawl (double-interrupted): Having missing jobs.
- Dual Test Full Crawl interrupted: after aspire shutdown in one instance the other instance continue the crawl but never ends, Not all Docs are published on Solr.
- Full test interrupted: after aspire shutdown and restarted docs are not published on Solr.
- NoSQL provider:
- Configurations - Encrypted fields is not working.
- Missing 'NoSQL provider unavailable' message when provider is down.
Connectors
The following items are deprecated on this Aspire version:
- Elasticsearch bootloader
- aspire-elastic-bootloader
- DCM
- aspire-amazonec2-dm
- aspire-zk-dm
- Big Data
- app-semantic-co-occurrence-hadoop
- app-semantic-co-occurrence-hadoop-soln
- aspire-hadoop-job-launcher
- aspire-hadoop-hdfs
- aspire-hadoop-wiki-dict-generator
- aspire-load-hdfs
- Connectors
- Staging Repo Connector (File System)
- SVN
- Services:
- Fast Components
- Fast Content API
- Fast Query Completion Listener
- Fast Query Listener
- Solutions
- Publishers
- Cloudsearch
- SharePoint 2013
- Staging Repo Publisher (File System)
IBM ConnectionsACLs not being extracted.
Exclude pattern works as expected.
Publishers
WebHDFS exception.
Services
Now loading correctly.
Known Issues
Aspire Core
- Aspire does not detect changes in the connector settings and is not asking to save them.
- New NoSQLSet utility class is not working as expected.
- Source Connector disabled in distributed scenario crawls items and counts them in the statistics.
- Auditing Tool - filtering by "Batch" and "All" & "Job and All" is not working.
- Debug console broken in Firefox.
- Aspire does not load even after the console says is loaded.
- Add option does not show results when filtering from the last page.
Applications
Deletion is not working with file names with special characters.
"Index Archive file job" is throwing exceptions or is not adding the job requested.
Connector indexes containers.
Connectors
- Aspire Connector Archetype
Aspire connector archetype not compiling because of a wrong dependency. In order to make it work, change the "aspire-connector-framework" dependency version from 3.0 to 3.1
Adds are reported as Updates.
Need to flush jobs on RDB Source Connector.
Source - Full crawl not working. Console and UI got stuck.
NPE when Domain is empty.
Items crawled and Items with error are the same if domain is empty.
"Cannot get content source from job" error when Content Source field is not specified.
Solutions
Publish to staging is not being added to the Workflow section when connector is added.
To Be Released
External Technical Limitations
- Changes in Box notes content are not considered for incremental crawls.
- Changes made to the attachments of the item type Opportunity in Salesforce are not considered for incremental crawls.
Important Note
- MapDB is not used in the new connector framework.