1. 11 11月, 2016 3 次提交
    • R
      Fix 2PC Recovery SeqId Miscount · 1ca5f6d1
      Reid Horuff 提交于
      Summary:
      Originally sequence ids were calculated, in recovery, based off of the first seqid found if the first log recovered. The working seqid was then incremented from that value based on every insertion that took place. This was faulty because of the potential for missing log files or inserts that skipped the WAL. The current recovery scheme grabs sequence from current recovering batch and increments using memtableinserter to track how many actual inserts take place. This works for 2PC batches as well scenarios where some logs are missing or inserts that skip the WAL.
      Closes https://github.com/facebook/rocksdb/pull/1486
      
      Differential Revision: D4156064
      
      Pulled By: reidHoruff
      
      fbshipit-source-id: a6da8d9
      1ca5f6d1
    • S
      Rocksdb contruns to new Sandcastle API · e095d0cb
      Sergey Balabanov 提交于
      Reviewed By: IslamAbdelRahman
      
      Differential Revision: D4114816
      
      fbshipit-source-id: 8082936
      e095d0cb
    • A
      Convenience option to parse an internal key on command line · 14c0380e
      Anirban Rahut 提交于
      Summary:
      enhancing sst_dump to be able to parse internal key
      Closes https://github.com/facebook/rocksdb/pull/1482
      
      Differential Revision: D4154175
      
      Pulled By: siying
      
      fbshipit-source-id: b0e28b1
      14c0380e
  2. 10 11月, 2016 6 次提交
  3. 09 11月, 2016 5 次提交
  4. 08 11月, 2016 6 次提交
  5. 06 11月, 2016 2 次提交
    • A
      Java API - Implement GetFromBatch and GetFromBatchAndDB in WBWI · 24bceb09
      Adam Retter 提交于
      Summary:
      Needed for working with `get` after `merge` on a WBWI.
      Closes https://github.com/facebook/rocksdb/pull/1093
      
      Differential Revision: D4137978
      
      Pulled By: yhchiang
      
      fbshipit-source-id: e18d50d
      24bceb09
    • A
      Insert range deletion meta-block into block cache · 815f54af
      Andrew Kryczka 提交于
      Summary:
      This handles two issues: (1) range deletion iterator sometimes outlives
      the table reader that created it, in which case the block must not be destroyed
      during table reader destruction; and (2) we prefer to read these range tombstone
      meta-blocks from file fewer times.
      
      - Extracted cache-populating logic from NewDataBlockIterator() into a separate function: MaybeLoadDataBlockToCache()
      - Use MaybeLoadDataBlockToCache() to load range deletion meta-block and pin it through the reader's lifetime. This code reuse works since range deletion meta-block has same format as data blocks.
      - Use NewDataBlockIterator() to create range deletion iterators, which uses block cache if enabled, otherwise reads the block from file. Either way, the underlying block won't disappear until after the iterator is destroyed.
      Closes https://github.com/facebook/rocksdb/pull/1459
      
      Differential Revision: D4123175
      
      Pulled By: ajkr
      
      fbshipit-source-id: 8f64281
      815f54af
  6. 05 11月, 2016 2 次提交
  7. 04 11月, 2016 3 次提交
  8. 03 11月, 2016 1 次提交
  9. 02 11月, 2016 3 次提交
  10. 01 11月, 2016 6 次提交
  11. 30 10月, 2016 3 次提交