Latest release : Thing in the future 3.9.0 on may 30th 2023
Thing in the future 3.9 integrates mainly bugfixes
Server (3.9.0)
Api (3.9.0)
SDT (1.5.0)
Admin (2.6.0)
OLS (9.2.0)
neo4j-procedures (1.0.7)
federator (1.3.0)
federator-admin (1.1.0)
API (3.6.1)
Server (3.6.1)
Neo4j procedures (1.0.6)
API (3.6.0)
thingin_uuid returned in body of POST /dtsServer (3.6.0)
Histdb-feed (3.6.0)
DT (1.3.0)
Please refer to https://wiki.thinginthefuture.com/e/en/public/DigitalTwinModule for new fetures description
Stat (2.4.2)
API (3.5.0)
Server (3.5.0)
Histdb-feed (3.5.0)
Admin (Portal) (2.3.6):
Admin (Portal) (2.3.5):
API (3.4.1): (2022/12/23)
Server (3.4.2): (2022/12/23)
Server (3.4.1): (2022/12/16)
Server (3.4.0):
API (3.4.0):
Admin (Portal) (2.3.0):
DT (1.2.0):
Technical changes:
RANGE_SLICE syntax change :
RANGE_SLICE [A; B] ... which was meaning from timestamp A included to timestamp B includedRANGE_SLICE [A; B) ... meaning from timestamp A included to timestamp B excludedOption Match queriesServer (2.8.0):
API (2.8.0):
Injectors (1.1.1):
Server (2.7.0):
API (2.7.0):
Server (2.6.0-0):
API (2.6.0-0):
Server (2.5.0-1):
API (2.5.0-1):
Server (2.5.0-0):
api (2.5.0-0):
avatar/update (if the id of the edge is given on update/set, if the edge with tis id already exists process an update, otherwise create it).$lastUpdated keyword for the search queries, enabling the filtering on the field _lastUpdated of the avatars (possible operators : $eq, $gt, $gte, $lt,$lte).Server (2.4.0-0):
Arango (3.6.13):
Server (2.3.0-0):
API (2.3.0-0):
Arango (3.6.10):
Server: 2.0.0-3 (2.0.0-5 on 2020/11/10, 2.0.0-4 on 2020/11/09)
Blob : On the graph, description of data objects can be attached to avatar. This object could be for instance image, icone, 3d model, building plan ... The data itself is not stored in the graph, only the description and the information to download it.
Compression : since the last version, the user is able to to use Accept-Encoding header set to "gzip" to get the response in a compressed way from the API. This allows a real benefit since the received data are JSON or RDF. Now the data exchange between API and Server are also compressed, releasing pressure on the message bus.
Fix a bug on user deletion (now all data owned by the deleted user are also deleted: avatars, ACLs, Security Groups, Clusters, Blobs...)
Bug fixed in 2.0.0-4: internal error could happen during avatar update
Bug fixed in 2.0.0-5: avatars with acl had a visibility of -1 in result of a get or search request
API: 2.0.0-7
OLS: 9.0.5-0
Specific injectors: 1.0.2 (unchanged)
Server: 2.0.0
API: 2.0.0
Portal (admin): 2.0.0
OLS: 9.0.4-0
Specific injectors: 1.0.2
Thing in the future 2.0.0 is a major release candidate