- 02 2月, 2015 4 次提交
-
-
由 Adam Retter 提交于
-
由 Adam Retter 提交于
-
由 Adam Retter 提交于
-
由 Adam Retter 提交于
-
- 31 1月, 2015 2 次提交
-
-
由 fyrz 提交于
Summary: As the C++ part exposes now SequenceNumber retrieval for Snapshots we want this obviously also in the Java API. Test Plan: make rocksdbjava make jtest mvn -f rocksjni.pom test Reviewers: yhchiang, adamretter, ankgup87 Subscribers: dhruba Differential Revision: https://reviews.facebook.net/D32571
-
由 fyrz 提交于
-
- 28 1月, 2015 1 次提交
-
-
由 fyrz 提交于
-
- 18 1月, 2015 1 次提交
-
-
由 fyrz 提交于
-
- 15 1月, 2015 2 次提交
-
-
由 Adam Retter 提交于
-
由 Adam Retter 提交于
-
- 19 12月, 2014 1 次提交
-
-
由 fyrz 提交于
Summary: - AssertionError when initialized with Non-Direct Buffer - Tests + coverage for DirectSlice - Slice sigsegv fixes when initializing from String and byte arrays - Slice Tests Test Plan: Run tests without source modifications. Reviewers: yhchiang, adamretter, ankgup87 Subscribers: dhruba Differential Revision: https://reviews.facebook.net/D30081
-
- 27 11月, 2014 2 次提交
-
-
由 Adam Retter 提交于
reference
-
由 Adam Retter 提交于
builds to be deleted
-
- 26 11月, 2014 3 次提交
- 22 11月, 2014 1 次提交
-
-
由 fyrz 提交于
Prevent non exist error message while executing clean twice.
-
- 21 11月, 2014 1 次提交
-
-
由 fyrz 提交于
- Updated the BackupableDBOptions functionality to 3.8.0. - Aligned Options implementation with remaining source code. - Invented test-case.
-
- 20 11月, 2014 2 次提交
-
-
由 fyrz 提交于
Previous to this commit too much targets got dependencies on javadocs target. Introduced one additional target "javalib" which resolves that situation. JavaDoc will now be generated once while executing a task with prefix "rocksdbjava".
-
由 fyrz 提交于
- Remove JNI includes on clean - Remove target folder generated by Maven - Remove shared object - Remove jar
-
- 15 11月, 2014 8 次提交
- 13 11月, 2014 3 次提交
-
-
由 fyrz 提交于
-
由 fyrz 提交于
********************* *************************** ******** ************* ******** ******** *********** ******** ******** ********* ******** ************************************* ************************************* ************************************* ****** *** *** ****** ****** *** *** *** ****** ****** *** ****** *************************** *********************
-
由 fyrz 提交于
[RocksJava] Extend Options with ColumnFamilyOptions implementation ColumnFamilyOptions implementation with tests [RocksJava] Extended ColumnFamilyTest Summary: Options Refactoring split part 3 Test Plan: make rocksdbjava make jtest Reviewers: yhchiang, ankgup87 Subscribers: dhruba Differential Revision: https://reviews.facebook.net/D28023
-
- 11 11月, 2014 2 次提交
- 10 11月, 2014 2 次提交
-
-
由 Adam Retter 提交于
-
由 Adam Retter 提交于
-
- 03 11月, 2014 2 次提交
-
-
由 fyrz 提交于
[RocksJava] Extend Options with DBOptions implementation [RocksJava] Included DBOptionsTest and refactored OptionsTest Summary: Options refactoring - Split Part2 Test Plan: make rocksdbjava make jtest Reviewers: yhchiang, ankgup87 Subscribers: dhruba Differential Revision: https://reviews.facebook.net/D28017
-
由 fyrz 提交于
-
- 31 10月, 2014 2 次提交
-
-
由 fyrz 提交于
Summary: Options extends now two interfaces DBOptionsInterface and ColumnFamilyOptionsInterface. There are also further improvements to the Options bindings: Optimize methods were ported to Java. (OptimizeForPointLookup, OptimizeLevelCompaction, OptimizeUniversalCompaction). To align BuiltinComparator with every other Enum it was moved to a separate file. Test Plan: make rocksdbjava make jtest
-
由 fyrz 提交于
- Added tests - Minor code-style changes
-
- 28 10月, 2014 1 次提交
-
-
由 fyrz 提交于
RocksIterator will sometimes Sigsegv on dispose. Mainly thats related to dispose order. If the related RocksDB instance is freed beforehand RocksIterator.dispose() will fail. Within this commit there is a major change to RocksIterator. RocksIterator will hold a private reference to the RocksDB instance which created the RocksIterator. So even if RocksDB is freed in the same GC cycle the RocksIterator instances will be freed prior to related RocksDB instances. Another aspect targets the dispose logic if the RocksDB is freed previously and already gc`ed. On dispose of a RocksIterator the dispose logic will check if the RocksDB instance points to an initialized DB. If not the dispose logic will not perform any further action. The crash can be reproduced by using the related test provided within this commit. Related information: This relates to @adamretter`s facebook rocksdb-dev group post about SigSegv on RocksIterator.dispose().
-