Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RocksJava] Added LevelCompactionDynamicLevelBytes to Options #532

Merged

Conversation

fyrz
Copy link
Contributor

@fyrz fyrz commented Mar 11, 2015

Summary: Added LevelCompactionDynamicLevelBytes to Options.

Test Plan:
make clean jclean rocksdbjava jtest
mvn -f rocksjni.pom package

Reviewers: adamretter, ankgup87, yhchiang

Subscribers: dhruba

Differential Revision: https://reviews.facebook.net/D34857

@fyrz fyrz force-pushed the RocksJava-LevelCompactionDynamicLevelBytes branch 2 times, most recently from c47178c to 4fc6d04 Compare March 14, 2015 19:59
Summary: Added LevelCompactionDynamicLevelBytes to Options.

Test Plan:
make clean jclean rocksdbjava jtest
mvn -f rocksjni.pom package

Reviewers: adamretter, ankgup87, yhchiang

Subscribers: dhruba

Differential Revision: https://reviews.facebook.net/D34857
@fyrz fyrz force-pushed the RocksJava-LevelCompactionDynamicLevelBytes branch from 4fc6d04 to c345d1e Compare March 18, 2015 20:38
@adamretter
Copy link
Collaborator

Review completed and tests run fine here.

adamretter added a commit that referenced this pull request Mar 19, 2015
…elBytes

[RocksJava] Added LevelCompactionDynamicLevelBytes to Options
@adamretter adamretter merged commit 836bcc2 into facebook:master Mar 19, 2015
@fyrz fyrz deleted the RocksJava-LevelCompactionDynamicLevelBytes branch March 19, 2015 13:34
@coveralls
Copy link

coveralls commented Oct 20, 2016

Coverage Status

Changes Unknown when pulling c345d1e on fyrz:RocksJava-LevelCompactionDynamicLevelBytes into * on facebook:master*.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants