Version 0.13.0

Version 0.13.0 Release

Fluree Version 0.13.0

**Update 6/10/30: This release is now in stable condition as 0.14.0. Get started here.

In addition to the below 0.13.0 features, 0.14.0 stable version includes the following improvements and changes.

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.

Fluree Developers —today we are excited to announce a new set of features and fixes available in our latest beta version 0.13.0 Release

What is different?

Analytical Query Improvements
Support for transactions with dependencies

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.

API endpoints to retrieve Ledger and Block Stats

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 endpoints 

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

Export

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 }

Improved Traceability

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.

Fluree Node.js Library (beta)

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

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

Fluree JavaScript Library (beta)

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

Fluree Worker Library (beta)

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

Fluree-React Wrapper (beta)

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

Admin UI Updates


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

New: Developer Hub!

Welcome to the Fluree Developer Hub. Here, you’ll be able to find download links for Fluree, example applications you can launch in under five minutes, and all of the tools, connectors, and extensions that Fluree releases.

Get Started

Share on facebook
Share on twitter
Share on linkedin

Share Article

Share on facebook
Share on twitter
Share on linkedin

Subscribe to the Fluree Newsletter

Get updates on new blog posts, news, and product announcements!

More Articles From Fluree

Introduction to Data-Centricity

The Data-Centric Architecture treats data as a valuable and versatile asset instead of an expensive afterthought. Data-centricity significantly simplifies security, integration, portability, and analysis while delivering faster insights across the entire data value chain. This post will introduce the concept of Data-Centricity and lay the framework for future installments on Data-Centricity.

Read More >

Making Data FAIR

As enterprises begin to invest heavily in extracting analytical and operational value from data, the FAIR data principles should be considered for highly-sophisticated master data management across various industries.

Read More >

Ready to Get Started with Fluree?

Let’s get in touch!