Log for tique/

• Add support for parsing queries using DisMax by Caio 6 years ago
• Fix goofy pure negative query detection 💬 by Caio 6 years ago

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

• Add initial DisMaxQuery implementation 💬 by Caio 6 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/
  

• Add support for changing field name 💬 by Caio 6 years ago

  And rename `queryparser::interpreter` mod to `parser`
  

• Decide the Occur at the raw parser level by Caio 6 years ago
• First working field-aware QueryParser by Caio 6 years ago
• Rename queryparser::parser to queryparser::raw by Caio 6 years ago
• Ensure it's hard to cause an Err() with this parser by Caio 6 years ago
• Add support for parsing +mandatory queries 💬 by Caio 6 years ago

  And rename `negated` to `prohibited`
  

• Add support for strict field names by Caio 6 years ago
• Add plumbing for field:based -queries:"like these" 💬 by Caio 6 years ago

  This patch makes the raw input parser identify field names in queries,
  but the interpreter completely ignores the information.
  
  The current thing is pretty rudimentary, so here's a brain dump of what
  I need to figure out when moving this forward:
  
  * Maybe `Vec<(String, Field)>` so that we don't tie to field name
  * Default field(s)
  * Per field weight
  * Decide how to handle unknown fields
      1. Phrases are obviously wrong
      2. Terms might:be:valid in some cases
  

• Make code examples slightly easier to manage by Caio 6 years ago
• Expose Keywords::{clone,len,is_empty}() by Caio 6 years ago
• Release tique-0.3.0 by Caio 6 years ago
• Support for conversion into weighted queries by Caio 6 years ago
• Upgrade to tantivy 0.12 by Caio 6 years ago
• Allow iterating over sorted (by relevance) Terms 💬 by Caio 6 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.
  

• Prepare for 0.2.0 release by Caio 6 years ago
• Regenerate README 💬 by Caio 6 years ago

  `cargo readme > README.markdown`
  

• Document `tique::topterms` by Caio 6 years ago
• Ensure fields are `text` with frequencies by Caio 6 years ago
• Swap `visit(score, doc)` with `visit(doc, score)` 💬 by Caio 6 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 6 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 6 years ago
• Make the README badges clickable by Caio 6 years ago
• Swap homepage and repository values 💬 by Caio 6 years ago

  From looking at the rendered output on crates.io/docs.rs, I think
  that's a better definition for each
  

• Bump to 0.1.1 💬 by Caio 6 years ago

  Just a trivial documentation update
  

• Regenerate README 💬 by Caio 6 years ago

  `cargo readme > README.markdown`
  

• Remove unstable mention from rustdocs 💬 by Caio 6 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 6 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.