NoSQL for Java - 1.8

Extension ID

com.castsoftware.nosqljava

What’s new?

See NoSQL for Java - 1.8 - Release Notes .

Supported NoSQL databases

The NoSQL for Java extension provides support for the following NoSQL databases:

Database Details about how the support is provided
Amazon DocumentDB Amazon DocumentDB support for Java source code
Apache Lucene Apache Lucene support for Java source code
Apache Solr Apache Solr support for Java source code
Azure Cosmos DB Azure Cosmos DB support for Java source code

Azure Cosmos DB support for Spring Data source code
Couchbase Couchbase support for Java source code

Couchbase support for Spring Data source code
CouchDB CouchDB support for Java source code
DynamoDB DynamoDB support for Java source code

DynamoDB support for Spring Data source code
Elasticsearch Elasticsearch support for Java source code

Elasticsearch support for Spring Data source code
MarkLogic MarkLogic support for Java source code
Memcached Memcached support for Java source code
MongoDB MongoDB support for Java source code

MongoDB support for Spring Data source code
Redis Redis support for Java source code

Redis support for Spring Data source code

Function Point, Quality and Sizing support

Function Points
(transactions)
(tick) A green tick indicates that OMG Function Point counting and Transaction Risk Index are supported.
Quality and Sizing (tick) A green tick indicates that CAST can measure size and that a minimum set of Quality Rules exist.

CAST Imaging Core compatibility

Release Operating System Supported
8.3.x Microsoft Windows (tick)

Prerequisites

Required? Extensions
(tick) com.castsoftware.jee ≥ 1.3.5-funcrel
(tick) com.castsoftware.internal.platform ≥ 0.9.11
(tick) com.castsoftware.wbslinker ≥ 1.7.19-funcrel

Download and installation instructions

The extension will not be automatically downloaded and installed in CAST Imaging Console. If you need to use it, should manually install the extension.

Handling of NoSQL Java Collection objects for transaction purposes

All NoSQL “Collection” type objects are not classed as having code - i.e. they are codeless and are created via “getcollection” statements. As such, these objects either exist or do not and therefore NoSQL for Java extension does not compute a checksum on them. See https://mongodb.github.io/mongo-java-driver/3.4/driver/tutorials/databases-collections/  for more information. This means that in reality, if a transaction is really changed to add or remove a collection, then the java code itself is changed and so the transaction will be  marked as modified. This in turn means that in an environment where the same release of a the NoSQL for Java extension is used for successive analyses, changes in java objects are enough to change the transaction values.

Data sensitivity

The NoSQL for Java extension is capable of setting a property on specific objects for the following:

  • custom sensitivity
  • GDPR
  • PCI-DSS

See Data Sensitivity  for more information. For example:

Structural rules

Release Link
1.8.3-funcrel https://technologies.castsoftware.com/rules?sec=srs_nosqljava&ref=||1.8.3-funcrel
1.8.2-funcrel https://technologies.castsoftware.com/rules?sec=srs_nosqljava&ref=||1.8.2-funcrel
1.8.1-funcrel https://technologies.castsoftware.com/rules?sec=srs_nosqljava&ref=||1.8.1-funcrel
1.8.0-funcrel https://technologies.castsoftware.com/rules?sec=srs_nosqljava&ref=||1.8.0-funcrel
1.8.0-beta2 https://technologies.castsoftware.com/rules?sec=srs_nosqljava&ref=||1.8.0-beta2
1.8.0-beta1 https://technologies.castsoftware.com/rules?sec=srs_nosqljava&ref=||1.8.0-beta1
1.8.0-alpha1 https://technologies.castsoftware.com/rules?sec=srs_nosqljava&ref=||1.8.0-alpha1