lichtenberger

50 ms·

1. 571.▲
   by lichtenberger 8y ago

   What do others think?
2. 572.▲
   by lichtenberger 8y ago

   Hmm, I wasn't sure or if a really short description and then setting up everything to get started isn't the best. That said, I have to look at that section, as it might even be a bit dated.
3. 573.▲
   by lichtenberger 8y ago

   Working with Java11 now :-)
4. 574.▲
   by lichtenberger 8y ago

   Okay, I guess simply there needs to be a newer Maven version on Travis and I messed up the release flag for the `maven-compiler-plugin`. That said, locally it already works with Java11 :-) ... just Travis fails as of now
5. 575.▲
   by lichtenberger 8y ago

   https://travis-ci.org/sirixdb/sirix/builds/473332290
6. 576.▲
   by lichtenberger 8y ago

   Has anyone an idea, why Travis doesn't build with Java11 because of Mockito and how to fix it? https://github.com/sirixdb/sirix/issues/59 I've mentioned, that I guess it's a transitive dependen
7. 577.▲
   by lichtenberger 8y ago

   What's your project idea by the way? :)
8. 578.▲
   by lichtenberger 8y ago

   Wow, thank you so much :-)
9. 579.▲
   by lichtenberger 8y ago

   During our copy-on-write we also do not necessarily store the whole record-page (leaf page with data/records), but depending on the versioning algorithm only changed records since some past state. The sliding snapshot algorithm for ins
10. 580.▲
    by lichtenberger 8y ago

    Ph.D. thesis which might also help from Marc (from which the idea and everything originates) http://www.uni-konstanz.de/mmsp/pubsys/publishedFiles/Kramis... From Sebastian Graf: https://kops.uni-ko
11. 581.▲
    by lichtenberger 8y ago

    Thanks so much for asking. I'm not sure how they are actually storing their bitemporal documents, but I think it must be some kind of a huge B(+)-tree maybe. I think the cool thing is that we have revision root pages and are able to re
12. 582.▲
    by lichtenberger 8y ago

    Key features are: - log-structured storage system with copy-on-write semantics especially well suited for SSDs (random reads, writes are batched and synced to disk when a commit is issued) - implements a novel versioning algorithm called sl
13. 583.▲
    by lichtenberger 8y ago

    Key features are: - log-structured storage system with copy-on-write semantics especially well suited for SSDs (random reads, writes are batched and synced to disk when a commit is issued) - implements a novel versioning algorithm called sl
14. 584.▲
    Show HN: SirixDB – versioning through efficient snapshotting

    55 points by lichtenberger 8y ago|24 comments
15. 585.▲
    by lichtenberger 8y ago

    I'm using Keycloak for authentication and Vert.x for aauthorization besides the main use case.
16. 586.▲
    by lichtenberger 8y ago

    I just updated the documentation slightly, how to set up and start the HTTP-server without docker.
17. 587.▲
    by lichtenberger 8y ago

    I almost gave up the work on http://sirix.io . But somehow still motivated to bring forth the idea of a versioned storage system capable of supporting temporal, analytical tasks. That is storing and querying snapshots of data in
18. 588.▲
    by lichtenberger 8y ago

    Oh by the way retrieval of nodes/records and storing modifications are logarithmic (O(log n)). Space complexity is O(n).
19. 589.▲
    by lichtenberger 8y ago

    It's somehow not connecting to the Keycloak-instance. Same with using the host network: `docker run --network=host -t -i -p 9443:9443 sirixdb/sirix`
20. 590.▲
    by lichtenberger 8y ago

    Maybe someone has an idea what's wrong with my simple Dockerfile, I'm getting the exception "io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: localhost/127.0.0.1:8080" when I want to r
21. 591.▲
    Show HN: SirixDB – Storing and Querying of Temporal Data (Java and Open Source)

    13 points by lichtenberger 8y ago|4 comments