sirix | evolutionary database system | Database library
kandi X-RAY | sirix Summary
kandi X-RAY | sirix Summary
sirix is a Java library typically used in Database applications. sirix has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has medium support. You can download it from GitHub, Maven.
SirixDB is a log-structured, temporal NoSQL document store, which stores evolutionary data. It never overwrites any data on-disk. Thus, we're able to restore and query the full revision history of a resource in the database.
SirixDB is a log-structured, temporal NoSQL document store, which stores evolutionary data. It never overwrites any data on-disk. Thus, we're able to restore and query the full revision history of a resource in the database.
Support
Quality
Security
License
Reuse
Support
sirix has a medium active ecosystem.
It has 839 star(s) with 188 fork(s). There are 34 watchers for this library.
It had no major release in the last 6 months.
There are 86 open issues and 129 have been closed. On average issues are closed in 257 days. There are 5 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of sirix is sirix-0.9.6
Quality
sirix has 0 bugs and 0 code smells.
Security
sirix has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
sirix code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
sirix is licensed under the BSD-3-Clause License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
sirix releases are not available. You will need to build from source code and install.
Deployable package is available in Maven.
Build file is available. You can build the component from source.
Installation instructions, examples and code snippets are available.
It has 1323180 lines of code, 9153 functions and 1386 files.
It has medium code complexity. Code complexity directly impacts maintainability of the code.
Top functions reviewed by kandi - BETA
kandi has reviewed sirix and discovered the below as its top functions. This is intended to give you an instant insight into sirix implemented functionality, and help decide if they suit your requirements.
- Creates a new page with the specified commit timestamp and revision
- Truncate the log
- Sets the revision timestamp
- Emit a JSON node
- Escapes the given string
- Emit meta data for a node
- Append a key and value pair
- Commits the page
- Truncate the log
- Sets the revision timestamp
- Set string value
- Inserts a number
- Emit a non - structural diff
- Set number value
- Insert an object record as left sibling
- Insert an object record as the right sibling
- Inserts an object record as last child
- Deletes an immutable element
- Compacts a new diff
- Set the current node
- Get the next key
- Performs serialization
- Insert a string value as last child
- Compare two nodes
- Changes the name of an object key
- Compare the changes
- Creates a new data record
- Get the next node key
Get all kandi verified functions for this library.
sirix Key Features
No Key Features are available at this moment for sirix.
sirix Examples and Code Snippets
No Code Snippets are available at this moment for sirix.
Community Discussions
Trending Discussions on sirix
QUESTION
Include maven dependencies built with Java9 or Java10 in a Kotlin project
Asked 2018-May-07 at 12:10
Is it possible to include Java9 (or 10) dependencies? As Kotlin is only able to compile to Java 8 so far. I'm getting an java.lang.UnsupportedClassVersionError error obviously stating that a class in the JAR/dependency I'm including has been compiled by a more recent version of the Java Runtime. However am I not able to specify a newer JDK, which is able to run classes compiled with older versions (the Kotlin stuff?).
ANSWER
Answered 2018-May-07 at 10:22I suspect that the problem is in the Kotlin Maven plugin, which infers the -jvm-target argument value directly from maven.compiler.source/maven.compiler.target properties, not taking into account the fact that the Kotlin compiler only supports versions 1.6 and 1.8. The workaround would be to specify the JVM bytecode target version explicitly to 1.8, for example (note that 1.8-targeted bytecode will run on Java 9 just fine):
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install sirix
or use the following dependencies in your Maven or Gradle project.
The REST-API is asynchronous at its very core. We use Vert.x, which is a toolkit built on top of Netty. It is heavily inspired by Node.js but for the JVM. As such, it uses event loop(s), which is thread(s), which never should by blocked by long-running CPU tasks or disk-bound I/O. We are using Kotlin with coroutines to keep the code simple. SirixDB uses OAuth2 (Password Credentials/Resource Owner Flow) using a Keycloak authorization server instance.
You can set up Keycloak as described in this excellent tutorial. Our docker-compose file imports a sirix realm with a default admin user with all available roles assigned. You can skip steps 3 - 7 and 10, 11, and simply recreate a client-secret and change oAuthFlowType to "PASSWORD". If you want to run or modify the integration tests, the client secret must not be changed. Make sure to delete the line "build: ." in the docker-compse.yml file for the server image if you want to use the Docker Hub image.
Open your browser. URL: http://localhost:8080
Login with username "admin", password "admin"
Create a new realm with the name "sirixdb"
Go to Clients => account
Change client-id to "sirix"
Make sure access-type is set to confidential
Go to Credentials tab
Put the client secret into the SirixDB HTTP-Server configuration file. Change the value of "client.secret" to whatever Keycloak set up.
If "oAuthFlowType" is specified in the ame configuration file change the value to "PASSWORD" (if not default is "PASSWORD").
Regarding Keycloak the direct access grant on the settings tab must be enabled.
Our (user-/group-)roles are "create" to allow creating databases/resources, "view" to allow to query database resources, "modify" to modify a database resource and "delete" to allow deletion thereof. You can also assign ${databaseName}- prefixed roles.
To created a fat-JAR. Download our ZIP-file for instance, then. And a fat-JAR with all required dependencies should have been created in your target folder. Furthermore, a key.pem and a cert.pem file are needed. These two files have to be in your user home directory in a directory called "sirix-data", where Sirix stores the databases. For demo purposes they can be copied from our resources directory.
cd bundles/sirix-rest-api
gradle build -x test
The REST-API is asynchronous at its very core. We use Vert.x, which is a toolkit built on top of Netty. It is heavily inspired by Node.js but for the JVM. As such, it uses event loop(s), which is thread(s), which never should by blocked by long-running CPU tasks or disk-bound I/O. We are using Kotlin with coroutines to keep the code simple. SirixDB uses OAuth2 (Password Credentials/Resource Owner Flow) using a Keycloak authorization server instance.
You can set up Keycloak as described in this excellent tutorial. Our docker-compose file imports a sirix realm with a default admin user with all available roles assigned. You can skip steps 3 - 7 and 10, 11, and simply recreate a client-secret and change oAuthFlowType to "PASSWORD". If you want to run or modify the integration tests, the client secret must not be changed. Make sure to delete the line "build: ." in the docker-compse.yml file for the server image if you want to use the Docker Hub image.
Open your browser. URL: http://localhost:8080
Login with username "admin", password "admin"
Create a new realm with the name "sirixdb"
Go to Clients => account
Change client-id to "sirix"
Make sure access-type is set to confidential
Go to Credentials tab
Put the client secret into the SirixDB HTTP-Server configuration file. Change the value of "client.secret" to whatever Keycloak set up.
If "oAuthFlowType" is specified in the ame configuration file change the value to "PASSWORD" (if not default is "PASSWORD").
Regarding Keycloak the direct access grant on the settings tab must be enabled.
Our (user-/group-)roles are "create" to allow creating databases/resources, "view" to allow to query database resources, "modify" to modify a database resource and "delete" to allow deletion thereof. You can also assign ${databaseName}- prefixed roles.
To created a fat-JAR. Download our ZIP-file for instance, then. And a fat-JAR with all required dependencies should have been created in your target folder. Furthermore, a key.pem and a cert.pem file are needed. These two files have to be in your user home directory in a directory called "sirix-data", where Sirix stores the databases. For demo purposes they can be copied from our resources directory.
cd bundles/sirix-rest-api
gradle build -x test
Support
We are currently working on the documentation. You may find first drafts and snippets in the documentation and in this README. Furthermore, you are kindly invited to ask any question you might have (and you likely have many questions) in the community forum (preferred) or in the Slack channel. Please also have a look at and play with our sirix-example bundle which is available via maven or our new asynchronous RESTful API (shown next).
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
