Rephrase Question: Should the field be fast

Open
#60 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
cli

Research direction

Start by locating the "Should the field be fast (Y/N)?" prompt in the new-index flow of tantivy-cli and read the surrounding interaction for context. Done means the question explains what "fast" controls and no longer suggests an obvious or unexplained choice; verify the updated prompt in the index-creation flow.

Written by the indexing model from the issue text.

Description

When creating a new index with tantivy, one of the questions is

Should the field be fast (Y/N)?

I'd guess that noone would like to deny that question. Maybe add some more context to this one :-)

Dominant language
Rust
Stars
404
Forks
70
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from quickwit-oss/tantivy-cli

All issues in quickwit-oss/tantivy-cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.