Log for tique/src/
-
Expose Keywords::{clone,len,is_empty}() by Caio 5 years ago
-
Support for conversion into weighted queries by Caio 5 years ago
-
Upgrade to tantivy 0.12 by Caio 5 years ago
-
Allow iterating over sorted (by relevance) Terms 💬 by Caio 5 years ago
Knowing the ordered sequence of most relevant terms is very useful and `limit` is unlikely to be a number which makes the `into_sorted_vec` step prohibitive, so this patch simply makes Keywords hold a sorted Vec instead of a BinaryHeap.
-
Document `tique::topterms` by Caio 5 years ago
-
Ensure fields are `text` with frequencies by Caio 5 years ago
-
Swap `visit(score, doc)` with `visit(doc, score)` 💬 by Caio 5 years ago
Aha! I made it backwards to make it easier to output consistently. The consistency part makes sense, but driving a container with score before the item being contained was too confusing.
-
Initial TopTerms implementation 💬 by Caio 5 years ago
TopTerms reads the index and extracts the most relevant terms in a given document or any arbitrary text input. You can use it to build keywords for your documents or, more interestingly, use the result as a query to find similar documents. It's pretty much a reimplementation of Lucene's MoreLikeThis. I don't particularly like this approach in prod (too many knobs, dependency on the index to formulate a query), but it yields pretty good results with little effort. Ref: https://lucene.apache.org/core/8_4_1/queries/org/apache/lucene/queries/mlt/MoreLikeThis.html
-
Expose the topk module internally by Caio 5 years ago
-
Remove unstable mention from rustdocs 💬 by Caio 5 years ago
I don't think it makes much sense to mention unavailable features on artefact docs, moving forward, enabling `unstable` should enable *more* (unexisting at the moment) docs
-
Remove outdated `tique_derive` mention 💬 by Caio 5 years ago
As I wasn't keen on making the proc_macro public, the whole crate got moved out - the functionality will return when/if I manage to encode this into something more manageable.
-
Remove everything `proc_macro` from what will go public 💬 by Caio 5 years ago
I thought the "proc macros need to live in a separate crate" problem was only a minor annoyance until now: publishing a crate that uses it implies publishing the proc macro crate too. This patch works around said annoyance by (mostly manually) reverting the move to the `tique` module. Now `cantine_derive` is self-contained.
-
Add top-level documentation by Caio 5 years ago
-
Add docs for the remaining public items by Caio 5 years ago
-
Expose CustomScoreTopCollector via `with_custom_scorer` by Caio 5 years ago
-
Use tantivy's CustomScorer trait family instead of DocScorer 💬 by Caio 5 years ago
Less code mo happy
-
More documentation work by Caio 5 years ago
-
Less unwrapping, more questions 💬 by Caio 5 years ago
This patch helps rustdoc infer a `main() -> Result<...>` by adding an explicit `Ok(())` result at the end of the code block.
-
Split compilation features into default and unstable by Caio 5 years ago
-
Start working on `conditional_collector` docs by Caio 5 years ago
-
Rename into{,unsorted}_collection_result 💬 by Caio 5 years ago
Better than hidden in a comment at least :P
-
Move logic to detect pagination to CollectionResult 💬 by Caio 5 years ago
And flatten `items_to_ids` into `render` since it's the only expected call site.
-
Remove DocId restriction from TopKProvider by Caio 5 years ago
-
Move merge_many impl to CollectionResult by Caio 5 years ago
-
Use `Ord` instead of `PartialOrd` for the doc id 💬 by Caio 5 years ago
Technically not required, but being stricter for the doc prevents the (very unlikely) case of ending up with non-Ord stuff being used as a doc (thinking of NaN) which would break sort stability.
-
Sunset top_collector module 💬 by Caio 5 years ago
The `conditional_collector` module effectively replaces it. It still doesn't contain a `TweakedScoreTopCollector`, but that's simply because I don't need it anymore since I'm not modifying scores to simulate order change.
-
Add `top_fast_field` helper method 💬 by Caio 5 years ago
This patch adds a method to `TopCollector` to convert it to a `CustomScoreTopCollector` sorted by a fast field. We can drive the whole thing via the basic top collector, which leads to something kinda cute: TopCollector::<i64, Ascending, _>::new(10, condition) .top_fast_field(field); -
Add support for customizing the scores 💬 by Caio 5 years ago
Kind of a `tique::top_collector::custom_score` copy pasta with cleaned up trait requirements and added support for type-based ordering.
-
Make CheckCondition<T> aware of the order 💬 by Caio 5 years ago
This looks totally like a wart and I think I'd prefer a more explicit provider-driven checker trait. I'll try to further encode it in the type, but I think I won't be able to make it easy to hold. Essentially, I'd need to move the condition trait into the provider, which would force it to be a struct holding _something_ (a `PhantomData` marker, likely) which might make it difficult to infer the type.
-
Use `cmp` instead of `partial_cmp` 💬 by Caio 5 years ago
That was the whole point of implementing Ord for Scored...