Merge pull request #414 from ArangoDB-Community/feature3.10/DE-342-en…

…hanced-cursor-stats

3.10: Added properties to CursorResponseStats

arangodb-net-standard/CursorApi/Models/CursorResponseStats.cs

@@ -31,5 +31,53 @@ public class CursorResponseStats
         public long Filtered { get; set; }
 
         public long HttpRequests { get; set; }
+
+        #region Introduced in v3.10
+
+        /// <summary>
+        /// Introduced in v3.10.
+        /// The total number of cursor objects created during 
+        /// query execution. Cursor objects are created for 
+        /// index lookups.
+        /// </summary>
+        public long? CursorsCreated { get; set; }
+
+        /// <summary>
+        /// Introduced in v3.10.
+        /// The total number of times an existing cursor 
+        /// object was repurposed. 
+        /// </summary>
+        /// <remarks>
+        /// Repurposing an existing 
+        /// cursor object is normally more efficient compared 
+        /// to destroying an existing cursor object and 
+        /// creating a new one from scratch.
+        /// </remarks>
+        public long? CursorsRearmed { get; set; }
+
+        /// <summary>
+        /// Introduced in v3.10.
+        /// The total number of index entries read from in-memory 
+        /// caches for indexes of type edge or persistent. 
+        /// This value will only be non-zero when reading from 
+        /// indexes that have an in-memory cache enabled, and 
+        /// when the query allows using the in-memory cache 
+        /// (i.e. using equality lookups on all index attributes).
+        /// </summary>
+        public long? CacheHits { get; set; }
+
+        /// <summary>
+        /// Introduced in v3.10.
+        /// The total number of cache read attempts for index entries
+        /// that could not be served from in-memory caches for indexes
+        /// of type edge or persistent. This value will only be non-zero
+        /// when reading from indexes that have an in-memory cache 
+        /// enabled, the query allows using the in-memory cache 
+        /// (i.e. using equality lookups on all index attributes) and
+        /// the looked up values are not present in the cache.
+        /// </summary>
+        public long? CacheMisses { get; set; }
+
+        #endregion
     }
-}
+}