## Nostr Event Store Version `v0.7.0` Release Log This update includes numerous feature enhancements, performance optimizations, and critical fixes, improving system stability and flexibility. Key updates are as follows: ### Important Features and Functionality - **Enhanced Aggregation Functionality** - Added metadata support for aggregation operations. - Support for multi-index aggregation queries, improving complex query capabilities. - Adjusted the maximum aggregation grouping key logic, improving aggregation efficiency under large data volumes. - Supplemented aggregation-related documentation. - **Replaceable Kind Event Configuration** - Added replaceable kind event configuration to both base-relay and remote-relay, supporting more flexible event replacement and deletion strategies. - **Batch Save and Validation** - Added validation after batch save operations to improve data consistency. - **Delete by Filter** - Added batch delete functionality based on conditions, supporting filtering for duplicate IDs, improving the accuracy and efficiency of deletion operations. ### Query and Index Optimization - **Added time limits to multi-index range construction** to prevent performance bottlenecks in extreme cases. - **Removed the default limit from the query interface**, supporting more flexible query needs. - **Added limits to count queries** to prevent excessive resource consumption. - **Bug fixes related to index rebuilding and refreshing**, including issues such as inconsistent index counts and flush errors. - **Enhanced WAL (Write-Ahead Log)** - Added ID verification to improve log consistency. - Adjusted log format, fixing the bug of only having a single WAL file. ### Other Fixes and Improvements - **Fixed the segment count error in the segment statistics interface**. - **Repaired and improved test cases**. - **Adjusted .gitignore file**. - **Performance and stability improvements**, including minor optimizations such as "fix too many pings". #nostr_event_store --- About nostr_event_store's Aggregation, you can read from here View quoted note → About nostr_event_store's deployment methods, you can read from here View quoted note →