summaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Fixed a few concurrency bugsDouglas Rumbaugh2025-03-0311-53/+51
|
* Bug fixesDouglas Rumbaugh2025-02-041-0/+5
|
* More updatesDouglas Rumbaugh2025-01-314-25/+38
|
* progressDouglas Rumbaugh2025-01-272-22/+39
|
* Continued developmentDouglas B. Rumbaugh2024-12-2214-225/+73
|
* Adjusted query result interfacesHEADmasterDouglas B. Rumbaugh2024-12-068-226/+246
| | | | | | | Now, the vector<> is part of the user-defined type, not required by the framework. This should allow for more flexibility in either using alternative containers, or for more sensible implementations of queries with single value results (like range count).
* Warning fixesDouglas B. Rumbaugh2024-12-063-2/+7
|
* Interface update (#5)Douglas B. Rumbaugh2024-12-0625-486/+571
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Query Interface Adjustments/Refactoring Began the process of adjusting the query interface (and also the shard interface, to a lesser degree) to better accommodate the user. In particular the following changes have been made, 1. The number of necessary template arguments for the query type has been drastically reduced, while also removing the void pointers and manual delete functions from the interface. This was accomplished by requiring many of the sub-types associated with a query (parameters, etc.) to be nested inside the main query class, and by forcing the SHARD type to expose its associated record type. 2. User-defined query return types are now supported. Queries no longer are required to return strictly sets of records. Instead, the query now has LocalResultType and ResultType template parameters (which can be defaulted using a typedef in the Query type itself), allowing much more flexibility. Note that, at least for the short term, the LocalResultType must still expose the same is_deleted/is_tombstone interface as a Wrapped<R> used to, as this is currently needed for delete filtering. A better approach to this is, hopefully, forthcoming. 3. Updated the ISAMTree.h shard and rangequery.h query to use the new interfaces, and adjusted the associated unit tests as well. 4. Dropped the unnecessary "get_data()" function from the ShardInterface concept. 5. Dropped the need to specify a record type in the ShardInterface concept. This is now handled using a required Shard::RECORD member of the Shard class itself, which should expose the name of the record type. * Updates to framework to support new Query/Shard interfaces Pretty extensive adjustments to the framework, particularly to the templates themselves, along with some type-renaming work, to support the new query and shard interfaces. Adjusted the external query interface to take an rvalue reference, rather than a pointer, to the query parameters. * Removed framework-level delete filtering This was causing some issues with the new query interface, and should probably be reworked anyway, so I'm temporarily (TM) removing the feature. * Updated benchmarks + remaining code for new interface
* Added a Bentley-Saxe layout policyDouglas Rumbaugh2024-05-011-0/+58
|
* Properly implemented support for iteratively decomposable problemsDouglas Rumbaugh2024-04-195-14/+17
|
* More trie baseline testsDouglas Rumbaugh2024-04-191-0/+55
|
* Updated FSTrie to use const char * instead of std::stringDouglas Rumbaugh2024-04-157-98/+61
| | | | Note: this requires the caller to manage the memory of the strings
* PointLookup: added a point lookup query for unique indexes, and some testsDouglas Rumbaugh2024-03-222-2/+113
|
* Concurrent Extension test cleanup/minor tweaksDouglas Rumbaugh2024-03-223-10/+3
|
* FSTrie testing and debuggingDouglas Rumbaugh2024-03-222-8/+6
|
* Updates/progress towards succinct trie supportDouglas Rumbaugh2024-03-209-15/+60428
|
* FST Shard w/ testsDouglas Rumbaugh2024-03-191-0/+55
| | | | | | | | | Needs some debugging--some methods currently fail within the library itself. The build system doesn't currently build the FST library. To compile, you'll first need to manually build it, and then place the libFST.so file in your LIBRARY_PATH and LD_LIBRARY_PATH.
* Triespline: added test to verify that crash is not due to this projectDouglas B. Rumbaugh2024-02-211-0/+63
|
* Framework: Fixed a bug where tagged deletes didn't release the epochDouglas Rumbaugh2024-02-091-8/+10
|
* Updated VPTree to new shard/query interfacesDouglas Rumbaugh2024-02-083-82/+87
|
* Cleaned up shard files (except VPTree)Douglas Rumbaugh2024-02-0720-1130/+488
| | | | | | Cleaned up shard implementations, fixed a few bugs, and set up some tests. There's still some work to be done in creating tests for the weighted sampling operations for the alias and aug btree shards.
* Fully realized shard concept interfaceDouglas Rumbaugh2024-02-0711-638/+36
|
* Fully implemented Query concept and adjusted queries to use itDouglas Rumbaugh2024-02-071-3/+4
|
* BufferView: Adjusted BV to avoid repeated modulus operationsDouglas Rumbaugh2024-02-051-0/+142
|
* Set up tombstone deletes properlyDouglas Rumbaugh2024-02-053-21/+31
|
* TrieSpline + testsDouglas Rumbaugh2024-01-302-240/+14
|
* Added RangeCount queryDouglas Rumbaugh2024-01-222-0/+210
|
* Multiple concurrency bug fixesDouglas Rumbaugh2024-01-175-41/+110
| | | | | | | | A poorly organized commit with fixes for a variety of bugs that were causing missing records. The core problems all appear to be fixed, though there is an outstanding problem with tombstones not being completely canceled. A very small number are appearing in the wrong order during the static structure test.
* Concurrency testing and bug fixesDouglas B. Rumbaugh2024-01-153-1/+438
|
* Initial pass at unit test refactoringDouglas Rumbaugh2024-01-1212-468/+757
| | | | | | Restructured unit tests to be a bit more modular. I have some further plans to expand on this, particular for the query tests (including both shard and framework level test functions that can be injected at will).
* InternalLevel update and testsDouglas Rumbaugh2024-01-111-4/+4
| | | | | Plus some assorted fixes for move semantics stuff in BufferView that accompanied these changes.
* Ported ISAMTree over to new buffer setupDouglas Rumbaugh2024-01-112-65/+72
| | | | | I may still play with the shard from shards constructor, and queries need some work yet too.
* Fixed some potential buffer-related concurrency bugsDouglas Rumbaugh2024-01-111-1/+1
|
* MutableBuffer: multithreaded insert test + bugfixesDouglas Rumbaugh2024-01-101-12/+20
|
* MutableBuffer+View: Implementation with unit testsDouglas Rumbaugh2024-01-101-141/+113
|
* Refactoring: corrected a number of names and added more commentsDouglas Rumbaugh2023-12-131-2/+2
|
* Tombstone Compaction: re-enabled tombstone compactionDouglas Rumbaugh2023-11-131-2/+0
| | | | | | | Currently, proactive buffer tombstone compaction is disabled by forcing the buffer tombstone capacity to match its record capacity. It isn't clear how to best handle proactive buffer compactions in an environment where new buffers are spawned anyway.
* Comment and License updatesDouglas Rumbaugh2023-11-0715-22/+22
|
* Merge branch 'query-refactor'Douglas Rumbaugh2023-11-0711-278/+249
|\
| * Switched default DE test case over to ISAMTreeDouglas Rumbaugh2023-11-076-136/+103
| |
| * Converted WIRS to the new interfaceDouglas Rumbaugh2023-11-071-33/+34
| |
| * Alias shard fixesDouglas Rumbaugh2023-11-071-4/+4
| |
| * Refactoring progressDouglas Rumbaugh2023-11-064-106/+110
| |
* | Scheduling: Switched over to a thread pool modelDouglas Rumbaugh2023-11-062-1/+8
|/
* DE CC Testing: initial test file for FIFOSchedulerDouglas B. Rumbaugh2023-10-311-0/+461
|
* DE Tests: updated existing tests to use single threaded operationDouglas B. Rumbaugh2023-10-314-4/+5
|
* Initial pass w/ new scheduler setupDouglas Rumbaugh2023-10-201-3/+4
| | | | currently there's a race condition of some type to sort out.
* Re-structuring Project + scheduling updatesDouglas Rumbaugh2023-09-253-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a big one--probably should have split it apart, but I'm feeling lazy this morning. * Organized the mess of header files in include/framework by splitting them out into their own subdirectories, and renaming a few files to remove redundancies introduced by the directory structure. * Introduced a new framework/ShardRequirements.h header file for simpler shard development. This header simply contains the necessary includes from framework/* for creating shard files. This should help to remove structural dependencies from the framework file structure and shards, as well as centralizing the necessary framework files to make shard development easier. * Created a (currently dummy) SchedulerInterface, and make the scheduler implementation a template parameter of the dynamic extension for easier testing of various scheduling policies. There's still more work to be done to fully integrate the scheduler (queries, multiple buffers), but some more of the necessary framework code for this has been added as well. * Adjusted the Task interface setup for the scheduler. The task structures have been removed from ExtensionStructure and placed in their own header file. Additionally, I started experimenting with using std::variant, as opposed to inheritence, to implement subtype polymorphism on the Merge and Query tasks. The scheduler now has a general task queue that contains both, and std::variant, std::visit, and std::get are used to manipulate them without virtual functions. * Removed Alex.h, as it can't build anyway. There's a branch out there containing the Alex implementation stripped of the C++20 stuff. So there's no need to keep it here.
* Bugfixes for tieringDouglas Rumbaugh2023-09-201-0/+24
| | | | | | | | | | | | Fixed a few issues that manifested during the tiering tests, 1) When a version is copied, it now contains copies of the levels, not just pointers (the levels themselves still hold pointers to the shards, though). 2) Ensure that tasks are scheduled with the correct timestamp, they were originally being scheduled backwards. The get_merge_tasks() method already returns them in the correct order, so reversing them again put it in the wrong order.
* General bugfixesDouglas Rumbaugh2023-09-181-3/+1
|