nessie
Flyway
nessie | Flyway | |
---|---|---|
13 | 81 | |
834 | 7,775 | |
3.6% | 0.6% | |
9.9 | 7.2 | |
4 days ago | 11 days ago | |
Java | Java | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nessie
-
A deep dive into the concept and world of Apache Iceberg Catalogs
Nessie is an innovative open-source catalog that extends beyond the traditional catalog capabilities in the Apache Iceberg ecosystem, introducing git-like features to data management. This catalog not only tracks table metadata but also allows users to capture commits at a holistic level, enabling advanced operations such as multi-table transactions, rollbacks, branching, and tagging. These features provide a new layer of flexibility and control over data changes, resembling version control systems in software development.
- FLaNK Stack Weekly 22 January 2024
-
Why is Hive Metastore everywhere? (Especially Iceberg)
Try Nessie https://github.com/projectnessie/nessie - it recently got trino support as well ..
- What are the main things I need to know to be hired as a Java developer?
- Is learning and mastering Spring & Spring boot worth it in 2023 ?
-
Which lakehouse table format do you expect your organization will be using by the end of 2023?
Project Nessie (https://projectnessie.org/) will be the catalog that eventually decouples Iceberg from Hive. At that point, I think it will be a no brainer to go Iceberg over Delta.
-
5 Reasons Your Data Lakehouse should Embrace Dremio Cloud
The Dremio Sonar query engine can query your data where it exists whether it's AWS Glue, S3, Nessie Catalogs, MySQL, Postgres, RedShift and an ever growing list of sources.
- Project Nessie: Transactional Catalog for Data Lakes with Git-Like Semantics
-
Introduction to The World of Data - (OLTP, OLAP, Data Warehouses, Data Lakes and more)
We will also need a catalog to track all of these tables, with the open source Project Nessie we can do just that, and also get great versioning features similar to using Git when developing applications allowing data engineers to practice "data as code" and "write-audit-publish" patterns on their data.
- DoltLab v0.2.0
Flyway
-
Let's write a simple microservice in Clojure
The session logs show that the application loads configurations and establishes a connection with a PostgreSQL database. This involves initializing a HikariCP connection pool and Flyway for database migrations. The logs confirm that the database schema validation and migration checks were successful. The startup of the Jetty HTTP server follows, and the server becomes operational and ready to accept requests on the specified port.
-
Ask HN: What tool(s) do you use to code review and deploy SQL scripts?
Also RedGate, but Flyway has some reasons to recommend it over RedGate Deploy depending on your DBAs/workflows: https://flywaydb.org/
(Though I don't think it is "complete" or "perfect", either.)
EF Migrations are in a really good place now if you like/don't mind C# as a language (and you can easily embed SQL inside the C#, too, but there are benefits to being able to also run high level C# code). With today's tooling you can package your migration "runner application" as a single deployable executable for most platforms. You can build the executable once and run it in all your environments. (The same tool that updates your QA and Staging updates your Prod, testably running the same migrations.) Given the single executable deployable I might even consider using it for projects not themselves written in C#.
-
PostgreSQL Is Enough
There is a bit of tooling needed but is already around. For Java for example I had very good experience with a combination of flyway [1] for migrations, testcontainers [2] for making integration tests as easy as unit tests and querydsl [3] for a query and mapping layer.
[1] https://github.com/flyway/flyway
[2] https://java.testcontainers.org/modules/databases/postgres/
[3] https://github.com/querydsl/querydsl
-
Using Flyway to version your database
When software starts using a database, it's advisable to have version control, just as we have Github to control our source code. This is all to be sure about what was executed for that specific version. For Java and Spring boot, we have the Flyway framework that aims to resolve this situation, free of charge.
-
CI/CD for Databricks
If you're looking for tools, like https://www.liquibase.com/ or https://flywaydb.org/, which are database-state-based schema migration toolkits - it might be relatively straightforward to build similar ones using Databricks SQL drivers.
-
Working with jOOQ and Flyway using Testcontainers
Honestly I kind of wish there was a Lukas Eder database migration library. Call it whatever jooq-migration. At least I would have more insight of what is going on (<-- seriously look at the commit history).
-
Strategy to run database scripts on Kubernetes
This is a 4th option, which should play nice with ArgoCD. The following example runs flyway as a k8s job. The desired migration changes are recorded as files within the chart. This helm chart can be integrated with your application (Using hooks to determine when the migration job is run) or run manually.
-
How do your teams run DB migrations?
By using an opinionated framework within the app/service (like Flyway, Migrate, Diesel, etc). Schema migrations happen on app/service start-up.
-
I've never created a production database from scratch and am wondering how much trouble it would be to transition a one-to-one relationship to a one-to-many relationship if I determine at some point that the latter is required.
Depending on the language or platform there are libraries you can use to manage this, such as Prisma on node and Flyway for Java/JVM.
-
How should I document and/or automate schema changes?
It's probably overkill but I've used github plus flyway at a couple places in the past which is pretty nice tool for tracking changes to a variety of db's, it's also very helpful if you ever need to replicate a db in a new region/environment.
What are some alternatives?
git-bug - Distributed, offline-first bug tracker embedded in git, with bridges
alembic - A database migrations tool for SQLAlchemy.
dvc - 🦉 ML Experiments and Data Management with Git
HikariCP - 光 HikariCP・A solid, high-performance, JDBC connection pool at last.
hiveberg - Demonstration of a Hive Input Format for Iceberg
roundhouse - RoundhousE is a Database Migration Utility for .NET using sql files and versioning based on source control
dremio-oss - Dremio - the missing link in modern data
H2 - H2 is an embeddable RDBMS written in Java.
noms - The versioned, forkable, syncable database
dbmate - :rocket: A lightweight, framework-agnostic database migration tool.
dolt - Dolt – Git for Data
Hibernate - Hibernate's core Object/Relational Mapping functionality