Log

• Temporarily ignore `Dismax::explanation()` test 💬 by Caio 4 years ago

  Since a DisMaxQuery is a combination of TermQuery items,
  trying to `explain()` it triggers a bug in tantivy that
  leads to a crash in debug builds.
  
  Upstream issue: tantivy-search/tantivy#915
  

• Ensure we don't seek back when reading postings 💬 by Caio 4 years ago

  This works around the debug-only crash when trying to seek
  to a doc_id that would have appeared before the current
  SegmentPostings cursor.
  
  Since DocSets now come already initialized, `.seek()`ing
  without checking if we're already at the desired position
  is likely a bug (hence the `debug_assert!` biting me, I
  suspect).
  
  On tantivy.git @ 730cceff one can see the subtle bug that
  the assertion can catch. Code that once looked like:
  
      let mut scorer = create_scorer();
      if scorer.seek(doc) != doc {
          ...
      }
  
  Should now look like:
  
      let mut scorer = create_scorer();
      if scorer.doc() > doc || scorer.seek(doc) != doc {
          ...
      }
  

• Use new DocSet/Scorer API 💬 by Caio 4 years ago

  Introduced on tantivy.git @ e25284ba
  
  This changeset is sufficient, however upstream's f71b04acb introduced
  a `debug_assert!(self.doc() <= target)` for `SegmentPostings::seek`
  that looks overzealous to me.
  
  In release mode all tests pass, but given that lot has changed since
  last I looked I'll be double checking the affected functionality
  prior to letting this go wild.
  

• Add links to download the crawl data by Caio 4 years ago
• Update Cargo.lock by Caio 4 years ago
• Simplify code by Caio 5 years ago
• Remove useless closure by Caio 5 years ago
• Adjust to new `extract_filtered` interface by Caio 5 years ago
• No need to consume the keyword acceptor by Caio 5 years ago
• Use a more concise iteration style by Caio 5 years ago
• Replace `map -> unwrap_or` with `map_or` by Caio 5 years ago
• Document known error conditions by Caio 5 years ago
• Replace `map -> flatten` with `and_then` by Caio 5 years ago
• Add missing docs to exported things 💬 by Caio 5 years ago

  And enable `missing_docs` and `missing_doc_code_examples`
  

• Do not execute assertion-less doc code examples by Caio 5 years ago
• Update Cargo.lock by Caio 5 years ago
• Prepare for v0.4.0 release by Caio 5 years ago
• Use tique::QueryParser 💬 by Caio 5 years ago

  Now only `QueryParser` is public, not the mod.
  

• Add QueryParser docs by Caio 5 years ago
• Rename tique's `unstable` feature to `queryparser` 💬 by Caio 5 years ago

  ... And somehow `tique` can't be built because `cantine` wants a
  feature that stopped existing? That kinda diminishes the usefulness
  of workspaces.
  

• Use multiple fields when indexing and querying 💬 by Caio 5 years ago

  This patch splits the `fulltext` index field into its sources: name,
  ingredients and instructions, making them available for individual
  strict querying.
  
  Unsurprisingly, using an OR-by-default boolean-query-based with multiple
  fields yields awful results for simple queries. To account for that, we
  switch the query parser to use dismax with a 10% tiebreaking increment.
  

• Move definitions around 💬 by Caio 5 years ago

  No changes
  

• Rust 1.42: Remove `extern crate proc_macro` by Caio 5 years ago
• Update Cargo.lock by Caio 5 years ago
• Add support for parsing queries using DisMax by Caio 5 years ago
• Fix goofy pure negative query detection 💬 by Caio 5 years ago

  And the weird leftofver copy-pasta in the test got removed
  

• Update Cargo.lock by Caio 5 years ago
• Merge branch 'multi_field_query_parser' by Caio 5 years ago
• Integrate QueryParser changes into cantine 💬 by Caio 5 years ago

  Not done, the default behaviour is changed, but I want to bring this
  branch back to master for some tests.
  

• Add initial DisMaxQuery implementation 💬 by Caio 5 years ago

  I was (unintentionally?) made aware that tantivy doesn't have a dismax
  query when @jackdoe pointed me at his cool new project. So I wrote one.
  
  Since I'm hacking on a dumb query parser that allows multiple fields
  and boosts, this will come in handy very soon.
  
  Ref: https://github.com/jackdoe/octopus_query/