From 4ed86d556b81e9a078d72d4889071644a66e0e43 Mon Sep 17 00:00:00 2001
From: Matthew Swift <matthew.swift@forgerock.com>
Date: Thu, 18 Dec 2014 21:34:29 +0000
Subject: [PATCH] OPENDJ-1602 (CR-5566) New pluggable storage based backend
---
opendj-sdk/opendj3-server-dev/src/server/org/opends/server/backends/pluggable/IndexBuffer.java | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/opendj-sdk/opendj3-server-dev/src/server/org/opends/server/backends/pluggable/IndexBuffer.java b/opendj-sdk/opendj3-server-dev/src/server/org/opends/server/backends/pluggable/IndexBuffer.java
index 2efd1e6..a22425d 100644
--- a/opendj-sdk/opendj3-server-dev/src/server/org/opends/server/backends/pluggable/IndexBuffer.java
+++ b/opendj-sdk/opendj3-server-dev/src/server/org/opends/server/backends/pluggable/IndexBuffer.java
@@ -235,6 +235,11 @@
*/
public void flush(WriteableStorage txn) throws StorageRuntimeException, DirectoryException
{
+ /*
+ * FIXME: this seems like a surprising way to update the indexes. Why not
+ * store the buffered changes in a TreeMap in order to have a predictable
+ * iteration order?
+ */
for (AttributeIndex attributeIndex : entryContainer.getAttributeIndexes())
{
for (Index index : attributeIndex.getAllIndexes())
--
Gitblit v1.10.0