From 3015bbe5aa975f4c89dc72aea47dff2e9f018c55 Mon Sep 17 00:00:00 2001 From: Barak Amar Date: Wed, 25 Oct 2023 10:58:49 +0300 Subject: [PATCH] docs: use blogs links --- docs/integrations/delta.md | 2 +- docs/understand/faq.md | 4 ++-- docs/understand/model.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/integrations/delta.md b/docs/integrations/delta.md index 36a1eaacd37..a6fdcc7d414 100644 --- a/docs/integrations/delta.md +++ b/docs/integrations/delta.md @@ -105,7 +105,7 @@ If you are trying to achieve that, please reach out on Slack and the community w ## Further Reading -See [Guaranteeing Consistency in Your Delta Lake Tables With lakeFS](https://lakefs.io/guarantee-consistency-in-your-delta-lake-tables-with-lakefs/) post on the lakeFS blog to learn how to +See [Guaranteeing Consistency in Your Delta Lake Tables With lakeFS](https://lakefs.io/blog/guarantee-consistency-in-your-delta-lake-tables-with-lakefs/) post on the lakeFS blog to learn how to guarantee data quality in a Delta table by utilizing lakeFS branches. diff --git a/docs/understand/faq.md b/docs/understand/faq.md index 96f6b36ad5d..787e1dbdca6 100644 --- a/docs/understand/faq.md +++ b/docs/understand/faq.md @@ -12,7 +12,7 @@ redirect_from: lakeFS is completely free, open-source, and licensed under the [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) License. We maintain a public [product roadmap][roadmap] and a [Slack channel](https://lakefs.io/slack) for open discussions. ### 2. How does lakeFS data versioning work? -lakeFS uses a copy-on-write mechanism to avoid data duplication. For example, creating a new branch is a metadata-only operation: no objects are actually copied. Only when an object changes does lakeFS create another [version of the data](https://lakefs.io/data-versioning/) in the storage. For more information, see [Versioning internals]({% link understand/how/versioning-internals.md %}). +lakeFS uses a copy-on-write mechanism to avoid data duplication. For example, creating a new branch is a metadata-only operation: no objects are actually copied. Only when an object changes does lakeFS create another [version of the data](https://lakefs.io/blog/data-versioning/) in the storage. For more information, see [Versioning internals]({% link understand/how/versioning-internals.md %}). ### 3. How do I get support for my lakeFS installation? We are extremely responsive on our Slack channel, and we make sure to prioritize the most pressing issues for the community. For SLA-based support, please contact us at [support@treeverse.io](mailto:support@treeverse.io). @@ -29,7 +29,7 @@ The data we gather is limited to the following: 1. Periodic aggregated action counters (e.g. how many "get_object" operations occurred). ### 5. How is lakeFS different from Delta Lake / Hudi / Iceberg? -Delta Lake, Apache Hudi, and Apache Iceberg all define dedicated, structured data formats that allow deletes and upserts. lakeFS is format-agnostic and enables consistent cross-collection versioning of your data using Git-like operations. Read our [comparison](https://lakefs.io/hudi-iceberg-and-delta-lake-data-lake-table-formats-compared/) for a more detailed comparison. +Delta Lake, Apache Hudi, and Apache Iceberg all define dedicated, structured data formats that allow deletes and upserts. lakeFS is format-agnostic and enables consistent cross-collection versioning of your data using Git-like operations. Read our [comparison](https://lakefs.io/blog/hudi-iceberg-and-delta-lake-data-lake-table-formats-compared/) for a more detailed comparison. ### 6. What inspired the lakeFS logo? The [Axolotl](https://en.wikipedia.org/wiki/Axolotl){:target="_blank"} – a species of salamander, also known as the Mexican Lake Monster or the Peter Pan of the animal kingdom. It's a magical creature, living in a lake - just like us! :) diff --git a/docs/understand/model.md b/docs/understand/model.md index e4b45e60e25..34b8b057417 100644 --- a/docs/understand/model.md +++ b/docs/understand/model.md @@ -29,7 +29,7 @@ lakeFS is spearheading version control semantics for data. Most of these concept ### Repository -In lakeFS, a _repository_ is a set of related objects (or collections of objects). In many cases, these represent tables of [various formats](https://lakefs.io/hudi-iceberg-and-delta-lake-data-lake-table-formats-compared/){:target="_blank"} for tabular data, semi-structured data such as JSON or log files - or a set of unstructured objects such as images, videos, sensor data, etc. +In lakeFS, a _repository_ is a set of related objects (or collections of objects). In many cases, these represent tables of [various formats](https://lakefs.io/blog/hudi-iceberg-and-delta-lake-data-lake-table-formats-compared/){:target="_blank"} for tabular data, semi-structured data such as JSON or log files - or a set of unstructured objects such as images, videos, sensor data, etc. lakeFS represents repositories as a logical namespace used to group together objects, branches, and commits - analogous to a repository in Git.