...
Database | Details about how the support is provided |
---|---|
Amazon DocumentDB | Amazon DocumentDB support for Java source code |
Azure Cosmos DB | |
Azure Cosmos DB support for Spring Data source data | |
Couchbase | Couchbase support for Spring Data source code |
Couchbase support for Java source code | |
CouchDB | CouchDB support for Java source code |
DynamoDB | |
DynamoDB support for Spring Data source code | |
Elasticsearch | Elasticsearch support for Java source code |
Elasticsearch support for Spring Data source code | |
MarkLogic | |
Memcached | Memcached support for Java source code |
MongoDB | |
MongoDB support for Spring Data source code | |
Redis | |
Redis support for Spring Data source code |
...
Download and installation instructions
You will need to The extension will not be automatically downloaded and installed in CAST Console. If you need to use it, should manually install the extension using the Application - Extensions interface. When installed, follow the instructions below to run a new analysis/snapshot to generate new results:
- Advanced onboarding - run and validate the initial analysis
- Advanced onboarding - snapshot generation and validation
...
:
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.
Structural rules
...