From e4574cdfcf3d5ceafc24d4863eb007b81051e1f6 Mon Sep 17 00:00:00 2001 From: Oleksandr Porunov Date: Wed, 18 Oct 2023 13:27:54 +0100 Subject: [PATCH] Add links to describe repeat step changes in more details Fixes #3799 Signed-off-by: Oleksandr Porunov --- docs/changelog.md | 2 ++ docs/operations/batch-processing.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/docs/changelog.md b/docs/changelog.md index 5ab4f95191..76d1f59b2f 100644 --- a/docs/changelog.md +++ b/docs/changelog.md @@ -267,6 +267,8 @@ With `closest_repeat_parent` mode vertices for batch registration will be receiv `repeat` step as well as the end of the closest `repeat` step (for the next iteration). Any other parent `repeat` steps will be ignored. +See detailed `repeat` step batch processing explanation [here](https://medium.com/@porunov/janusgraph-1-0-0-batch-queries-multi-query-14abc8f66d93#b09f). + ##### ConfiguredGraphFactory now creates separate indices per graph in Elasticsearch If the ConfiguredGraphFactory is used together with Elasticsearch as the index backend, then the same Elasticsearch diff --git a/docs/operations/batch-processing.md b/docs/operations/batch-processing.md index 29a225f9ab..a78247e842 100644 --- a/docs/operations/batch-processing.md +++ b/docs/operations/batch-processing.md @@ -304,6 +304,8 @@ Thus, JanusGraph provides a configuration option `query.batch.repeat-step-mode` (for the first iterations), the `and` step input (for the first iterations), and from the `out("knows")` output (for the next iterations). +See `repeat` step batch processing explanation [here](https://medium.com/@porunov/janusgraph-1-0-0-batch-queries-multi-query-14abc8f66d93#b09f). + #### Batch processing for `match` step Currently, JanusGraph supports vertices registration for batch processing inside individual local traversals of the `match`