github.com/cockroachdb/pebble@v1.1.2/internal/keyspan/testdata/fragmenter_covers (about)

     1  # This datadriven test uses a single command 'build' that illustrates a sequence
     2  # of calls to a fragmenter.
     3  #
     4  # 'add' lines add a new span with the provided sequence number and the provided
     5  # bounds. 'add' outputs nothing.
     6  #
     7  # 'deleted' lines test whether the provided key is deleted by a RANGEDEL in the
     8  # fragmenter when read at the trailing snapshot sequence number.
     9  
    10  build
    11  deleted a.SET.0     5
    12  add 3: a-----------m
    13  deleted a.SET.0     5
    14  deleted a.SET.1     5
    15  deleted a.SET.1     2
    16  deleted a.SET.2     5
    17  deleted a.SET.3     5
    18  deleted l.SET.3     5
    19  add 2:      f------------s
    20  deleted e.SET.3     5
    21  deleted f.SET.2     5
    22  deleted l.SET.2     5
    23  deleted m.SET.2     5
    24  add 1:          j---------------z
    25  deleted j.SET.1     5
    26  deleted j.SET.1     1
    27  deleted j.SET.2     5
    28  deleted j.SET.3     5
    29  deleted l.SET.2     5
    30  deleted m.SET.2     5
    31  deleted r.SET.1     5
    32  deleted r.SET.1     1
    33  deleted s.SET.1     5
    34  deleted y.SET.0     5
    35  deleted z.SET.0     5
    36  ----
    37  a#0,1: none
    38  a#0,1: visibly
    39  a#1,1: visibly
    40  a#1,1: invisibly
    41  a#2,1: visibly
    42  a#3,1: none
    43  l#3,1: none
    44  e#3,1: pebble: keys must be in order: f > e#3,SET
    45  f#2,1: visibly
    46  l#2,1: visibly
    47  m#2,1: none
    48  j#1,1: visibly
    49  j#1,1: invisibly
    50  j#2,1: visibly
    51  j#3,1: none
    52  l#2,1: visibly
    53  m#2,1: none
    54  r#1,1: visibly
    55  r#1,1: invisibly
    56  s#1,1: none
    57  y#0,1: visibly
    58  z#0,1: none