Version 0.13.0 Release

JavaScript Libraries (beta)

• Support keep-alive function to re-connect with a Fluree server after a socket error.  This feature reduces user headaches due to network glitches.  Of course, the connection will eventually timeout if a Fluree server cannot be accessed.

• Support client-override of default logging level.  The default logging level is :warning.  The supported levels are :severe, :warning, :info, :config, :fine, :finer and :finest.  Examples coming soon!

• Support ability to create password-authenticated account. Examples coming soon!

Bug fixes

• When selecting from a subject, results should include flakes even where an object is false.  Previously, only objects with a value of true were included in the results. 

• Previously, a SPARQL union returned different results when variable names were on left versus right.

SELECT ?x ?y
WHERE  { { ?na fdb:_collection/name ?x } 
UNION { ?na fdb:_predicate/name  ?y } }

• Analytical queries now applies a case insensitive sort. 

Given the following strings:   “abc”, “def”, “ABC”, “DEF”
The sorted results will be:   “abc”, “ABC”, “def”, “DEF”

• Previously, an error was thrown when a predicate was first created as non-unique and then, without adding any data, you attempted to designate the predicate as unique.  This scenario is now fixed.

• Fixed issue where executing a selectOne query against a large record set (e.g., > 1 million records) doesn’t trigger fuel error or time out, instead the request hung indefinitely.

• Previously, when working with large record sets (e.g. > 1 million records), queries without any “limit” would apply the default 100-limit AFTER resolving the query. Whereas, if you specify “limit”: 100, the query engine would only traverse the first 100 records that satisfy the query. Now, there is no longer a default limit of 100 records.

• Previously, when working with large record sets, queries would fail when a max-fuel limit was hit.  Now, the query process just stops when the max-fuel is hit and returns the available results.

• Previously, a ‘unique predicate already exists’ error referenced the tempid instead of the original value.

• If a port conflict exists when Fluree transactor starts, a user-friendly error message is logged instead of the machine-generated message.

• When Fluree transactor starts, the Admin UI URL is logged for easy reference.

• Fluree now includes a logback file for ease of setup.

• Recursion support for Analytical Queries
• Full-text search in 10 languages enabled in analytical queries
• Support for cross-database, cross-time, cross-network analytical queries
• Unions, strStarts, strEnds, (SPARQL and property paths)

Support for commands with dependencies and unsigned commands when using an open API:

You can designate one or more transactions that must execute successfully before a transaction executes. If any of the dependent transactions fail or hasn’t been submitted, the current transaction fails.

We’ve provided APIs (cljs/clj) to retrieve ledger-info and ledger-stats.

• endpoint block-range-with-txn-async returns block stats as well as flakes and transactions for the specified block(s)
• endpoint ledger-stats provides ledger stats such as status, # of flakes, current block and ledger size (in kbytes)

/add-server and /remove-server BETA features to allow dynamic configuration changes to a network.

This endpoint exports an existing ledger into either xml or ttl.

You can optionally specify a block (as an integer). If none provided, defaults to the most recent block. You can optionally specify a format (xml or ttl). If none provided, defaults to ttl.

Action: POST
Endpoint: http://localhost:8080/fdb/dev/main/export
Headers: None
Body: {"format": "ttl"}
Action: POST
Endpoint: http://localhost:8080/fdb/dev/main/export
Headers: None
Body: { "format": "xml" , "block": 10 }

When viewing the history of a set of flakes, you can now view the auth records that issued each of those flakes. You can also search for a particular auth record’s updates.

Using the Fluree Node.js library, a node service can be configured as a fully-functioning query peer.   

• Documentation for v0.13 available @https://docs.flur.ee/library/nodejs/overview
• Install the latest from npm: npm install @fluree/flureenjs

Download example from https://github.com/fluree/fluree-nodejs-server

Running Fluree JavaScript library, as an extension of our linear-scaling query peer service, makes trusted data readily accessible in the browser. 

• Documentation for v0.13 available @https://docs.flur.ee/library/javascript-library/overview
• Install the latest from npm: npm install @fluree/flureedb

The Fluree Worker library runs as a browser service worker, providing trusted data to your application.   

• Documentation for v0.13 available @ https://docs.flur.ee/library/serviceworker/overview
• Install the latest from npm: npm install @fluree/flureeworker

The Fluree-React Wrapper provides an example leveraging the Fluree Worker to create a local query peer in your browser.

• Download template from: https://github.com/fluree/fluree-react
• Example leveraging Fluree Worker and Fluree-React coming soon!

Account Info includes the current block, size (kb) & number of flakes for each ledger.  

Explorer Ledger, our newest addition, provides insight into a ledger.  You can scroll through blocks, collections and predicates. 

Explore Flakes in a block

Explore transactions in a block

No UI Support yet for

• Support for commands with dependencies and unsigned commands when using an open API.
• /add-server and /remove-server endpoints
• Export