Conversation
| } | ||
|
|
||
| @Nullable | ||
| public Feature getPrefetchFeature() { |
There was a problem hiding this comment.
setPrefetchFeature() was removed but getPrefetchFeature() and the prefetchFeature field remain (always null). Consider removing the getter and dead fields on the builder, store, and service as part of this cleanup.
| System.setProperty(SYS_PROP_PREFETCH, "true"); | ||
| } | ||
|
|
||
| @AfterClass |
There was a problem hiding this comment.
After dropping sys-prop setup, consider adding a test that calls DocumentNodeStore.prefetch() (not CacheWarming directly) with default builder setup and asserts cache warming — that would lock in the always-on store path this PR introduces.
There was a problem hiding this comment.
I don't quite understand; is this about adding a test that we should have had before?
|
|
@rishabhdaim - thx for the review, and please see my questions (PR minimally updated). (this shows that even removing a toggle is not totally trivial) |
|
Outside this diff —
- CacheWarming cw = new CacheWarming(ds);
DocumentNodeStore store = builderProvider.newBuilder().setAsyncDelay(0)
.setDocumentStore(ds).getNodeStore();
...
- cw.prefetch(children, store.getRoot());
+ store.prefetch(children, store.getRoot());
...
- cw.prefetch(paths, store.getRoot());
+ store.prefetch(paths, store.getRoot()); |
|



No description provided.