-
Sam Xiao authored
- Adding stack for keeping track of path visited - Using stacks to build a search graph - Update makefile - Use Redis as both Forward/Backward search for caching - Use config.yaml to drive some of the settings - No longer need concurrency-safe hashmap for caching - Switch to use Redis as Distributed Stack infra as well. - Use Goroutine's Worker pool to title page search - Refactor some codes - Adding unit tests for Query - Adding worker - Enable Context and Cancel for all goroutine functions - Adding a logger - Use Goroutine's implementation of worker pool for querying - Merge Forward/Backward into a single Search func - Since the algorithm for both Forward and Backward search functions are identical, except the cache data structure used in opposite ways. - Fixing workers completed before all the jobs are sent - Fixing some linting errors as well - Adding docs - Add license file - Update doc to reflect how `go get` is using to obtain this repo
202bdbb9Sam Xiao authored- Adding stack for keeping track of path visited - Using stacks to build a search graph - Update makefile - Use Redis as both Forward/Backward search for caching - Use config.yaml to drive some of the settings - No longer need concurrency-safe hashmap for caching - Switch to use Redis as Distributed Stack infra as well. - Use Goroutine's Worker pool to title page search - Refactor some codes - Adding unit tests for Query - Adding worker - Enable Context and Cancel for all goroutine functions - Adding a logger - Use Goroutine's implementation of worker pool for querying - Merge Forward/Backward into a single Search func - Since the algorithm for both Forward and Backward search functions are identical, except the cache data structure used in opposite ways. - Fixing workers completed before all the jobs are sent - Fixing some linting errors as well - Adding docs - Add license file - Update doc to reflect how `go get` is using to obtain this repo
This project is licensed under the MIT License.
Learn more
Loading