5584776409
66%

Ran 18 Jul 2023 08:44AM UTC

Jobs 1

Files 250

Run time 5s

Badge

Embed ▾

Committed 18 Jul 2023 07:53AM UTC coverage: 67.22% (-0.1%) from 67.328%

Build # 5584776409

Build Type

push

Committed by

web-flow

Commit Message

doc(restore): add docs for mutations in between incremental restores (#8908)

If we do mutations in between incremental restores, those will get lost.
The next incremental restore will overwrite any data that is written in
between two incremental restores. It is not very useful to try to block
the next incremental restore after in between mutations because it is
really hard to detect that a change was made.

For example, let's say we detect the mutations done in between two
incremental restores by looking at the data in memtable. But then, if we
restart Dgraph, or drop any other attribute (predicate), that may end up
doing compaction and would persist all the data from memtable to
sstables. This would make it impossible to figure out that a change was
made.

It wouldn't be very useful to store this information (that a mutation
was done) in an in memory flag either. It would get destroyed if the
alpha restarts. Any other methodology seems too complex to me. I think
I'd rather keep the semantics of the incremental restore to say that it
will overwrite any in between mutations that are done if any.

Closes: DGRAPHCORE-276

Run Details

58492 of 87016 relevant lines covered (67.22%)

2234306.94 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	5584776409.1	18 Jul 2023 08:44AM UTC	0	67.22

Source Files on build 5584776409

Detailed source file information is not available for this build.

dgraph-io / dgraph / 5584776409
66%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 5584776409

dgraph-io / dgraph / 5584776409 66%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 5584776409

dgraph-io / dgraph / 5584776409
66%

README BADGES
x